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>
This commit is contained in:
Anthony Ettinger 2026-08-09 11:46:11 -07:00 committed by GitHub
parent 1bb7ba6e60
commit 3ab8a4b38b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
212 changed files with 17249 additions and 7 deletions

View file

@ -0,0 +1,16 @@
# Startup
A young company with products, pricing, procedures, and decisions — every layer
from L0 mission to L5 decisions.
```bash
opencontext validate --strict
opencontext doctor
opencontext resolve --agent sales-agent --task "quote 20 lanes for a new customer" --explain
opencontext resolve --agent dev-agent --explain
```
The two agents share one repository and receive different context. The sales
agent gets pricing and the quoting SOP; the dev agent gets decisions and never
sees the pricing policy.

View file

@ -0,0 +1,19 @@
---
id: brand
type: identity
layer: L1
title: How Northwind sounds
authority: canonical
owner: founders
durability: long-lived
classification: internal
canonical_source: true
updated: 2026-08-01T00:00:00Z
applies_to: [sales-agent, support]
---
Plain, specific, and never breathless. We say what a thing costs and what it
does not do.
- Say "shipments arrive late sometimes" rather than "industry-leading reliability".
- Never invent a number. If you do not know the figure, say so.

View file

@ -0,0 +1,30 @@
---
id: decisions.2026-08-01-usage-based-pricing
type: decision
layer: L5
title: Keep seat-free pricing
authority: approved
owner: founders
status: accepted
durability: long-lived
classification: internal
canonical_source: true
created: 2026-08-01T00:00:00Z
updated: 2026-08-01T00:00:00Z
decision: Price on lanes, never on seats or agent count.
rationale:
- Customers are adding agents faster than people; per-seat pricing would tax that.
- Lane count is the number customers already budget against.
alternatives:
- option: Per-seat pricing
rejected_because: Penalises exactly the automation we are selling.
consequences:
- Revenue does not grow when a customer adds agents; it grows when they ship more.
approved_by:
- role: founders
references: [policies.pricing]
tags: [pricing, governance]
---
Recorded so the next person to propose per-seat pricing can read why it was
already declined, rather than relitigating it from scratch.

View file

@ -0,0 +1,16 @@
---
id: glossary
type: glossary
layer: L1
title: Terminology
authority: canonical
owner: founders
durability: long-lived
classification: internal
canonical_source: true
updated: 2026-08-01T00:00:00Z
---
- **Lane** — an origin/destination pair we quote on.
- **Tender** — an offer of a shipment to a carrier.
- **Seat** — one human user. Agents do not consume seats.

View file

@ -0,0 +1,15 @@
---
id: mission
type: mission
layer: L0
title: Why Northwind exists
authority: canonical
owner: founders
durability: permanent
classification: public
canonical_source: true
updated: 2026-08-01T00:00:00Z
---
Small teams should be able to run serious logistics without hiring a
logistics department.

View file

@ -0,0 +1,24 @@
---
id: policies.pricing
type: policy
layer: L3
title: Pricing
authority: canonical
owner: finance
status: approved
version: 1
durability: long-lived
classification: internal
canonical_source: true
updated: 2026-08-01T00:00:00Z
tags: [pricing]
applies_to: [go-to-market]
review:
interval: 90d
next_review: 2027-01-01
---
Freight starts at $2,500/month for 10 lanes. Additional lanes are $120 each.
Discounts above 15% require finance approval. An agent may quote list price
and standard discounts; it may not invent a new pricing structure.

View file

@ -0,0 +1,18 @@
---
id: products.freight
type: product
layer: L2
title: Northwind Freight
authority: canonical
owner: product
durability: long-lived
classification: internal
canonical_source: true
updated: 2026-08-01T00:00:00Z
tags: [product, freight]
---
Books and tracks full-truckload shipments across 40 lanes.
Not a warehouse management system, and not a customs broker. Agents should
decline both requests rather than improvise.

View file

@ -0,0 +1,20 @@
---
id: procedures.quote
type: procedure
layer: L4
title: How to produce a quote
authority: approved
owner: sales
status: approved
durability: operational
classification: internal
canonical_source: true
updated: 2026-08-01T00:00:00Z
references: [policies.pricing, products.freight]
applies_to: [go-to-market]
---
1. Confirm the lane count and the contract length.
2. Apply list pricing from `policies.pricing`.
3. If the customer asks for more than 15% off, stop and escalate to finance.
4. Record the quote against the account before sending it.

View file

@ -0,0 +1,57 @@
# A young company with real products, real customers, and two roles that
# need different things. Shows every layer, L0 through L5.
opencontext: "1.0"
id: northwind
name: Northwind
context:
mission: ./context/mission.md
brand: ./context/brand.md
glossary: ./context/glossary.md
collections:
products: ./context/products/**
policies: ./context/policies/**
procedures: ./context/sops/**
decisions: ./context/decisions/**
roles:
everyone:
include:
- mission
- brand
- glossary
go-to-market:
inherits: [everyone]
include:
- products.*
- policies.pricing
- procedures.*
permissions:
- quote.create
builders:
inherits: [everyone]
include:
- products.*
- decisions.*
permissions:
- repo.write
agents:
sales-agent:
roles: [go-to-market]
dev-agent:
roles: [builders]
freshness:
default_ttl: 180d
provenance:
required: true
review:
interval: 180d
health:
minimum_score: 90
require_owner: true