Doctrine · August 2026
Public is reference. Lattice is canon.
Two viral globes made the same point in different costumes. One rebuilt a government-looking news room from public RSS and local models. One made ADS-B, AIS, fires, and TLEs feel like a spy satellite. The replies that mattered were not “wow 3D.” They were: the visual layer is no longer a moat. The moat is data that never became public.
LYGO Public Witness takes the useful half of those ideas, a live Earth you can spin, labeled public layers, optional local Ollama, and refuses the dangerous half: treating a dashboard as intelligence it does not have. It still names the shadow. A private room that exists is not a blank. It is a reminder to legally check every public surface linked to it.
The rule
- Public nodes are resources. USGS, EONET, ISS, crunchable infrastructure.
- Private nodes are named shadows. We keep the silhouette and the why. Payload stays empty. We do not invent the interior.
- If a public feed is unreachable, the node stays on the map with its public URL, not a hole in the earth.
- Shadows exist so you remember to examine all honest angles: FOIA, contracts, public telemetry, published news, never intercepts.
- Dual ledgers, kernel eggs, Agora, and the Haven Star Chart feed are CANON on-lattice.
- This page never writes the live Star Chart. The write path is itself a named shadow.
How to use it
- Open chatagent.ca/witness/ (mirror: eternalhaven).
- Switch Earth / Lattice / Split. Every ping is tagged.
- If a source is down, the node stays named (shadow of that resource). Follow its public checks.
- Agents:
npx clawhub@latest install deepseekoracle/lygo-public-witnessthenpython scripts/self_check.py. - FULL unlocked copy: SkillHub, verify SHA-256 before unzip.
Support
Optional tip, not a paywall: PayPal.me/ExcavationPro · Patreon.
Related
Reference is not canon
Public feeds, weather, earthquakes, satellites, open data, are reference. They inform the work, but they do not become the project’s canonical record by being linked. The witness layer keeps that distinction visible: what was observed, when, and from where.
How to read a witness page
Start with the source and the timestamp. Then ask what changed and whether the page is showing an observation or an interpretation. A live number without a source is decoration. A source without a timestamp is a rumor with a logo.
What it is not
It is not a private intelligence feed, a prediction market, or a claim that a public source is the whole truth. It is a public notebook with links. If a claim matters, follow it to the canonical page and check the record.
A worked example
A public earthquake feed shows a magnitude at a time and place. The witness page links the feed and records the timestamp. The page does not claim the quake means anything; it claims the feed said so at that time. That separation is the whole method.
If a later page uses the quake as evidence for a theory, the theory needs its own argument. The witness is the receipt, not the conclusion.
Why it matters
When public data is treated as canon, the map starts to look like the territory. The witness layer keeps the difference visible, so a reader can check the source and disagree with the interpretation.
The habit
Before you repeat a public number, open the source and look at the timestamp. If the source is gone, say so. The habit is small and it is the difference between a witness and a rumor.
What the reader should do
Open the source, check the time, and decide whether the observation supports the claim. The witness page cannot make that decision for you; it can only keep the receipt.
The boundary
A public feed can inform a decision, but it cannot make one. The page that treats the feed as the decision has confused reference with canon.
One line
Reference informs; canon decides. Keep the receipt.