Poesis
Usage / Use case Implemented
Review sourced obligations before binding them
Prepare a source-linked shortlist of architecture, quality and regulatory requirements for a bounded IT review.
CISO / Security leadership / Enterprise Architect / Specification reader / modeler
Platform
What serves this use case
Features
- Ontology: TOGAF Implemented
- Ontology: ISO 25010 Implemented
- Ontology: ISO 25012 Implemented
- Ontology: GDPR Implemented
- Ontology: NIS2 Implemented
- Ontology: SCAP Implemented
Values
Values composed with this use case
- Value Partial
Connect governance and policy tools.
Use shared definitions and obligations as inputs to planned policy, attestation, observation and delivery integrations, with dedicated adapters for each tool.
Supported by Capabilities(4)
Supported by Features(10)
Realized through Use cases(6)
- Value Partial
Inspect the model and its sources.
Evaluate adoption against versioned content, source mappings and visible research questions. Neutral stewardship remains a stated direction, distinct from consortium endorsement.
Supported by Affordances(1)
Supported by Capabilities(1)
Supported by Features(10)
- Value Partial
Start from reusable vocabulary.
Build on selected sourced content, then focus authoring effort on installation, interpretation and bindings for your domain.
Supported by Capabilities(1)
Supported by Features(7)
- Value Partial
Inspect source mappings.
Review concepts in the source taxonomy with available clause references, checking coverage and legal applicability for your scope.
Supported by Capabilities(1)
Supported by Features(7)
Pains
Pain points
- Pain point Partial
Selected vocabulary and unbound templates are mistaken for complete, applicable obligations.
Subjects or concerns are omitted and requirements are applied without a justified adopting scope.
Addressed by Affordances(1)
Addressed by Capabilities(2)
Addressed by Features(7)
Experienced by Actor types(5)
Addressed through Use cases(6)
- Pain point Partial
Every framework lives in its own silo — and they collide on your desk.
TOGAF, ISO, GDPR, and NIS2 each demand their own registry and their own reconciliation; overlaps and conflicts are discovered by accident.
Addressed by Affordances(1)
Addressed by Capabilities(2)
Addressed by Features(11)
Experienced by Actor types(6)
Addressed through Use cases(7)
- Compose and reuse a governance selection
- Resolve competing obligations before adoption
- Review sourced obligations before binding them
- Review a governance package upgrade
- Compose an IT governance fabric for an adopting scope
- Adopt a sourced framework or regulation
- Review selected obligations together