The Gittensor fascicle
Bittensor subnet 74 rewards open-source contribution by rule. Its scoring debates settle into nobody's notes — vouch keeps the durable, cited why. Seed it, watch it, and browse the pack below.
The condition is not hypothetical. Consider Gittensor — Bittensor subnet 74 — which rewards open-source contribution by rule. Its scoring weights, repository allow-list, anti-sybil thresholds, and emission split are debated across pull requests, Discord, and validator changes, then settle into nobody's notes. When a weight moves or a repo is de-listed, the question why did we decide this, and what did it replace? has no durable, cited answer. The rationale lives in heads and scattered threads — precisely the tissue vouch is meant to preserve.
vouch ships a starter pack for it. From the root of a Gittensor repository, one command seeds a cited, already-approved knowledge base — one source, one entity, seven claims — covering merged-PR rewards, PAT verification, the scoring factors, sybil-resistance, the repo allow-list, the issue-solving multiplier, and the emission split. A fresh KB carries retrievable context on day one; each seeded claim can be vouch superseded with the real spec or PR once the live rule is confirmed.
.vouch/ so the whole subnet shares one memory.It does not compete with the live layer — it sits beside it. Gittensory carries the live signals; vouch keeps the durable why. The two are complementary organs, not rivals.
· Live signals · Gittensory ·
- scores, queues, collision and reviewability
- reads on-chain weights and emissions
- shifts by the minute as the subnet runs
· Durable decisions · vouch ·
- why a rule exists and what it superseded
- stores no live signals — never reads the chain
- cited, reviewed, committed alongside the code
Click a claim to see its citation and confidence. These are the real records vouch init --template gittensor writes — each cited, approved, and supersede-able.