---
vault_clearance: KETER
halo:
  classification: RESTRICTED
  confidence: MEDIUM
  front: "11_Project_WordsOfTomorrow"
  custodian: "The Architect"
  created: 2026-03-27
  updated: 2026-03-27
  wing: UNASSESSED
  containment: "FORM — encryption & prose policy map"
---
# FORM — Full-Object Replica Management

**BOOK:** [BOOK.md](BOOK.md) — NIST/RFC-class refs when policy text cites them.

> **F**ull-**O**bject **R**eplica **M**anagement.
> Whole-vault boundary discipline: each replica (local, OneDrive, git) has an explicit plaintext vs encrypt posture — not folder-by-folder fantasy.

Map **partial encryption / ad hoc secrecy** vs **whole-replica posture + prose standard**.

---

## The Two Paradigms

### Orthodox (selective secrecy)
- **Philosophy:** Encrypt “the sensitive folders”; leave the rest plaintext; hope grep never leaks.
- **Free parameters:** Which subtree, which tool, which forgotten clone.
- **Tools:** Ad hoc VeraCrypt volumes, password-protected zips, chat-based key exchange.
- **Output:** **Schrodinger compliance** — you never know which replica is authoritative.

### Words of Tomorrow (ours)
- **Philosophy:** **Either encrypt the whole vault for a boundary, or accept plaintext for that boundary** (project README axiom). Deployment truth table for Local / OneDrive / Git.
- **Free parameters:** Boundary choice is explicit — not per-file whim.
- **Tools:** [PROTOCOL_WORDS_OF_TOMORROW.md](PROTOCOL_WORDS_OF_TOMORROW.md), [WRITE_STANDARD.md](WRITE_STANDARD.md), sensory helpers.
- **Output:** One honest envelope story + better lab prose under stress.

---

## Head-to-Head: Axes That Matter

| Axis | Orthodox | Words of Tomorrow |
|------|----------|-------------------|
| **Replica parity** | Drift | Declared posture per replica |
| **Keys** | Scattered | O5 authority; no keys in git |
| **Prose quality** | Afterthought | WRITE_STANDARD when it matters |
| **HALO** | Ignored until incident | Align with vault classification |

---

## The Murder Board — Where Orthodox Fails

1. **Partial encrypt fantasy** — attackers read the rest.
2. **Key sprawl** — recovery impossible under stress.
3. **Git + secrets** — “we’ll rotate later.”
4. **Incoherent classification** — RESTRICTED content in PUBLIC export.

**Countermove:** Axiom + truth table + PROTOCOL; cross-read [HALO_PROTOCOL.md](../HALO_PROTOCOL.md) USB section.

---

## What We Take From Orthodox (Honestly)

| From industry practice | Why | Into WoT how |
|-------------------------|-----|---------------|
| **BitLocker / VeraCrypt** | Proven envelopes | Document when/how, not vibes |
| **Backup keys** | Survival | INTERNAL-only recovery docs |
| **Style guides** | Clarity | WRITE_STANDARD density rules |

---

## The Proof: Concrete Comparisons to Run

1. **Replica audit:** Three replicas — plaintext vs encrypted stated for each; no silent fourth.
2. **Grep secrets:** `git grep` for key-shaped strings; must be empty.
3. **Export dry-run:** `halo_gate validate` on a PUBLIC export tree.
4. **Prose sample:** Rewrite one RESTRICTED note to WRITE_STANDARD — legibility without leaking.

---

## Expected Result

- **Orthodox** wins **illusory convenience**.
- **Words of Tomorrow** wins **honest envelopes and legible failure modes**.

---

## FORM — Final Assessment

Project 11 owns **how the vault meets borders** — disk, cloud, git, handoff. FORM maps why “encrypt a little” is a **risk management lie**.

---

*FORM — Full-Object Replica Management. One boundary; whole truth.*