SCHEMA.md

Wiki Schema

Wiki Schema

This wiki supports the writing of Futureproofing Society. It exists to help the author think through concepts, track arguments across chapters, and catch gaps, repetitions, and contradictions.

Directory Structure

wiki/
├── SCHEMA.md           # This file — structure and rules
├── HOT.md              # Hot context: current focus, pending decisions, active questions
├── INDEX.md            # Master index of all pages
├── INGEST.md           # Instructions for processing new material
│
├── raw/                # DROP ZONE — new material goes here
│   └── (transcripts, articles, notes, PDFs, links, voice memo transcripts)
│
├── ingested/           # Processed material — one page per source
│   └── (structured summaries with integration suggestions)
│
├── queue/              # EDITORIAL QUEUE — what needs rewriting and where
│   └── (one file per suggested change, ordered by priority)
│
├── chapters/           # One page per chapter — current state and cross-references
├── concepts/           # One page per major concept or argument
├── evidence/           # One page per key piece of evidence, trial, or example
├── fiction/            # Chantal timeline, character notes, fiction-nonfiction bridges
├── counterarguments/   # Major objections and how the book addresses them
├── research/           # Research threads from notes/ with usage tracking
└── questions/          # Open questions, unresolved tensions, things to investigate

The Ingestion Pipeline

How it works

  1. Drop material in raw/ — transcripts, articles, notes, PDFs, links, voice memo transcripts, rough thinking. Any format. Name doesn't matter.

  2. Run ingestion — during a session, ask Claude to process what's in raw/. For each item, the system:

    • Reads and understands the material
    • Extracts key ideas, arguments, evidence, and connections
    • Creates a structured page in ingested/ with:
      • Summary of the material
      • Key ideas extracted
      • Where it fits: specific chapter suggestions with reasoning
      • How it helps: which existing arguments it strengthens, challenges, or extends
      • What's new: ideas that don't fit existing structure (potential new sections)
    • Creates entries in queue/ for each suggested manuscript change
    • Updates relevant concept/evidence/chapter pages with new connections
    • Moves the raw file to raw/_processed/ (not deleted, just archived)

  3. Review the queue — queue/ contains prioritised editorial actions. Each entry specifies:

    • What to change and where (chapter + approximate location)
    • Why (what new material motivates it)
    • How (suggested approach — extend existing argument, add new section, replace weak evidence, etc.)
    • Priority (how much it strengthens the book)

The editorial queue (queue/)

Queue entries use this format:

---
title: "Add Barrett's constructed emotion theory to Chapter 14"
type: queue
priority: high | medium | low
target_chapter: 14
target_section: "AI risk framing"
source: "ingested/transcript-2026-04-15-consciousness.md"
status: pending | in-progress | done | rejected
created: 2026-04-15
---

## What

[Specific description of the change]

## Why

[What new material or thinking motivates this]

## How

[Suggested approach — where exactly in the chapter, what to add/modify/replace]

## Impact

[What this strengthens in the book's argument]

Queue priorities

  • high: Fills a gap the book currently has, strengthens a weak argument, or introduces a genuinely new idea that advances the book's thesis
  • medium: Useful enhancement — better evidence, clearer framing, stronger connection between chapters
  • low: Nice to have — additional examples, minor improvements, alternative phrasings

Page Frontmatter

Every wiki page uses this frontmatter:

---
title: "Page title"
type: concept | evidence | fiction | counterargument | question | chapter | research | ingested | queue
status: seed | developing | solid | needs-review
chapters: [2, 5, 12]          # which chapters reference this
related: [other-page-slug]     # cross-references to other wiki pages
last_updated: 2026-04-15
confidence: low | medium | high # how well-supported is this page's content
---

Status definitions

  • seed: placeholder — the page exists to mark that this topic matters, but content is minimal
  • developing: partial content, still being fleshed out
  • solid: content reflects the manuscript accurately and is useful for reference
  • needs-review: something changed (in the manuscript or in our understanding) that may make this page stale

Confidence definitions

  • low: based on a single source or the author's intuition; needs more evidence
  • medium: supported by multiple sources or arguments; coherent but not airtight
  • high: well-evidenced, appears across multiple chapters, counterarguments addressed

Page Content Structure

Concept pages (concepts/)

Each concept page answers:

  1. What does the book argue about this? — the core claim(s), reflecting the book's ORIGINAL arguments
  2. Where does it appear? — chapter-by-chapter tracking of how the argument develops
  3. What evidence supports it? — links to evidence pages
  4. What challenges it? — links to counterargument pages
  5. Connections — how this concept relates to others
  6. Open questions — what remains unresolved or underdeveloped

Evidence pages (evidence/)

Each evidence page tracks:

  1. What is it? — brief description of the evidence, trial, or example
  2. What claim does it support? — the argument it serves
  3. Where is it used? — which chapters cite it
  4. Strength — how strong is this evidence? Any caveats or limitations?
  5. Over-reliance risk — is this example carrying too much weight across the book?

Fiction pages (fiction/)

  • chantal-timeline.md — master timeline of Chantal's appearances, age, circumstances
  • fiction-bridges.md — maps what question each fiction section raises and which nonfiction chapter answers it
  • Character-specific pages as needed

Counterargument pages (counterarguments/)

Each counterargument page tracks:

  1. The objection — stated as strongly as possible
  2. The book's response — how and where the book addresses this (the book's ACTUAL response, not conventional discourse)
  3. Coverage assessment — is the response adequate, or does it need strengthening?
  4. Chapter locations — where this counterargument appears or should appear

Question pages (questions/)

Open questions, tensions, and things to investigate. These get resolved (moved to relevant concept/evidence pages) or archived.

Ingested pages (ingested/)

Each ingested source gets a page tracking:

  1. Source — what was ingested, when, what format
  2. Key ideas — extracted and summarised
  3. Integration map — where each idea fits in the book
  4. Queue entries generated — links to editorial queue items created from this source

Operational Rules

  1. The manuscript is source of truth. Wiki pages describe and analyse; they don't replace the manuscript.
  2. The book contains original thought. Never project conventional UBI/AI discourse onto the book's arguments. Read the actual text.
  3. Update timestamps. When a page changes, update last_updated.
  4. Cross-reference liberally. Use [slug](#unresolved-slug) notation in body text; list in frontmatter related field.
  5. Keep HOT.md under 500 words. It loads at every session start.
  6. Retire stale pages. If something no longer applies, move it to a _archive/ directory rather than deleting.
  7. Confidence is honest. Don't inflate — low confidence is fine; it's a signal to investigate, not a failure.
  8. Queue drives editorial work. The queue is the primary output of the wiki system — it tells the author exactly what to change and where.