2026-07-19 · updated 2026-08-21 · Walid Abdulhameed
Why we physically cannot store your source code
Zero source retention: Beacon borrows a short-lived GitHub window for one diagnosis, then drops it. What we keep is scrubbed telemetry — not your repository.
LAWDE Shield stores 0 bytes of your source code as a durable product copy. Beacon context is burn-after-read.
What does zero source retention mean?
It means LAWDE Shield is not a mirror of your repository. Beacon may fetch a bounded source window around a stack frame for a single Athena run, then that window falls out of scope.
We never keep raw source as a durable product copy. That is the Zero Liability covenant — 0 bytes of source stored as a product artifact.
How does Beacon stay read-only?
Beacon uses read-only GitHub access for diagnosis. It does not take write scopes to “fix” your repo. If a path matches .lawdeignore, Nuclear Abort stops the GitHub fetch and AI grounding for that event.
What is still stored?
Scrubbed error messages, stack metadata, cluster identity, trust scores, and AI verdicts. Those are telemetry — not your codebase.
Our Full Shield roadmap (Argus and Phantasos — planned v2.0) can stay honest because of this constraint, not in spite of it.