Skip to content

Damage audit: harden AI-assisted governance/schema/prototype surfaces #39

Description

@mdheller

Purpose

Track the superconscious damage-audit and keep-but-harden remediation sequence.

This issue is the work tracker for the audit plan added in PR #38.

Core risk

The risk is not primarily destructive runtime code. The risk is semantic overpromotion:

  • schema validation appearing to verify invariants;
  • fixture polarity appearing to prove runtime behavior;
  • doctrine references importing authority without commit pins;
  • theorem-facing language appearing proof-complete without proof-review evidence;
  • exploratory prototypes appearing canonical;
  • CI success being read as semantic, mathematical, or runtime verification.

Work packages

  • H0 — Containment ledger: confirm baseline SHA, open/draft PRs, ahead-of-main branches, and branch dispositions.
  • H1 — External doctrine source pinning: commit-pin ProCybernetica / cross-repo doctrine references.
  • H2 — Schema-only guarantee banners: add explicit Layer 1 declaration-only disclaimers to binding schemas/docs.
  • H3 — Claim-status ledger: record high-risk claim surfaces with normalized status and evidence requirements.
  • H4 — Theorem-language review gate: demote or proof-review all theorem/theorem-pattern language.
  • H5 — CI polarity and aggregate target audit: verify make certificate-ci and make -f GNUmakefile certificate-ci coverage and polarity.
  • H6 — Branch/content reconciliation: classify every ahead-of-main branch as captured, superseded, quarantine, merge-candidate, or delete-after-capture.
  • H7 — PR Add Neuronpedia v0.1 schema tranche with fixture naming #37 readiness gate: keep Neuronpedia PR in draft until polarity and Layer 1/Layer 2 boundaries are recorded.

Non-destruction rule

Do not delete or close useful work merely because it was weakly reviewed. Allowed outcomes:

merge after hardening
replay after demotion
capture as exploratory
record supersession
record intentional non-capture
then delete stale branch only after capture/supersession is durable

Immediate state

Acceptance criteria

This issue can close only after every high-risk surface has an explicit disposition and all retained surfaces carry correct claim-status boundaries.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions