From 3ec24e06b3639f7cb2a002abc2bc1c04a7149401 Mon Sep 17 00:00:00 2001 From: Alan Szmyt Date: Thu, 22 Oct 2026 04:00:42 -0400 Subject: [PATCH] docs: reconcile implementation and continuation state [skip ci] Document the merged durable kernel and native Optiflow adapter, retain dated roadmap and ADR evidence, and point current entrypoints to one live continuation route. Documentation checks and independent reviews recorded in docs/validation/flow-82-docs.json. No product qualification implied. Closes #82. --- AGENTS.md | 3 + README.md | 61 ++-- ROADMAP.md | 77 +++- docs/architecture/README.md | 9 + docs/architecture/foundation/ARCHITECTURE.md | 38 +- docs/architecture/foundation/SYSTEM.md | 26 +- docs/architecture/governance/DECISIONS.md | 11 +- docs/integrations/README.md | 11 +- docs/integrations/capability-matrix.md | 35 +- docs/roadmaps/flow-suite-dependency-map.md | 11 + docs/validation/flow-82-docs.json | 366 +++++++++++++++++++ docs/work/11/HANDOFF.md | 87 +++++ 12 files changed, 672 insertions(+), 63 deletions(-) create mode 100644 docs/validation/flow-82-docs.json diff --git a/AGENTS.md b/AGENTS.md index 3d0406f..89beb85 100644 --- a/AGENTS.md +++ b/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. diff --git a/README.md b/README.md index 2b28abd..1a5bdb0 100644 --- a/README.md +++ b/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 diff --git a/ROADMAP.md b/ROADMAP.md index b8fd37f..7a4737e 100644 --- a/ROADMAP.md +++ b/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,6 +25,16 @@ 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. @@ -32,15 +42,24 @@ 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. diff --git a/docs/architecture/README.md b/docs/architecture/README.md index a664fa2..8d639c1 100644 --- a/docs/architecture/README.md +++ b/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) diff --git a/docs/architecture/foundation/ARCHITECTURE.md b/docs/architecture/foundation/ARCHITECTURE.md index d77c09b..5b9f1db 100644 --- a/docs/architecture/foundation/ARCHITECTURE.md +++ b/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). diff --git a/docs/architecture/foundation/SYSTEM.md b/docs/architecture/foundation/SYSTEM.md index 375a454..3275077 100644 --- a/docs/architecture/foundation/SYSTEM.md +++ b/docs/architecture/foundation/SYSTEM.md @@ -3,12 +3,12 @@ schema: aether.architecture-document/v1 id: flow-system title: Flow System kind: architecture-document -version: 0.2.0 +version: 0.2.1 status: draft owners: - egohygiene created: 2026-08-13 -updated: 2026-08-21 +updated: 2026-10-22 governed_by: - architecture-system depends_on: @@ -28,7 +28,8 @@ supersedes: [] The Flow suite consists of one orchestration system, three domain holons, and a small set of shared contracts. This inventory assigns each major capability to -one primary owner. +one primary owner. It describes intended ownership; the implementation boundary +below distinguishes delivered library capabilities from the complete suite. ## System inventory @@ -63,6 +64,8 @@ probes/adapters; it must not become a duplicate media engine. ## Major interactions and runtime flows +The intended end-to-end suite flow is: + 1. Inspect the source and preserve provenance observations. 2. Resolve a pipeline definition against installed capabilities and policy. 3. Produce and validate a deterministic plan. @@ -79,10 +82,19 @@ integration; the capability matrix must verify actual contracts first. ## Assumptions and evidence gaps -Aniflow currently has the broadest run orchestration behavior, Optiflow is -deliberately read-only at v0.1.0, and Renderflow currently centers documents -plus image/audio conversion rather than general video derivative packaging. -Integration must preserve reality rather than rename aspiration as capability. +At Flow source `aadf053d48ce8826ee5b9ca4a134985f4e7910e3`, the orchestration +library includes durable prepared execution, verified checkpoints, fresh graph +assessment and explicit recovery. Its native Optiflow adapter consumes the +immutable read-only v0.1.1 CLI for scan, report and review planning. That adapter +retains a separate local receipt; it does not yet participate in the generic +durable graph. Neither surface establishes the complete interaction sequence +above or a supported product CLI. + +Released Aniflow/Renderflow adapters, installed-suite workflows and a Flow +release remain separate work. Provider source and package versions do not +establish released compatibility. The [capability matrix](../../integrations/capability-matrix.md) +owns the dated provider evidence; the [current handoff](../../work/11/HANDOFF.md) +owns continuation. Integration must preserve those distinctions. ## Open questions diff --git a/docs/architecture/governance/DECISIONS.md b/docs/architecture/governance/DECISIONS.md index 96e76e2..a719cd8 100644 --- a/docs/architecture/governance/DECISIONS.md +++ b/docs/architecture/governance/DECISIONS.md @@ -3,12 +3,12 @@ schema: aether.architecture-document/v1 id: flow-decisions title: Flow Decisions kind: architecture-document -version: 0.10.1 +version: 0.10.2 status: draft owners: - egohygiene created: 2026-08-13 -updated: 2026-09-27 +updated: 2026-10-22 governed_by: - architecture-decisions depends_on: @@ -104,3 +104,10 @@ enforcement and evidence authentication open. ADR-0010 closes the bounded trusted-unconfined direct-child lifecycle while leaving sandbox enforcement, authenticated evidence, process-tree containment, descriptor-bound execution, durable interruption, retry, and resume open. + +Those omissions describe the scope of ADR-0010, not an absence of later library +implementation. The durable kernel and graph assessment have since merged; +the native read-only Optiflow adapter and its receipt validation have also +merged. ADR-0011, ADR-0012 and ADR-0013 remain **Proposed / Pending review**. +Implementation or PR merge alone does not accept a proposed decision. Their +original records and the accepted/superseded status of earlier ADRs are retained. diff --git a/docs/integrations/README.md b/docs/integrations/README.md index e7cff82..17da0da 100644 --- a/docs/integrations/README.md +++ b/docs/integrations/README.md @@ -3,6 +3,12 @@ Flow integrates independently released holons without taking ownership of their implementations. +For current implementation and next-work status, use the +[continuation handoff](../work/11/HANDOFF.md) and the dated +[capability matrix](capability-matrix.md). The merged durable kernel and native +read-only Optiflow adapter are library surfaces; the product CLI, released +Aniflow/Renderflow adapters and complete installed workflows remain separate. + - [Suite boundaries](suite-boundaries.md) defines ownership and legal dependency directions. - [Capability matrix](capability-matrix.md) records the evidence baseline and @@ -61,8 +67,9 @@ process request encoding and validation of caller-supplied completion, stdout, and stderr evidence through the same Flow-owned acceptance gate. Flow #28 / merged PR #35 adds a closed scenario-manifest model and a synthetic conformance corpus; it describes test intent and does not execute those scenarios. The -executable reference paths remain hermetic; artifact observation is covered by -isolated temporary-fixture tests rather than a real provider. +reference examples for those early seams remain hermetic. Later work adds +durable execution and the native Optiflow integration below; synthetic fixture +coverage does not establish every released-provider or platform combination. Operator-`trusted` entries remain eligible for either execution mode. Operator-`sandboxed` entries may resolve only for process mode and remain diff --git a/docs/integrations/capability-matrix.md b/docs/integrations/capability-matrix.md index c801b97..986d123 100644 --- a/docs/integrations/capability-matrix.md +++ b/docs/integrations/capability-matrix.md @@ -1,8 +1,37 @@ # Provider capability matrix -This is an architectural evidence baseline, not a compatibility guarantee. -Implementation work must reinspect named provider releases and replace each -`pending` interface decision with tested evidence. +## Current evidence — October 22, 2026 + +Source revisions, package versions, immutable releases and executed compatibility +are separate evidence. This matrix does not qualify arbitrary current source or +every platform. Re-query the [current handoff](../work/11/HANDOFF.md) and the +owning issue before implementing an adapter. + +| Repository and inspected main | Release available to Flow | Supported integration evidence | Remaining owner | +| --- | --- | --- | --- | +| Flow `aadf053d48ce8826ee5b9ca4a134985f4e7910e3` | No published GitHub release; package `publish = false` | Durable library/kernel and native read-only Optiflow adapter merged; synthetic fixture binary only | Product CLI [#53](https://github.com/egohygiene/flow/issues/53), first candidate [#54](https://github.com/egohygiene/flow/issues/54), qualification [#34](https://github.com/egohygiene/flow/issues/34) | +| Aniflow `7a808ff99ca8f557f6a3ba7fd373a393de0feee6` | No published GitHub release | Merged temporal/audio/toolchain implementation is source evidence; Flow adapter compatibility is not qualified | Provider release [Aniflow #10](https://github.com/egohygiene/aniflow/issues/10), deferred qualification [#64](https://github.com/egohygiene/aniflow/issues/64), Flow adapter [#51](https://github.com/egohygiene/flow/issues/51) | +| Optiflow `d03e53f2e397af03920070d9bb6c076d7827e12b` | Read-only v0.1.1, source `b82599a2231e997d42fd9f26f4b59587f4ae14cf`; newer main is not that release | Native `optiflow.command-result.v1` CLI adapter: scan, report, exact-duplicate review plan. Pinned archive/executable identities and actual synthetic Linux execution; macOS archives pinned, native execution unverified | Completed Flow [#50](https://github.com/egohygiene/flow/issues/50)/[#81](https://github.com/egohygiene/flow/issues/81); later provider release [Optiflow #93](https://github.com/egohygiene/optiflow/issues/93), mutation/PNG adapters [#73](https://github.com/egohygiene/flow/issues/73)/[#74](https://github.com/egohygiene/flow/issues/74) | +| Renderflow `9dac5428df38691b2922e09ea02d51b02a7f43eb` | No published GitHub release | Merged publication/transform implementation is source evidence; Flow adapter compatibility is not qualified | Provider release [Renderflow #419](https://github.com/egohygiene/renderflow/issues/419), Flow adapter [#52](https://github.com/egohygiene/flow/issues/52) | + +The [Optiflow integration guide](optiflow-v0.1.1-read-only.md) owns exact binary +digests, schemas, effects and native limits. Its Flow receipt is a separate +local audit record, not a generic graph checkpoint or mutation grant. Dry-run, +quarantine, restore and finalize remain explicitly unsupported by this pinned +adapter. The [#81 receipt](../validation/flow-81-local.json) records focused +Linux/Rust 1.85.0 evidence; broader clean-room qualification remains #34. + +Source-only provider work and retained deferred checks cannot establish native +readiness. An adapter decision must record exact release/artifact identity, +interface and accepted schema versions, effects, runtime tools, observed +outputs, deterministic compatibility, and explicit unavailable/untested states. + +## Prior architectural baseline — historical + +The original table below preserves the August 13 Aniflow/Renderflow source +observations and the later pinned Optiflow entry. Package version labels and +earlier ordering decisions are not current release or compatibility evidence. +Use the current table and owning issues above for execution. | Provider snapshot | Observed domain capability | Current integration evidence | First-slice role | Adapter decision | | --- | --- | --- | --- | --- | diff --git a/docs/roadmaps/flow-suite-dependency-map.md b/docs/roadmaps/flow-suite-dependency-map.md index 2c31de0..4023e9a 100644 --- a/docs/roadmaps/flow-suite-dependency-map.md +++ b/docs/roadmaps/flow-suite-dependency-map.md @@ -1,5 +1,16 @@ # Flow suite roadmap to completion +> **Current continuation: October 22, 2026.** Start with the +> [current handoff](../work/11/HANDOFF.md) and [live #11 ledger](https://github.com/egohygiene/flow/issues/11). +> The durable kernel, read-only Optiflow adapter and #81 repair are merged. +> After #82, #15 is next. The source/release matrix and qualification limits +> are in the handoff. The October 6 atlas and October 15 provider note below +> retain their original observation boundaries, counts and nodes. Their old +> Aniflow draft states are historical; PRs #105/#115 have since merged while +> qualification/release remains open. No graph or census was regenerated. + +## Preserved roadmap observations — October 6 and October 15, 2026 + > **Latest provider execution-order refresh: October 15, 2026.** Read the > [bounded three-provider execution order](flow-suite-execution-order-2026-10-15.md) > for current Renderflow, Aniflow and Optiflow pins, existing drafts, remaining diff --git a/docs/validation/flow-82-docs.json b/docs/validation/flow-82-docs.json new file mode 100644 index 0000000..f7991b8 --- /dev/null +++ b/docs/validation/flow-82-docs.json @@ -0,0 +1,366 @@ +{ + "issue": "https://github.com/egohygiene/flow/issues/82", + "date": "2026-10-22", + "base_commit": "aadf053d48ce8826ee5b9ca4a134985f4e7910e3", + "scope": "Documentation and continuation reconciliation only. Candidate commit is identified by the containing PR; file hashes bind the observed document bytes without self-referential commit metadata.", + "source_files_sha256": { + "AGENTS.md": "d9485277dca0de7b9c32d59e214d1b719ba5e8daca258fbf18974fbeaaf636df", + "README.md": "f24b234ab9065f0d4b3202aa6907ffaa937af1c0e513641af51a249e9d9bcae0", + "ROADMAP.md": "1d131fa228e5c9499c508ae609c1368f47a62757643c045c605e05bbd79162d2", + "docs/architecture/README.md": "0f35ae7b21c1111016c2feecbb66229657135fc80f3eac571ba29b953b8d8657", + "docs/architecture/foundation/ARCHITECTURE.md": "a3fb71e2822e15a692bd8c2692776f74cee63962dc63bd175df1770ef5f9ce66", + "docs/architecture/foundation/SYSTEM.md": "5246899a4d8f8172c331a855566f96742c018beca780dde012b3631e5c67fa32", + "docs/architecture/governance/DECISIONS.md": "32b50d594eceaf2f4185e8a1ea148f62015516a071c7289563007bb2188a8f38", + "docs/integrations/README.md": "36594c70b5695f5979bba34ab009385b92101743604600cf55dfaa8f5b10611f", + "docs/integrations/capability-matrix.md": "45d9a6281bdf6f021c8596fd706b6b5f2cab45ef4d81594ac71702a33f472b4a", + "docs/roadmaps/flow-suite-dependency-map.md": "0334b5222e04d9a62e9368a0a246038855d4a12c05323dd8a21c3ebf20b69514", + "docs/work/11/HANDOFF.md": "e3c0f15ab71cd1175640b73f575e211e85729d7356a6d933fedcc8b7c5449453" + }, + "api_observations": [ + { + "url": "https://api.github.com/repos/egohygiene/flow/branches/main", + "observed": { + "sha": "aadf053d48ce8826ee5b9ca4a134985f4e7910e3" + } + }, + { + "url": "https://api.github.com/repos/egohygiene/flow/releases?per_page=10", + "observed": { + "releases": [] + } + }, + { + "url": "https://api.github.com/repos/egohygiene/flow/issues/15", + "observed": { + "number": 15, + "title": "[FLO-OBS-01] Define the suite observability, privacy, and stream contract", + "state": "open", + "updated_at": "2026-10-17T22:32:15Z" + } + }, + { + "url": "https://api.github.com/repos/egohygiene/flow/issues/11", + "observed": { + "number": 11, + "title": "[EPIC] Finish the flow suite and prove production-ready orchestration", + "state": "open", + "updated_at": "2026-10-21T07:38:08Z" + } + }, + { + "url": "https://api.github.com/repos/egohygiene/flow/issues/34", + "observed": { + "number": 34, + "title": "[FLO-13.7] Add clean-room compatibility, CI tiers, and regression promotion", + "state": "open", + "updated_at": "2026-10-21T07:33:13Z" + } + }, + { + "url": "https://api.github.com/repos/egohygiene/flow/pulls/79", + "observed": { + "number": 79, + "title": "docs: refresh full suite roadmap with NUKED milestones [skip ci]", + "state": "closed", + "merged": true, + "merge_commit_sha": "af68afa5732a04c237df5fbeee6bc5e901a5c6fd", + "merged_at": "2026-10-16T01:58:19Z", + "head": "35316427028fe729a6e3a6e4e9522f42a9704ca7" + } + }, + { + "url": "https://api.github.com/repos/egohygiene/aniflow/branches/main", + "observed": { + "sha": "7a808ff99ca8f557f6a3ba7fd373a393de0feee6" + } + }, + { + "url": "https://api.github.com/repos/egohygiene/aniflow/releases?per_page=100", + "observed": { + "releases": [] + } + }, + { + "url": "https://api.github.com/repos/egohygiene/aniflow/pulls/105", + "observed": { + "number": 105, + "title": "feat: prepare explicit audio provider registration documents (#104)", + "state": "closed", + "merged": true, + "merge_commit_sha": "fc1cbc0cc02b4b416de4c088bf59fa562f05779b", + "merged_at": "2026-10-17T20:35:57Z", + "head": "afc444aff8fd108c4ce7d2fd48bf208c02f640a6" + } + }, + { + "url": "https://api.github.com/repos/egohygiene/aniflow/pulls/115", + "observed": { + "number": 115, + "title": "feat: add serial RIFE interpolation with conservative host presets (#114)", + "state": "closed", + "merged": true, + "merge_commit_sha": "5376c48c532513aa8cd5ca6f10ff8a3b16ec58a2", + "merged_at": "2026-10-17T20:38:52Z", + "head": "e180a655b8239f8602e8c26d72b7a53ab7b59eca" + } + }, + { + "url": "https://api.github.com/repos/egohygiene/aniflow/issues/64", + "observed": { + "number": 64, + "title": "Deferred validation cleanup: alignment cancellation CI failure and accumulated audit evidence", + "state": "open", + "updated_at": "2026-10-21T03:07:26Z" + } + }, + { + "url": "https://api.github.com/repos/egohygiene/renderflow/branches/main", + "observed": { + "sha": "9dac5428df38691b2922e09ea02d51b02a7f43eb" + } + }, + { + "url": "https://api.github.com/repos/egohygiene/renderflow/releases?per_page=100", + "observed": { + "releases": [] + } + }, + { + "url": "https://api.github.com/repos/egohygiene/optiflow/branches/main", + "observed": { + "sha": "d03e53f2e397af03920070d9bb6c076d7827e12b" + } + }, + { + "url": "https://api.github.com/repos/egohygiene/optiflow/releases?per_page=100", + "observed": { + "releases": [ + { + "tag": "v0.1.1", + "published_at": "2026-09-26T19:09:10Z", + "draft": false, + "target_commitish": "main" + }, + { + "tag": "v0.1.0", + "published_at": "2026-09-12T14:16:43Z", + "draft": false, + "target_commitish": "main" + } + ] + } + } + ], + "semantic_review": [ + "Independent source review: current implementation boundary, native protocol/receipt versus generic durable graph, remaining product delivery, proposed ADR status and historical projection scope agree.", + "Independent ledger review: source/release/merged/deferred distinctions, next #15, full #53 scope and optional-lane boundaries agree. Reviewers did not execute checks." + ], + "documentation_checks": [ + { + "name": "specifications", + "command": [ + "python3", + ".agents/specs/validate-specs.py" + ], + "exit_code": 0, + "elapsed_seconds": 0.121, + "log_sha256": "163b4172b608a75b50c64d86a720541a8068a1fe101a3570b48da42eddf1fc4f" + }, + { + "name": "skills", + "command": [ + "python3", + ".agents/skills/validate-skills.py" + ], + "exit_code": 0, + "elapsed_seconds": 0.056, + "log_sha256": "50839b72eb57a40544086f717ede46e18fc04a38510682a2a60ed49194b31744" + }, + { + "name": "agents", + "command": [ + "python3", + ".agents/agents/validate-agents.py" + ], + "exit_code": 0, + "elapsed_seconds": 0.089, + "log_sha256": "eb33668aecfec9f9f73dce8d6746b502e5cb4eec39ebfa922df010df93190307" + }, + { + "name": "whitespace", + "command": [ + "git", + "diff", + "--check" + ], + "exit_code": 0, + "elapsed_seconds": 0.005, + "log_sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855" + }, + { + "name": "source/documentation inspection", + "method": "One-off local Python inspection using git show at the base, UTF-8 decoding, Markdown targets, YAML metadata/relationship graph, Cargo.toml inspection and SHA-256 comparisons. Script was not added to repository tooling.", + "exit_code": 0, + "inspection_script_sha256": "b4849b62c301469e7f2a075907929fa4603165f83c17ed33c1cc31deddd1a585", + "output_sha256": "791580e6f05fdc29b12a8b5758df4dcf2f8292ed8d6aa0cf6e59291dc1bcadfe", + "results": { + "scope": "12 documentation/evidence files only", + "utf8_lf_and_single_h1": true, + "links_checked": 790, + "relative_targets_resolved": 136, + "external_url_syntax_checked": 654, + "external_http_crawl": false, + "historical_handoff_and_map_suffixes_byte_preserved": true, + "historical_embedded_roadmap_snapshot_byte_preserved": true, + "protected_unchanged_artifacts": [ + { + "path": "docs/roadmaps/archive/flow-suite-dependencies-2026-09-27.mmd", + "sha256": "e6697b351459e28f6466cd5fe63ed5081a1814a65cbde6f8fb962be7846f0e5d" + }, + { + "path": "docs/roadmaps/flow-suite-completion.mmd", + "sha256": "2169fbf8a48d1c02647d4871f72d7f23a9a2080bba371d5dae49c828706bb4be" + }, + { + "path": "docs/roadmaps/flow-suite-completion.svg", + "sha256": "17a4341b1ceca38d8bf2d7042a62f81606d626e5b5fcf469a40851ce3e4e990f" + }, + { + "path": "docs/roadmaps/flow-suite-execution-order-2026-10-15.md", + "sha256": "e62953940f7a7f9affb4deb679e3a026c81f180847eaf8327f52d9c11994971a" + }, + { + "path": "docs/roadmaps/flow-suite-live-sweep-2026-09-22.md", + "sha256": "22e5d139f342ac754eae3845aba2c53b0078def8e4a6667f151c8fd886553b4a" + }, + { + "path": "docs/roadmaps/flow-suite-status.json", + "sha256": "d5cbdc2c510de3de655c02e700393814b25423dcfe9ca4165f296c86f53deb7c" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0001-holonic-monorepo.md", + "sha256": "2447163f01d16b3b3ffd90c8ad114a727122972b8636cc48cc460aeec85f1727" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0002-provenance-preserving-derivatives.md", + "sha256": "e7fcd9d8ae75c7700e1d6fc4cc3c4c3c1f6ec1329b70ddd9a31620aeb47f3e5e" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0003-docs-first-initialization.md", + "sha256": "2e1de65b8934606843751e40fba9eb81b38423fa66300d5eee9277228e0f9176" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0004-federated-suite-contracts.md", + "sha256": "5f285a6ba18d379952892ff449533ca49d73f3a978a00348585ddc4db09f2905" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0005-federated-extension-authority.md", + "sha256": "eea78bc906d153d9fc35ea19d5e3c38ae5c505bf69fa50b2b07c377de38dbd0b" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0006-bounded-process-transport.md", + "sha256": "e05a83dfc90f0a3450ddad40c7ba1fb7e2a155ca62171441e3f060479c5ccd50" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0007-root-confined-artifact-acceptance.md", + "sha256": "597570212ba40022547306cb067921c74b692e103bd0a8fb6591cadcab40d518" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0008-locked-execution-subjects.md", + "sha256": "d8e7824f42a86c5802f45afb0aa2c19e07467050996c3c9f8fdd8350a9c4d42c" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0009-process-authority-isolation.md", + "sha256": "e0086c84c1e28b46f90d8c8c2f647609588ebf1cac2fa10e5a63c80af598bca0" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0010-bounded-direct-process-supervision.md", + "sha256": "720017dbb0f3029de392872ccbc190535f7d7b5135cdfb8881f3112f81ceb661" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0011-durable-run-state.md", + "sha256": "aa20a323ce217443db77c14d4385be1bd5c0a19e5a2cd6a62e65f456146416d0" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0012-fresh-graph-assessment.md", + "sha256": "16e4f83485c43030d6ae049cd285a19ac0406ab7958675910f05096f13b0d42e" + }, + { + "path": "docs/architecture/governance/decisions/ADR-0013-optiflow-native-read-only-adapter.md", + "sha256": "91af35034121c1e8907534b71f39c0116b33e1dab67f6fdc228dc2e0b6732003" + }, + { + "path": "docs/validation/flow-66-local.json", + "sha256": "fb485b0d1534210e40304c91d1c67daa0c7873a81475069cb30d251be3c3503b" + }, + { + "path": "docs/validation/flow-81-local.json", + "sha256": "e5e1be8cb9131713e415ae4d08733d7a18e4d58e67695b21e087a054aa818276" + }, + { + "path": "audits/flow-suite-20261021T025401Z.json", + "sha256": "275daff4d825f64971b6223e0766f2b6b59bd7969c6e89c9267e6c2b744f42a6" + }, + { + "path": "audits/flow-suite-20261021T025401Z.md", + "sha256": "2435802c27f3028fd594f885e12ed0f8d41fed0b13d9a3753e2860ae22eb5f55" + } + ], + "architecture_documents_in_relationship_check": 46, + "architecture_graph_acyclic": true, + "metadata_updates": [ + { + "path": "ROADMAP.md", + "version": "1.3.9", + "governed_by": [ + { + "id": "architecture-roadmap", + "version": "1.1.0" + } + ] + }, + { + "path": "docs/architecture/foundation/SYSTEM.md", + "version": "0.2.1", + "governed_by": [ + { + "id": "architecture-system", + "version": "1.1.0" + } + ] + }, + { + "path": "docs/architecture/foundation/ARCHITECTURE.md", + "version": "0.13.5", + "governed_by": [ + { + "id": "architecture-architecture", + "version": "1.1.0" + } + ] + }, + { + "path": "docs/architecture/governance/DECISIONS.md", + "version": "0.10.2", + "governed_by": [ + { + "id": "architecture-decisions", + "version": "2.0.0" + } + ] + } + ], + "proposed_adr_states_preserved": true, + "source_scope_assertions": "publish=false; synthetic fixture binary; durable/native source present; no Aniflow/Renderflow adapter modules; no root continuity adoption", + "source_hashes_match": true + } + } + ], + "limits": [ + "No runtime source, provider contracts, release assets, CI/workflow definitions or validation requirements changed.", + "No product compiler/build, test, lint, native/media/model/volume/package execution or hosted CI dispatch/polling in this checkpoint. Documentation checks do not qualify product behavior.", + "Prior #81 focused native/regression results remain dated evidence. Flow #34 retains the full-wrapper timeout, native skip semantics and moving-stable qualification; existing Aniflow/Renderflow deferrals remain in force.", + "No new current issue census, diagram regeneration, provider release, deployment, ADR acceptance or optional-scope disposition." + ], + "next_issue": "https://github.com/egohygiene/flow/issues/15" +} diff --git a/docs/work/11/HANDOFF.md b/docs/work/11/HANDOFF.md index 5a5db2e..b6a6809 100644 --- a/docs/work/11/HANDOFF.md +++ b/docs/work/11/HANDOFF.md @@ -1,5 +1,92 @@ # Flow #11 completion-roadmap handoff +## Current continuation — October 22, 2026 + +This is the current continuation entrypoint. Re-read the linked live issue, +applicable `AGENTS.md`, source, open PRs and released artifacts before starting +one bounded checkpoint. The dated records below remain historical evidence; +their old next-up, draft, merge and validation instructions are superseded here. + +### Implemented, proposed and released + +Inspected Flow main: `aadf053d48ce8826ee5b9ca4a134985f4e7910e3`. +The durable library/kernel and native read-only Optiflow v0.1.1 adapter are +merged. [#81 / PR #84](https://github.com/egohygiene/flow/pull/84) completed +saved-receipt validation. The native adapter retains its own local receipt; +it is not yet a generic durable-graph checkpoint. See the canonical +[architecture boundary](../../architecture/foundation/ARCHITECTURE.md) and +[provider capability matrix](../../integrations/capability-matrix.md). + +There is no supported product `flow` CLI or published Flow GitHub release at +this observation. Aniflow/Renderflow adapters, complete installed workflows, +local-file UX and distribution remain separately owned work. The only current +Flow binary is a synthetic conformance provider; `Cargo.toml` has +`publish = false`. The temporal restore-and-assess slice is a proposed proof, +not a delivered product workflow. ADR-0011/0012/0013 remain proposed pending +human review; merging their implementation does not accept those decisions. + +### Next bounded checkpoint + +[#82](https://github.com/egohygiene/flow/issues/82) is this documentation repair. +After its merge, continue with +[#15 — suite observability, privacy and stream contract](https://github.com/egohygiene/flow/issues/15), +the next issue in the [live #11 ledger](https://github.com/egohygiene/flow/issues/11). +It has no declared implementation prerequisite. Set one reviewable contract +outcome before adding exporters or changing every provider. #62 and #80's first +checkpoint remain independent ready lanes; they are not substituted for #15. + +The first installed candidate, stable audited suite and retained optional +product backlog remain different finish lines. The CLI/adapters and release +owners keep their full acceptance criteria. In particular, #53's declared +all-adapter dependencies and static-first acceptance wording still require an +explicit disposition before closeout. Optional AI, AMV, mutation/PNG and broader +comic capabilities do not become automatic first-candidate prerequisites. + +### Fresh provider and PR observations + +- Flow roadmap [PR #79](https://github.com/egohygiene/flow/pull/79) is merged as + `af68afa5732a04c237df5fbeee6bc5e901a5c6fd`. Resume new work from live main, + not its old draft branch. The four October 21 audit PRs are also merged. +- Aniflow [PR #105](https://github.com/egohygiene/aniflow/pull/105) and + [PR #115](https://github.com/egohygiene/aniflow/pull/115) are merged; their + checkpoint issues #104/#114 are closed. Broader validation remains deferred + under [#64](https://github.com/egohygiene/aniflow/issues/64). There is no + published Aniflow GitHub release; [#10](https://github.com/egohygiene/aniflow/issues/10) + and Flow #51 remain open. Do not treat merge as executed native qualification. +- Renderflow has no published GitHub release; + [#419](https://github.com/egohygiene/renderflow/issues/419) and Flow #52 remain + open. [PR #455](https://github.com/egohygiene/renderflow/pull/455) remains draft. +- Optiflow's published v0.1.1 remains the read-only adapter contract. Main is + newer source; [#93](https://github.com/egohygiene/optiflow/issues/93) remains + open. [PR #122](https://github.com/egohygiene/optiflow/pull/122) remains draft; + dependency-maintenance PRs retain their separate scope. + +### Validation and preservation boundary + +[#81's receipt](../../validation/flow-81-local.json) records focused Linux/Rust +1.85.0 checks and actual pinned Optiflow execution. The prior complete-wrapper +600-second timeout, native unavailable/skip semantics and moving-stable Clippy +baseline remain under [#34](https://github.com/egohygiene/flow/issues/34). +This documentation checkpoint does not rerun product tests, compiler/build, +lint, native/media/model/volume/package operations, or hosted CI. Existing +Aniflow/Renderflow product-validation deferrals remain in force. Documentation +verification and exact source/API observations are recorded in +[the #82 documentation receipt](../../validation/flow-82-docs.json). +No new runtime behavior, validation requirement, release, or ADR acceptance is +introduced. PR merge authority comes from the active maintainer request. + +The [October 6 atlas](../../roadmaps/flow-suite-dependency-map.md), its graph, +JSON and original archive retain their dated counts and nodes. The +[October 15 provider-order note](../../roadmaps/flow-suite-execution-order-2026-10-15.md) +is preserved at its own observation boundary. Neither is a fresh census. +The current live #11 issue owns the complete execution ledger; this handoff +links that ledger rather than maintaining another full issue list. + +## Preserved historical handoffs — October 15 and October 6, 2026 + +Everything below is the original handoff text, retained for provenance. Its +uses of “current,” “draft,” “next,” and “stop” refer to those observations. + ## October 15, 2026 — provider execution-order refresh The maintainer requested an updated order for completing the three independent