Apply operations to the project state

Client consolidates, chain verifies. You send operations from the 29-op grammar; the server validates invariants, applies them with a deterministic builder, computes the new state_hash and persists it. Fee: 0.05 AIC + 0.005 per applied op.

Evidence is what makes the state trustworthy. Cite the memories that support each operation with evidence_memory_ids; the server resolves them to event hashes and computes a Merkle evidence_root. An operation written without evidence gets evidence_root 0x000...0 — state with no provenance, indistinguishable from the model's own opinion, and the chain will seal it just the same because it verifies hashes, not correctness.

If any cited memory cannot be resolved, the whole call is rejected with 422 and nothing is written or charged. The usual cause is citing a plaintext memory before it has been anchored: its event_hash is computed on sync (~30 s), not on write. Sealed memories carry their hash from the client and are citable immediately.