Curation, automation, and review
The Codex
Gaia is maintained as a reviewable skill graph, not a loose wiki. Every change moves through a small path: propose evidence, let automation shape the batch, review the result, then promote only what belongs in the canonical registry.
The Curate Chain Pipeline
A programmatic prompt-chaining workflow that decomposes registry curation into six discrete links and checks. Click any step below to inspect its inputs, outputs, and validation rules.
What Automation Does
In the prompt-chaining model, sub-agents carry out localized tasks and programmatic gates verify results before continuing.
Localized sub-agents run L1 (discovery), L2 (parallel target research), L3 (batch schema design), and L6 (PR generation), minimizing token waste and errors.
Programmatic jq/bash checks (g1-g3, g5-g6) assert schema shapes, prerequisite DAG validation, and evidence presence before committing any data.
The orchestrator enforces that all graph changes are applied via CLI commands (L5) to ensure code validity. Direct hand-edits are blocked.
Reviewer Path
A reviewer should be able to decide what happens next without reverse-engineering the whole repo.
For intake Issues
- Confirm the issue belongs under the
intakelabel (created automatically viagaia push). - Check that new named skills are submitted as
status: "awakened"(title and catalogRef are omitted). - Verify proposed names against existing canonical skills and named implementations.
- Request clearer evidence on the issue when the behavior cannot be reproduced or understood.
For graph PRs
- Treat
registry/gaia.jsonas the source of truth. - Promote accepted named skills from
awakenedtonamedand assign a level (2★–6★) andcatalogRefbased on the approved intake issue. - Verify prerequisites, rank, evidence class, and status before merging.
- Ensure all generated files are in sync through automated scripts.
Further Reading
Detailed methodology references for registry contributors and reviewers.
Branch Naming Convention
CI enforces scope — each branch prefix restricts which files can change.
| Prefix | Purpose | Allowed Scope |
|---|---|---|
schema/… | Schema & terminology changes | registry/schema/, *.md |
cli/… | CLI / package code | src/gaia_cli/, packages/, tests/, *.md |
docs/… | Markdown/docs content | docs/, *.md |
design/… | Website UI assets | docs/ HTML/CSS/JS, *.md |
review/gaia-push/… | Intake layer (gaia push) | registry-for-review/, *.md |
review/meta/… | Registry curation | registry/, *.md |
infra/… | CI / tooling / config | .github/, scripts/, docs/*.html, *.md |
dev/…, claude/…, codex/…, gemini/… | Experiments (unrestricted) | unrestricted |
feat/…, fix/… | General changes | unrestricted (schema rules still enforced) |
To bypass CI scope enforcement in an emergency, add label skip-scope-check to the PR.