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

Object SHA-256

d3250e03a81ddfe358225003fd8556897b71f4ceb996d2268dc48c2fec21a1cd

identity_check=PASS

02 / PAYLOAD

Declared object state.

{
  "route": "/track01",
  "label": "Track 01",
  "role": "enterprise-context-ontology",
  "claim": "TRACK01_IMPLEMENTATION_STATUS",
  "project": "HydraDG",
  "evidence_class": "DETERMINISTIC_APPLICATION_METADATA",
  "custody_state": "HASHED",
  "signature_state": "NOT_SIGNED",
  "claim_ceiling": "TRACK01_IMPLEMENTATION_STATUS",
  "hackathon_authorship_window": "2026-08-12_OR_LATER_REQUIRED"
}

03 / FCG EDGES

Follow the dependency route.

Incoming · 1

SiteSection

fco:d86d1afb0c92d65dc426ec28a09c0a814b863e1d45269890c36801c5e0937d4a

INSPECTS_TRACK_LENS →

Outgoing · 2

SiteSection

fco:2b95479c61d1413bfa60b74d6efd54ec767d18776c0820bad65058988960f2bd

SUPPORTED_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.