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:b73d8f182a68ce94910df14e83b2f217b1b54a323b7db3fdc6fb7671792ccf31

Object SHA-256

b73d8f182a68ce94910df14e83b2f217b1b54a323b7db3fdc6fb7671792ccf31

identity_check=PASS

02 / PAYLOAD

Declared object state.

{
  "route": "/best-use",
  "label": "Best Use of HydraDB",
  "role": "graph-native-use-case-scale-economics-and-deterministic-accounting",
  "claim": "DEDUP_ACCOUNTING_K_DEPTH_AND_HYDRADB_USE_CASE_WITH_EXPLICIT_MEASUREMENT_BOUNDARIES",
  "project": "HydraDG",
  "evidence_class": "DETERMINISTIC_APPLICATION_METADATA",
  "custody_state": "HASHED",
  "signature_state": "NOT_SIGNED",
  "claim_ceiling": "DEDUP_ACCOUNTING_K_DEPTH_AND_HYDRADB_USE_CASE_WITH_EXPLICIT_MEASUREMENT_BOUNDARIES",
  "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.