Harness Score
Establishes the baseline, evaluates frozen evidence, exposes confidence, and verifies improvement.
Score the system you have. Understand the evidence behind it. Improve it safely. Verify what changed.
Knowledge harnesses emerge from instructions, agents, tools, permissions, memory, generated projections, runtime state, and years of accumulated change.
File presence is not architecture. Documentation is not mechanism. Activity is not health.
Without evidence and dependency context, a confident score is theater—and a simple cleanup can become a migration incident.
Harness Score is the first user experience. Foundation, Trace, and Wires quietly establish the admissible evidence before any number appears.
harness review TARGET --output RUN_DIR produces a verified offline report. See the real synthetic run ↗Establishes the baseline, evaluates frozen evidence, exposes confidence, and verifies improvement.
Turns architecture, vitality, evidence, drift, and risk into navigable human views.
Creates baseline-bound impact and rollback plans. Mutation is deliberately unavailable in the alpha.
Defines schemas, standards, invariants, authority rules, and compatibility contracts.
Discovers artifacts, binds evidence, models vitality, compares history, and reports blind spots.
Resolves dependencies, lineage, data flow, coupling, and change-propagation paths.
Target content is untrusted data. Discovery never executes it.
Blind spots, budgets, and partial status remain visible.
Architecture, mechanism, vitality, and proof are not interchangeable.
The alpha stops at a baseline-bound plan and numbered approval record. It cannot mutate.
Install the three skills, run the synthetic fixture, and challenge the evidence: false-positive reports, adversarial fixtures, accessibility feedback, and clean-install witnesses are the highest-value contributions.