Poesis
Usage / Use case Implemented
Hold definitions as the authoritative, revision-bound source
Maintain typed definitions through the API and retrieve their stable identities, current revisions and retained history as one governed source. Apply tenant/object access and retention boundaries; a stored draft is not accepted intent.
Platform / Ops / SRE lead / Authorized integration client / Enterprise Architect
Platform
What serves this use case
Capabilities
- SIE: Authoritative definition store Implemented
Values
Values composed with this use case
- Value Partial
Make shared context attributable.
Build toward policy-filtered snapshots that people and AI can inspect. Direct API authoring is independent of sourcing, with MCP planned as an additional interface.
Supported by Affordances(1)
Supported by Capabilities(2)
Supported by Features(1)
- Value Partial
Make transitions inspectable.
Check lifecycle advancement against defined transitions, with authentication, policy and current grammar alignment completing the governance boundary.
Supported by Affordances(1)
Supported by Capabilities(3)
Supported by Features(2)
Realized through Use cases(6)
- Assess dependent definitions after foundation invalidation
- Author and approve a shared definition
- Read and revise definitions through the API
- Hold definitions as the authoritative, revision-bound source
- Enforce definition lifecycle boundaries
- Make review and activation boundaries explicit
Pains
Pain points
- 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
- Pain point Partial
Compliance is reconstructed in spreadsheets before every audit.
Posture exists only at audit time; between audits, nobody can answer what is actually covered.
Addressed by Affordances(1)
Addressed by Capabilities(2)
Addressed by Features(3)
Experienced by Actor types(7)
Addressed through Use cases(7)
- Retrieve the basis of a historical decision
- Review a scoped IT appraisal
- Review recurring patient-portal appraisal
- Inspect retained contribution evidence
- Run a scoped IT compliance appraisal
- Hold definitions as the authoritative, revision-bound source
- Evaluate identified inputs against supported Norms