Make technical documentation testable.
See cited contradictions across ADRs, runbooks, API contracts, and agent instructions— checked against the technical sources your team has approved.
Your docs PR should fail when it contradicts an approved ADR or production runbook.
Additive to your existing repository, wiki, tracker, and developer portal. Start with one bounded corpus—no platform migration required for the first audit.
The operational problem
Code changes quickly. Shared technical truth does not keep up.
Search can retrieve a document. It cannot tell an engineer whether that document still agrees with the architecture decision, the API contract, and the runbook the on-call team will trust at 03:00.
During normal development
An ADR changes. The service guide, runbook, onboarding page, and agent instructions do not.
During an incident
The runbook looks authoritative, but its recovery path describes last quarter’s architecture.
When agents enter the loop
A coding agent reads contradictory context as truth and propagates the wrong assumption at machine speed.
The old docs problem wasted time. Agent-readable drift can multiply the wrong decision.
The core
Git discipline for the knowledge your systems depend on.
Cited technical answers
Ask the approved corpus and open the exact supporting source. When approved documents disagree, the disagreement stays visible.
Contradiction and drift audits
Surface conflicts across ADRs, runbooks, API contracts, service docs, and agent-readable instructions—with the evidence behind each finding.
Governed change
Route proposed edits—human or agent—through reviewable, revertible ChangeSets. Nothing is silently written to a governed file.
Product proof
The Systems surface is real—and built for technical work.
A capture from the running Systems product on its Harbor Desk demonstration corpus, not a marketing reconstruction.
How a check reads
Cited or silent. Proposed, never smuggled in.
Human and agent answers resolve to the same approved context. A conflict is surfaced with its evidence; a proposed change enters review rather than writing to a governed file.
Git-host and CI integration is scoped with each design partner—not presented as universal plug-and-play.
$ docs-check proposed-change.md
CONFLICT · production/runbooks/catalog.md:42
Approved ADR requires edge caching for catalog reads.
Proposed change disables caching for the same endpoint.
Review required · no governed file changed
Illustrative rendering of the evidence contract.
Early access
Start with the drift. Prove the workflow.
Systems is in early access with design partners. Pilots are by application and credit in full toward the annual license. When the workflow proves out, Systems is priced by the engineers who govern documentation—$39 per dev seat per month, with reviewers free. Enterprise and self-hosted deployments are scoped separately.
Somewhere in your docs, two approved statements disagree.
The pilot's drift audit is the fastest way to find out where—and whether continuous checks are worth adding to the workflow.