Poesis
Usage / Use case Implemented
Read and revise definitions through the API
Create, query and revise typed definitions through the REST contract, inspecting validation, revision and access responses without treating a successful draft write as approval.
Platform
What serves this use case
Features
Values
Values composed with this use case
- 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
Anything can change anything — there is no approval trail.
Definitions, standards, and obligations mutate without review; who approved what, and when, is unanswerable.
Addressed by Affordances(1)
Addressed by Capabilities(4)
Addressed by Features(7)
Experienced by Actor types(8)
Addressed through Use cases(9)
- Review a governance package upgrade
- Author and approve a shared definition
- Execute a bounded response and inspect the receipt
- Read and revise definitions through the API
- Qualify an execution adapter for an integration
- Enforce definition lifecycle boundaries
- Run a Mechanism inside declared bounds
- Serve authorized definition context to a model
- Make review and activation boundaries explicit
- 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