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:994abc0e6927470000e22eae1d7a4a6f280eda0e0225670f9ed7eb0e22528090
Object SHA-256
994abc0e6927470000e22eae1d7a4a6f280eda0e0225670f9ed7eb0e22528090
identity_check=PASS
{
"slug": "anticube",
"term": "Anticube",
"definition": "Independent SELF/NONSELF × SAFE/NONSAFE + UNKNOWN admission/classification surface.",
"how_to": "Treat classification as a scoped event. It may admit, challenge, quarantine, abstain, or reject without overwriting provenance.",
"graph_query": "ClassificationReceipt",
"external_source": null,
"knowledge_href": "/knowledge#anticube",
"graph_href": "/graph?q=ClassificationReceipt",
"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.