Poesis
Usage / Use case Planned
Answer an IT question from the governed model
Assess a proposed IT change by combining dependency and obligation paths with cited read-only answers over the same authorized definitions. Compare affected parties and unresolved evidence before choosing an option; graph traversal is not causal simulation.
Platform
What serves this use case
Capabilities
Values
Values composed with this use case
- Value Partial
Reduce uncertainty about a specified change
Bring relevant context and affected definitions into a shared review, making dependency paths and missing evidence visible before deciding.
Supported by Capabilities(2)
Supported by Features(2)
- Value Planned
Coordinate IT work around shared definitions.
Reuse common inputs across appraisal, analysis and document generation so profiles can review decisions against the same definitions. Outputs and scenarios remain subject to review.
Supported by Capabilities(1)
Supported by Features(3)
- Value Planned
Check answers against sources.
Use the planned copilot to find relevant definitions and inspect cited evidence, snapshot age and uncertainty alongside each answer.
Supported by Capabilities(1)
Supported by Features(1)
Realized through Use cases(2)
Pains
Pain points
- Pain point Planned
Impact analysis is a guess made in a meeting.
Coupling is discovered in incident reviews, after the change shipped.
Addressed by Capabilities(1)
Addressed by Features(1)
Experienced by Actor types(6)
- Pain point Partial
AI agents act on stale wikis and tribal knowledge.
Without a trustworthy machine-readable source of truth, agent autonomy is either blocked or reckless.
Addressed by Affordances(1)
Addressed by Capabilities(2)
Addressed by Features(2)
Experienced by Actor types(5)