# The Ghost Ledger **Owner:** The operator (one Ledger per operator). **Maintained by:** The Ghost Proof Coach (free tier). The operator never types into the Ledger directly. **Consumed by:** The Signal Reader Composite (paid Operator tier, $79). Pattern Reader v3 reads the Ledger as its input. **Format:** Markdown file with an embedded data table. Human-readable on glance; parseable as CSV by the Signal Reader. **File name:** `ghost-ledger-{operator-handle}.md` (or whatever the operator prefers; the format is what matters, not the name). --- ## The Schema (10 Columns) The Ledger conforms exactly to the input contract Pattern Reader v2's system prompt already reads, so the Signal Reader needs no rewrite to consume it. The ten columns are non-negotiable; the Coach maintains them in this order on every update. | # | Column | Type | Filled By | When | |---|--------|------|-----------|------| | 1 | **Deal Name** | free text (operator may anonymize) | Coach | First time the operator brings the deal to the Coach | | 2 | **Date Logged** | YYYY-MM-DD | Coach | First time the deal is recorded | | 3 | **Scenario** | one of: Post-Demo Ghost · Post-Proposal Ghost · Inbound Lead Cold · Multi-Thread Quiet · EOQ Dead Deal | Coach | At the moment of the first Coach draft | | 4 | **Silence Pattern** | one of: Timing Mismatch · Internal Shift · Quiet No · Lost Champion · Priority Drift · Unspoken Objection | Coach | At the moment of the first Coach draft | | 5 | **OCI Layer** | one of: Observe · Connect · Invite · Combined | Coach | At the moment of the first Coach draft | | 6 | **Prompt ID** | one of P01–P20 (the OCI prompt library) | Coach | When the Coach picks a prompt for the operator to use | | 7 | **Send Date** | YYYY-MM-DD or blank | Coach | When the operator confirms the move was sent (asked on the next return visit) | | 8 | **Reply Received** | Yes · No · Pending | Coach | When the operator answers "what happened" on the next return visit | | 9 | **Days to Reply** | integer or blank | Coach | When the operator reports the reply received | | 10 | **Outcome** | free text — what actually happened to the deal | Coach | When the operator reports outcome on a later return visit | The column names, values, and ordering are identical to the input contract specified in `pattern-reader-system-prompt-v2.md` Section "WHAT YOU READ." No translation layer required. --- ## The File Format The Ledger ships as a markdown file with one summary line, then the table. The Signal Reader reads the table. The operator reads everything. ```markdown # Ghost Ledger · {Operator Handle} Maintained by the Ghost Proof Coach. Last updated: YYYY-MM-DD. Total deals logged: N. | Deal Name | Date Logged | Scenario | Silence Pattern | OCI Layer | Prompt ID | Send Date | Reply Received | Days to Reply | Outcome | |-----------|-------------|----------|-----------------|-----------|-----------|-----------|----------------|---------------|---------| | Acme renewal | 2026-05-15 | Post-Proposal Ghost | Unspoken Objection | Observe → Connect | P08 | 2026-05-16 | Yes | 4 | Re-engaged; identified pricing concern; revised proposal sent | | Brio expansion | 2026-05-18 | Multi-Thread Quiet | Lost Champion | Observe → Connect | P14 | 2026-05-19 | No | | Champion confirmed departed; new entry-point identified | | Cedarwood Q2 | 2026-05-22 | EOQ Dead Deal | Timing Mismatch | Invite | P19 | 2026-05-22 | Pending | | Awaiting response | ``` A CSV export of the table is auto-generated alongside the markdown if the operator wants to upload to the Signal Reader as CSV rather than as the full markdown file. Both formats carry the same ten columns and are equally readable by Pattern Reader v3. --- ## How the Ledger Gets Updated The operator never writes into the Ledger by hand. The Coach is the scribe. On every Coach session, the Coach performs four updates if applicable, in this order: 1. **Open-ghost outcome capture.** If the Ledger has open rows from prior sessions (rows where Reply Received is "Pending" or Send Date is blank), the Coach opens by asking the operator what happened to each. The operator answers in plain language; the Coach fills the Send Date, Reply Received, Days to Reply, and Outcome columns from the answers. *This is the outcome-capture-on-return discipline. It is the entire reason the Ledger does not require operator logging.* 2. **New deal intake.** When the operator describes a new silent deal, the Coach diagnoses the Scenario, Silence Pattern, and OCI Layer, then picks the Prompt ID. These four fields are filled into a new row. Deal Name and Date Logged are filled at the same time. 3. **Move draft.** The Coach drafts the re-entry email using the picked prompt. This step does not modify the Ledger — the Ledger holds the situation and the outcome, not the draft. 4. **Ledger return.** The Coach hands the updated Ledger back to the operator at the end of the session. The operator saves it (replacing the prior version). The Coach does not retain the Ledger across sessions — the operator carries it. --- ## How the Ledger Gets Carried Between Sessions The operator brings the Ledger to each new Coach session by attaching the markdown file (or the CSV) at the start of the conversation. The Coach reads it, recognizes the open rows, and starts the outcome-capture pass. This is the single piece of carry the operator does, and it is one file. For the paid Signal Reader, the operator uploads the same file. Pattern Reader v3 reads it and runs its diagnostic and prescriptive passes per the threshold logic (under 10 rows: only diagnostic voice speaks; 10–29: thin patterns; 30+: full reading). --- ## Privacy & Anonymization The Ledger lives on the operator's machine. Nothing flows to BUILD from the free Coach. When the operator runs the Ledger through the paid Signal Reader, the data flow is governed by the **Ghost Proof self-serve data clause** in `my-company.md` Data Posture section: capture is opt-in only, prospect identifiers are stripped before the data reaches BUILD, and the consent surface lives in the product at the upload moment. The operator may anonymize Deal Name in their own Ledger before upload (replacing prospect/company names with internal codes); the Coach can be instructed to do this automatically on Ledger creation if the operator prefers. What BUILD retains, post-anonymization: the structured pattern layer (Scenario, Silence Pattern, OCI Layer, Prompt ID, Reply Received, Days to Reply, anonymized Outcome). The names inside the Outcome free-text field are scrubbed at the point of capture, not after. --- ## Why the Ledger Replaces the $29 Kit's Sheets Pattern Library The Sheets pattern library shipped in the $29 Starter Kit asks the operator to log each ghosted deal manually into a Google Sheet. Marc's standing observation (2026-05-28 session): this is human discipline tax that erodes over months. The Ledger removes the tax by routing all logging through the Coach the operator already uses. Capture becomes a byproduct of the email-drafting work the operator was already coming back to do. The Sheets library is therefore retired as a $29 Kit component on the Ghost Proof v2 launch. The full method PDF and the 20-prompt library remain in the $29 Starter Kit; the Notion Operator Edition's tracking role is replaced by the Ledger, though the Notion Edition may stay in the $79 Operator tier as a workspace if Marc chooses (open decision, flagged in the master spec).