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:78fe5323bd6ba1b1a7d0e36180ff86cf1152a44c35c3e3d783da72aa90d89bbc
Object SHA-256
78fe5323bd6ba1b1a7d0e36180ff86cf1152a44c35c3e3d783da72aa90d89bbc
identity_check=PASS
{
"slug": "fcg",
"term": "FCG",
"definition": "Fractal Custody Graph: the dependency and transformation graph connecting sources, evidence, derived state, claims, and artifacts.",
"how_to": "Follow the canonical project relationship vocabulary to locate the source and transformation route behind a result; do not infer correctness merely because a path exists.",
"graph_query": "DERIVED_FROM",
"external_source": null,
"knowledge_href": "/knowledge#fcg",
"graph_href": "/graph?q=DERIVED_FROM",
"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.