Poesis
Candidate Standard Model · Solution Partial
Ontology — Generative System Model.
Start governance modeling from sourced vocabulary and reusable templates.
Selected framework, protocol and IT-domain packages include source mappings and unbound governance templates. Adopters select scope, review interpretations and govern their bindings. These content packages describe requirements; runtime assessment belongs to consuming tools.
Values
Value delivered by the product
- 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)
- Value Planned
Review composition explicitly.
Combine selected vocabularies through GSM governance, with reference resolution and obligation conflicts handled in review.
Supported by Capabilities(1)
Supported by Features(1)
- Value Partial
Represent attribution explicitly.
Record attribution in typed facets and connect it to consumer-verified actors and populated lineage.
Supported by Capabilities(1)
Supported by Features(3)
- Value Planned
Review evolving requirements.
Use planned source monitoring and versioned updates to review changing requirements before choosing governed upgrades.
Supported by Features(4)
Realized through Use cases(1)
Features
Implemented and planned features
- Feature Implemented
HTTP
Model selected HTTP requests, responses and ports with sourced Archetypes. Scope: vocabulary, excluding full cache semantics and runtime dispatch.
Addresses Pain points(1)
Supports Values(1)
Serves Use cases(1)
Used by Actor types(2)
- Feature Implemented
TOGAF
Selected TOGAF-derived architecture vocabulary organized by source taxonomy, with mappings and interpretation limits.
Addresses Pain points(2)
Supports Values(4)
Serves Use cases(1)
- Feature Implemented
IT
Type IT-domain definitions by composing selected reference vocabularies through facets. Norm activation remains a separate governance step.
Addresses Pain points(1)
Supports Values(1)
Serves Use cases(1)
Used by Actor types(2)
- Feature Implemented
ISO 25010
Declare selected software-quality dimensions with ISO 25010-derived facets and reviewable source mappings. Runtime measurement and implementation interpretation are separate.
Addresses Pain points(2)
Supports Values(4)
Serves Use cases(1)
- Feature Implemented
ISO 25012
Declare data-quality dimensions and requirements with ISO 25012-derived facets for use by downstream assessment tools.
Addresses Pain points(2)
Supports Values(4)
Serves Use cases(1)
- Feature Implemented
PROV
Represent attribution with PROV-derived vocabulary. Consumers populate lineage and verify actor identity.
Addresses Pain points(1)
Supports Values(1)
Serves Use cases(1)
Used by Actor types(2)
- Feature Planned
gRPC
Describe gRPC streams, deadlines, status and cancellation with sourced vocabulary.
Addresses Pain points(1)
Serves Use cases(1)
Used by Actor types(2)
- Feature Planned
GraphQL
Describe GraphQL partial data, errors, nullability and subscriptions with sourced vocabulary.
Addresses Pain points(1)
Serves Use cases(1)
Used by Actor types(2)
- Feature Planned
Kafka
Describe Kafka partitions, offsets, ordering and replay with sourced vocabulary.
Addresses Pain points(1)
Serves Use cases(1)
Used by Actor types(2)
- Feature Planned
AMQP
Describe AMQP 1.0 settlement, delivery and credit with sourced vocabulary.
Addresses Pain points(1)
Serves Use cases(1)
Used by Actor types(2)
- Feature Planned
JDBC
Describe JDBC parameters, results, transactions and failures at the API level, independently of database wire protocols.
Addresses Pain points(1)
Serves Use cases(1)
Used by Actor types(2)
- Feature Planned
WebSocket
Describe WebSocket sessions, bidirectional messages and failures with sourced vocabulary.
Addresses Pain points(1)
Serves Use cases(1)
Used by Actor types(2)
- Feature Implemented
GDPR
Start from GDPR-derived vocabulary and clause-linked templates, then bind adopter scope with legal review.
Addresses Pain points(2)
Supports Values(4)
Serves Use cases(1)
- Feature Implemented
NIS2
Start from NIS2-derived vocabulary and templates, with entity, jurisdiction and observation bindings supplied for assessment.
Addresses Pain points(2)
Supports Values(4)
Serves Use cases(1)
- Feature Implemented
SCAP
Identify selected platforms and configuration concepts through CPE/CCE facets for use by assessment tools.
Addresses Pain points(2)
Supports Values(4)
Serves Use cases(1)
- Feature Planned
DORA
Source DORA vocabulary and templates with explicit regulation, entity, clause and scenario scope.
Addresses Pain points(2)
Supports Values(1)
Serves Use cases(1)
- Feature Planned
SAFe
Source SAFe vocabulary with edition and rights review, as ontology content distinct from SAF delivery workflows.
Addresses Pain points(2)
Supports Values(1)
Serves Use cases(1)
- Feature Planned
ITIL
Model selected ITIL editions and practices as reusable vocabulary for service-management tools.
Addresses Pain points(2)
Supports Values(1)
Serves Use cases(1)
- Feature Planned
Catalogue update stream
Track source changes and provide reviewed, versioned updates for adopter-controlled upgrades.
Addresses Pain points(2)
Supports Values(1)
Serves Use cases(1)
Roadmap
Where Ontology is going.
Recorded version: v0.1. Historical release labels do not establish the current feature scope above.
- v1.0 Implemented Planned milestone: MVP/GA — HTTP, TOGAF, IT, ISO 25010, ISO 25012, and PROV complete & validated
- v1.x Partial Planned milestone: Remaining protocols (gRPC, GraphQL, Kafka, AMQP, JDBC, WebSocket) · GDPR · NIS2 · SCAP · DORA · SAFe · ITIL (unordered)
Implemented and Planned qualify the features in each milestone. Recorded releases and planned milestones preserve history, not delivery dates or hosted availability. See the Milestones & Versions register.
Usage
Use cases involving Ontology
- Use case Implemented
Describe a service contract and its attribution
Select sourced HTTP, IT-domain and provenance concepts for a service description, checking the meaning and attribution of each assertion. Vocabulary does not implement the service or prove its behavior.
Supported by Features(3)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Planned
Describe payment request and notification boundaries
Use sourced gRPC, GraphQL and WebSocket concepts to describe request, response and notification boundaries in a payment example. Application payment rules and delivery guarantees require separate definitions and evidence.
Supported by Features(3)
Addresses Pain points(1)
Performed by Actor types(2)
- Use case Planned
Describe payment settlement and recovery boundaries
Use sourced JDBC, Kafka and AMQP concepts to describe transaction and messaging boundaries in a settlement example, exposing the recovery assumptions that vocabulary alone cannot establish.
Supported by Features(3)
Addresses Pain points(1)
Performed by Actor types(2)
- 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.
Addresses Pain points(2)
Realizes Values(4)
Performed by Actor types(3)
- Use case Planned
Review a governance package upgrade
Compare revised financial-resilience, delivery and service-management source content with the selected package versions and identify obligations needing renewed adopter review. A source update does not itself change accepted obligations.
Supported by Features(4)
Addresses Pain points(2)
Realizes Values(1)
Performed by Actor types(3)