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:da497052c6158548663924c4358481e292cb527719b65873803cb6cde57a4c22
Object SHA-256
da497052c6158548663924c4358481e292cb527719b65873803cb6cde57a4c22
identity_check=PASS
Declared object state.
{
"slug": "hydraontology",
"term": "HydraOntology",
"definition": "Track 01 HydraDG experiment for enterprise context, identity resolution, conflicting evidence, and ontology state.",
"how_to": "Use bounded entity-resolution canaries first; only promote to real benchmark claims after the corresponding EnterpriseRAG/HERB receipts exist.",
"graph_query": "HydraOntology",
"external_source": null,
"knowledge_href": "/knowledge#hydraontology",
"graph_href": "/graph?q=HydraOntology",
"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.