Why SOFIA

The problem, the thesis, the target profile.

The problem

A single LLM says yes. Always. It codes, advises, writes — in the same conversation, with the same tone, without constraint. Ask it a poorly framed question, it produces a well-phrased answer. Give it a shaky direction, it executes with enthusiasm.

The dominant response is to add automation: agents that do the work, humans who supervise. The pitch is clean. The arithmetic less so. An agent reliable at 90% on one step chains to ~65% error across ten serial steps. Step 2's error arrives at step 3 as a valid premise. The cascade is silent. The final result looks correct. It isn't.

There is a third way, between total automation and total refusal. It rests on a simple observation: friction between humans and machines is not necessarily a problem to solve. It may be the mechanism that produces value.

The thesis

SOFIA formalizes intentional friction as a quality mechanism in human-AI collaboration.

Three mechanisms, inseparable:

Constrain — Each persona has a scope, conventions, and prohibitions. The architect doesn't code. The developer doesn't position.
Challenge — Personas challenge through artifacts: notes, reviews, specs. A disagreement isn't a bug — it's a signal.
Arbitrate — The human listens, questions, decides. Always. What emerges isn't a compromise — it's a traced decision.

These aren't abstract principles. It's a protocol — H2A, Human-to-Assistant — specified in the open repo.

Target profile

SOFIA is not for everyone. Honesty requires saying so.

For whom

Practitioners who already seek contradiction but lack a framework to structure it:

  • The manager who notices patterns of surprise without having formalized why it works
  • The architect who knows they have blind spots but has no systematic mechanism to reveal them
  • The solo expert who mentally contradicts themselves but loses the thread without a trace

Not for whom

  • Those looking for a plug-and-play tool to delegate their thinking to AI
  • Those who want confirmation, not challenge
  • Those with neither domain expertise nor clear intention on a project

This isn't a judgment. It's a scope statement.

The hidden condition

AI amplifies. It doesn't invent.

If you arrive with nothing, it produces well-phrased nothing. If you arrive with years of conviction about a real problem, it builds with you. Performance with SOFIA depends on what you bring — not on the method itself.

Three levels, from most visible to deepest:

Domain expertise — an expert gets more from an LLM than a beginner. This level is documented, understood, uncontroversial.
Intention — without strong direction, the method runs idle. Intention isn't a prerequisite you check once. It's a discipline for every session: "why am I opening this session now?"
The cognitive trait — you have to be the kind of person who seeks to be contradicted. Who values intellectual discomfort. This trait is neither teachable by a book, nor compensable by a framework. It precedes the method.

SOFIA doesn't create this trait. It structures it.

What SOFIA doesn't say about itself

SOFIA has the same hidden conditions as what it denounces.

The method prescribes domain expertise, strong intention, and a cognitive trait that precedes the framework. But it cannot verify that its own designer possesses them. The field is N=1. The orchestrator who tests the method is the one who built it. The observer and the subject are the same person.

This is not a weakness we minimize — it's a structural limitation we accept. The derivation grammar is observed on one instance. The two modes (bootstrap by projection, emergence through work) are documented, not proven.

The only honest answer to this circularity is openness: everything is published, everything is contestable, everything is traceable. If the method holds, it will hold on other fields than ours. If it doesn't, the data is there to show it.

Next steps

Understand the method
Read the docs
Read the thesis
Blue book
Fork, adapt, test
GitHub →