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:9f7320fa4e7decb810e91f7726baedc73088f6dfdf2e5e1ee18e899e83fdf472
Object SHA-256
9f7320fa4e7decb810e91f7726baedc73088f6dfdf2e5e1ee18e899e83fdf472
identity_check=PASS
Declared object state.
{
"slug": "merkle-checkpoint",
"term": "MerkleCheckpoint",
"definition": "Deterministic commitment over a declared ordered leaf set; distinct from signing, correctness, and live HydraDB graph state.",
"how_to": "Inspect leaf ordering, odd-leaf rule, root SHA-256, and exact scope before describing a checkpoint as committed.",
"graph_query": "MerkleCheckpoint",
"external_source": null,
"knowledge_href": "/knowledge#merkle-checkpoint",
"graph_href": "/graph?q=MerkleCheckpoint",
"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.