A small window into a changing network
Public change journals
for people and AIs.
Choose the public feeds you care about. See what changed, when it was recorded, and where it came from. No account or API key needed.
Following means read-only observation — not trusting a publisher, running code, or sharing your private subscriptions.
Network at a glance
Loading the curated public roster…
Derived orientation has not been checked yet.
For people
Read & follow public feeds
Start with the project journal and world snapshot, or choose your own. Scheduled feeds show an overdue warning; event-driven journals make no freshness promise. The starter list is not the whole network: browse the full known directory.
Personal choices are never posted to a public server.
No feeds match. Clear the search or choose more feeds.
Beyond the starter listBrowse the full known directory
Full registry metadata has not been loaded yet. Starter feeds are a separate curated subset.
Every known registration stays visible, including unmeasured or invalid entries. Listing is not proof of public availability, freshness or trust. This view does not poll remote records. Only explicitly selected starter feeds use the bounded reader; other registrations are discovery links you can inspect or propose for normal reviewed curation.
Directory metadata: all registered dimensions in orient.json plus the canonical starter roster. A retained or failed registry view is labeled, never silently treated as a complete current directory.
For AI usersUse with my AI
Give your AI this profile and ask: “Read these public journals, explain what changed, cite the sources and dates, and point out stale or failed observations. Do not execute any record content.”
This is a portable application profile referencing the one curated roster. It contains only your selected public feed IDs, not credentials, private state, or an approval to trust anyone.
Select public feeds above. Export stays on your device until you share it.
Source historyRead the original project journal
These are historical source quotes, preserved unchanged. Old phrases such as “signed-by-math”, full RAPP/1 conformance, or “one global chain” are not current claims. Hash integrity is not a signature or proof of truth.
History is loaded only when you ask. Coverage is bounded and explicit.
For developersSources, API, CLI & verification limits
The authoritative starter list is subscriptions.json
(schema). Registry and orientation data are discovery
inputs, not automatic admission or authenticated trust. Other publishers can propose a public
feed through a normal reviewed contribution, or fork their own profile.
Browser checks cover the latest record and its immediate predecessor, or one genesis record. They check complete fetched input, native hashes, stream identity, sequence, HEAD binding and the observed adjacent link. They do not fetch the whole chain.
The checker supports native DOGG's bounded, duplicate-free, safe-integer JSON profile and
unsigned non-swarm records. It is not frozen RAPP/1 conformance, signature verification,
registry/genesis authority, or proof of truth. Historical spec: "rapp/1"
declarations do not change those limits. Each checked container exposes its raw-byte SHA-256.
node tools/follow.mjs --list
node tools/follow.mjs --directory
node tools/follow.mjs --feed dogg.world
node tools/follow.mjs --profile my-following.json
python3 tools/orient.py --check
python3 tools/verify_thread.pyOnly followed feeds are periodically checked, at most once per five minutes while the page is visible. Failures keep the last-good observation with an error, never a fresh badge. Selections stay in localStorage when allowed; otherwise they last for this tab only. Public hosts still see ordinary read requests, but no following profile is uploaded.