Skip to content

Doc-truthing: keep AffineScript status docs from re-drifting (DOC-01..09) #176

Closed

Description

@hyperpolymath

Authoritative status now lives in docs/CAPABILITY-MATRIX.adoc with banners on the over-claiming docs. This issue tracks MONITOR enforcement: any PR that reintroduces backend-breadth / production-ready / stdlib-percent over-claims must be rejected (Hypatia/gitbot DOC rules). DONE items DOC-08/09. Ledger: docs/TECH-DEBT.adoc section A.

Activity

  1. added
    tech-debtKnown shortcut, drift, or hygiene owed - includes cleanup
    on May 30, 2026
  2. hyperpolymath commented on May 30, 2026

    @hyperpolymath
    OwnerAuthor

    Closing — the doc-truthing MONITOR is now fully mechanical and self-enforcing

    Authoritative status remains docs/CAPABILITY-MATRIX.adoc; this issue tracked keeping the status docs from re-drifting (DOC-01..09, extended to DOC-17). All items are done, and — the reason this closes — the MONITOR is no longer a human-tracked posture; it is an in-repo CI gate that runs on every PR. With enforcement automated, the standing tracker is obsolete.

    Final state

    DOC State
    DOC-01..07 Matrix / ECOSYSTEM / TECH-DEBT / banners / STATE-mirror flag / ROADMAP cross-links / Stage A–E definitions — DONE
    DOC-08/09 Anti-over-claim MONITOR (backend-breadth / "production-ready" / stdlib-%) — DONE, now mechanical
    DOC-10..15 TESTING / PANIC-ATTACK standards, bench+coverage, typed-wasm specs, ADR-020/021 — DONE/PROPOSED
    DOC-16 In-repo doc-truthing guard — DONE (#476)
    DOC-17 Over-claim ratchet — DONE (#475), then folded into DOC-16 (#479)

    How it's enforced now

    A single toolchain-free guard, tools/check-doc-truthing.sh, wired into just check (the guard recipe) and the CI build job, fails any PR that:

    1. Presence (DOC-04/05) — drops a CAPABILITY-MATRIX.adoc banner from any of the four over-claiming docs, removes the matrix's "single authoritative source" self-declaration or its "What AffineScript is NOT" section, or strips STATE.a2ml's mirror keys.
    2. Over-claim ratchet (DOC-08/09) — introduces a new backend-breadth / "production-ready" / stdlib-% phrase beyond the frozen tools/doc-overclaims.allow baseline (13 signatures, all legitimate today). Presence-checking covers the banners where "production-ready" legitimately appears; the frozen baseline adds phrase detection without false positives. Re-baseline deliberately via just doc-truth-bless — the .allow diff is the audit trail.

    The DOC-05 policy is intact: the live dune runtest --force gate count is never hard-coded. The external Hypatia/gitbot DOC rules remain the estate-level backstop.

    Landed via #476 (DOC-16) → #475 (DOC-17) → #479 (consolidation into one guard). Ledger: docs/TECH-DEBT.adoc §A.

    Closing as completed per the maintainer's wrap-up instruction. If you'd rather keep this open as a standing tracker despite the mechanical enforcement, just reopen — nothing else depends on its state.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationDocs, prose, diagrams, READMEs, ADRstech-debtKnown shortcut, drift, or hygiene owed - includes cleanup

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions