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:5ad8877bcc81bc7417050a722b1d8737788d45595ba9f01449eb0f16bc4b5b2c

Object SHA-256

5ad8877bcc81bc7417050a722b1d8737788d45595ba9f01449eb0f16bc4b5b2c

identity_check=PASS

02 / PAYLOAD

Declared object state.

{
  "route": "/models",
  "label": "Models Used",
  "role": "model-lane-and-runtime-boundaries",
  "claim": "MODEL_INVOLVEMENT_AND_CLAIM_BOUNDARY_DOCUMENTATION",
  "project": "HydraDG",
  "evidence_class": "DETERMINISTIC_APPLICATION_METADATA",
  "custody_state": "HASHED",
  "signature_state": "NOT_SIGNED",
  "claim_ceiling": "MODEL_INVOLVEMENT_AND_CLAIM_BOUNDARY_DOCUMENTATION",
  "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.