logicsrc/packages/schemas/schemas/logicsrc-opencontext-diagnostic.schema.json
Anthony Ettinger 3ab8a4b38b
Add the LogicSRC OpenContext specification (#132)
* Add the LogicSRC OpenContext specification

OpenContext is an open specification for durable, portable, permissioned,
provenance-aware context shared between humans and AI agents. It defines how
organizational knowledge is described, authorized, versioned, resolved,
audited, and handed between replaceable workers without losing institutional
state.

Follows the OpenPRD/OpenOntology pattern already in the repo: self-contained
JSON Schemas in @logicsrc/schemas, a reference implementation package, CLI
subcommands, docs, examples, and an OpenPRD record.

Schemas (8, all self-contained so a third party can fetch one file and
validate against it with no further resolution):
  manifest, object, bundle, role, provenance, decision, diagnostic,
  audit-event — registered in @logicsrc/validators and schemas:validate.

Reference implementation (@logicsrc/opencontext):
  loader with upward manifest discovery, the full resolution pipeline,
  authority/supersession, permissions, redaction, lifecycle, provenance,
  deterministic digests, doctor, search, graph, history/diff, guarded writes,
  audit events, and file/http/git/sqlite adapters.

CLI: all 15 specified commands, as a standalone `opencontext` binary and as
`logicsrc context`, sharing one implementation so the two cannot drift.

Design decisions worth noting:

- Supersession is declared, never inferred from version numbers. Inferring it
  would hide the governance failure it represents and make
  multiple-active-versions and duplicate-canonical impossible to detect.

- The bundle digest identifies the resolved context, not the moment it was
  computed, so generated_at/bundle_id/digest/as_of are excluded while objects,
  lifecycle states, exclusions and warnings are covered. That is what lets a
  decision record cite exactly the context that produced it.

- A role's own max_classification beats an inherited one, so a ceiling on a
  shared base role cannot silently cap a role deliberately granted more;
  requesting several roles at once still takes the lowest, so combining roles
  never escalates.

- Scope wildcards match whole dotted segments only. A trailing .* covers a
  subtree; an interior * matches exactly one segment. Substring matching here
  would be an access-control bug.

- --include narrows an existing scope and is applied after it, never merged
  into it, so a request can never widen what a role holds.

Verified: 226 tests across core primitives, permissions/redaction, the
resolution pipeline, security, the published conformance fixtures (13 valid,
35 invalid, 8 resolution scenarios), project behaviour, and the five shipped
examples — which are held to --strict and a 100% health score. Benchmarks meet
every published budget (resolve 1,000 objects in ~33ms against a 2s target).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Point install docs at @logicsrc/opencontext; record the npm name collision

The unscoped `opencontext` name is already published on npm by an unrelated
third party (federicodeponte/opencontext, 2.0.0), so `npx opencontext` would
install a stranger's package. Docs now use `npx @logicsrc/opencontext`; the bin
stays named `opencontext` so the command reads as the PRD specifies once
installed.

Recorded in PRD 0003 as a blocker to resolve before any publication, along with
the fact that no @logicsrc spec package has ever been published, so there is no
existing release path to slot into.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Advance the logicsrc-mcp next-PRD-id assertion to 0004

standards.test.ts asserts prd_next_id against the live prd/ directory, so
adding PRD 0003 makes the next free id 0004. The test's own comment
anticipates this: "advances with every PRD added".

Caught by CI, not locally — the earlier verification ran per-package tests for
the packages this branch touches, and logicsrc-mcp is coupled to the PRD
directory without importing from it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-09 11:46:11 -07:00

123 lines
5.5 KiB
JSON

{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://logicsrc.com/schemas/opencontext/diagnostic.schema.json",
"title": "OpenContext Diagnostic Report",
"description": "The machine-readable output of `opencontext validate` and `opencontext doctor`: every finding, where it came from, how bad it is, and the resulting health score. Diagnostics are the contract CI depends on, so the codes are normative and stable — a pipeline that fails on duplicate-canonical must keep failing on it across implementations and versions.",
"type": "object",
"required": ["opencontext", "ok", "findings"],
"additionalProperties": false,
"properties": {
"opencontext": { "type": "string", "pattern": "^\\d+\\.\\d+(\\.\\d+)?$" },
"ok": {
"type": "boolean",
"description": "True when no finding meets or exceeds the configured failure severity. This is what the exit code follows."
},
"generated_at": { "type": "string", "format": "date-time" },
"namespace": { "type": "string", "pattern": "^[a-z0-9][a-z0-9-]*$" },
"score": {
"type": "number",
"minimum": 0,
"maximum": 100,
"description": "Context health, 0-100. Computed as 100 minus the sum of weight x affected objects for each finding, normalised by the object count and clamped at 0. The weights are documented and configurable, so a score is comparable only within a repository's own configuration."
},
"counts": {
"type": "object",
"additionalProperties": false,
"description": "Roll-up used by the human-readable report.",
"properties": {
"objects": { "type": "integer", "minimum": 0 },
"errors": { "type": "integer", "minimum": 0 },
"warnings": { "type": "integer", "minimum": 0 },
"info": { "type": "integer", "minimum": 0 },
"stale": { "type": "integer", "minimum": 0 },
"expired": { "type": "integer", "minimum": 0 },
"conflicting": { "type": "integer", "minimum": 0 },
"orphaned": { "type": "integer", "minimum": 0 },
"missing_owner": { "type": "integer", "minimum": 0 },
"broken_sources": { "type": "integer", "minimum": 0 }
}
},
"findings": {
"type": "array",
"description": "Every finding, ordered most severe first, then by code, then by object id, so two runs over the same repository produce byte-identical reports.",
"items": { "$ref": "#/$defs/finding" }
},
"extensions": {
"type": "object",
"propertyNames": { "type": "string", "pattern": "^[a-z0-9]+(\\.[a-z0-9-]+)+$" },
"additionalProperties": true
}
},
"$defs": {
"severity": {
"type": "string",
"enum": ["info", "warning", "error"],
"description": "error breaks the contract and fails a strict run; warning is context rot that needs attention but still resolves; info is advisory."
},
"finding": {
"type": "object",
"required": ["code", "severity", "message"],
"additionalProperties": false,
"properties": {
"code": {
"type": "string",
"enum": [
"schema-invalid",
"manifest-invalid",
"duplicate-id",
"duplicate-canonical",
"unknown-authority",
"conflict-declared",
"conflict-ambiguous",
"broken-supersession",
"supersession-cycle",
"multiple-active-versions",
"broken-reference",
"orphaned",
"missing-owner",
"missing-provenance",
"missing-digest",
"stale",
"expired",
"not-yet-valid",
"review-overdue",
"unapproved",
"unknown-scheme",
"source-unavailable",
"path-traversal",
"invalid-permission",
"unknown-role",
"role-cycle",
"empty-scope",
"secret-detected",
"untrusted-canonical",
"unknown-extension"
],
"description": "Stable diagnostic code. duplicate-canonical, conflict-ambiguous, and broken-supersession are the checks that keep the resolver from quietly guessing; secret-detected and path-traversal are security checks; unknown-extension is only ever raised in strict mode."
},
"severity": { "$ref": "#/$defs/severity" },
"message": {
"type": "string",
"minLength": 1,
"description": "What is wrong, in a sentence an author can act on."
},
"id": { "type": "string", "description": "Context object id the finding concerns." },
"ids": {
"type": "array",
"items": { "type": "string" },
"description": "Every object involved, when a finding is about a relationship rather than one object — the two canonical policies that collide, or the chain that broke."
},
"file": { "type": "string", "description": "Path the object was loaded from, relative to the manifest." },
"line": { "type": "integer", "minimum": 1, "description": "1-indexed line, when the source format carries positions." },
"column": { "type": "integer", "minimum": 1 },
"field": { "type": "string", "description": "Dotted path of the offending field, e.g. permissions.read." },
"expected": { "description": "What the field should have been." },
"actual": { "description": "What it was." },
"remediation": {
"type": "string",
"description": "The concrete next action, e.g. 'Add owner: support, or set health.require_owner: false'."
}
}
}
}
}