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

Object SHA-256

eea471a7adff00e9f5cf451118daca943bbffd0620497292b762e52fcb51a5c6

identity_check=PASS

02 / PAYLOAD

Declared object state.

{
  "route": "/evolution",
  "label": "Evolution",
  "role": "presentation-and-release-lineage",
  "claim": "PRESENTATION_LINEAGE_ONLY",
  "project": "HydraDG",
  "evidence_class": "DETERMINISTIC_APPLICATION_METADATA",
  "custody_state": "HASHED",
  "signature_state": "NOT_SIGNED",
  "claim_ceiling": "PRESENTATION_LINEAGE_ONLY",
  "hackathon_authorship_window": "2026-08-12_OR_LATER_REQUIRED"
}

03 / FCG EDGES

Follow the dependency route.

Incoming · 1

SiteSection

fco:dc1258c712cfc939b559ce7228dd49e645d6bb2fb4cff72e4175adae61a22219

HAS_LINEAGE_VIEW →

Outgoing · 2

SiteSection

fco:1a3f660ab952cb559aba8cb14a33f4090f1308be1a1bb9e7d7bb8484f5cc998a

BOUNDED_BY →

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.