klappy.dev

The RecordMethods

Method: Writing Predocumentaries

Description

This method exists because reconstructions need a constrained voice to prevent drift into science fiction, allegory, or polemic. Cinematic reconstructions serve one audience — sensory, emotional, literary. Predocumentaries serve another — institutional, procedural, investigative. Both derive from the same system-voice fragments. Neither is canon. The constraint is the register.


When to Use This Method

Use predocumentary format when:

  • The fragment's implications surface through institutional context — HR systems, legal filings, procurement processes, committee hearings
  • The strongest rendering is mundane, not dramatic
  • The reader should think "this could be next quarter," not "this is a parable"
  • The content feeds investigative or journalistic media pipelines

Do not use predocumentary format when:

  • The fragment is best served by sensory imagery and temporal unfolding — use reconstruction instead
  • The rendering requires emotional resonance over institutional specificity
  • The scenario requires speculative technology or far-future worldbuilding — this is not science fiction

Voice Constraints

Documentary, Not Fiction

Predocumentaries read as journalism. They have sources, dates, locations, job titles, case numbers. The specificity is the point — it makes the scenario feel reported, not imagined.

Mundane, Not Cinematic

The drama comes from the institutional machinery, not from spectacle. A payroll discrepancy. A thesis rejection. A dismissed case. The events are small. The implications are not.

Near-Future, Not Speculative

Everything in a predocumentary must be plausible within the current technology landscape plus one step. No new physics. No new biology. No inventions. Just the consequences of what already exists, deployed at the next increment of scale.

No Heroes, No Villains

Characters are people doing their jobs. The payroll administrator files a ticket. The general counsel dismisses it. The judge rules on standing. No one is evil. No one is heroic. The system produces outcomes without requiring malice.

Does Not Resolve

Predocumentaries end with open questions, pending appeals, unanswered follow-ups, closed tickets. The situation is not resolved. It is documented.

B2B/B2C Language Accuracy

Use institutional language accurately. Customers are businesses that deploy agents. Users are people who interact with them. SaaS agreements, deployment licenses, workforce management systems — the vocabulary must be correct. If the terminology is wrong, the documentary register collapses into fiction.


Structure

The Hook — Grounded in Institutional Specificity

Open with a specific person, role, date, location, and institutional context. The reader should feel they are reading a case file, not a story.

The Setup — The System Working as Designed

Describe the institutional context that makes the scenario inevitable. The technology is deployed. The processes exist. Everything is functioning within parameters.

The Moment — When the Implication Surfaces

The fragment's core tension manifests through an institutional event — a filing, a report, a committee vote, a diagnostic result. The moment is not dramatic. It is procedural.

The Fallout — Institutional Response

The institution responds the way institutions respond: dismissal, reclassification, rollback, appeal. The response is not villainous. It is bureaucratic.

The Open Question — What Was Not Resolved

End with the question no one answered. The ticket that was closed. The appeal that is pending. The definition no one was prepared to write.


Relationship to Fragments

A predocumentary derives from a system-voice fragment. It never contradicts the fragment. It expands the fragment's implications through human and institutional context — the people, processes, and structures that encounter the reality the fragment describes.

The fragment says what the system observed. The predocumentary shows what happened when the institution encountered that observation.


Relationship to Content Pipeline

The production sequence is:

  1. Fragment — system-voice source (canon-adjacent, append-only)
  2. Predocumentary — documentary rendering (not canon)
  3. NotebookLM audio — generated from predocumentary
  4. Micro-documentary episode — final production output

Each step adds interpretation. Each step moves further from canon. The fragment is the anchor. Everything downstream is rendition.


The Smell Test

Passes when the reader thinks: "This could be next quarter."

Fails when it sounds like:

  • A parable with a lesson
  • Science fiction with invented technology
  • A sermon with a moral conclusion
  • A prophecy about what will happen

If the reader can identify the genre as "fiction," the predocumentary has failed.


Anti-Patterns

The Sermon

The predocumentary begins to argue a position. Characters make speeches. The conclusion is moral instruction. Fix: Remove all explicit argumentation. Let the institutional facts speak.

The Prophecy

The predocumentary predicts a specific future. It names outcomes with certainty. Fix: End with open questions, not conclusions. The future is not known. Only the trajectory is visible.

The Allegory

The predocumentary becomes a transparent metaphor for a current issue. The institutional details are window dressing for a message. Fix: Make the institutional details load-bearing. If you remove them, the piece should collapse.

The Hero's Journey

A character transforms, grows, or learns a lesson. The narrative has an arc. Fix: Characters encounter a situation and respond within their institutional role. They do not grow. They file reports.

The Sci-Fi Slide

The technology exceeds what currently exists. New capabilities are introduced to make the scenario work. Fix: Use only technology that exists today or is one deployment step from existing. If the scenario requires invention, it is not a predocumentary.

Markdown · RSS · built from klappy/klappy.dev@b750d7d