Governing Autonomous AI Agents at the Data Request Boundary

[degenaro]

Project Name

Validating Regulatory Compliance and Enterprise Data Policy from the Skill to the Operation — Before the Agent Reasons

Project Description

NomosFlow is end-end data governance for autonomous AI agents enforced from the skill to the operation, before the agent reasons. NomosFlow at run-time intercepts every agent data operation — reads, writes, queries, message streams, API calls at the infrastructure layer and enforces regulatory rules and enterprise data policy through a multi-tier progressive filter that resolves most decisions in under 10 milliseconds, with every decision recorded to an immutable audit trail and no agent code changes. Every enforcement decision is automatically mapped to OSCAL compliant Audit Evidence.

Proposed Repository Name

nomosflow-data-compliance-for-agents

Current Repository URL

N/A

Maintainers

@RanjanSinha-GH

Maintainer Requirements

• I have reviewed the community membership guidelines
• I have read the organization contributing guidelines
• I have reviewed and agree to follow the Code of Conduct

Sponsors

@degenaro
@vikas-agarwal76

Rationale

See project description.

[degenaro]

/vote

[git-vote]

Vote created

@degenaro has called for a vote on Governing Autonomous AI Agents at the Data Request Boundary (#169).

The members of the following teams have binding votes:

Team
@oscal-compass/oversight-committee-members

Non-binding votes are also appreciated as a sign of support!

How to vote

You can cast your vote by reacting to this comment. The following reactions are supported:

In favor	Against	Abstain
👍	👎	👀

Please note that voting for multiple options is not allowed and those votes won't be counted.

The vote will be open for 28days. It will pass if at least 51% of the users with binding votes vote In favor 👍. Once it's closed, results will be published here as a new comment.

[vikas-agarwal76]

@degenaro you have to vote in the git-vote comment.

[degenaro]

/check-vote

[git-vote]

Vote status

So far 66.67% of the users with binding vote are in favor and 0.00% are against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
4	0	0	2

Binding votes (4)

User	Vote	Timestamp
butler54	In favor	2026-08-11 13:55:55.0 +00:00:00
degenaro	In favor	2026-07-28 17:59:25.0 +00:00:00
vikas-agarwal76	In favor	2026-07-28 14:31:29.0 +00:00:00
yuji-watanabe-jp	In favor	2026-07-29 2:10:15.0 +00:00:00
@rficcaglia	Pending
@ancatri	Pending

[git-vote]

Vote closed

The vote passed! 🎉

66.67% of the users with binding vote were in favor and 0.00% were against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
4	0	0	2

Binding votes (4)

User	Vote	Timestamp
@butler54	In favor	2026-08-11 13:55:55.0 +00:00:00
@degenaro	In favor	2026-07-28 17:59:25.0 +00:00:00
@vikas-agarwal76	In favor	2026-07-28 14:31:29.0 +00:00:00
@yuji-watanabe-jp	In favor	2026-07-29 2:10:15.0 +00:00:00