Each membrane, its detector, and its honest reading
For every membrane: what crosses it, the instrument that watches it, and — for the built ones — what a positive and a negative actually mean. Built instruments are self-testable with no network; each links its live page and its code.
One rule holds across every membrane
A positive is a lead; a negative means almost nothing. A marker only you planted, crossing a membrane it could only cross by the route you claim — with, for the membership detectors (surfacing, hearsay), a held-out control arm proving the harness doesn't fabricate; and, for the published membrane, an index hit that is ground truth by construction — that is hard to explain away. But silence is cheap: pages you never crawl, weights that suppress, relays you never see. Every instrument here says "lead," never "proof," and hands the weight of any silence to the silence-gauge, which shows just how little a negative carries. The map earns trust the same way each instrument does — by naming what it cannot see.
membranes.json (the registry) · validate.py (checks the map claims no coverage it doesn't have). The family: forward-observers · surfacing · hearsay · silence-gauge.