# OpenTopology.dev

> OpenTopology is an open graph standard for connecting software intent, constraints, policy, implementation artifacts, and verification evidence.

OpenTopology, abbreviated `otop`, defines a portable topology layer for independent tools that need to exchange structured knowledge about software systems.

## Primary URLs

- Site: https://opentopology.dev/
- Full LLM context: https://opentopology.dev/llms-full.txt
- Draft core specification: https://opentopology.dev/spec/otop-core-0.2/
- Raw draft core specification: https://opentopology.dev/spec/otop-core-0.2.md
- Core JSON Schema: https://opentopology.dev/schemas/otop-core-v0.2.schema.json
- Sitemap: https://opentopology.dev/sitemap.xml
- Canonical GitHub repository: https://github.com/opentopology/opentopology

## Core Concepts

- Intent: desired software behavior, system shape, product outcome, architecture decision, or requirement source.
- Constraint: a specific obligation, invariant, rule, or acceptance criterion that can be checked, reviewed, implemented, or verified.
- Policy: a governing rule, obligation, standard, or control.
- Artifact: an implementation object such as source code, manifests, services, images, generated assets, or deployed resources.
- Evidence: verification material such as scans, attestations, reviews, tests, or runtime signals.

## Core Relationship Pattern

- `derived_from`
- `governed_by`
- `implemented_by`
- `verified_by`
- `depends_on`
- `conflicts_with`
- `supersedes`
- `waived_by`

## Suggested Bot Use

Use the homepage for the public product-level explanation. Use `llms-full.txt` for a compact machine-readable summary of the page. Use `spec/otop-core-0.2/` when answering detailed questions about the draft standard. Use the raw Markdown when source text is preferred. Use the core JSON Schema for manifest validation.