From Unzip to Verified PASS in Three Minutes: Assembling an AI Agent Team That Checks Its Own Work

Description and use

Step‑by‑step recipe for assembling a 16‑role AI agent team with automated verification that ensures reproducibility and precise error diagnostics.

Problem

Reproducible assembly of a 16‑role AI agent team and automated verification of its configuration.

Outcome

The verify script ensures all 22 charters exist, cross‑references resolve, role roster matches charters, and hard‑boundary clauses are present; it reports PASS or the exact missing/inconsistent file.

Workflow

• Unpack the archive (zip or tar.gz) into a clean directory.
• Copy the 22 charters and 5 templates to docs/empire/ and the two knowledge‑graph seed files to docs/knowledge-graph/.
• Create an empty battle log file docs/PROJECT_MEMORY.md.
• Run node scripts/verify-empire.mjs <project-root> to verify the assembly. If needed, run verify-graph.mjs and pack-lint.mjs.

Evidence

The whole assembly is four steps: 1) Unpack. 2) Copy two things to two places. 3) Create an empty battle log. 4) Run the check.

Source

If it prints PASS, the team is assembled. If it doesn't, it tells you exactly which file is missing or inconsistent.

Source

The verify script isn't a formality. It checks that the 22 charters are all present, that cross‑references between them resolve, that the role roster matches the charters, and that the hard‑boundary clauses exist where the rules say they must.

Source

One more script ships in the pack: a lint that scans every markdown file for terms that shouldn't be in a public distribution — the author's internal project names, platform identifiers, automation IDs, that layer of private context.

Source