Testing OS — on npm

testing-os proves it ships.

Centralized dogfood evidence system. 13 active repos (14 governed — the 14th, `dogfood-labs`, is the archived legacy repo retained for historical evidence), 8 surfaces, all currently-tracked active repos: last verdict = pass, all enforcement required. Single canonical schema validator across every consumer (one Ajv instance per schema per process; workspace-hoist split is a hard gate). Structured top-level errors with stable codes and a `Next:` hint on every failure path. See the [CHANGELOG](https://github.com/dogfood-lab/testing-os/blob/main/CHANGELOG.md) for the current release entry.

How it works Read the Handbook

Install

npm install -g @dogfood-lab/dogfood-swarm

Verify

npm run verify

Recover

swarm revalidate <run-id> --reason "<text>" --domain=<name>:<corrected.json> --apply

What It Does

Auditable dogfood governance for the entire org.

Evidence-Based

Every dogfood run produces a structured record with schema validation, provenance checks, and policy compliance.

Policy-Driven

Per-repo enforcement tiers (required, warn-only, exempt) with promotion paths and review dates.

Full Coverage

13 active repos across 8 product surfaces: CLI, desktop, web, API, MCP server, npm package, plugin, library. (The 14th governed entry, `dogfood-labs`, is the archived legacy repo retained for historical evidence.)

Architecture

Seven Contracts

# Foundational three
# Record — what a dogfood run looks like
# Scenario — what constitutes real exercise
# Policy — what rules the verifier enforces

# Intelligence layer four
# Finding — a single learning from a run
# Pattern — a reusable shape across findings
# Recommendation — a candidate action derived from patterns
# Doctrine — accepted recommendation, binding across the org

# See: handbook/contracts/ for the full canonical model

Data Flow

Source repo → repository_dispatch
  → Central verifier (schema + provenance + policy)
  → Accepted record → records///
  → Rebuilt indexes → latest-by-repo.json

Consumers

shipcheck   → Gate F enforcement
repo-knowledge → SQLite mirror
org audit   → Portfolio consumer