docs: reconcile implementation and continuation state [skip ci]

AGENTS.md

@@ -14,6 +14,9 @@ Before changing architecture or source boundaries, read:
 Use the repository-local specifications and skills in `.agents/`. Their
 supported validation commands are documented in `.agents/README.md`.
 
+For current work, begin with `docs/work/11/HANDOFF.md` and re-query its linked
+issue before choosing a checkpoint. Dated roadmap snapshots remain history.
+
 ## Architectural rules
 
 - Preserve originals and evidence before transformation.

README.md

@@ -2,8 +2,8 @@
 
 > One coherent way to inspect, plan, transform, validate, and explain content.
 
-Flow is the suite and future orchestration layer for Ego Hygiene's independently
-useful Rust tools:
+Flow is the developing orchestration library and suite architecture for Ego
+Hygiene's independently useful Rust tools:
 
 | Holon | Owns | Does not own |
 | --- | --- | --- |
@@ -36,10 +36,13 @@ explicit recovery decisions, and fresh dependency-graph assessment before
 caller-selected downstream execution. Stale prerequisites invalidate their
 descendants for reuse while unrelated valid branches retain their eligibility.
 
-Follow the [maintained suite dependency map](docs/roadmaps/flow-suite-dependency-map.md)
-for the suite completion path, current implementation/validation state and
-the preserved original Mermaid roadmap. The [full completion diagram](docs/roadmaps/flow-suite-completion.svg)
-retains old milestones, marks completed issues NUKED and includes newer work.
+Start with the [current continuation handoff](docs/work/11/HANDOFF.md) and
+[live roadmap issue #11](https://github.com/egohygiene/flow/issues/11).
+The [maintained suite dependency map](docs/roadmaps/flow-suite-dependency-map.md)
+and [completion diagram](docs/roadmaps/flow-suite-completion.svg) preserve the
+October 6, 2026 issue atlas; the linked October 15 provider note is another
+dated observation. Their counts, draft states and next-up text are historical,
+and should be re-queried before execution.
 
 ## Executable checkpoint
 
@@ -169,22 +172,36 @@ skills, agents, templates, and validators used to maintain these documents.
 
 ## Status
 
-Flow is in the **executable contract seam** phase. Issues #23, #26, #28, #36,
-#38, #40, #42, #44, and #45 are merged through PRs #24, #27, #35, #37, #39,
-#41, #43, #47, and #48. PR #60 consolidates #46's four sequential checkpoints:
-physical and evidence adversaries, deterministic single- and two-provider
-compositions, exact package/executable content-identity correlation, a closed
-behavior catalog, and the parent #29 evidence matrix. After that PR merges and
-default-branch CI is green, #46 and #29 can close and #30 becomes the next
-conformance-matrix checkpoint.
-The synthetic providers are not the two real adapters required to finish
-FLO-Q03. The process seam still does not implement authenticity verification,
-operating-system sandbox enforcement, authenticated host evidence,
-descriptor-bound launch, or process-tree containment, and the scenario contract
-is not an executor.
-The holons remain independently released repositories. Optiflow v0.1.1 is
-the first pinned real provider adapter; Aniflow and Renderflow adapters and
-the restore-and-assess workflow remain follow-up work.
+As inspected on **October 22, 2026**, at source
+`aadf053d48ce8826ee5b9ca4a134985f4e7910e3`, Flow has a merged durable library
+kernel, synthetic acceptance/lifecycle infrastructure, and a native read-only
+Optiflow v0.1.1 adapter. The saved-receipt repair is complete in
+[#81 / PR #84](https://github.com/egohygiene/flow/pull/84).
+
+The supported product CLI ([#53](https://github.com/egohygiene/flow/issues/53)),
+released Aniflow/Renderflow adapters ([#51](https://github.com/egohygiene/flow/issues/51),
+[#52](https://github.com/egohygiene/flow/issues/52)), installed workflows and
+Flow's first release ([#54](https://github.com/egohygiene/flow/issues/54)) remain
+separate work. `Cargo.toml` is not publishable; its only binary is the synthetic
+conformance provider. There is no published Flow GitHub release at this observation.
+The [capability matrix](docs/integrations/capability-matrix.md) distinguishes
+provider source, immutable releases and platform qualification.
+
+Use the [current handoff](docs/work/11/HANDOFF.md) for one continuation route;
+after this documentation checkpoint, the roadmap's next issue is
+[#15 — observability, privacy and streams](https://github.com/egohygiene/flow/issues/15).
+The first installed candidate, stable audited suite and optional product backlog
+remain different finish lines. The proposed temporal restore-and-assess workflow
+is not delivered by the library foundations alone.
+
+The [#81 validation receipt](docs/validation/flow-81-local.json) records focused
+Linux/Rust 1.85.0 checks and actual pinned native execution. Full-suite and
+moving-stable qualification remain in [#34](https://github.com/egohygiene/flow/issues/34).
+Synthetic providers do not qualify the remaining real integrations. The process
+seam still lacks publisher authentication, an operating-system sandbox,
+authenticated host evidence, descriptor-bound launch and process-tree containment.
+The scenario contract is not a general runtime executor. ADR-0011/0012/0013
+remain proposed pending human review in the [decision index](docs/architecture/governance/DECISIONS.md).
 
 ## License
 

ROADMAP.md

@@ -3,12 +3,12 @@ schema: aether.architecture-document/v1
 id: flow-roadmap
 title: Flow Roadmap
 kind: architecture-document
-version: 1.3.8
+version: 1.3.9
 status: draft
 owners:
   - egohygiene
 created: 2026-08-13
-updated: 2026-10-06
+updated: 2026-10-22
 governed_by:
   - architecture-roadmap
 depends_on:
@@ -25,22 +25,41 @@ supersedes: []
 
 ## Maintained suite dependency view
 
+The [current continuation handoff](docs/work/11/HANDOFF.md) and
+[live #11 ledger](https://github.com/egohygiene/flow/issues/11) own current
+execution navigation. At the October 22, 2026 observation, the durable kernel,
+synthetic acceptance/lifecycle foundations, native read-only Optiflow adapter
+and #81 repair are merged. After #82, continue with #15. Released
+Aniflow/Renderflow adapters, product CLI and the first installed Flow candidate
+remain distinct from the stable audited suite and optional product backlog.
+The [capability matrix](docs/integrations/capability-matrix.md) owns current
+source/release evidence and explicit unqualified states.
+
 The [Flow suite dependency map](docs/roadmaps/flow-suite-dependency-map.md)
 connects the independent provider lanes to an installable suite and the full
 retained product backlog, including the inspectable comic artifact-tree outcome.
 The October 6 refresh preserves all 80 original nodes, includes every open issue
 and newer completed checkpoints, and marks bounded completed issues NUKED.
 Open the [full completion diagram](docs/roadmaps/flow-suite-completion.svg) or
 [editable Mermaid source](docs/roadmaps/flow-suite-completion.mmd). It preserves
-current evidence states, scoped dependencies and the update protocol. Its time-qualified
+October 6 evidence states, scoped dependencies and the update protocol. Its time-qualified
 snapshot supersedes older execution-status claims below where they conflict;
 live issues and repository evidence remain authoritative.
 
-Use the [current documentation handoff](docs/work/11/HANDOFF.md) to resume this
-capture. Detailed tracker state belongs in that dependency view and GitHub,
+Use the handoff to resume one bounded checkpoint. Detailed tracker state
+belongs in the live #11 issue; dated dependency views preserve prior observations,
 while this document retains strategic horizons. Optional capability lanes do
 not silently become first-release requirements.
 
+## Preserved execution snapshots — September 24–27, 2026
+
+The handoffs and embedded execution manifest below, through
+`END ROADMAP EXECUTION SNAPSHOT`, retain their original dates, evidence and
+step states. Their “current,” “next” and draft instructions are historical.
+FLO-Q03 still needs remaining released-provider integrations; #30 and the
+durable kernel are already merged. The current continuation route above
+supersedes these older queues without regenerating their projection.
+
 ## 2026-09-27 Optiflow read-only adapter handoff
 
 Flow #50 now proposes a pinned Optiflow v0.1.1 native CLI library adapter for
@@ -398,13 +417,15 @@ issues: []
 
 ## Strategic context
 
-Flow begins with three independently released Rust tools. Its first executable
-checkpoint is a bounded extension resolution and execution seam: merged
-in-process evidence, host-neutral process transcript validation, and one bounded
-`trusted-unconfined` local runner. It is not yet a product orchestrator or real
-provider integration. Flow will integrate named releases through public
-libraries or versioned CLI contracts. It will not consolidate repositories,
-copy sibling source, or hide missing provider capabilities inside the facade.
+Flow coordinates three independently versioned Rust tools through released
+public contracts. Its merged library includes extension resolution, validated
+execution, a bounded `trusted-unconfined` local runner, durable prepared state,
+fresh graph assessment and explicit recovery. Its first real released-provider
+integration is native read-only Optiflow v0.1.1 with a separate receipt. These
+foundations do not yet establish a product CLI, generic native graph composition
+or complete installed workflows. Remaining integrations consume named releases
+through public libraries or versioned CLI contracts, preserving each provider's
+ownership and independent use.
 
 This roadmap advances on capability evidence rather than dates.
 
@@ -434,6 +455,12 @@ sibling dependency is permitted.
 
 ## Now — Prove released integration seams
 
+The contract, library, process, artifact and durable foundations below are
+merged building blocks. Their delivered evidence is bounded to each surface;
+older omissions describe that checkpoint rather than the whole current library.
+The remaining strategic outcome is to compose qualified released providers into
+an installed product experience. Detailed issue order remains in the handoff.
+
 ### Freeze the federated extension contract
 
 Use provider-owned manifests plus Flow-owned locks, invocation/event/result
@@ -521,8 +548,9 @@ roots. It remains test-owned sequencing rather than a graph scheduler. Flow #59
 adds candidate closeout evidence for the exact materialized package layouts,
 correlated package and executable digests across the manifest, locks, and
 observations, tamper rejection, redistribution terms, behavior-to-test catalog,
-parent #29 requirement matrix, residual gaps, and #30 handoff. Parent closure
-waits for PR #60 to merge and default-branch CI to pass.
+parent #29 requirement matrix, residual gaps, and #30 handoff. That kit and the
+subsequent acceptance matrix have merged; they are no longer the next closeout
+gate. Synthetic composition remains separate from real released-provider proof.
 
 ### Verify locked package and executable subjects
 
@@ -578,7 +606,17 @@ positive/adversarial tests. It does not provide a sandbox, descendant
 containment, descriptor-bound execution, durable state, retry/resume, or a real
 provider adapter.
 
-### Pin the capability matrix
+### Compose the durable library and native adapter foundations
+
+Prepared plans, persisted intent/authority, immutable snapshots, accepted
+checkpoints, fresh dependency assessment and explicit recovery are implemented
+library surfaces. The native Optiflow adapter pins v0.1.1 read-only inspection
+and validates retained evidence, including the #81 receipt repair. Its separate
+receipt does not yet make it a generic graph checkpoint. Remaining work composes
+qualified providers and the supported CLI without weakening either boundary.
+ADR-0011/0012/0013 remain proposed pending human review.
+
+### Maintain the capability matrix
 
 Reinspect each provider at named released revisions. Record available public
 libraries, CLI commands, structured formats, side effects, runtime tools, and
@@ -638,7 +676,11 @@ general video packaging as present capability.
 **Exit evidence:** each provider remains independently buildable and releasable;
 Flow compatibility fixtures exercise only public released interfaces.
 
-## Next — Build orchestration primitives
+## Next — Deliver the orchestration CLI over existing primitives
+
+These are intended product commands, not currently installed Flow commands.
+Reuse the merged library/kernel; do not recreate persistence or recovery in
+the delivery layer.
 
 - `flow doctor`: discover provider versions and explain compatibility.
 - `flow inspect`: preserve source observations and artifact identity.
@@ -651,7 +693,8 @@ Flow compatibility fixtures exercise only public released interfaces.
 
 ## Later
 
-- Versioned events, results, provenance evidence, plans, and run manifests.
+- Extend the existing versioned events, results, plans and run-state contracts
+  for qualified suite workflows and richer provenance evidence.
 - Opt-in provenance tooling and honest derivative claims under ADR-0002.
 - Reusable signed pipeline packs and third-party adapter contracts.
 - Cross-run content-addressed caching with explicit privacy and invalidation.

docs/architecture/README.md

@@ -5,6 +5,15 @@ independently useful holons. Suite documents own shared intent and rules. Holon
 documents refine those rules into tool-specific capability and dependency
 boundaries.
 
+## Current implementation and continuation
+
+Use the [current handoff](../work/11/HANDOFF.md) to resume work. The durable
+library kernel and native read-only Optiflow v0.1.1 adapter are merged; the
+supported Flow CLI, remaining released-provider adapters and Flow release have
+separate gates. The [capability matrix](../integrations/capability-matrix.md)
+distinguishes source snapshots, released interfaces and native qualification.
+This reading order describes architectural ownership, not universal delivery.
+
 ## Reading order
 
 1. [Purpose](identity/PURPOSE.md)

docs/architecture/foundation/ARCHITECTURE.md

@@ -3,12 +3,12 @@ schema: aether.architecture-document/v1
 id: flow-architecture
 title: Flow Architecture
 kind: architecture-document
-version: 0.13.4
+version: 0.13.5
 status: draft
 owners:
   - egohygiene
 created: 2026-08-13
-updated: 2026-10-21
+updated: 2026-10-22
 governed_by:
   - architecture-architecture
 depends_on:
@@ -32,9 +32,11 @@ implementation decisions.
 
 ### Suite applications
 
-The `flow` CLI is a thin delivery adapter over an orchestration library. It owns
-argument parsing, human presentation, stable exit mapping, and shell completion,
-but not planning or execution logic.
+The intended `flow` CLI is a thin delivery adapter over the orchestration
+library. Its responsibility is argument parsing, human presentation, stable
+exit mapping and shell completion. The supported product CLI remains
+[#53](https://github.com/egohygiene/flow/issues/53); the existing synthetic
+conformance-provider binary is not that delivery surface.
 
 ### Orchestration core
 
@@ -328,9 +330,15 @@ adding a scheduler or rewriting accepted history. Issue #65 adds the bounded
 [durable lifecycle corpus](../../integrations/lifecycle-scenarios.md), including
 fresh-process restart and deterministic recovery receipts. Issue #66 extends it
 with authority denials, observable effect counters, and retained cleanup residuals
-using the existing public APIs, without changing runtime schemas. Flow does not yet supply
-the public CLI, real holon adapters, signature or transparency verification,
-provider-native artifact validation, an atomic filesystem snapshot, an
+using the existing public APIs, without changing runtime schemas. Completed
+issue #50 supplies the native read-only Optiflow v0.1.1 adapter described
+above; #81 / merged PR #84 strengthens its saved receipt contract and native
+artifact correlation. It is a released-provider integration through a library
+API and a separate native protocol, not a generic graph checkpoint.
+
+Flow does not yet supply the supported public CLI, released Aniflow or
+Renderflow adapters, complete installed-suite workflows, signature or
+transparency verification, an atomic filesystem snapshot, an
 operating-system sandbox or authenticated enforcement evidence,
 descriptor-bound execution, process-tree containment, automatic retry/resume,
 or provider-native checkpoint restoration. Structural units beyond these library seams
@@ -345,7 +353,7 @@ current source layout.
 
 ## Validation
 
-Default-branch CI run 35558851556 validates Rust 1.85 and stable library builds,
+Historical default-branch CI run 35558851556 validated Rust 1.85 and stable library builds,
 closed contract models, deterministic resolution, the hermetic in-process and
 process-transcript seams, scenario-manifest identity, and repository
 architecture metadata plus artifact acceptance and exact execution subjects at
@@ -358,9 +366,19 @@ execution-subject schema, canonical identity, filesystem, content-mismatch,
 context-replay, contradictory-evidence, and unsupported-claim checks. Forbidden
 dependency-edge checks, CLI-thinness, signature/transparency verification,
 authenticated sandbox conformance, descriptor-bound launch, process-tree
-containment, provider-native artifact validation, and scenario execution remain
+containment, broader provider-native/domain qualification, and general scenario execution remain
 later gates for their corresponding runtime surfaces. Issue #42 adds real Unix
 direct-child conformance for literal launch state, supervised transport,
 overflow, interruption, grace, escalation, and reaping. Issue #58 additionally
 validates deterministic fixed-order composition without adding plan/run state,
 retry, checkpoint, resume, or real holon algorithms.
+
+Later merged work adds the durable coordinator and bounded native Optiflow
+checks described above. [#81's local receipt](../../validation/flow-81-local.json)
+records focused Linux/Rust 1.85.0 regression checks and actual pinned v0.1.1
+execution. This is separate from the earlier CI observation and from full-suite
+qualification. [#34](https://github.com/egohygiene/flow/issues/34) retains the
+observed all-target timeout, native unavailable/skip semantics and moving-stable
+Clippy baseline. No current all-target green or release qualification follows
+from merging these implementations. ADR-0011, ADR-0012 and ADR-0013 remain
+proposed in the [decision index](../governance/DECISIONS.md).