V18 Continuum slices 11-15

CHANGELOG.md

@@ -7,6 +7,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Added
+
+- V18 Continuum compatibility now exposes a runtime-backed generated-family
+  readiness inventory for receipt, settlement, neighborhood-core, and
+  runtime-boundary families, separating projection-ready families from
+  authored-only families before later source-fact projections.
+- V18 Continuum compatibility now exposes a runtime-backed tick witness ladder
+  that separates patch replay core, receipt witness core, and receipt shell
+  explanation while rejecting mismatched patch/receipt facts.
+- V18 Continuum compatibility now exposes runtime-boundary reading-envelope
+  source facts for translated git-warp read results while preserving the
+  authored-only readiness status until Wesley profiles and fixtures exist.
+- V18 Continuum compatibility now exposes runtime-boundary witnessed-suffix
+  source facts for translated git-warp sync/export suffixes while keeping the
+  existing sync protocol intact.
+
 ### Fixed
 
 - V18 Continuum review follow-up now validates constructor envelopes before

docs/BEARING.md

@@ -57,14 +57,14 @@ Continuum role.
 
 Current branch state at this boundary:
 
-- Branch: `v18-continuum-slices-6-10`
+- Branch: `v18-continuum-slices-11-15`
 - Base branch: `main`
-- Latest remote head inspected: `origin/main` at `42f15812`
+- Latest remote head inspected: `origin/main` at `a4c5467e`
 - Latest released package line: `17.0.1`
-- Latest merged PR: #93, recursive tree OID read fanout and v17.0.1 release
-  repair
+- Latest merged PR: #94, v18 Continuum slices 6 through 10 plus review
+  repairs
 - Latest completed v18 implementation cycle:
-  `0158-v18-warp-ttd-receipt-smoke`
+  `0163-v18-witnessed-suffix-source-facts`
 
 The release ladder is now:
 
@@ -166,9 +166,9 @@ read-model groundwork, sync hardening, release gates, and package publishing.
 
 ## What comes next
 
-Run the next v18 slices in order. Each slice gets a design document before
-implementation, RED before GREEN, and a BEARING update before the final commit
-for that slice.
+Run v18 slices 11 through 15 in order. Each slice gets a design document
+before implementation, RED before GREEN, and a BEARING update before the final
+commit for that slice.
 
 ## Running Task List
 
@@ -230,8 +230,37 @@ for that slice.
   sibling `~/git/warp-ttd` adapter at execution time, rejects plain local
   receipt DTOs, and proves `warp-ttd` can summarize generated-family git-warp
   receipt projection facts while preserving translated evidence posture.
-- [ ] 11. Re-plan with evidence in hand before expanding into reading-envelope,
-  suffix/runtime-boundary, neighborhood-core, and settlement-family slices.
+- [x] 11. Re-plan with evidence in hand after slices 1 through 10 and PR #94:
+  [0159-v18-replan-with-evidence](design/0159-v18-replan-with-evidence/v18-replan-with-evidence.md)
+  keeps slices 12 through 15 as translated source-fact compatibility work, not
+  a full v19 observer/runtime rewrite.
+- [x] 12. Refresh the generated Continuum/Wesley family inventory before
+  projecting more families:
+  [0160-v18-generated-family-inventory-refresh](design/0160-v18-generated-family-inventory-refresh/v18-generated-family-inventory-refresh.md)
+  adds runtime-backed readiness rows for the four current Continuum families.
+  Receipt and settlement are projection-ready; neighborhood core and runtime
+  boundary stay authored-only until Wesley profiles and fixtures exist.
+- [x] 13. Audit the `TickPatch`/`TickReceipt` witness ladder into replay core,
+  witness core, and receipt shell:
+  [0161-v18-tickpatch-tickreceipt-witness-ladder](design/0161-v18-tickpatch-tickreceipt-witness-ladder/v18-tickpatch-tickreceipt-witness-ladder.md)
+  names `GitWarpTickPatchReplayCore`, `GitWarpTickReceiptWitnessCore`,
+  `GitWarpTickReceiptShell`, and `GitWarpTickWitnessLadder`, validates
+  patch/receipt alignment, and promotes the old up-next backlog note into the
+  cycle packet.
+- [x] 14. Project one git-warp read result into runtime-boundary
+  reading-envelope source facts:
+  [0162-v18-reading-envelope-source-facts](design/0162-v18-reading-envelope-source-facts/v18-reading-envelope-source-facts.md)
+  adds `GitWarpReadingEnvelopePayloadFact` and
+  `GitWarpReadingEnvelopeSourceFacts`, requires git-warp evidence to be
+  translated, and keeps runtime-boundary marked as authored-only until Wesley
+  profiles and fixtures exist.
+- [x] 15. Project one git-warp sync/export suffix into translated
+  witnessed-suffix source facts:
+  [0163-v18-witnessed-suffix-source-facts](design/0163-v18-witnessed-suffix-source-facts/v18-witnessed-suffix-source-facts.md)
+  adds `GitWarpWitnessedSuffixPatchFact` and
+  `GitWarpWitnessedSuffixSourceFacts`, rejects empty suffix patch lists, and
+  keeps the current sync protocol intact while runtime-boundary remains
+  authored-only.
 
 The loop stays strict: write or update the cycle doc, capture RED, green the
 slice, update this BEARING task list before the final commit, validate, then

docs/design/0159-v18-replan-with-evidence/v18-replan-with-evidence.md

@@ -0,0 +1,155 @@
+---
+cycle: 0159
+task_id: V18_replan_with_evidence
+status: Complete
+sponsors:
+  human: James
+  agent: Codex
+started_at: 2026-05-22
+completed_at: 2026-05-22
+release_home: v18.0.0
+bearing_task: 11
+---
+
+# V18 Re-Plan With Evidence
+
+## Sponsor Human
+
+James.
+
+## Sponsor Agent
+
+Codex.
+
+## Hill
+
+Re-plan v18 slices 11 through 15 from the evidence that actually landed in
+PR #94, without widening v18 into the full v19/v21 observer and distributed
+runtime program.
+
+## Playback Questions
+
+- Can an agent tell which v18 evidence is now real, and which compatibility
+  surfaces remain projections rather than native Continuum witnesshood?
+- Can the next five slices be executed as one-commit cycle boundaries without
+  losing the generated-artifact authority posture from slices 5 through 10?
+- Can a human reviewer see why reading envelopes, suffix shells, and
+  runtime-boundary facts are source-fact projections in this campaign, not a
+  full observer or sync rewrite?
+- Does BEARING now name the active 11 through 15 runway instead of leaving
+  slice 11 as a vague re-plan placeholder?
+
+## Accessibility / Assistive Reading Posture
+
+The deliverable is text-first and table-friendly. The next-slice list in
+BEARING uses ordered task entries and explicit family names so screen readers
+and plain text readers do not need layout or color to recover priority.
+
+## Localization / Directionality Posture
+
+No UI copy or locale-sensitive formatting is introduced. The plan uses stable
+repository nouns, file paths, and ASCII punctuation so later translation work
+does not have to infer visual directionality.
+
+## Agent Inspectability / Explainability Posture
+
+The slice records:
+
+- current inspected cross-repo heads;
+- the merged PR that supplies the evidence base;
+- which slices are compatibility projections;
+- which later substrate cuts are deliberately deferred.
+
+Future agents should be able to audit the plan from BEARING and this design
+without reading chat history.
+
+## Evidence Snapshot
+
+Current inspected sources at re-plan time:
+
+| Source | Head / ref | Evidence |
+| --- | --- | --- |
+| `git-warp` | `origin/main` at `a4c5467e` | PR #94 merge, BEARING task list, cycles 0146 through 0158 |
+| Continuum | `01e0735` | `docs/contract-family-registry.md`, `schemas/continuum-*-family.graphql`, `wesley/profile/scopes.mjs` |
+| Wesley | `62328dba` | `out/proof/realization/manifest.json`, Continuum role docs |
+| `warp-ttd` | `0491be6` | `src/adapters/gitWarpAdapter.ts`, receipt shell summary tests |
+| Echo | `f8d8720` | Continuum alignment and neighborhood/settlement design docs |
+
+## What PR #94 Proved
+
+- Generated Continuum artifact descriptors can be admitted only through an
+  explicit load context and generated authority.
+- Evidence posture is explicit; generated family shape alone does not imply
+  native Continuum witnesshood.
+- Receipt-family projection exists for local `TickReceipt`,
+  `DeliveryObservation`, and optional `ReceiptShard` source facts.
+- `warp-ttd` can consume generated-family git-warp receipt projection facts
+  through an explicit smoke without becoming a runtime dependency.
+- Patch commit success now means visible writer-tip advancement, and
+  same-writer races use CAS conflict posture instead of hidden overwrite.
+
+## Re-Plan
+
+The next five slices should keep the compatibility line narrow:
+
+| Slice | Boundary | Purpose |
+| ---: | --- | --- |
+| 11 | Re-plan | Close the explicit re-plan placeholder with repo-visible evidence. |
+| 12 | Generated-family inventory | Refresh family readiness before projecting more families. |
+| 13 | Witness ladder | Split replay core, witness core, and receipt shell for `TickPatch`/`TickReceipt`. |
+| 14 | Reading-envelope source facts | Project one read result toward runtime-boundary family shape. |
+| 15 | Witnessed-suffix source facts | Project one export suffix toward runtime-boundary suffix shape. |
+
+Slices 14 and 15 are intentionally source-fact projections. They are not the
+full v19 observer-plan runtime or a replacement sync protocol.
+
+## Non-Goals
+
+- Do not implement the node-record, edge-record, or attachment-plane substrate
+  cuts in this PR.
+- Do not claim native Continuum witnesshood for translated git-warp facts.
+- Do not pull the full v19 observer-plan runtime into v18.
+- Do not pull the full v21 local-site or distributed neighborhood calculus
+  into v18.
+- Do not make Echo the owner of git-warp's Continuum role.
+
+## RED
+
+Observed before this slice:
+
+```text
+docs/BEARING.md still named task 11 only as "Re-plan with evidence in hand"
+and did not enumerate the 11 through 15 execution runway.
+```
+
+## GREEN
+
+Added this cycle document and updated BEARING to:
+
+- anchor the re-plan to PR #94 and the current cross-repo evidence snapshot;
+- mark task 11 complete;
+- name tasks 12 through 15 as the active next five slices.
+
+## Verification
+
+```text
+npx markdownlint-cli2 docs/BEARING.md docs/design/0159-v18-replan-with-evidence/v18-replan-with-evidence.md
+```
+
+## Closeout
+
+Slice 11 closes the planning placeholder and gives slices 12 through 15 a
+bounded reviewable runway. The next commit should implement the generated
+family inventory refresh as its own cycle boundary.
+
+## SSJS Scorecard
+
+- Runtime-backed forms: green; this slice introduces no runtime code.
+- Boundary validation: green; generated authority stays in the next-slice
+  inventory plan.
+- Behavior ownership: green; Continuum owns family semantics, Wesley compiles,
+  git-warp projects source facts, and `warp-ttd` consumes.
+- Message parsing: green; no behavior branches introduced.
+- Ambient time or entropy: green; no runtime code introduced.
+- Fake shape trust or cast-cosplay: green; translated evidence remains the
+  named default posture.

docs/design/0160-v18-generated-family-inventory-refresh/v18-generated-family-inventory-refresh.md

@@ -0,0 +1,147 @@
+---
+cycle: 0160
+task_id: V18_generated_family_inventory_refresh
+status: Complete
+sponsors:
+  human: James
+  agent: Codex
+started_at: 2026-05-22
+completed_at: 2026-05-22
+release_home: v18.0.0
+bearing_task: 12
+---
+
+# V18 Generated Family Inventory Refresh
+
+## Sponsor Human
+
+James.
+
+## Sponsor Agent
+
+Codex.
+
+## Hill
+
+Add a runtime-backed inventory of current Continuum/Wesley family readiness so
+later v18 projections can ask whether a family is projection-ready before they
+emit generated-family-shaped facts.
+
+## Playback Questions
+
+- Can the runtime name every current Continuum family in one inventory without
+  relying on an external chat transcript?
+- Can code distinguish profiled fixture-witnessed families from authored-only
+  families before projecting more source facts?
+- Does the inventory reject missing, duplicate, or unknown family entries?
+- Does the public export surface include the inventory nouns needed by later
+  slices without making git-warp the semantic owner of Continuum families?
+
+## Accessibility / Assistive Reading Posture
+
+The inventory remains code-level data with tests and a design table. It has no
+visual-only affordances. Human reviewers can read one ordered table in this doc
+and one ordered test fixture in the unit test.
+
+## Localization / Directionality Posture
+
+No UI text is introduced. The status labels are stable ASCII protocol labels,
+not localized prose.
+
+## Agent Inspectability / Explainability Posture
+
+The inventory objects answer the questions later agents need before adding
+projections:
+
+- which family exists;
+- which authored schema path anchors it;
+- whether Wesley has profiled and fixture-witnessed it;
+- what source facts git-warp can currently provide;
+- what compatibility cut remains open.
+
+## Evidence Snapshot
+
+The slice reflects the same inspected cross-repo evidence used by slice 11:
+
+| Family | Authored home | Wesley status | Current v18 posture |
+| --- | --- | --- | --- |
+| `receipt-family` | `schemas/continuum-receipt-family.graphql` | `profiled`, `fixture-witnessed` | projection-ready |
+| `settlement-family` | `schemas/continuum-settlement-family.graphql` | `profiled`, `fixture-witnessed` | projection-ready |
+| `neighborhood-core-family` | `schemas/continuum-neighborhood-core-family.graphql` | `authored` | authored-only |
+| `runtime-boundary-family` | `schemas/continuum-runtime-boundary-family.graphql` | `authored` | authored-only |
+
+## Design
+
+Add these domain concepts:
+
+- `ContinuumGeneratedFamilyStatus` for the readiness label;
+- `ContinuumGeneratedFamilyInventoryEntry` for one family row;
+- `ContinuumGeneratedFamilyInventory` for complete inventory validation;
+- `createCurrentContinuumGeneratedFamilyInventory()` for the current v18
+  source-fact inventory.
+
+`profiled-fixture-witnessed` means the family is safe for translated
+git-warp source-fact projection when the projection also uses generated
+descriptor authority. `authored-only` means the family exists but must not be
+treated as projection-ready yet.
+
+## Non-Goals
+
+- Do not parse Continuum Markdown in domain code.
+- Do not make git-warp the authority for Continuum family semantics.
+- Do not infer native Continuum witnesshood from inventory readiness.
+- Do not load sibling repos at runtime.
+
+## RED
+
+Observed first failure:
+
+```text
+npx vitest run test/unit/domain/continuum/ContinuumGeneratedFamilyInventory.test.ts --reporter=verbose
+Error: Cannot find module '../../../../src/domain/continuum/ContinuumGeneratedFamilyInventory.ts'
+```
+
+The test failed because the inventory nouns did not exist yet.
+
+## GREEN
+
+Implemented the runtime-backed inventory classes, exported them from the
+package entry point, and updated BEARING task 12.
+
+## Verification
+
+```text
+npx vitest run test/unit/domain/continuum/ContinuumGeneratedFamilyInventory.test.ts \
+  test/unit/domain/index.exports.test.ts --reporter=verbose
+npm run typecheck
+npx eslint src/domain/continuum/ContinuumGeneratedFamilyStatus.ts \
+  src/domain/continuum/ContinuumGeneratedFamilyInventoryEntry.ts \
+  src/domain/continuum/ContinuumGeneratedFamilyInventory.ts \
+  src/domain/continuum/createCurrentContinuumGeneratedFamilyInventory.ts \
+  test/unit/domain/continuum/ContinuumGeneratedFamilyInventory.test.ts \
+  test/unit/domain/index.exports.test.ts
+npx markdownlint-cli2 docs/BEARING.md \
+  docs/design/0160-v18-generated-family-inventory-refresh/v18-generated-family-inventory-refresh.md
+```
+
+The first lint pass rejected the inventory factory for exceeding the
+max-lines-per-function limit. The GREEN implementation splits each family row
+into a focused entry function.
+
+## Closeout
+
+Slice 12 gives later projections one complete, validated readiness inventory.
+Receipt and settlement are projection-ready; neighborhood core and runtime
+boundary are authored-only until Wesley profiles and fixtures exist.
+
+## SSJS Scorecard
+
+- Runtime-backed forms: expected green; inventory concepts are classes.
+- Boundary validation: expected green; no raw sibling-repo parsing enters the
+  domain.
+- Behavior ownership: expected green; Continuum and Wesley authority stays
+  descriptive, while git-warp only records projection readiness.
+- Message parsing: expected green.
+- Ambient time or entropy: expected green.
+- Fake shape trust or cast-cosplay: expected green; readiness does not imply
+  native witnesshood.