Poesis
Usage / Use case Partial
Maintain a governed IT definition inventory
Keep typed IT definitions, their review lenses, authorizations and decision sessions coherent so every review works from the same attributable inventory.
Enterprise Architect / IT service owner / CISO / Security leadership
Platform
What serves this use case
Capabilities
Values
Values composed with this use case
- Value Partial
Repeatable review boundaries
Reuse explicit selection and traversal rules so reviewers can compare decisions against identified subjects and snapshot boundaries.
Supported by Capabilities(1)
Supported by Features(1)
- Value Partial
Coherent records of related decisions
Retain agendas, participation and per-revision decisions together while keeping discussion, voting and authorized lifecycle decisions distinct.
Supported by Capabilities(1)
Supported by Features(2)
- Value Partial
Keep governance closer to its evidence.
Bring shared definitions, reviewed candidates and scoped appraisal together to simplify reconciliation. For running systems, keep observation coverage and freshness visible.
Supported by Affordances(2)
Supported by Capabilities(2)
Pains
Pain points
- Pain point Partial
Reviewers work from different selections and lose related decisions across meeting notes.
Decisions cannot be compared or reconstructed against the same agenda, subject set and evidence boundaries.
Addressed by Affordances(1)
Addressed by Capabilities(1)
Addressed by Features(2)
Experienced by Actor types(7)
- Pain point Partial
Architecture, compliance, and quality tools don’t speak to each other.
Each tool keeps its own model of the same IT reality; integrations are bespoke mappings that rot, and knowledge stays siloed per tool and per team.
Addressed by Affordances(1)
Addressed by Capabilities(6)
Addressed by Features(17)
Experienced by Actor types(9)
Addressed through Use cases(16)
- Inspect one subject across framework perspectives
- Agree a reusable domain typing contract
- Qualify transfer between independent processors
- Read and model a governance decision
- Describe a service contract and its attribution
- Describe payment request and notification boundaries
- Describe payment settlement and recovery boundaries
- Incorporate an accepted grammar extension
- Read and revise definitions through the API
- Qualify an execution adapter for an integration
- Maintain a governed IT definition inventory
- Type a governance concern with the systemic primitives
- Define a domain vocabulary as an Archetype
- Express an obligation in the governance grammar
- Describe an interaction with sourced protocol vocabulary
- Work from shared, typed definitions