AC-031: enforce public repository publication boundary

[veraxis-protocol]

AC-031 — Public Repository Publication Boundary Enforcement

Executor state: SUBMITTED FOR REVIEW. Do not merge without Engineering Lead adjudication.

What changed

• A previously partner-specific clean-room validation artifact was generalized into a fully generic public runbook, with no partner/customer/prospect-specific identifiers or private-collaboration framing.
• A repository-wide, case-insensitive scan of the tracked tree (content and filenames) confirms zero remaining partner/customer/prospect-specific identifiers.

Unchanged

Runtime code, tests, fixtures, workflows, docs/SOTA.md, and docs/SOTA-EVIDENCE.md are untouched by this change.

Claim ceiling

Unchanged in substance: no production-readiness, legal/regulatory, arbitrary-integration-compatibility, broad source-to-rule-derivation, cross-domain-correctness, security-certification, or full-formal-proof claim is made. Scope remains MVP-alpha / synthetic Specimen 001 external testability only.

Tests

python3 -m pytest -q → 342 passed.

Historical cleanup

Older commits and a closed PR retain pre-remediation content in Git history. That is out of scope for this PR and is being handled as a separate, subsequent decision.

---

Generated by Claude Code