Poesis
Usage / Use case Planned
Produce a named IT document family from pinned definitions
Select an IT baseline and its recorded decisions, bind a versioned document family to those inputs, and review generated packs together for consistency and missing evidence. Recurring jobs preserve the same inspection and acceptance boundaries.
Operational knowledge owner / Enterprise Architect / Platform / Ops / SRE lead
Platform
What serves this use case
Capabilities
- ITIP: IT artifact generation Planned
Values
Values composed with this use case
- Value Partial
Distinguish generated output from accepted completion
Inspect binding resolution, grounding constraints, missing inputs and job outcomes before accepting or reusing a generated deliverable.
Supported by Affordances(1)
Supported by Capabilities(1)
Supported by Features(1)
Realized through Use cases(6)
- 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 Planned
Reduce repeated document assembly.
Generate reviewable document families from reusable definitions and templates, then focus effort on review, correction and template upkeep.
Supported by Capabilities(1)
Supported by Features(1)
Pains
Pain points
- Pain point Partial
Incorrect bindings, unsupported narrative and partial files pass for completed deliverables.
Reviews discover missing evidence and output errors only after reports have been distributed.
Addressed by Affordances(1)
Addressed by Capabilities(3)
Addressed by Features(4)
Experienced by Actor types(6)
Addressed through Use cases(13)
- Author and maintain reusable output bindings
- Preview bindings before generating an artifact
- Set grounding constraints for generated narrative
- Operate recurring report production
- Investigate partial or failed generation
- Deliver a reviewed artifact through a local workflow
- Validate a mediated artifact write
- Define a deliverable schema and template
- Publish artifacts through configured CI checks
- Produce a named IT document family from pinned definitions
- Check a produced artifact against its contract
- Gate an advancement on an authenticated human decision
- Generate artifacts through declared workflows
- 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