Poesis
Portability & sovereignty
Local, self-hosted and hosted routes each carry their own acceptance boundary.
- Quality Implemented
Model independence
Governance does not depend on one provider
Model profiles support selection for bounded tasks. Each host mapping and model change needs compatibility and quality checks.
Borne by Organization Intelligence Platform(1)
- Quality Implemented
Local and sovereign execution
Define the data boundary explicitly
Local execution supports control, but models, tools, telemetry, remotes and backups can transmit data. Egress and retention policies remain necessary.
Borne by Organization Intelligence Platform(1)
- Quality Implemented
Cloud where appropriate
Managed infrastructure without ceding control
Deploy services through managed infrastructure where it makes sense, while the control boundary stays explicit rather than assumed.
Borne by Organization Intelligence Platform(1)
- Quality Implemented
Vendor-neutral standard
Governance you can inspect, not a black box
GSM is a candidate common Definition model. Interchange requirements support inspectability; compatible consumers and draft-preserving migration still need acceptance.
Borne by Organization Intelligence Platform(1)
- Quality Implemented
Open and inspectable
Trust cannot be proprietary
GSM specification content exists in source, with publication pending. SAF local tools use Apache-2.0; SIE and the planned bridge have separate licenses. Inspect each product and its terms.
Borne by Organization Intelligence Platform(1)
- Quality Partial
Runs where you work
No delivery-plane tenancy to adopt
The harness and workspace operate on local checkouts under Apache-2.0. Hosts and model routes are declared rather than assumed.
Borne by Solutions(1)
Interoperability
Governed THINK connects to the BUILD and RUN environments you already operate.
- Quality Planned
Git repositories
Planned candidates from pinned revisions
Supported analysis is planned to produce reviewable candidates. Acquisition, conflict reduction and governed registration are distinct steps.
Borne by Organization Intelligence Platform(1)
- Quality Planned
API contracts
The interaction surface of your estate
Planned adapters describe declared interaction surfaces with explicit coverage. Contracts alone do not prove actual traffic or applicable obligations.
Borne by Organization Intelligence Platform(1)
- Quality Planned
SBOMs
Planned dependency evidence
SBOM analysis identifies declared dependencies in a supported scope. Presence does not prove deployed use, reachability or compliance.
Borne by Organization Intelligence Platform(1)
- Quality Planned
Infrastructure
Separate intent from observations
Planned infrastructure sourcing reads declared configuration. Deployed identity, observation time and coverage are needed to describe what runs.
Borne by Organization Intelligence Platform(1)
- Quality Partial
Named conformance profiles
Conformance is stated against a profile
Definition interchange is scoped to a declared profile. A processor conforms to profiles it names, not to the model as a whole.
Borne by Products(1)
- Quality Planned
Testable requirements
Requirements are meant to be executed
Interchange requirements are written to be testable. A conformance suite and compatible consumers still need acceptance.
Borne by Products(1)
Governability
Who decided what, on which revision, and what the decision does not assert.
- Quality Planned
Accepted intent
What the organization has agreed
Reviewed definitions carry the authority of an accepted decision. Acceptance records intent; it does not assert that the estate already matches it.
Borne by Solutions(1)
- Quality Planned
Inspected revision
What a pinned source says
Sourced candidates stay bound to the revision they were read from. A source revision is not deployed reality and is reconciled before registration.
Borne by Solutions(1)
- Quality Planned
Observed deployment
What was seen running, and when
Deployed observations need an identity, an observation time and a stated coverage. Absent observations are reported as unknown rather than compliant.
Borne by Solutions(1)
- Quality Planned
Human-gated advancement
Agents propose; people advance
Workflow advancement passes through explicit gates. Authenticated gates and effect safety need acceptance before autonomous progression is claimed.
Borne by Solutions(1)
- Quality Partial
Revision-bound decisions
A decision names the revision it was made on
Transition controls bind a decision to the revision it reviewed, so a stale write is refused rather than silently applied.
Borne by Products(1)
Determinism
Reproducible outcomes from pinned inputs, so probabilistic work never becomes the authority.
- Quality Partial
Pure verdicts
The same inputs give the same verdict
Norm evaluation is scoped and side-effect free. Rule and input versions are part of the verdict; continuous operation additionally needs observations and scheduling.
Borne by Solutions(1)
- Quality Partial
Bounded execution
Mechanisms run inside a declared sandbox
Mechanism execution is confined to a declared protocol surface. Effect safety and authorized action remain acceptance boundaries.
Borne by Solutions(1)
- Quality Planned
Explicit unknowns
Missing evidence is a result, not a pass
Applicability, freshness and unknown states are first-class outcomes. An unevaluated obligation is never reported as satisfied.
Borne by Solutions(1)
- Quality Partial
Contracted artifacts
Written artifacts are checked against a schema
Mediated writes are validated against matched schemas. Scope is structured data and Markdown metadata; prose quality has a separate boundary.
Borne by Solutions(1)
- Quality Partial
Qualified model routes
Ranking alone does not establish suitability
Model profiles are selected by task capability and configured cost ranking. Routes are qualified using retained workload-specific quality, cost and disclosure evidence.
Borne by Products(1)
Isolation
Every read, write and disclosure resolves inside a declared boundary.
- Quality Partial
Tenant-scoped storage
Definitions never leave their tenant schema
Retained snapshots and queries resolve within a tenant boundary. Tenant/object authorization across the full API surface is being completed.
Borne by Products(1)
- Quality Partial
Authenticated by default
Only declared endpoints are public
The authenticated shell exists; health and info endpoints are the declared exceptions. Permissive local behavior stays profile-gated.
Borne by Products(1)
- Quality Planned
Role and attribute access
Role and attribute both bound the request
Planned enforcement combines role grants with object attributes. External identity synchronization is a separate, recoverable concern.
Borne by Products(1)
- Quality Planned
Disclosure limits
What a route may be told is bounded
Instruction delivery and disclosure limits are evaluated per workload. A host change is a change of behavior, not a configuration detail.
Borne by Products(1)
Openness
Definitions, provenance and terms can be inspected rather than taken on trust.
- Quality Partial
Model-native taxonomy
Each framework keeps its own structure
TOGAF, ISO 25000, GDPR, NIS2 and protocol vocabularies are sourced under their own taxonomies. Composition happens through Directives, not schema cross-references.
Borne by Solutions(1)
- Quality Partial
Cited provenance
Every sourced statement names its clause
Sourced Directives and Norms cite the section they derive from. Citation supports review; it does not establish legal completeness.
Borne by Solutions(1)
- Quality Partial
Stable identity
Published identifiers are not rewritten
Archetype identifiers are logical and versioned. Content exists in source; publication, neutral stewardship and processor conformance are separate steps.
Borne by Solutions(1)