Generated from the maintained method library. Read or download equivalent Markdown.

Historical source. Do not apply to new work; consult the current Method Reference.

On this page

The V-V-V Focus Line Structure: Violation → Verb → Vision

Status / authority: Legacy; do not use for new current-method work
Effective date: Retired from current use 2026-07-29
Dependencies: ../LEGANT_METHOD_REFERENCE.md §3; ../Direction/Four Narrative Constraints.md; Tension Framework.md; accepted methodology decision LL-ADR-013; frozen ARC release
Supersedes: Earlier V-V-V specifications for historical interpretation only
Current replacement: the nine-question Operating Manual's "What I choose" answers (../LEGANT_METHOD_REFERENCE.md §§2–3). The Four Narrative Constraints, which replaced Focus Line on 2026-07-29, are themselves legacy since 2026-10-20.

Legacy-use notice: Preserve this document to interpret historical artifacts and existing approved Focus Lines. Do not generate a new Focus Line, use it as an extraction lens, or restore it as an analytical checksum.

Canonical Relationship to Tension (July 23, 2026)

The V-V-V Focus Line is now understood as a story-facing compression of Core Tension, not the complete person model.

A concrete Violation can trigger the Verb, but Violation is not the entire Tension, and negative perception is not the only possible trigger. Positive possibility can create the same force when a person sees what could exist but does not yet.

For current boundaries around Core Tension, Violation, Verb, and Vision, read Tension Framework.md. For current direction work, read the Method Reference §§2–3 (the Operating Manual's "What I choose" answers); the legacy Four Narrative Constraints.md records the intermediate framework.

The sections below preserve the historical V-V-V model and its rationale. They are not instructions for constructing a current direction.

Historical Purpose

In the legacy ARC design, a Focus Line (Violation → Verb → Vision) distilled a person's value-creation. This module upgraded the Violation component so it carried the same conviction, filter-power, and self-assuredness that Patrick O'Shaughnessy describes as "inventing on principle."

The goal is not to add more parts. The goal is to make the first part of the Focus Line do more work.

The Story Structure Principle

"If there is something in the world you feel is a wrong, and you have a vision for what a better world could be, you can find your guiding principle."
— Bret Victor, "Inventing on Principle"

Every compelling life story needs an antagonist: a coherent obstacle the protagonist must contend with. At the scale of a Personal Challenge, that antagonist is the Challenge/adversary. A Violation is how the effects of that adversary become legible and charged to a particular Inner Species.

A scattered story chases disconnected obstacles. A coherent story keeps returning to a coherent Tension.

The Focus Line has always been structured as a story: a character who wants something and overcomes obstacles to get it. But the original "Problem/Purpose" specification was undercooked—functional but low-voltage. Patrick O'Shaughnessy's "principle for invention" framework clarifies what we were always reaching for:

A recurring Violation can reveal the deeper Core Tension your Inner Species is attuned to and the response it tends to activate.

This module upgrades the Violation component to what it should have been all along.

Definitions

The V-V-V Structure

The Focus Line follows a three-part narrative arc:

Violation → Verb → Vision

Where:

This structure maps directly to story: Antagonist → Protagonist Action → Resolution.

Principle for Invention

The Principle for Invention is the quality standard the Violation component of a Focus Line must meet. The Focus Line is the complete operating instruction (Violation → Verb → Vision); the Principle for Invention is the bar the Violation must clear.

The concept originates from Bret Victor's "Inventing on Principle" talk and Patrick O'Shaughnessy's articulation: "The principle should be something that when you see it violated, it is your obligation to go correct it."

Victor identifies three philosophical qualities of a principle worth living by:

  1. Reaction to Injustice — not preference, but visceral response ("When I see ideas dying, it hurts... it feels like a moral wrong")
  2. Cause Over Craft — you define yourself by what you fight for, not your job title (Larry Tesler wasn't "a computer scientist"—he was the person who fought to eliminate modes)
  3. Important, Necessary, and Right — "something you believe is important and necessary and right"

Note on Victor's register: Victor's compulsion expressed as moral outrage. That's his register—not a universal requirement. The same structural quality (reliable, identity-level compulsion that persists across vehicles) can show up as moral outrage, engineering itch, structural recognition, or aesthetic revulsion. What matters is that the compulsion is real, reliable, and not dependent on a specific vehicle or context.

ARC translates these into three operational properties a well-formed Violation should exhibit:

Victor's qualities describe what makes something a real principle. ARC's properties describe what a real principle does for the person who holds it. Both sets are complementary, not interchangeable.

A principle is not a preference, vibe, or trend. It is an identity-level refusal that reliably predicts what the person will keep building—even when it's hard or unpopular. The emotional register of the compulsion varies by person; the reliability of the compulsion does not.

Note on "Cause Over Craft": This quality maps directly to ARC's Verb vs. Noun distinction (see Methodology Section 2). The larger Tension helps identify the cause; the Verb is how you respond to it; the Noun (vehicle) is merely the current vessel. This is why the underlying Tension must be vehicle-agnostic even when its Violations change form.

Violation

A Violation is a negatively valenced expression or instance of Core Tension: something experienced as wrong, wasted, missing, distorted, or unfit. A concrete Violation can trigger a response, but the deeper pattern is the relationship among the perceived discrepancy, the force it creates, and the Verb it tends to activate. Positive possibility can also activate the same Tension.

A well-crafted Violation articulates:

It operates at a compulsion register, not necessarily a moral one. The defining quality is reliability of response—when you encounter this pattern, you act. For some people, that compulsion shows up as moral outrage (Bret Victor: "When I see ideas dying, it hurts. It feels like a moral wrong, like an injustice."). For others, it's an engineering itch ("this could be systematized and it hasn't been—why?"), a structural recognition ("this path should exist but doesn't"), or a quiet, steady sense that something is wrong in the design sense. All of these are valid Violations if they pass the operational test below.

The bar is not emotional intensity. The bar is: Does this class of discrepancy recur across different vehicles, contexts, and time periods? Does encountering it reliably create force toward the person's characteristic response, rather than only intellectual agreement that something is a problem?

Your Inner Species is not obligated to solve this; you can choose not to act. The Tension identifies a recurring source of activation, not a moral duty or guaranteed destiny. Direction comes from deliberately selecting a larger, worthy version of that Tension to work on.

Core Tension carries possibility, not just critique. The full relation holds both:

The Vision in your Focus Line articulates that better world you're building.

Design Requirement

A principle implies a constraint for solution design:

This often becomes part of your Boundary Line consideration and prevents solution drift into "sophisticated conformity."

Why This Matters in ARC

1) It turns the Focus Line into a stronger decision filter

A generic problem can be correct but low-voltage. A principle-based Violation becomes a high-charge filter:

2) It makes "confidence" portable (not dependent on outcomes)

Vehicle fit can exist without explicit principle clarity. But principle clarity makes fit:

3) It upgrades ARC's "anti-scatter" goal from willpower to default-shifting

ARC's aim isn't "try harder to be yourself." It's: Design systems where the aligned path is the path of least resistance.

Principle makes that requirement explicit.

A Note on Difficulty

Finding and articulating your Principle-based Violation is not trivial. As Bret Victor notes: "It can take time to find a principle... it took me a decade." Patrick O'Shaughnessy echoed this: he couldn't articulate his principle clearly until very recently, despite living it for years.

For ARC clients: The downstroke distillation process accelerates discovery, but Core Tension may emerge directionally first and sharpen through lived experience. A Violation is one evidence-bearing expression of it, not the whole target.

A Note on Register: Some clients will immediately connect with the word "violation" as moral outrage. Others will register the same Core Tension as an engineering itch, structural recognition, design-sense wrongness, or positive possibility. The diagnostic question is not only "does this make you angry?" but "does this class of discrepancy reliably create force toward your characteristic response across contexts and time?"

This is a higher bar than identifying a generic problem space. A clear Core Tension helps separate durable direction from a transient concern.

How It Fits Into Existing ARC Architecture

This module lives primarily inside:

It does not require adding a fourth Focus Line ingredient. It changes the quality bar of the first ingredient.

The V-V-V Focus Line Structure

ARC Focus Line is:

Violation → Verb → Vision

Ingredient 1: Violation (The Obstacle)

Must include:

Avoid:

Templates:

Make it vehicle-agnostic:

The violation should work whether you're helping individuals, organizations, communities, or systems. Use universal nouns (potential, clarity, signal, momentum) rather than vehicle-specific ones (people, companies, students).

The vehicle narrows it. The principle stays universal.

Ingredient 2: Verb (Capability Stack)

The most succinct articulation of your Innate Edge in action. Keep it verb-forward and wiring-specific:

Ingredient 3: Vision (What Right Looks Like)

Keep it short, external-facing, and aspirational:

Why Vision matters: It articulates the better world you're creating. This completes the narrative arc from Violation (what's wrong) through Verb (how you fight) to Vision (what right looks like).

How to Extract the Violation

The Art (Not Algorithm)

There's an art to this that would be lost with overly prescriptive steps. But the principle typically surfaces in interviews through recognizable evidence patterns:

Look for the coherent thread across:

The Core Tension is the coherent relation that shows up in different disguises across these domains. The Violations are its negatively valenced expressions.

Integration with Existing Process

The 11-step Focus Line distillation process remains largely intact:

  1. Project Brief
  2. Violation Harvest ← Look specifically for what feels wrong and what it costs
  3. Distil Violation ← Extract the recurring negative expression; test what deeper Tension connects it across domains
  4. Capability Mining
  5. Capability Distillation
  6. Payoff Harvest ← Now looking for Vision language
  7. Vision Distillation ← Craft what-right-looks-like statements
  8. Sentence Generation ← Apply V-V-V templates
  9. Select & Polish ← Rate for voltage + vehicle-agnosticism
  10. Devil's-Advocate Test
  11. Client Voice Pass

The key shift: In steps 2-3, mine for violations (what appears wrong), consequences (what it costs), and the deeper Tension they express. In steps 6-7, look for vision language about the condition that would fit instead.

For 80/20 Rapid Assessments

For quick assessments (Core Wiring X-Ray), the Violation may be directional rather than definitive.

The goal: Give the client the TARGET to aim for and the PATTERN to watch for, knowing they'll sharpen it through lived experience and upstroke iteration.

A directional Violation is still better than a generic pain point—it gives the client something to test against reality.

Worked Examples

Example 1: Chris (Before and After)

Before (Original):

"I break conformity down to first principles then engineer creative frameworks that unlock extraordinary potential."

Analysis:

After (V-V-V Upgrade):

"When conformity boxes potential, turning one-shot lives into scattered effort, I reverse-engineer uniqueness into systematic frameworks that unlock compounding advantage."

Breakdown:

Alternative (Tighter):

"When conformity turns potential into waste, I reverse-engineer uniqueness into frameworks that make progress compound."

Example 2: Bret Victor (Source Example)

Bret's Principle:

"Digital creators should have immediate connection with what they're creating."

The Violation (in his words):

"When I see ideas dying, it hurts. It feels like a tragedy... like a moral wrong, like an injustice."

What's dying? Ideas that could have been explored but weren't, because creators couldn't see what they were making in real-time. The gap between creation and feedback kills exploration.

Inferred V-V-V Focus Line:

"When the gap between creation and feedback causes ideas to die unseen, I design tools and environments that give creators immediate connection to their work, so creation becomes exploration rather than guesswork."

Breakdown:

Why this example matters:

This is what a principle-based Violation sounds like at full voltage. Bret doesn't say "delayed feedback is inefficient." He says ideas are dying and it feels like a moral wrong. That's the standard.

His design requirement:

"I will not build tools that separate creators from their creation. Every tool must provide immediate visual feedback."

This principle has guided 15+ years of work—from interactive design tools to research on dynamic media. The principle stayed constant; the vehicles changed.

---

Example 3: Patrick O'Shaughnessy (Inferred)

V-V-V Focus Line:

"When potential goes overlooked, leaving builders underleveraged, I spot and champion them—providing capital, platform, and network—so their work compounds and expands the positive-sum frontier."

Breakdown:

Note: This is an ARC-style inference based on expressed themes in the podcast, not a self-authored statement.

Example 4: Hypothetical (Educator → Consultant)

Generic Version:

"I help people learn complex topics through clear explanations."

V-V-V Version:

"When complexity obscures truth, causing insight to stay buried, I distill core principles into simple frameworks that make understanding click."

Breakdown:

Why better:

Common Failure Modes (and Fixes)

1) Violation becomes vague moralizing

Symptom: feels true but doesn't constrain action. Fix: force a design requirement ("A real solution must... I will not...")

2) Violation is just the problem repeated

Symptom: opening says the same thing twice. Example: "When people lack clarity, I create clarity." Fix: Violation \= what causes the problem, consequence \= what the problem causes

3) Vision is internal-only ("so I feel fulfilled")

Symptom: not vehicle-usable. Fix: Vision must be legible externally; internal fulfillment is implied.

4) Too vehicle-specific

Symptom: Only works in one narrow context. Example: "When startups lack product-market fit..." Fix: Generalize while keeping the charge:

5) Violation is actually a status preference

Symptom: shifts with trends; doesn't survive discomfort. Test: "Would you still tackle this if it didn't make you look good? If no one ever knew?"

If yes → principle. If no → status game.

6) Assuming the Violation must feel like moral outrage

Symptom: Client shows a clear, recurring response to a discrepancy but cannot connect with "violation" because the word implies anger or moral flinch. Fix: Test the deeper Tension: "Does this class of discrepancy reliably create force toward your characteristic response across contexts, vehicles, and time?" Moral outrage is one negative register. Engineering itch, structural recognition, design-sense wrongness, and positive possibility may reveal the same Tension.

Vehicle Engineering Implications

A vehicle is not "good" if it forces you to violate your principle—even if it pays well.

Vehicle Fit Check (Principle Version)

Ask:

  1. Does this vehicle make the Violation easier to fight or harder to fight?
  2. Does it reward solutions your principle demands?
  3. Does it force you to ignore violations you can't unsee?

Green vehicles amplify the principle by default. Yellow vehicles require constant self-policing. Red vehicles corrupt the principle (high drift risk).

Example: If your Violation is "When complexity obscures truth, causing decisions to drift," then:

Summary: What Changed

The Focus Line has three parts: Violation → Verb → Vision.

This V-V-V structure creates a complete narrative arc:

By upgrading from generic "problems" to principles-based Violations, and from transactional "payoffs" to aspirational Visions, the Focus Line becomes a higher-voltage compass that functions as both internal decision filter and external story.

Bottom line: A coherent direction needs a coherent Tension. The Focus Line communicates one story-facing expression of it: Violation → Verb → Vision.