Incoming · 0
No incoming edges in this bounded application graph.
FCO inspector · content-addressed application object
WebsiteKnowledgeTerm
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:dac354d92fe2f156cd751df875f6d25431acbddf0b0c3013903fda00d029cd76
Object SHA-256
dac354d92fe2f156cd751df875f6d25431acbddf0b0c3013903fda00d029cd76
identity_check=PASS
Declared object state.
{
"slug": "antidote",
"term": "antidote",
"definition": "A declared recovery intervention intended to restore a reference-compatible state without deleting perturbation history.",
"how_to": "Apply restoration as a new state, then compare the current-state and outcome metrics against the frozen reference while retaining the poison path.",
"graph_query": "restoration",
"external_source": null,
"knowledge_href": "/knowledge#antidote",
"graph_href": "/graph?q=restoration",
"evidence_class": "DETERMINISTIC_APPLICATION_KNOWLEDGE_METADATA",
"claim_ceiling": "WEBSITE_KNOWLEDGE_NAVIGATION_ONLY",
"canonical_project_fcg_state": "BOUND_TO_CURRENT_APPLICATION_FCO_FCG",
"hydradb_projection_state": "HOSTED_CANONICAL_PROJECT_FCG_READBACK_VERIFIED__WEBSITE_TERM_PROJECTION_IS_APPLICATION_METADATA",
"custody_state": "HASHED"
}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.