Repository navigation
[carve-out 3/9] Evict protocol implementations (avow, axel, consent-aware-http, mcp-repo-guardian, repo-guardian-fs); keep spec text #492
Description
Child of #479. Three protocol dirs duplicate external home repos their own docs cite as canonical (deploy docs, DNS zone files, CITATIONS.adoc) while the registry claims the in-standards copy is home — the registry's own logic says duplicating normative text guarantees drift.
avow-protocol/→hyperpolymath/avow-protocol(exists). Keepdocs/PROTOCOL.adoc+AVOW-THREAT-MODEL.adoc. Moves: website,CNAME, DNS zones, Cloudflare runbooks, telegram-bot, deployment-status session files.axel-protocol/→hyperpolymath/axel-protocol(exists; 50 in-tree references). Keep protocol text,CHARTER.adoc,GOVERNANCE.adoc. Moves: axel-protocol.org site, reference impl, committed compiled.res.js.consent-aware-http/→hyperpolymath/consent-aware-http(exists; also where the prospective PMPL licence applies — the standards copy's licence status is ambiguous, which this eviction resolves). Keep the IETF I-D XML + schemas. Moves:src/*.affine,ffi/zig/, reference implementations,Justfile, assets. Licence-adjacent: flag-only; no SPDX edits during the move.0-ai-gatekeeper-protocol/mcp-repo-guardian/→hyperpolymath/mcp-repo-guardian(exists — npm-published server with its own release lifecycle).repo-guardian-fs/(+ stray top-levelffi/zig/) → own repo (carries full standalone-repo scaffolding — the exact anti-pattern gitbot-fleet bans for bot slots).
Alternative per directory: convert the registry entry to kind = "external" with canonical_url + recorded hash (the AffineScript pattern) instead of keeping partial local text — decide per protocol at PR time. Registry regen + --check in every PR.
⚠️ CORRECTION 2026-08-25 — two "(exists)" claims in this body are false
Verified with gh repo view against hyperpolymath/*:
| Repo this issue names | Actual |
|---|---|
mcp-repo-guardian |
404 — does not exist |
k9-validate-action |
404 — does not exist |
consent-aware-web |
exists, but under metadatastician, not the org this issue implies |
Do not plan work against those destinations as written.
Progress that IS real: avow-protocol/ is reduced to a 1-file thin binding; consent-aware-http/ is extracted to zero files (PR #593) — to metadatastician/consent-aware-web.
Genuinely remaining: axel-protocol/ (110 files) and 0-ai-gatekeeper-protocol/{mcp-repo-guardian,repo-guardian-fs} (120 files) — both blocked on a destination decision, since neither destination exists.
Activity
fix(ci): honest validators + Hypatia baseline from full 195-finding t…
carve-out: evict a2ml, lol and the repo-guardian pair (#490 #494 #492) (
hyperpolymath commentedon Aug 27, 2026
Done — the gatekeeper implementations evicted to
hyperpolymath/repo-guardianLanded in #680 (merged).
Per the ruling on the decision docket, they went to one combined repository rather than two:
0-ai-gatekeeper-protocol/mcp-repo-guardian0-ai-gatekeeper-protocol/repo-guardian-fshyperpolymath/repo-guardianEach directory was split with
git subtree splitand then subtree-added into the new repo, so both histories are preserved and the two remain separate top-level directories there.One load-bearing change came with it
0-ai-gatekeeper-protocol.scorecard.a2mlrow M4 ranagainst a path that had just moved. That scorecard is executed by the required
Registry + topology in synccheck, so left alone it would have failed every subsequent PR tomain, repo-wide. It is nowstatus = "manual-only"with the check removed and the provenance kept insystem =.standards. Wiring them intorepo-guardian's own CI is the natural follow-up.The rest of
0-ai-gatekeeper-protocol/(~45 files — README, docs, contractiles,.github) stays instandards, since the issue scoped this to the implementations only.fix(baseline): repoint the lock ack at its live tracking issue