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:6ccbc44eb8216433659cc524f0a25c11c20cc57ffb97743772b1c8a66a47ff45

Object SHA-256

6ccbc44eb8216433659cc524f0a25c11c20cc57ffb97743772b1c8a66a47ff45

identity_check=PASS

02 / PAYLOAD

Declared object state.

{
  "route": "/knowledge",
  "label": "Knowledge",
  "role": "terminology-and-how-to",
  "claim": "DOCUMENTATION_AND_SOURCE_NAVIGATION",
  "project": "HydraDG",
  "evidence_class": "DETERMINISTIC_APPLICATION_METADATA",
  "custody_state": "HASHED",
  "signature_state": "NOT_SIGNED",
  "claim_ceiling": "DOCUMENTATION_AND_SOURCE_NAVIGATION",
  "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.