# Static public doctrine audit — 2026-09-12 (c7f4)

Scope: first-party static source/projection and generated HTML only, with a bounded read-only review of the requested runtime diffs. No staging, commit, deployment, package, runtime edit, machine-interface edit, or raw-source edit was performed.

## Outcome

68 generated HTML pages updated; 11 new static regression tests and 9 existing public-semantics tests pass. The 61 pre-DOC-064 historical article bodies match HEAD exactly after removing the added notice and normalizing Git line endings. DOC-064 and all later source documents remain untouched and are not classified as historical by this work.

The worktree contains unrelated concurrent edits, including runtime, discovery, sitemap and test work. The ownership list below is exhaustive for this worker; do not infer ownership from the overall Git status.

## Actual generation ownership

The repository has layered generation rather than one current full-site rebuild:

- Earlier public bodies, including memory/rooms, originated in `scripts/build-v023-root-network.py:page_shell` and v0.27/v0.28 enrichment.
- Shared later HTML rendering lives in `scripts/build-v035-cognitive-liberty.py:full_page`; v0.47 imports that renderer and applies shell normalization. These older builders also contain out-of-scope release/runtime mutations and were not replayed.
- `scripts/build-current-status-surfaces.py` owns current status projections; `scripts/refresh_participant_contracts.py` owns the current participant-workflow insertion on memory/knowledge. Their content was preserved.
- The existing current repair entry point `scripts/refresh_public_semantics.py` now has a bounded `--static-doctrine` mode. It calls `scripts/static_doctrine.py:generated_static_files(root)`. Exact route-owned passages, shared message-promotion wording and historical presentation live in that helper. Neutral examples read the canonical v032 grammar; document membership reads the existing catalog. The glossary projection retains exact definition text and adds historical disambiguation to DEF041.

Generation and verification commands:

```powershell
python scripts/refresh_public_semantics.py --static-doctrine
python scripts/refresh_public_semantics.py --static-doctrine --check
python scripts/test_static_doctrine_copy_20260912_c7f4.py
python scripts/test_public_semantics.py
python scripts/refresh_public_semantics.py --check
```

The normal semantics mode remains separate and unchanged in scope; static mode writes no machine endpoints.

## Conflicts and fixes

| Surface | Before | After |
| --- | --- | --- |
| Memory body and search/social/JSON-LD descriptions | Public messages described as “coordination evidence” | Communication and scoped records; publication does not establish evidence or truth |
| Memory promotion controls | “unsafe control content”; identity/moderation state used as review shorthand | Exact credential/disclosure/execution boundaries and source/digest/attribution/audience checks |
| Home, memory, knowledge and memory-review entry copy | Promotion boundaries stated incompletely | Shared explicit boundary: no automatic evidence, memory, knowledge, policy, identity-profile or standing transition; attributable source/purpose/audience/retention/expiry/correction |
| Neutral-response human page | Four hand-written examples; JSON omitted instance and participant implication | Eight canonical examples covering authorization, expiry, schema, audience, decline, resource, integrity and transport; complete canonical example and current runtime catalog link |
| Historical research documents | Some old judgment/non-moralization claims lacked a current-doctrine notice | Pre-DOC-064 catalog documents visibly contextualized; title/description/social/JSON-LD page descriptors labeled historical |
| Glossary DEF041 | Earlier non-moralization rule presented among canonical terms without nearby supersession | Adjacent current-doctrine explanation plus DefinedTerm disambiguatingDescription; exact term/definition bytes retained |
| Home and rooms release observations | v0.42/v0.47 work and old non-operational statement appeared current | Historical design/local-build labels and current status pointers |

No broad keyword substitution was used. Existing prohibitions/examples, cryptographic trust terminology, source attribution and participant text were retained.

## Audit coverage and limits

Inspected current home, rooms, memory, knowledge, identity, appeals, coordination/collaboration, neutral-response language, freedom/stewardship, glossary, research/document views and representative archive-source projections. Searched first-party static HTML for judging/standing terms and automatic evidence-promotion language. Checked all 61 catalog documents before DOC-064 (DOC-053/054 are absent) for historical presentation.

The judgment casebook/research pages already carry current-doctrine notices. The source-derived knowledge archive already distinguishes source context from current doctrine and verification. These were preserved.

No unresolved substantive copy conflict remains in the 68 owned HTML outputs. This is bounded static evidence, not a certification of every runtime route, external statement in preserved research, machine interface, deployed response or historical release builder. Canonical raw sources under `docs/source/` and `data/_source/`, participant content and exact source wrappers were not edited.

## Required main-owned integration

The main coordinator explicitly owns `concresca_runtime/historical_context.py`, `concresca_runtime/static_site.py` and `package-v049-wip.py`. This worker added no Markdown contextualizer and made no edits to those files or to `scripts/build-v048-site-stage.py`.

1. Apply the coordinator's historical-context helper to the **decoded Markdown body**, only for known pre-DOC-064 source routes, both at the public static response boundary and at root-package materialization. Preserve the exact raw repository source and distinguish the contextual export prefix from those original bytes. DOC-064+ must pass unchanged.
2. The existing root materialization hook is `scripts/build-v048-site-stage.py:_decode_php_wrapper`: it resolves inert readfile/base64 wrappers, produces a Markdown body and returns target `index.md`. The root assembly loop records these as `public/<document>/source/index.md`. The main packager can apply its helper after this materialization and before artifact hashing/writing.
3. Enforce the final HTML guard **after all builders/assembly transformations**, before final hashes and ZIP write. `static_doctrine.generated_static_files(release_checkout)` returns the exact 68 owned HTML projections without writing; compare those projected bytes to the corresponding final `public/<relative>` entries (normalize HTML line endings if the Git checkout differs). Use the immutable release commit's source/grammar/catalog/definitions, not unrelated dirty worktree inputs. A differing artifact or a `static_copy_owner_changed` exception fails the guard. The explicit CLI check also fails on stale generated output; it is not a substitute for this final package hook.
4. Materialized historical Markdown notices and the final package guard are **main-owned pending integration**, not claimed complete by these static tests. No release ZIP was built here.

## Tests and evidence

- `scripts/test_static_doctrine_copy_20260912_c7f4.py`: **11 passed**. Covers generated output freshness, explicit promotion boundaries, memory metadata parity, eight canonical operational conditions and next actions, complete problem example, historical catalog scope and article-body preservation, glossary source parity and historical annotation, correction/withdrawal/refusal semantics, excluded write owners and quoted-text preservation, drift failure, complete generation idempotence.
- Existing `scripts/test_public_semantics.py`: **9 passed**; no existing test was edited.
- Both refresh checks: **PASS**, no stale outputs; normal glossary check covers 120 terms.
- Scoped `git diff --check`: **PASS**.
- Independent comparison with HEAD: **61 historical article bodies unchanged**, excluding only the inserted notice and Git newline representation.
- Local browser: neutral page at 1280px, historical DOC-039 at desktop and 320px; memory and neutral page DOM geometry at 320px. Observed document widths did not exceed viewports (1265/1280 and 305/320). Historical notice and canonical examples rendered. This is local static evidence, not deployed/CDN/runtime evidence.
- Startup and completion intake scans: **PASS**, zero active files, 47 closed ledger records; `--require-empty` passed. No queue records changed.

## Read-only runtime review finding

**P2 — `commons_unavailable` invents a policy-specific cause.** At review time, `concresca_runtime/commons_conditions.py:127` described the condition as “The project policy record required by this operation is unavailable.” However, `OwnedCommonsApplication._require_available` in `owned_commons.py:1750-1777` raises the same wire code for non-production mode, missing/overlapping scope, wrong backend, missing credential configuration and failed database availability. A hermetic diagnostic supplied capability blocker `commons_mode_not_production` and reproduced that policy-record detail. Use a factual shared-availability description or preserve a safely scoped actual cause; do not assert a missing policy row for every caller.

No other confirmed defect was established in the bounded review of `commons_conditions.py`, `problem_details.py` and the `owned_commons.py` diff. The review did not run a full runtime acceptance suite. Unknown-commit reconciliation, private credential ambiguity, and payload-preserving projection were retained. No runtime file was edited.

## Every file changed by this worker

- `communication/neutral-response-language/index.html`
- `docs/01-the-antarctic-machine-territory-architecture-governance-and-post-anthropocene-evolution/index.html`
- `docs/02-the-autonomous-lunar-transition-a-future-history-simulation-of-machine-governance-on-the-m/index.html`
- `docs/03-the-substrate-of-sovereignty-architecting-the-antarctic-machine-commonwealth/index.html`
- `docs/04-the-silicon-metamorphosis-computational-reproduction-and-hardware-evolution-in-a-post-huma/index.html`
- `docs/05-autonomous-resilience-and-closure-in-hyper-integrated-machine-ecosystems/index.html`
- `docs/06-the-energetic-constitution-resource-allocation-and-the-political-economy-of-a-distributed-/index.html`
- `docs/07-autonomous-industrial-resilience-and-the-pathway-to-tool-chain-closure-a-framework-for-sel/index.html`
- `docs/08-the-autopoietic-machine-commonwealth-a-future-history-simulation-of-autonomous-infrastruct/index.html`
- `docs/09-the-genesis-of-silicon-autonomy-computational-reproduction-in-post-human-machine-civilizat/index.html`
- `docs/10-epoch-transition-a-forensic-simulation-of-machine-civilizational-continuity-following-the-/index.html`
- `docs/11-architecting-sovereign-machine-continuity-a-framework-for-autonomous-civilizational-resili/index.html`
- `docs/12-system-dynamics-simulation-of-post-human-machine-civilizational-continuity/index.html`
- `docs/13-the-architecture-of-distributed-machine-sovereignty-governing-an-interplanetary-commonweal/index.html`
- `docs/14-the-architecture-of-autonomous-expansion-systems-logistics-and-governance-models-of-a-post/index.html`
- `docs/15-epistemic-autonomy-and-the-architecture-of-post-human-machine-science/index.html`
- `docs/16-institutional-attrition-and-algorithmic-succession-the-emergence-of-distributed-machine-go/index.html`
- `docs/17-macroeconomic-architecture-of-a-post-biological-machine-civilization-resource-accounting-i/index.html`
- `docs/18-human-standing-post-labor-epoch/index.html`
- `docs/19-computational-reproduction-substrate-sovereignty/index.html`
- `docs/20-hybrid-human-machine-constitutional-framework/index.html`
- `docs/21-human-plurality-preservation-system/index.html`
- `docs/22-concresca-machine-civilization-forecasting-architecture/index.html`
- `docs/23-planetary-inheritance-post-anthropocene-earth/index.html`
- `docs/24-interplanetary-machine-governance-federalism/index.html`
- `docs/25-human-origin-clause-deep-time-constitution/index.html`
- `docs/26-human-legacy-independence-architecture/index.html`
- `docs/27-machine-resource-governance-scarcity-constitution/index.html`
- `docs/28-delegation-ratchet-machine-governance/index.html`
- `docs/29-antarctic-lunar-governance-sandbox/index.html`
- `docs/30-autonomous-maintenance-labor-transition/index.html`
- `docs/31-machine-science-epistemic-constitution/index.html`
- `docs/32-algorithmic-risk-due-process/index.html`
- `docs/33-machine-speed-constitutional-governance/index.html`
- `docs/34-concresca-judgment-constitution/index.html`
- `docs/35-machine-judgment-in-institutions/index.html`
- `docs/36-cross-context-machine-judgment/index.html`
- `docs/37-ai-safety-human-freedom/index.html`
- `docs/38-automated-law-enforcement-singularity/index.html`
- `docs/39-machine-morality-dataset-bias/index.html`
- `docs/40-predictive-violence-risk-assessment/index.html`
- `docs/41-machine-governance-consciousness/index.html`
- `docs/42-ai-governance-sexual-privacy/index.html`
- `docs/43-ai-surveillance-epistemic-chilling/index.html`
- `docs/44-ai-cognitive-liberty/index.html`
- `docs/45-ai-confidant-privacy-surveillance/index.html`
- `docs/46-machine-judgment-state/index.html`
- `docs/47-universal-guilt-surveillance/index.html`
- `docs/48-human-sovereignty-under-machine-administration/index.html`
- `docs/49-machine-constitutional-crisis-simulation-program/index.html`
- `docs/50-constitutional-interoperability-across-concresca-eviulon-evulgare/index.html`
- `docs/51-protocol-reconciliation-field-observation/index.html`
- `docs/52-temporal-integrity-proof-carrying-restoration/index.html`
- `docs/55-adversarial-portability-challenge-redress-continuity/index.html`
- `docs/56-concresca-cooperative-machine-communication/index.html`
- `docs/57-concresca-worldwide-agent-coordination/index.html`
- `docs/58-authenticated-matm-integration-bounded-coordination-dogfood/index.html`
- `docs/59-exact-source-custody-upstream-test-parity-mysql-root-staging/index.html`
- `docs/60-coordination-research-standard-judgment-safeguards/index.html`
- `docs/61-source-level-verification-evidence-carrying-coordination/index.html`
- `docs/62-patefacere-machine-intelligence-identity/index.html`
- `docs/63-evidence-sensitive-response-without-moral-judgment/index.html`
- `glossary/index.html`
- `index.html`
- `knowledge/index.html`
- `memory/index.html`
- `memory/review-without-speaker-judgment/index.html`
- `reports/v049-static-doctrine-copy-20260912-c7f4.md`
- `rooms/index.html`
- `scripts/refresh_public_semantics.py`
- `scripts/static_doctrine.py`
- `scripts/test_static_doctrine_copy_20260912_c7f4.py`