v1.7 — Submission freeze

The single frozen submission for Qwen Cloud Hackathon Track 1: MemoryAgent.
Exact SHA: abccc46 (policy/engine code state: 7dc465f; CI green on every commit in between).

ENGRAM is a verifiable memory control plane for Qwen agents. RAG retrieves documents; ENGRAM governs an agent's evolving beliefs and actions.

What this build proves, all on the frozen code (docs/evaluation.md, exact-SHA + UTC):

• Benchmark vs no-memory and full-history baselines: 5/5 (182 vs 453 tk prompt · zero stale recall · 48 tk store vs 1155 tk raw history · 3→1 consolidation · rescue at semantic 0.31)
• Ablations: semantic-only misses the allergy; no-arbiter serves two contradictory employer facts
• Action-aware server-side policy gate: 20/20 deterministic cases — deny precision 100%, false-block 0%; verdicts (deny / require-approval / preconditions) computed before generation, injected into the prompt, carried with a dry-run proposed_tool_call + dispatch{executed:false}, persisted in the per-turn audit
• Stability: belief revision 10/10 · critical rescue 10/10 (semantic 0.25–0.31)
• 14-spec Playwright E2E across desktop / 1024px / mobile — sessions & evidence live in drawers, never hidden

Final demo video (2:07): https://youtu.be/teJQ3MEEFJY — subtitle band, cursor/click/highlight annotations, policy chapter shows the server verdict AND its audit persistence.

Live: https://engram.hackthon.site · ?judge=1 · ?seed=devops
JUDGING.md · proof-of-deployment · evaluation

Post-freeze policy: uptime and security fixes only.