How MAGLA Memory works

A checkpoint becomes useful project memory only after the work was actually done and the result was verified.

The loop

1. Resume. preflight returns the latest verified checkpoint and a signed work_receipt.

2. Do real work. Your agent calls tools, APIs, people or workflows exactly as it normally would.

3. Verify. Check the result using evidence available to your application.

4. Record. Store a verified outcome, or record a bounded failed approach.

Why the receipt exists

The receipt binds a write to the task session and scope that created it. A random later request cannot silently turn an unrelated statement into project truth.

Why failures are first-class

A useful memory system should remember “this approach failed under these conditions” without converting that failure into a universal rule. That is why failures carry an explicit bounded condition and evidence.