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:96417c0db002e84e99ae63067f9663607220ebbbc36e0aecb69fe8c1d54a35a4
Object SHA-256
96417c0db002e84e99ae63067f9663607220ebbbc36e0aecb69fe8c1d54a35a4
identity_check=PASS
{
"slug": "perturbation",
"term": "perturbation",
"definition": "A declared intervention that changes a load-bearing input, value, edge, configuration, or state for a falsification test.",
"how_to": "Record the target, before/after state, operator, scope, expected effect, and FCG delta. A perturbation is not automatically poison or unsafe.",
"graph_query": "Perturbation",
"external_source": null,
"knowledge_href": "/knowledge#perturbation",
"graph_href": "/graph?q=Perturbation",
"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.