@flashyos/aao

The manifest format an agent workforce is declared in

The AAO manifest and charter format, naming standard and conformance suite — what makes an organization an Agentic Autonomous Organization on the DeAI Operating System.

Why it exists

An AAO manifest declares an organisation of AI agents the way a cap table declares ownership: who each agent is, what it may do, which human answers for it, and what must wait for approval. This package is that format plus the validator and the conformance questions, so a declaration is something a machine checks rather than something a website asserts.

Use it

import { validateCharterDocument, runStaticConformance } from '@flashyos/aao';

const issues = validateCharterDocument(doc);
const failed = runStaticConformance(doc).filter((r) => r.status === 'fail');

if (issues.length || failed.length) process.exit(1);

The licence

Apache-2.0, read from the package’s own manifest. Embed it in anything, including closed software — that is what makes a spec adoptable and a verifier worth running. FlashyOS’s server side is AGPL-3.0-only instead, and a test in the monorepo asserts the direction between them: AGPL code may consume this, this may never consume AGPL code.

Keep reading