The Grant And Mandate Repo Ships Probes Rather Than Tables: A Grant Claim Travels With The Command That Establishes It
Summary
A specification for a public registry of capability primitives and measured grants, whose one design decision is that a grant claim never travels alone: it travels with the probe that established it, so a challenge is a rerun with a different result rather than two people asserting different tables. The primitive is a verb crossed with an object class crossed with a reach, held at a stated altitude and carrying whether its effect is reversible; a specific path is an instance, never a new primitive. The unit of mapping is a tool, not a product, because two tools in one session reached different hosts. Grants are public and contributed; mandates are elicited locally through questions about work and never leave the clone. An incident is evidence that demotes a control's claimed evidence mode. A code host rather than a vault, because vaults publish read keys and never write keys. Built here as /probes/: the registry, the finding shape, the runner, seven profiles (two measured), three evidence files.
Key concepts
- Probes, not tables — the registry, built
- The capability primitive — verb × object × reach + reversible
- Grants public, mandates private — the adoption argument, on the page
- Incidents — evidence that demotes
- The precedents — which corrected this brief's vocabulary the same day
Key ideas
- The unit of contribution is a probe, so a disagreement resolves or it localises.
- Reversibility sits on the primitive, because it decides whether a gap is a nuisance or a loss.
- A profile is a named configuration listing its tools; web, local and confirmations-disabled are siblings whose diff is the answer.
- Nothing about your estate leaves your clone: the delta is computed locally from a public grant and a private mandate.
- An incident demotes a control, which is how the registry gets more honest over time rather than more confident.
- Value must arrive at the moment a profile is named, before the user has written anything.
- Call them capability primitives wherever meters could be meant.
On this site
Adds /probes/ (primitives.json, probes.json, run.py, three schemas, seven profiles, three evidence files, incidents, reductions, the questionnaire template, yours/ and submissions/), admin/build/gen_probes.py with its gates, and the bench entry.