---
vault_clearance: EUCLID
halo:
  classification: INTERNAL
  confidence: MEDIUM
  front: "03_Project_Technomancer"
  custodian: "The Architect"
  created: 2026-03-27
  updated: 2026-03-27
  wing: UNASSESSED
  containment: "FORM — recorder comparison map"
---
# FORM — Fixed-Order Recorder Mechanics

**BOOK:** [BOOK.md](BOOK.md) — arXiv / tooling rows for recorder and AI-stack context.

> **F**ixed-**O**rder **R**ecorder **M**echanics.
> Map platform memory defaults vs append-only tape and warp↔vault bridges.

---

## The Two Paradigms

### Orthodox (platform memory)
- **Philosophy:** The product owns the thread; export is a feature; history is a UI.
- **Free parameters:** Retention knobs, moderation, invisible summarization, model-specific context windows.
- **Tools:** Chat UIs, notebooks, proprietary APIs.
- **Output:** Convenient — until subpoena, account loss, or model change.
- **Trust model:** “They probably kept it.”

### Technomancer (ours)
- **Philosophy:** **Recorder does not think — it persists.** Tape at vault root; mechanical adapters ingest from browser/warp; Daemon is *queryable knowledge*, not the tape.
- **Free parameters:** Ingest format and cursor rules — explicit, not “smart.”
- **Tools:** `.event_log.jsonl`, sequence files, Live_Stack adapters, sync scripts.
- **Output:** Forkable, grep-friendly, long-horizon witness.
- **Trust model:** “You can read the bytes.”

---

## Head-to-Head: Axes That Matter

### 1. Provenance

| Axis | Orthodox | Technomancer |
|------|----------|--------------|
| **Who wrote line N?** | Opaque | Append-only line with metadata |
| **Tamper story** | Trust vendor | Git + vault policy |

### 2. Portability

| Axis | Orthodox | Technomancer |
|------|----------|--------------|
| **Move labs** | Export zip if allowed | Clone repo |
| **AI rotation** | Context loss | Thread cursors + boards |

### 3. Warp boundary

| Axis | Orthodox | Technomancer |
|------|----------|--------------|
| **Remote collaborator** | Lives in vendor cloud | Warp reads; vault remains ground truth |

---

## The Murder Board — Where Orthodox Fails

1. **Summarization as amnesia** — “Helpful” condensation deletes the evidentiary chain.
2. **Account death** — entire timeline evaporates.
3. **Ambiguous merge** — human+model edits without mechanical ordering.
4. **False equivalence** — treating chat as the same class of memory as commits.

**Technomancer countermove:** Mechanical ingest; explicit cursors; refuse “the model remembers for us.”

---

## What We Take From Orthodox (Honestly)

| From platforms | Why | Into Technomancer how |
|----------------|-----|------------------------|
| **Webhooks / HTTP** | Universal ingress | Adapters that only *append*, never rewrite |
| **Browser UX** | Low friction capture | Tampermonkey / local relay patterns |
| **JSONL ecosystems** | Streaming parsers | Keep one obvious tape format |

---

## The Proof: Concrete Comparisons to Run

1. **Byte replay:** Re-ingest historical slice; compare hash to canonical log.
2. **Cursor contract:** New session — does the thread cursor prevent double-counting?
3. **Fail closed:** Kill adapter mid-flight — is partial write detectable?
4. **Warp read:** Exterior NAME pulls `vault/breakthroughs/vault.md` — still matches file on disk after sync.

---

## Expected Result

- **Orthodox** wins on **zero-setup friction**.
- **Technomancer** wins on **sovereignty, audit, and survival across vendor churn**.

They answer different questions:
- **Orthodox:** “What did the product show me last Tuesday?”
- **Technomancer:** “What can I prove was said, in order, under our vault’s law?”

**The play:** Use platforms to *talk*; use Technomancer to *remember*.

---

## FORM — Final Assessment

Technomancer is the **spine** between body (disk/git) and warp (reach). FORM states the moral: **memory must not depend on a merciful vendor.**

---

*FORM — Fixed-Order Recorder Mechanics. Persist first; interpret later.*