Features · Wherefore 0.11.0
Everything it does, and what's next.
Every feature in the release this site pins, tagged with the release it arrived in. When a release adds a feature, this site has to describe it before it can build. Every release, and what it printed
Scan since 0.3.0
Point it at your site or docs: it finds every value you state more than one way, and where the copies disagree.
wherefore scanStart a corpus since 0.1.0
One command starts a repository; the skill walks your agent through the first fact.
wherefore initThe gate since 0.1.0
On every push, each file must be built from the source, written by a person for a stated reason, or a capture stamped with what it shows. Anything else stops the change, and says why.
wherefore gateThe build since 0.1.0
Every asset rebuilt from the source, the same way every time, so you see exactly what a change moves.
wherefore buildWhat builds what since 0.7.0
A page for every repository: each file, how it is made, and what changes when a source does. One command draws it, and changes nothing.
wherefore graphProofs since 0.1.0
No check is trusted until it has failed: each proof plants the fault its check exists to catch.
wherefore proveRetired facts since 0.1.0
Retire an old price, name or limit once, and nothing a person reads may say it again.
wherefore check retiredReach since 0.1.0
Wherefore changes each fact, one at a time, and checks that everything stating it changes too.
wherefore check reachClaims since 0.1.0
Give a claim like “SOC 2 certified” a rule, and no page can say more than the rule allows.
wherefore check claimsDerived from elsewhere since 0.5.0
Copied something you can't pin, like a partner's spec sheet? The deploy fails the day its source changes.
wherefore check upstreamOne palette since 0.10.0 New in 0.10.0
Your brand lives in one file. Type a colour anywhere else and the build names the file and the line, unless the file says, with a reason, that the colour is somebody else's.
wherefore check paletteThe pre-push hook since 0.1.0
A push that would ship a stale document stops before it leaves your machine.
wherefore hook installThe skill, for Claude Code and Codex since 0.2.0
Claude Code or Codex learns the rules from a skill that ships with each release.
What's next
The open-source engine's roadmap, as its repository states it.
Docs from each release Next
The product's docs, compiled from the release they describe.
Launches that wait Later
A launch that holds until its page, docs and demo agree.
Drift, on the map Later
What the scan finds - a value stated in several places that no source holds - drawn on the map beside the files that say it, so what is not yet tracked is seen, and seen shrinking.
Your things, in one place Later #12
An app you log in to and see every repository you connected: what each builds, what is held, and what is drifting.