Incoming · 3
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
The content hash is the canonical address.
FCO ID
fco:77c81a92be5bc5ddf072f06f234012b1142547815cf7d983d4b053bb56812437
Object SHA-256
77c81a92be5bc5ddf072f06f234012b1142547815cf7d983d4b053bb56812437
identity_check=PASS
Declared object state.
{
"route": "/graph",
"label": "4D FCG",
"role": "custody-graph-visualization",
"claim": "EVIDENCE_LINKED_VISUALIZATION",
"project": "HydraDG",
"evidence_class": "DETERMINISTIC_APPLICATION_METADATA",
"custody_state": "HASHED",
"signature_state": "NOT_SIGNED",
"claim_ceiling": "EVIDENCE_LINKED_VISUALIZATION",
"hackathon_authorship_window": "2026-08-12_OR_LATER_REQUIRED"
}Follow the dependency route.
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.