Greenways suite · 05 · current product laboratory
Spaces ↔ Flow handoff
A traceable question-to-work-to-result loop with included context, excluded authority, lifecycle, and attributable evidence.
- Foreground applications
- Spaces · Flow
- Selected application
- Suite context
- Behaviour
- Static specimen · no command connected
Current cross-application loop
Space question → Flow work → selected result → same Space.
space/open-distributionbrief/open-distribution-04 · question/portable-rights
flow/project/release-24flow/work/claim-evidence · optional milestone/release-candidate-04
space/open-distribution/source/flow-result-8f2aReported artifact becomes a Space reference only after explicit selection.
- Selected cited brief revision
- Eight exact source anchors
- Question and expected deliverable
- Return target in the same Space
- Other Space notes or membership
- Standing publish authority
- Host credentials or provider sessions
- Automatic acceptance as a reviewed finding
- 01preparedObserved transition required
Context assembled; nothing dispatched
- 02approval requiredObserved transition required
Human review needed for bounded source read
- 03readyObserved transition required
Approved scope and target project resolved
- 04acceptedObserved transition required
Flow accepted the work item; not completed
- 05creatingObserved transition required
Project work and claim are being reconciled
- 06receivedObserved transition required
Artifact reported back; not selected
- 07selectedObserved transition required
Human selected one result for return
- 08completedAttributable receipt
Reference written back to the same Space
Current specimen
Approval required before the exact source anchors can be read in Flow.
- Handoff ID
- handoff/space-brief-04-to-release-24
- Idempotency
- space-brief-04/release-24/v1
- Requested capability
- Read the eight included anchors once
- Excluded consequence
- No Space membership, publishing, host, or credential authority
- Return condition
- One explicitly selected artifact or a truthful partial/failed state
Non-happy paths
Failures remain first-class and attributable.
Unactivated-target conformance
Future targets are not launcher entries and cannot be selected by this handoff. Internal requests return an explicit unavailable result.