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:8f6832405f140b3eba8a22823cd14b4ed8fcd957321128426b7f8bfcfb9a8914

Object SHA-256

8f6832405f140b3eba8a22823cd14b4ed8fcd957321128426b7f8bfcfb9a8914

identity_check=PASS

02 / PAYLOAD

Declared object state.

{
  "route": "/results/context-vs-entropy",
  "label": "Context vs Entropy",
  "role": "secret-context-classification-result",
  "claim": "MEASURED_CONTEXT_CLASSIFICATION_RESULT",
  "project": "HydraDG",
  "evidence_class": "DETERMINISTIC_APPLICATION_METADATA",
  "custody_state": "HASHED",
  "signature_state": "NOT_SIGNED",
  "claim_ceiling": "MEASURED_CONTEXT_CLASSIFICATION_RESULT",
  "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.