Poesis
Usage / Use case Partial
Work from shared, typed definitions
Align an architect's dependency review and an AI-assisted enquiry on the same typed, versioned definition basis, tracing scope, access and interpretation differences before making a decision. A shared representation does not prove live-state correspondence or answer quality.
Enterprise Architect / CISO / Security leadership / Head of AI / Authorized integration client
Platform
What serves this use case
Affordances
- Governed organizational context Partial
Values
Values composed with this use case
- 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)
- 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
Build toward shared definition semantics.
Give compatible tools a common vocabulary for definitions, analogous to shared observability conventions. Interchange depends on implemented profiles and independent consumer compatibility.
Supported by Affordances(1)
Supported by Capabilities(3)
Supported by Features(4)
Realized through Use cases(6)
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
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)
- 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