otop-core 0.2.0 / draft

Make software intent verifiable.

OpenTopology is a portable topology layer that connects intent, constraints, policy, implementation, and evidence across the software lifecycle.

The OpenTopology Model
The OpenTopology ModelA common model for connecting software intent, rules, implementation and proof.ConstraintThe query pointIntentDesired behaviourPolicyGoverning ruleArtifactImplementationEvidenceVerificationderived fromgoverned byimplemented byverified by

Software teams already have intent, policies, artifacts, and evidence. They just live in different tools.

OpenTopology gives them a shared graph, so independent tools can exchange structured knowledge about what software is meant to do, which constraints express it, what governs it, where it is implemented, and what proves it.

Intent

Declare what software is meant to do.

Use it toModel desired behavior before it becomes implementation detail.

Constraint

Turn intent into a specific obligation.

Use it toMake rules checkable, governable, implementable, and verifiable.

Policy

Describe what governs it.

Use it toAttach controls, obligations, and standards to the graph.

Artifact

Connect intent to implementation.

Use it toTrace services, manifests, images, and generated assets.

Evidence

Prove what is true.

Use it toLink scans, attestations, reviews, and runtime signals.

  • derived_fromcanonical
  • governed_bycanonical
  • implemented_bycanonical
  • verified_bycanonical
  • depends_onlifecycle
  • conflicts_withgovernance
  • supersedeslifecycle
  • waived_bygovernance

Designed for tools, not slides.

OpenTopology gives scanners, policy engines, CI systems, documentation generators, and agentic workflows a common graph of software intent, constraints, and evidence.

For standards

A portable model of intent, constraints, policy, implementation, and evidence.

For tools

A graph shape that independent tools can exchange and validate.

For agents

A queryable map of what exists, what governs it, and what proves it.