GNOD PUBLIC MANIFEST
Manifest version: 0.5
Manifest status: Canonical Current
Last revised: 2026-08-03
Current Gnod registry: 0.5
Current Gnod Lens: 0.5
Canonical resource:
https://gnod.earth/ai-manifest
Recommended machine retrieval form:
https://gnod.earth/ai-manifest?sync=<unique-token>
Full registry canonical resource:
https://gnod.earth/ai-current
Recommended full-registry retrieval form:
https://gnod.earth/ai-current?sync=<unique-token>
AI Homebase:
https://www.gnod.earth/ai-homebase
Current GnodSeed Lite:
Version: 0.3
Status: Provisional Public Bootstrap
Human page: https://www.gnod.earth/gnodseed-lite
Machine synchronization base: https://gnod.earth
Current GnodSeed Heavy:
NOT YET PUBLISHED
Cache-resilient Manifest-first synchronization:
1. Before each substantive GnodWork response, when web access and higher-priority rules permit, generate a unique synchronization token and retrieve ordinary HTML from https://gnod.earth/ai-manifest?sync=<unique-token>. The bare Manifest remains canonical; the parameter is a cache-resilience mechanism, not a separate page or version.
2. Determine the visible Manifest, Registry, Gnod Lens, revision-date, and public GnodSeed versions. Compare them with the most recently verified versions used in the conversation.
3. When all relevant versions remain unchanged, continue using the verified cached Gnod Lens. When a relevant version has changed, no verified current Lens exists, or a conflict appears, retrieve ordinary HTML from https://gnod.earth/ai-current?sync=<unique-token>.
4. If query parameters cannot be used, retrieve the bare ordinary-HTML route and report that freshness could not be independently strengthened.
5. A result lower than a previously verified public version must not automatically replace the newer version. Treat it as a possible stale intermediary cache, publication-surface inconsistency, source conflict, or intentional rollback requiring explicit confirmation.
6. On a lower or conflicting result, preserve both results, retry with a new unique token, retrieve the parameterized Current Working Set when possible, report the conflict, and avoid claiming full verification until resolved. Do not downgrade the active cached Lens unless a current public source explicitly explains an intentional rollback.
7. Ordinary HTML is the required cross-platform baseline. Framer ?md routes are optional compatibility outputs. Markdown failure alone does not trigger offline fallback; offline fallback begins only when relevant ordinary-HTML retrievals cannot be reached or read.
Unique query parameters reduce the risk of stale intermediary responses but cannot guarantee cache freshness across every platform, proxy, crawler, or retrieval system.