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:47ae02fd60392410188b096c49adac14981fd036b449c2a4dfb3ed26225d5f5e

Object SHA-256

47ae02fd60392410188b096c49adac14981fd036b449c2a4dfb3ed26225d5f5e

identity_check=PASS

02 / PAYLOAD

Declared object state.

{
  "route": "/custody",
  "label": "Custody",
  "role": "hash-signature-and-key-boundary",
  "claim": "CRYPTOGRAPHIC_STATUS_AND_SIGNING_SCOPE_DOCUMENTATION",
  "project": "HydraDG",
  "evidence_class": "DETERMINISTIC_APPLICATION_METADATA",
  "custody_state": "HASHED",
  "signature_state": "NOT_SIGNED",
  "claim_ceiling": "CRYPTOGRAPHIC_STATUS_AND_SIGNING_SCOPE_DOCUMENTATION",
  "hackathon_authorship_window": "2026-08-12_OR_LATER_REQUIRED"
}

03 / FCG EDGES

Follow the dependency route.

Incoming · 3

SiteSection

fco:5ad8877bcc81bc7417050a722b1d8737788d45595ba9f01449eb0f16bc4b5b2c

GOLDEN_PATH_NEXT →

SiteSection

fco:b73d8f182a68ce94910df14e83b2f217b1b54a323b7db3fdc6fb7671792ccf31

BOUNDED_BY →

SiteSection

fco:5ad8877bcc81bc7417050a722b1d8737788d45595ba9f01449eb0f16bc4b5b2c

BOUNDED_BY →

Outgoing · 2

SiteSection

fco:2b95479c61d1413bfa60b74d6efd54ec767d18776c0820bad65058988960f2bd

GOLDEN_PATH_NEXT →

SiteArtifact

fco:f0ea99eed0a6a3c6baf2775c75115dcc0b84505b57e2d0b6550c4cf0f6126c74

PART_OF_SITE_ARTIFACT →

04 / NAVIGATION

Resolve the object in context.

4D FCG Evidence index Knowledge Base How to use Release JSON

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.