Estate tracking: verify + sign the per-repo AFFIRMATIONs (run suites in-env, GPG-sign, re-anchor to main)

[hyperpolymath]

Source: the 2026-06-19 estate-wide AFFIRMATION rollout — all 9 in-scope repos now carry an AFFIRMATION.adoc + a scoped Must/Intend/Wish table, each from a real gate run.

By environment constraint those runs had no build/test/proof suite executed (julia/gleam/lean/dune/just/deno all absent) and no GPG signature. Every affirmation honestly says "files exist, pass-state unconfirmed." This issue tracks upgrading each from "structure verified" → "verified + signed" — the work the affirmations' own contract names as remaining.

Per-repo checklist

For each: run the suite in-env (upgrades "files exist" → "tests pass"), then GPG-sign the affirmation commit, optionally re-anchor to main.

• echo-types — agda All.agda + Smoke.agda
• krl — no runnable suite; sign once instantiation lands → Complete RSR-template instantiation (close half-instantiated debt) krl#38
• quandledb — julia --project=server … Pkg.test() (READINESS D; obligations property-tested); 1 lineage rsr-template-repo ref
• tangle — dune runtest + Lean proofs → Finish RSR-template instantiation + reconcile stack-diagram vs KRL-stack grounding tangle#56
• Skein.jl — julia --project=. … Pkg.test() (~1089 tests); 2 placeholders / 6 refs
• KnotTheory.jl — julia --project=. … Pkg.test(); 4 placeholders / 8 refs
• nextgen-databases — per-sub-project (julia/gleam) → Pay down template debt + execute ReScript/TS→AffineScript migration + give verisim-core its own AFFIRMATION nextgen-databases#42
• nextgen-languages — catalog (no build); 3 placeholders / 4 refs
• nextgen-typing — coordination (no build)

Decisions / notes

• Placement asymmetry: AFFIRMATION.adoc sits under docs/ in the 2 coordination repos (nextgen-databases, nextgen-languages) but at root in the other 7, because the coordination repos' placement guard forbids new root files. To normalise to root-everywhere, allowlist AFFIRMATION in the central guard (hyperpolymath/standards).
• Affirmations are anchored to feature-branch commits, not main — re-anchor when re-run.
• GitHub repo descriptions/topics were not cross-checked (no gh this session).
• Two redundant commits were dropped when re-basing tables on main (reflog-recoverable): nextgen-languages 0f5ef2d "ban ReScript", nextgen-typing 1a0cd0d "email standardize".

Cross-references

• Each repo's AFFIRMATION.adoc; honest-gaps pattern: Known Gaps (honest) — tracking issue eclexia#35.
• Repo-debt issues: Complete RSR-template instantiation (close half-instantiated debt) krl#38, Pay down template debt + execute ReScript/TS→AffineScript migration + give verisim-core its own AFFIRMATION nextgen-databases#42, Finish RSR-template instantiation + reconcile stack-diagram vs KRL-stack grounding tangle#56.

Out of scope (tracked centrally — outside this session's repo set)

• Central CI-health reds (Hypatia actions/cache action-pin, workflow staleness, verisimdb K9 pedigree, trusted-base) → 🟠 Estate CI-health backlog: public repos with independently-red CI hypatia#464.
• Axis-2 preventative insertion + Wish→like table normalisation — parked with the canonical-store rework; relates to EPIC: v0.2 maintenance roadmap (corrective · adaptive · perfective) arghda-core#27.

Filed from the 2026-06-19 estate AFFIRMATION-rollout retrospective.