Poesis
Usage / Use case Partial
Define a delivery ceremony and its handoffs
Specify the sequence of roles, context and artifacts for a ceremony, identifying human-decision checkpoints separately from the planned implementation that authenticates them.
Platform
What serves this use case
Features
Values
Values composed with this use case
- Value Partial
Keep decisions attributable.
Bind advancement to authenticated human decisions on exact revisions and scope through the planned approval workflow.
Supported by Affordances(1)
Supported by Capabilities(2)
Supported by Features(2)
Pains
Pain points
- Pain point Partial
AI agents ship work nobody scoped, gated, or can replay.
Agentic delivery state is trapped in chat sessions; pull requests appear without a mandate; there is no event log and no human authority at the layer where it matters.
Addressed by Affordances(1)
Addressed by Capabilities(4)
Addressed by Features(7)
Experienced by Actor types(5)
Addressed through Use cases(14)
- Approve an agent resource and action mandate
- Deliver a reviewed artifact through a local workflow
- Set up a workspace and publish checked artifacts
- Resolve the next eligible workflow step
- Inspect a captured harness invocation sequence
- Assign a delivery responsibility from the role catalog
- Select a practice playbook for a delivery task
- Define a delivery ceremony and its handoffs
- Select versioned instructions for an engineering role
- Run an agentic workflow with deterministic controls
- Adopt the agentic SAFe operating model
- Gate an advancement on an authenticated human decision
- Deliver from a local-first, reproducible plane
- Generate artifacts through declared workflows