OIC/ZTL maturation rebase — reflect current semantic boundary

[inventor1975]

DOCUMENTATION + CONTRACT UPDATED
RUNTIME ADAPTER STILL BLOCKED

No semantic runtime implementation is introduced.
No Tier-1 reproduction claim is made.
No historical kernel profile is rewritten.

What this changes

The repository described a merge as pending that had already happened, and described ZTL
through a July dossier. It also did not say, at the front door, where the OIC↔ZTL boundary
actually is. This change makes the repository truthful about the architecture that already
exists. It adds no runtime code and promotes no schema.

Front door — dated supersession, historical text retained. README.md and STATUS.md
gain dated current-state blocks above the historical wording, which is kept. They establish
only: PR #40 merged 2026-09-06; bounded candidate admission and provisional interpretation are
present on main; semantic implementation has not started; ZTL runtime attachment remains
blocked.

Four architecture documents.

• docs/architecture/OIC-ZTL-MATURATION-DELTA-001.md
• docs/architecture/OIC-ZTL-LAYER-OWNERSHIP-001.md
• adapters/ztl/CURRENT-STATE-001.md
• docs/darpa/OIC-ZTL-DARPA-CROSSWALK-001.md

The state they describe

Two matured sides and one missing centre, all three true at once:

• the OIC admission plane is materially implemented — frozen admission runtime, fifteen
  terminal states, recomputable receipts, provisional interpretation;
• ZTL reasoning and warrant semantics have materially matured, well beyond the July
  dossier;
• between them, three institutional transitions do not exist — institutional semantic
  admission → stable admitted proposition → evidence-bearing formalization.

The repository therefore becomes both more mature and more explicitly incomplete, in the right
place. That is not a contradiction; it is the architecture's actual state.

ZTL RUNTIME ATTACHMENT = BLOCKED follows from the missing centre, and from nothing else. It
is corroborated by three artifacts already in the repository: scripts/verify_code_start_gate.py
("broader production semantic gate BLOCKED"), CAPABILITY_MATRIX.json
(production_semantic_gate: "BLOCKED"), and
docs/gates/OIC-SEMANTIC-CODE-START-GATE-CLOSURE-v0.1.md ("SEMANTIC IMPLEMENTATION HAS NOT
STARTED").

Currentness ownership

Stated as an ownership rule, not a logic claim, and not by rewriting any ADR:

ZTL may reason over supplied epoch, expiry, revocation and currentness facts. ZTL does not
create institutional currentness, validity, expiry authority or revocation authority.

Deliberately not done

• No runtime code. src/oic/** and schemas/draft/** untouched. No adapter, no envelope
  constructor, no receipt producer, no canonical-formula path — the lawful input does not
  exist, and its absence is a result to preserve rather than conceal.
• docs/contracts/kernel-profiles/ztl-v0.1.json untouched. Its historical tag names remain
  historical evidence; a tag recovered in September does not retroactively replace them.
• docs/capabilities/CAPABILITY_MATRIX.json untouched. It cannot carry the ZTL boundary
  without breaking its own gate: adding a single restrictive ceiling key makes
  scripts/verify_code_start_gate.py fail with evidence ceiling expanded. Returned as a
  representation gap rather than forced into one field.
• KILL-Z8 and KILL-Z9 remain OPEN / UNGUARDED — future executable negative controls for
  components that do not yet exist. They are not a defect count and are not grounds to say the
  current code is unsafe.

Validation

• scripts/verify_code_start_gate.py → PASS, exit 0.
• Full suite → 1719 passed, 1 skipped, 1 failed. The skip is the declared
  gitignored local receipts case. The failure is
  test_installed_versions_match_the_dev_lock, which compares installed distributions against
  requirements/dev.txt; the drift is the executing workstation's, not this repository's. No
  repository failures. The same three figures hold at the unmodified base.

Claim wording remains subject to curator review before merge. Do not merge.

[veraxis-protocol]

Request changes before merge.

Canonical GitHub CI is green: all 9 jobs passed, with 1,732 tests passed and 1 declared skip. The remaining blockers are documentation identity and claims consistency:

1. Replace references describing c4a325c5 / tree b8e31ec4 as current main. PR #42 is based on main@8ebac66965997748061d8cc0f1bfde73cb7b216a, tree 6e450750d7b6b1d1f0b493b050ed7d866d42b264. If the older pair is intentionally retained, label it explicitly as the Gate-G-validated PR #40 merge state, not current main.

2. docs/architecture/OIC-ZTL-MATURATION-DELTA-001.md says docs/capabilities/CAPABILITY_MATRIX.json was “corrected minimally in this change,” but the matrix is not changed and the PR description correctly says it remains untouched. Correct the document.

3. Replace unqualified “semantic implementation has not started” wording with “production semantic implementation has not started.” The same new block states that bounded candidate admission and provisional interpretation are materially implemented, so the present wording is internally contradictory.

4. Update the PR validation section: the workstation dependency-lock failure is environmental evidence, but canonical GitHub CI passed all jobs and reported 1,732 passed / 1 declared skip.

Do not merge this PR yet. Keep it open while the separate OIC bounded-results/README evidence update is completed. Then rebase PR #42 onto the resulting main and rerun the full review and CI sequence. No runtime, capability-matrix, benchmark-status, or claim-ceiling expansion is authorized.