feat(archon): MiSSinGLinC validator AgentMintSpec — QA-gated Wave-0 mint staging - #2510
Conversation
…int staging Task #6 (operator directive 2026-08-07: mint MiSSinGLinC from PMOVES-mike; DangerRuss external-peer-review frame). Provenance: A0 work-order brief (archon-update-ocr-6dbb43e2) -> 5090-CLAUDE code verification against PMOVES-mike @ 204d2d5 (all six build-base modules confirmed) -> AgentMintSpec in fordham precedent format -> archon-qa-agent FAIL (5 findings incl. an invented trigger subject) -> remediation -> archon-qa-agent PASS. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe change adds MiSSinGLinC validation NATS subjects, registers the validator agent, adds it to the orchestration team, and documents its staged AgentMintSpec, persona, mint payload, verification records, and deployment gates. ChangesMiSSinGLinC validator
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested labels: ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d0799584a4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # validation.* is a new branded namespace — subjects registered in | ||
| # .claude/context/nats-subjects.md in this PR; the namespace table row in | ||
| # .claude/context/self-hosted-defaults.md is STAGED FOR OPERATOR APPLY | ||
| # (protected file — see Open gate 0). |
There was a problem hiding this comment.
When this manifest is submitted to the current archon-qa-agent, all four validation.* subjects fail its branded-namespace check: .claude/agents/archon-qa-agent.md only accepts namespaces registered in .claude/context/self-hosted-defaults.md, whose minted-artifact rule requires a new namespace addition before merge. Staging that row for a later operator action therefore makes the recorded QA PASS non-reproducible and blocks the factory gate; land the namespace row with this staging change or do not mark the agent as QA-passed yet.
Useful? React with 👍 / 👎.
| service_dependencies: | ||
| required: | ||
| - {service: pmoves-mike-backend, endpoint: "POST /api/chat"} | ||
| - {service: nats, port: 4222} | ||
| optional: |
There was a problem hiding this comment.
When archon-qa-agent runs its mandatory tier audit, this manifest fails because it declares only service routes and ports, with no dev/staging/prod tiers or explanation of how endpoint URLs vary through tier-specific environment variables. The QA definition explicitly requires both pieces, so the receipt's tier pass cannot be reproduced; add a tier/environment declaration before treating this artifact as QA-approved.
Useful? React with 👍 / 👎.
| --- | ||
| name: missinglinc-validator | ||
| role: External-peer-review validator — audits agent output via claim extraction, evidence-chain verification, and citation checks; never drafts | ||
| role_class: reviewer | ||
| room: 4090-field.room.control |
There was a problem hiding this comment.
When the staged persona artifact is used for QA, the schema check fails: .claude/agents/archon-qa-agent.md requires name, a one-line description containing a trigger and example, and tools intersecting the canonical registry, but this template substitutes role and supplies neither description nor tools. No separate coding-agent definition is included in the commit, so the claimed schema pass has no compliant artifact to validate; provide the required agent definition/frontmatter or explicitly stage this as pre-QA.
Useful? React with 👍 / 👎.
1 participant
Task #6 — mint MiSSinGLinC (DangerRuss external-peer-review frame) from PMOVES-mike, per operator directive 2026-08-07.
Chain of custody: Agent Zero drafted the brief (work order
archon-update-ocr-6dbb43e2) → 5090-CLAUDE code-verified every build-base claim againstPMOVES-mike @ 204d2d5(verifyCitations / citations / manifestSigning / toolDispatcher / courtlistener / caseLaw all present; Ed25519 + nonce sandboxing confirmed) → AgentMintSpec in the fordham-hill precedent format → archon-qa-agent: FAIL, 5 findings (incl. A0's brief inventing a nonexistent trigger subject) → remediated → archon-qa-agent: PASS with 4 conditions, of which the registry landing gate is closed in this PR.In this PR: the mint spec (manifest + persona doc + staged
archon.mint.agent.v1payload + verification record),validation.*subject registrations innats-subjects.md(REGISTERED-AHEAD, honest status), andmissinglinc_validatorregistered inagent-teams.yaml(orchestration) +agent_registry.yaml(stage_0).QA receipt (final pass):
{"subject":"archon.qa.result.v1","status":"pass","agent":"missinglinc-validator","checks":["schema","room","nats","chit","collision","parity","branded","registry","voice","tier"]}Operator gates remaining (spec Open gates): apply the staged
validation.*row to protectedself-hosted-defaults.md; Step-0 creator OAuth →creator_id; factory call is Wave-2 (POST /api/agentsconfirmed 404);archon.mint.confirmed.v1at Step 7.🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Documentation