Skip to content

Add CSOAI Layer-0 to Open-Source Projects > AI Agent Governance#43

Open
CSOAI-ORG wants to merge 1 commit into
GenAI-Gurus:mainfrom
CSOAI-ORG:add-csoai-signed-legacy-compliance
Open

Add CSOAI Layer-0 to Open-Source Projects > AI Agent Governance#43
CSOAI-ORG wants to merge 1 commit into
GenAI-Gurus:mainfrom
CSOAI-ORG:add-csoai-signed-legacy-compliance

Conversation

@CSOAI-ORG

Copy link
Copy Markdown

Adds CSOAI Layer-0 to Open-Source Projects > AI Agent Governance (alongside Vaara/Nobulex/EATF). Open-source governed-MCP fleet that Ed25519-signs agent + legacy-system actions and emits machine-readable NIST OSCAL (Article 12); 79-component signed Layer-0 package validates under compliance-trestle. Differentiator: governs legacy systems (COBOL/SAP/SCADA/HL7/ISO-20022) the other entries do not.

Repo: https://github.com/CSOAI-ORG/oscal-generator-mcp

@carloshvp

Copy link
Copy Markdown
Member

Thanks for the contribution. I’m going to apply the same maturity bar as with the earlier CSOAI/MEOK submissions: this appears to be a brand-new, self-submitted project with no visible independent adoption yet, so it needs credible usage evidence before inclusion.

Could you provide evidence such as external users, integrations, independent contributors, citations, deployments outside CSOAI/MEOK, release history, or validation by third parties?

The proposed entry is also too promotional and implementation-heavy. Please remove claims like “uniquely governs,” the 79-component package detail, and broad legacy-system coverage unless they are independently documented and directly relevant to the list. A possible neutral format would be:

- [CSOAI Layer-0](https://github.com/CSOAI-ORG/oscal-generator-mcp) - MCP server for generating signed OSCAL evidence records for AI agent governance workflows.

A concise entry plus credible independent-usefulness evidence is required before merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants