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:31b87dcb8787709c0fcc4f805899bb4dcf09310f0b1c14305569abb5746a3a6a
Object SHA-256
31b87dcb8787709c0fcc4f805899bb4dcf09310f0b1c14305569abb5746a3a6a
identity_check=PASS
{
"slug": "beam",
"term": "BEAM",
"definition": "Long-context memory benchmark across 100K/500K/1M and separately 10M-token-scale conversations.",
"how_to": "Keep probing questions/ideal answers evaluation-only and ingest conversation turns as the memory substrate.",
"graph_query": "BEAM",
"external_source": "https://huggingface.co/datasets/Mohammadta/BEAM",
"knowledge_href": "/knowledge#beam",
"graph_href": "/graph?q=BEAM",
"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.