Poesis
Usage / Use case Planned
Source IT definitions from inspected evidence
Run revision-pinned acquisition, review its coverage limits and register the resulting candidates as drafts, keeping source revision distinct from deployed reality.
Platform / Ops / SRE lead / Enterprise Architect / Authorized integration client
Platform
What serves this use case
Capabilities
Values
Values composed with this use case
- Value Partial
Inspect acquisition scope and freshness
Distinguish inspected revisions from missing, failed or stale collection before relying on source evidence.
Supported by Affordances(1)
Supported by Capabilities(1)
Supported by Features(2)
Realized through Use cases(6)
- Value Partial
Give AI attributable context.
Ground planned read-only answers in authorized, versioned definitions, with citations and abstention for review. Build that context through direct authoring or reviewed sourcing.
Supported by Affordances(1)
Supported by Capabilities(2)
Supported by Features(1)
- Value Partial
Compare contributed partial views.
Bring conflicting candidates into shared panels so reviewers can compare evidence and identify gaps in the collected views.
Supported by Affordances(1)
Supported by Capabilities(2)
Supported by Features(1)
Pains
Pain points
- Pain point Partial
Collection scope, incomplete runs and stale evidence are mistaken for current coverage.
Reviews rely on uninspected or outdated inputs and repeat work when collection failures emerge late.
Addressed by Affordances(1)
Addressed by Capabilities(1)
Addressed by Features(2)
Experienced by Actor types(4)
Addressed through Use cases(6)
- Pain point Partial
The architecture repository is out of date the day it’s written.
Hand-maintained models detach from the territory the moment delivery moves on — and every decision made on them inherits the drift.
Addressed by Affordances(1)
Addressed by Capabilities(3)
Addressed by Features(2)
Experienced by Actor types(4)
Addressed through Use cases(7)
- Author and approve a shared definition
- Reconcile code evidence into reviewed definitions
- React to a committed definition change
- Extract definition candidates from a code revision
- Source IT definitions from inspected evidence
- Hold definitions as the authoritative, revision-bound source
- Review candidates from selected sources