GOLDEN PATH

FCO inspector · content-addressed application object

SiteSection

One canonical FCO → one canonical SHA-256 identity. Follow FCG edges to reconstruct dependencies without treating identity as correctness.

HASH IDENTITY PASSIDENTITY ≠ CORRECTNESS
01 / IDENTITY

The content hash is the canonical address.

FCO ID

fco:e1c85d3b83fca52867b7d1348f2466e471b876dae8128892b51ba7a77c4e2bad

Object SHA-256

e1c85d3b83fca52867b7d1348f2466e471b876dae8128892b51ba7a77c4e2bad

identity_check=PASS

02 / PAYLOAD

Declared object state.

{
  "route": "/submission",
  "label": "Submission",
  "role": "immersive-commons-submission-hero",
  "claim": "SUBMISSION_HERO_NAVIGATION_AND_CUSTODY_RECEIPT_ONLY",
  "project": "HydraDG",
  "evidence_class": "DETERMINISTIC_APPLICATION_METADATA",
  "custody_state": "HASHED",
  "signature_state": "NOT_SIGNED",
  "claim_ceiling": "SUBMISSION_HERO_NAVIGATION_AND_CUSTODY_RECEIPT_ONLY",
  "hackathon_authorship_window": "2026-08-12_OR_LATER_REQUIRED"
}
03 / FCG EDGES

Follow the dependency route.

04 / NAVIGATION

Resolve the object in context.

The canonical hosted FCG has a separate readback/parity receipt. Website FCOs are deterministic application objects. Signature state and Merkle commitment remain separate from hashing and are not implied here.