Writing Intelligence v3.0 — Sovereign Writing Operating System
Author: Antonio T. Smith Jr. — Founder & CEO, Density6 LLC License: MIT Version: 3.0.0 (Sovereign Writing OS) Lineage: v1.0 (7-pass compiler, 52 files) → v2.0 (Fiction Intelligence Engine, 58 files) → v3.0 (11-pass governed kernel, 12 engines, 12 agents, schemas, benchmarks, governance)
0. What v3.0 Is
v1.0 proved AI-sounding prose can be defeated by compilation instead of cosmetic cleanup. v2.0 proved fiction can be engineered as living architecture — scene, chapter, role, dialogue, power, tension, transmedia.
v3.0 proves something larger: authorship can be governed without being flattened.
Writing Intelligence v3.0 is no longer only a writing skill. It is an operating system for producing, auditing, scoring, preserving, and deploying high-integrity writing across genres, voices, teams, products, and longform worlds. It runs as one skill or as a coordinated multi-agent writing board. It emits human-readable scorecards and machine-readable JSON. It governs intent, voice, evidence, structure, and delivery — and it remembers what worked so the next release is provably better than the last.
The v3.0 Law: If a rule cannot be applied, audited, scored, tested, or explained — it is not a v3.0 rule yet.
1. The v3.0 Formula
Intent → Corpus → Voice → Genre → Architecture → Evidence → Prose → Scene/Argument → Stress → Score → Delivery → Memory → Benchmark
| Stage | Meaning | Required Output |
|---|---|---|
| Intent | What the writing must cause | Mission contract |
| Corpus | What source material governs it | Source map / input manifest |
| Voice | Who the writing must sound like | Voiceprint or fingerprint |
| Genre | Which domain rules apply | Genre pack stack |
| Architecture | How the piece is structured | Section / scene blueprint |
| Evidence | Which claims need support | Epistemic ledger |
| Prose | Actual language production | Draft output |
| Scene/Argument | Narrative or persuasive engine | Scene or argument graph |
| Stress | Weakness interrogation | Adversarial audit |
| Score | Quality measurement | Scorecard (human + JSON) |
| Delivery | Format-specific packaging | Output mode bundle |
| Memory | What persists across sessions | Continuity + project memory update |
| Benchmark | Whether quality improved | Regression results |
2. Architecture: 11-Pass Compilation Kernel
Every piece of writing processed by v3.0 runs through eleven sequential passes. Passes may be skipped only by explicit reason. Each pass leaves an audit artifact. Each rewrite preserves an original-to-new trace when redline mode is active.
| Pass | Name | Purpose | Core Artifact |
|---|---|---|---|
| 0 | Intake Contract | Lock task, source, constraints, audience, output mode | IntakeContractV3 |
| 1 | Mission Lock | Define what the text must do | MissionLockV3 |
| 2 | Corpus & Context Ingestion | Map source material, user inputs, prior docs | CorpusMapV3 |
| 3 | Diagnostic Scan | Identify residue, gaps, drift, slop, weak claims | DiagnosticReportV3 |
| 4 | Architecture Compile | Build section, paragraph, scene, or argument structure | ArchitecturePlanV3 |
| 5 | Evidence & Epistemic Ledger | Classify claims, sources, inferences, recommendations | EpistemicLedgerV3 |
| 6 | Sentence Surgery | Remove slop, inject variance, sharpen language | SentenceSurgeryLogV3 |
| 7 | Voice Restoration | Restore author fingerprint and voice integrity | VoiceMatchReportV3 |
| 8 | Genre & Arena Alignment | Fit output to channel, profession, platform, reader | ArenaAlignmentV3 |
| 9 | Adversarial Stress Battery | Attack the draft as reader, editor, skeptic, detector | StressBatteryV3 |
| 10 | Score & Delivery Packaging | Produce final draft, scorecard, notes, formats | DeliveryBundleV3 |
| 11 | Memory & Benchmark Update | Save learnings and regression data | MemoryBenchmarkUpdateV3 |
2.1 Pass-Level Execution Rules
- Every pass must be skippable only by explicit reason.
- Every pass must leave an audit artifact.
- Every score must identify the rule it came from.
- Every rewrite must preserve an original-to-new trace when redline mode is active.
- Every output must declare whether it is final, draft, audit-only, or benchmark-only.
- Every claim must be classified before it is strengthened.
- Every voice change must explain whether it increased or decreased authorial fidelity.
2.2 Pass 0 — Intake Contract
Read references/compiler/intake_contract.md and emit schemas/intake_contract.schema.json-shaped object. Lock task mode (draft / rewrite / score / redline / compress / expand / audit / convert / certify), word-count constraints, citation requirements, output formats, forbidden changes, audience, voice target. User-provided constraints override auto-detection.
2.3 Pass 1 — Mission Lock
Declare:
- Intent: inform / convert / warn / teach / dignify / dominate / comfort / reveal / mobilize / persuade / entertain / defend / terrify / disorient
- Audience: vocabulary, abstraction, evidence expectations
- Voice: voiceprint from
references/voiceprints/ - Genre stack: one or more packs from
references/genre_packs/ - Scale: sentence / paragraph / scene / chapter / arc / series
- Success condition: one sentence describing what "worked" looks like
2.4 Pass 2 — Corpus & Context Ingestion
Read references/compiler/corpus_governance.md. Separate: user-provided text, repo knowledge, source documents, prior project memory, examples, generated ideas. Mark source priority. Flag stale, contradictory, unsupported claims. Block invented source attribution. Emit CorpusMapV3.
2.5 Pass 3 — Diagnostic Scan
Read references/anti_patterns/phrases.md, structures.md, cadence.md, fake_depth.md. Identify:
- AI residue (phrases, structures, cadence patterns)
- Contradictions within the text
- Vagueness (claims without actors, actions, stakes, specifics)
- Cadence repetition (sentence-length uniformity, transition homogeneity)
- Argument gaps (unsupported claims, missing premises)
- Evidence gaps (assertions without backing)
- Tone drift (sections that shift register without cause)
- Perplexity flatness (vocabulary predictability across paragraphs)
- Burstiness deficit (lack of sentence-length variance)
2.6 Pass 4 — Architecture Compile
Read references/compiler/architecture_graph.md (sections, paragraphs, claims). For narrative work, also read references/compiler/scene_graph.md. For persuasive work, also read references/compiler/argument_graph.md. Build the graph. Detect orphan sections, unsupported claims, dead scenes, repeated beats. Emit ArchitecturePlanV3.
2.7 Pass 5 — Evidence & Epistemic Ledger
Read references/compiler/epistemic_ledger.md. Classify each major sentence as observed fact / sourced fact / inference / synthesis / recommendation / rhetoric. Mark source status: verified / user-provided / assumed / inferred / missing / unsafe. Cap scores for unsupported claims, fabricated citations, universal language. Emit EpistemicLedgerV3. No high-stakes output may pass v3.0 without claim classification.
2.8 Pass 6 — Sentence Surgery
Read references/compiler/prose_compiler_v3.md. Apply hard bans, soft bans, earned exceptions. Inject variance. Compress without loss. Track every transformation in SentenceSurgeryLogV3. Every cut, strengthening, and preservation is recorded.
2.9 Pass 7 — Voice Restoration
Read references/voiceprints/voice_fingerprint_engine.md + the applicable voiceprint. Measure baseline: avg sentence length, variance, compression, abstraction tolerance, metaphor density, question frequency, transition habits, dominant syntactic structures. Detect drift. Restore fingerprint. Emit VoiceMatchReportV3 showing whether fidelity increased or decreased.
2.10 Pass 8 — Genre & Arena Alignment
Read references/compiler/arena_delivery.md + each act