Prove reference journey compositions

docs/REFERENCE_JOURNEY_PROGRAM.md

@@ -42,11 +42,13 @@ does neither stays in the backlog until a concrete consumer exists.
 The Records vertical now supplies the journey's native file plan, immutable
 record and item revisions, chronology, close/reopen, retention calculation,
 holds, appraisal, independent disposition approval, recovery-ledger evidence,
-and archive-neutral package simulation. The executable Records fixture proves
-those native transitions without claiming archival custody. The journey still
-needs Forms Runtime/Decisions filing, resumable user handoffs, search
-reconstruction in the pinned composition, and one target-tested archive
-profile.
+and archive-neutral package simulation. Forms Runtime, Cases, and Decisions
+expose exact, permission-rechecked source revisions for explicit filing, and
+all three contribute metadata-only native Search projections that can be
+rebuilt from authoritative state. The executable fixtures prove those native
+transitions without claiming archival custody. The journey still needs
+resumable user handoffs, pinned-composition reconstruction evidence, and one
+target-tested archive profile.
 
 ## Why this sequence
 

docs/STRATEGY_STATUS.md

@@ -4,7 +4,7 @@
 
 | Field | Value |
 | --- | --- |
-| Reconciled on | 2026-08-05 |
+| Reconciled on | 2026-08-06 |
 | Source scope | Local workspace manifests, source inventory, focused journey checks, signed release evidence, and live Gitea issue state |
 | Stable direction | [Platform Core Ideas](PLATFORM_CORE_IDEAS.md) and [Connected Governance Platform Roadmap](CONNECTED_GOVERNANCE_PLATFORM_ROADMAP.md) |
 | Delivery source | Gitea issues |
@@ -67,8 +67,12 @@ prevent a reference-ready claim.
 
 Services, Forms, Forms Runtime, Cases, Parties, Mandates, Approvals, Committee,
 Voting, Decisions, Portal, Postbox, and Audit have an executable service-to-
-decision fixture. Browser-complete assisted intake, production identity,
-records, delivery, and target evidence remain.
+decision fixture. Public and invitation intake can retain Files-backed
+evidence; Forms submissions, Cases, and formal Decisions can be explicitly
+filed as exact eAkte source revisions and reconstructed through permission-
+rechecked native Search projections. Browser-complete assisted intake,
+resumable work guidance, production identity and delivery, a named archive
+profile, and target evidence remain.
 
 ### Governed data and assurance
 
@@ -97,9 +101,11 @@ reconciliation, publication/export, and guided handoff evidence.
 2. Complete governed communication and Postbox against a named target.
 3. Complete the monthly-data flow and use it as the data foundation for
    sanctions screening.
-4. Complete one digital and assisted service-to-decision journey with an eAkte.
-5. Add native PostgreSQL search coverage for the objects used by those
-   journeys; keep OpenSearch optional.
+4. Complete the browser and resumable-work proof for the digital and assisted
+   service-to-decision journey with its existing exact eAkte filing contracts.
+5. Extend native PostgreSQL search coverage from the implemented service-to-
+   decision objects to the communication and monthly-data journeys; keep
+   OpenSearch optional.
 6. Prove one external product connector and one GovOPlaN federation exchange.
 7. Finish multi-host, restore, provider, accessibility, and independent signed
    target evidence before increasing maturity claims.