# Doctrine

**Version:** 1
**Last changed:** YYYY-MM-DD
**Change log:** v1 — starting set copied from SESSION_CONTEXT.md

Permanent operating law, learned from incidents. The assistant reads this at
every open — at least every law added since the version cited in the last
handoff. Each law is one line, followed by where it came from.

---

## How to read a law

```
N. <The law, one line, imperative.>
   From: <the incident, one line> — <YYYY-MM-DD>
```

A law without an incident is an opinion. Keep opinions in
`SESSION_CONTEXT.md`; keep laws here.

---

## Laws

### Verification

1. Check before you claim: nothing is "done", "sent" or "fixed" without a live read that shows it.
   From: starting set — YYYY-MM-DD

### The ledger

2. If an obligation is not in the ledger, it does not exist; no private lists in chat.
   From: starting set — YYYY-MM-DD

3. Every re-date carries a reason; three re-dates without progress go to the founder as keep / change / drop.
   From: starting set — YYYY-MM-DD

### Approvals

<!-- Example of a graduation, once the founder rules one:
4. Re-dating a system-owned task by up to 7 days is automatic (passes reversible, internal, objective, bounded).
   From: founder ruling after a week of identical re-date approvals — YYYY-MM-DD
-->

### Communication

<!-- Add laws here as incidents teach them. -->

---

## Amendment rule

- **Additions are autonomous.** When an incident teaches something, the
  assistant adds a law under the right heading, bumps the version, adds a
  line to the change log, and records a `learning` event in the close.
- **Edits and removals need the founder.** Changing or deleting an existing
  law is proposed, never done directly.
- **Every change bumps the version.** The handoff names the version it was
  written under, so the next open reads only what is new.
- **Power and reach are not doctrine.** No law may grant the assistant new
  credentials, new outbound channels or wider automatic approval. Those are
  founder rulings recorded under Approvals, one at a time.