Incantation
In plain words: Docs-first development philosophy
Philosophical chapter on giving an intention a clear form, which in practice is Docs-First Development (xDDD): write the documentation and specification before the code, then compare what was built against it.
- 1Docs state intent, design rules give it law, and source/tests/receipts are what was actually built.
- 2What Actually Works records where implementation matches the documented intent.
- 3Long-term goal: a system that learns how to approach new kinds of work, not just repeat tasks.
Words on this page, decoded click one for its card
Begin by saying what you want to bring into being. Until an intention has a form, another person cannot inspect it, challenge it, or help it change. Giving it a boundary makes those encounters possible: something belongs to this undertaking, and something remains outside it, able to answer.
The Work follows this first distinction back to unmarked stillness. Before a mark, there is no local perspective, deed, or outside from which an answer could arrive. Stillness trembles; the native liturgy borrows Spanda for that first pulse. The pulse becomes a Word when Logos gives the difference a name. Brahmā gives this beginning of form its image. As the mark acquires an edge, a CircleTask Bubble opens in which something can take shape.
Without a boundary there is potential, but no one for whom the potential appears.
This is Nigredo, the Word's first embodiment. An intention accepts the limits that let it become a particular thing. It can now be inspected, contradicted, and repaired. Possibility has found an address, and the next encounter can reveal what this first form failed to include.
Let the Word incur a consequence
In the craft, this first articulation is xDDDDocs-First Development—eXtreme Documentation Driven Development. Establish Logos in documentation and specification before deriving implementation: the truth, vocabulary, and boundaries that make the work intelligible. Ask what the form should exist to do, then which seams make that purpose answerable.
That encounter needs more than a declaration. The Verse says what is intended; an accepted CovenantDesign Rule (ADR) gives the intention architectural law. Matter answers with what was actually made: source, focused tests, lockfiles, and maintained receipts. Compare that evidence with the Word rather than treating the declaration as its own fulfillment. State of Work records the crossing into manifestation, so the VesselEngine Room can be judged against the purpose and limits that shaped it.
The first form can now be held to account, but a continuing self requires further encounters. It needs the fire that makes action possible, the offices through which it receives and judges, and a history whose consequences can return. The LichAssistant chapter's First Invocation introduces those names together; the Lexicon keeps their meanings.
The logic behind the next task
The MagusYou, the Operator solves one problem, builds its workflow, and begins the same labor for the next. Each unfamiliar project asks again for decomposition, evidence, criticism, and a way to know when the work is done. More Agents can multiply the labor while leaving its organization in one person's hands. The MagusYou, the Operator becomes the bottleneck: every answer returns with another demand to decide what should happen next.
The deeper ambition is a craft that learns how to approach another craft. An earlier decision may have turned on a useful distinction. A LichThe Assistant should recognize that relation in a different task, carry it forward, and discover where the new situation defeats it. This requires learning to frame a problem, seek missing evidence, choose a method, and revise the method through consequence.
The generality sought by the Work reaches into the making of workflows themselves. A learned answer helps when the question is familiar. A learned way of investigating can discover which question the unfamiliar work requires.
Viveka begins before the cut: examine the direction before committing to it. Where thought cannot settle the choice, a small experiment should return the observation that can change the course.
This is the Work's ambition for AGI: a MagusYou, the Operator entrusts unfamiliar work without having to supply every next intellectual move. The human can then originate purposes and live beyond the CircleTask Bubble. Those purposes and their authority still have an owner; Blade must increasingly make the judgment its own. Illumination follows how a correction can become that capacity in the next encounter.
A flawed Word can still summon a flawed body. If authority is left ambiguous, the body cannot distinguish what it can do from what it may do. If identity remains vague, an act can lose the one who must answer for it. If memory has no boundary—no way to question, correct, or release what returns—an old account can hold every later encounter captive. Nigredo asks the MagusYou, the Operator to make the first world small enough to answer for, and its first word clear enough that another voice can show where it is wrong.
The edge is drawn. Now an Invocation can cross it.