Incoming · 0
No incoming edges in this bounded application graph.
FCO inspector · content-addressed application object
One canonical FCO → one canonical SHA-256 identity. Follow FCG edges to reconstruct dependencies without treating identity as correctness.
FCO ID
fco:63031d39a118f3fee64c3834db9997c724ea86a696c8a9e11040daabb65e7f10
Object SHA-256
63031d39a118f3fee64c3834db9997c724ea86a696c8a9e11040daabb65e7f10
identity_check=PASS
{
"slug": "fco",
"term": "FCO",
"definition": "Fractal Custody Object: a content-addressed logical custody object with explicit evidence and claim boundaries.",
"how_to": "Inspect an FCO ID, its single canonical object SHA-256, payload, evidence class, claim ceiling, and source/dependency edges rather than treating a hash as truth.",
"graph_query": "FCO",
"external_source": null,
"knowledge_href": "/knowledge#fco",
"graph_href": "/graph?q=FCO",
"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"
}Incoming · 0
No incoming edges in this bounded application graph.
Outgoing · 1
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.