Implement a versioned cross-holon orchestration vertical slice

[szmyty]

Outcome

Compose one real inspect-plan-transform-validate workflow through stable public contracts with state, provenance, recovery, and explanation owned by Flow.

Scope

• Implement the work owned by egohygiene/flow that is necessary to deliver this outcome.
• Coordinate cross-repository work through the dependencies below; do not copy sibling implementations into this repository.
• Keep unrelated refactors, mutable cross-repository source dependencies, and secret material outside this issue.

Extension-contract foundation

#7 defines the reusable federated plugin/adapter/hook contract. This vertical slice should consume that contract rather than inventing scenario-specific discovery or lifecycle semantics.

Acceptance criteria

• Choose a scenario that uses at least two independent holons
• Persist versioned run state and immutable input/output references
• Support interruption, resume, failure explanation, and partial-result inspection
• Prove each holon remains independently usable
• Discover and invoke participating capabilities through the versioned extension/provider contract from [Extensions] Define the federated plugin, adapter, and hook contract #7
• Record provider identity, compatibility, permissions, validation, and provenance in the persisted run

Dependencies

FLO-01, OPT-07, REN-01

Source and decisions

• Portfolio ID: FLO-02
• Priority: P2
• Dependency wave: 4 - Product capabilities
• Source: Flow README; architecture discussions
• Suggested labels: priority:p2
• Assignee: szmyty

This scope was approved for creation from the Ego Hygiene Organization Issue Portfolio dated August 18, 2026.

Durable foundation merged — 2026-09-26

#49 is complete: PR #63 merged as 711fbe3c19c0e080ab6c67b74d7945cd29675a74, with all five default-branch CI jobs green. It adds versioned prepared intent, atomic immutable state, accepted checkpoints, fresh eligibility checks, and explicit recovery decisions.

#31 is active through #64 → #65 → #66: fresh graph assessment and safe dependent execution, deterministic durable lifecycle traces, then authority/effect and recovery-residual proofs. This foundation does not close the overall vertical slice or satisfy the two-real-holon criterion; released-provider adapters and the remaining #53 reconciliation still apply.