Poesis
Usage / Use case Partial
Turn delivery history into definition candidates
Correlate pinned artifact revisions with captured invocation history and derive typed candidates whose provenance, uncertainty and source limitations remain inspectable. Candidate contributions are neither accepted definitions nor evidence of deployed systems.
Platform
What serves this use case
Capabilities
- SAF: Delivery evidence sourcing Partial
Values
Values composed with this use case
- Value Partial
Reduce avoidable reconstruction and rework
Reuse shared context and generated artifacts so effort can shift from repeated assembly to curation and review. Net savings depend on the workflow and compute costs.
Supported by Capabilities(2)
Supported by Features(1)
- Value Partial
Reuse delivery evidence.
Derive candidates from pinned artifacts and journals through the planned bridge, then review and promote them through a client-owned stage.
Supported by Capabilities(1)
- Value Partial
Reuse captured delivery evidence.
Make captured delivery evidence available for review and further reasoning through planned sourcing, with missing records and uncertainty kept visible.
Supported by Capabilities(1)
Supported by Features(1)
Pains
Pain points
- Pain point Partial
Every deliverable is hand-crafted, again and again.
ADR packs, evidence, baselines, and roadmaps are rebuilt by hand — and stale against each other by the time they ship.
Addressed by Affordances(1)
Addressed by Capabilities(2)
Addressed by Features(2)
Experienced by Actor types(7)
Addressed through Use cases(8)
- Author and maintain reusable output bindings
- Operate recurring report production
- Generate and review an architecture decision pack
- Reuse captured delivery evidence as definition proposals
- Extract definition candidates from delivery history
- Produce a named IT document family from pinned definitions
- Turn delivery history into definition candidates
- Generate artifacts through declared workflows
- Pain point Partial
The reason for a decision stays in an email thread instead of reaching the next reviewer.
In a manual handoff, the next reviewer repeats interviews to recover assumptions and unresolved objections.
Addressed by Capabilities(2)
Addressed by Features(1)
Experienced by Actor types(7)
Addressed through Use cases(6)