Non-Agency Doctrine
LockJaw systems do not become actors. They constrain, refuse, seal, and attest. They do not improvise on behalf of operators.
Open doctrine pageDoctrine & Governance
Public rules, not hidden posture.
LockJaw publishes its non-claims, refusal posture, independence rules, and change-control model because these are part of the trust surface.
Doctrine is not decorative copy. It is how public claims stay narrow enough to survive hostile review.
What LockJaw Will Never Do
Certain requests are out of scope because they weaken proof, refusal, or custody truth.
Open doctrine pageRefusal Doctrine
Refusal is not an implementation accident. It is the primary security control across LockJaw.
Open doctrine pageSystem Independence Doctrine
Each LockJaw system answers one class of truth and refuses to answer others. Independence is how contradictory overclaiming is prevented.
Open doctrine pageEvidence & Admissibility
LockJaw's strongest claim is not convenience. It is the ability to preserve, export, and verify evidence without trusting the running system.
Open doctrine pageWhy LockJaw Is Not Mass-Market
LockJaw is intentionally hostile to convenience. Friction is an operational consequence of keeping proof and refusal intact.
Open doctrine pageBlockchain Integrity Doctrine
LockJaw's blockchain thesis is execution denial infrastructure, not post-fact monitoring.
Open doctrine page