13.8 — Building a Code You Can Actually Keep

Seven chapters of theory, and this is where it becomes something you write down.

And the reason to write it down is specific: you will not construct it in the moment. Every chapter in this Part has said the same thing — 13.7's line decided in advance, 3.9's room, 8.6's rule made before the moment. A code is what you have when your judgement is compromised, and your judgement is compromised exactly when it matters.

What a usable code is not

Three failures, and they are why most attempts collapse within a month.

Not a list of virtues. Be honest, be kind, be courageous. Nobody has ever changed as a result of writing that down (8.11, 13.4).

Not a comprehensive system. You are not going to derive your conduct from first principles at the moment of decision, and a code that requires you to is a document rather than a tool.

And not aspirational. A code you cannot keep is worse than none, because breaking it teaches you that your commitments are decorative.

What it is

A short list of specific commitments, in the situations you actually meet, that you can keep on a bad day.

Five parts.

Part one: the lines

Three to five things you do not do, stated as behaviours, with no exceptions clause.

These are 13.3's constraints: not absolutes, but things that do not get entered into the calculation — because the calculation is where the manipulation happens.

Examples of the right shape:

I do not say things about people that I would not say in front of them.

I do not agree to something in a meeting that I intend not to do.

I do not present a number I know to be wrong, however it is framed.

I do not raise my voice at anybody who cannot raise theirs at me.

The test of a good line: it is checkable by somebody else, it names a behaviour rather than a quality, and you can tell within a day whether you broke it.

Part two: the tests

Three questions to run when the situation is unclear, taken from the best of this Part.

Could I tell them exactly what I am doing and why? (10.9, 13.6.) The strongest single test in this volume, and it catches manipulation, deception and using somebody, all at once.

Who pays if I am wrong, and did they get a say? (2.5, 8.3, 4.10.) The question that separates a hard duty from an imposition, and the one Rama fails in 2.15.

And what will this look like in the harshest accurate description? (2.4.) **Not the softened version — the version somebody who dislikes you would give. If you cannot say the harsh version out loud, do not do the soft one.

Part three: the exception procedure

Because you will break a line, and the question is what happens then.

From 4.11, and this is the part almost no personal code has and every one needs.

Who benefits? A rule broken for somebody else's protection is a different act from one broken for your own advantage.

Will I say out loud that I broke it? Not redefine it. Yudhishthira's whispered "the elephant" is the corrupt move, not the lie (3.14). A breach acknowledged leaves the rule standing; a breach smuggled in under a redefinition destroys it.

And will I take the charge? A person who breaks a rule and then argues they should not be held to it has made a new rule that suits them.

Write these three into the code explicitly. A code with no exception procedure will be broken silently, and then it is gone.

Part four: the standing commitments

Two or three things you do, on a schedule, regardless of how you feel about them.

This is 9.7's obligatory action and 12.7's finding: the practice has to be unconditional or it stops within a month.

And they should be small. A weekly call. A fixed proportion given, decided once. The daily audit (8.11). Fifteen minutes of attention practice (6.9).

One or two, kept for a year, is worth more than eight kept for six weeks.

Part five: the review

Because a code with no review is a document.

Daily, five minutes (8.11): which of the six enemies was running, where specifically, what did it cost, one behaviour, and what went well.

Weekly, ten minutes: did I hold the lines? Is there anybody who has been trying to tell me something? What is the exit price on the thing I am avoiding, and has it gone up? (8.10.)

And annually: re-read the code and ask whether it still fits the life you actually have. A code written for a life you no longer live is 3.2's vow, and taking the release when it is offered is the correct move.

The whole thing, assembled

A worked example, for shape rather than for copying. Yours will be different and should be.

Lines. I do not say about people what I would not say to them. I do not commit to something I do not intend to do. I do not present a number I know is wrong. I do not go silent in a room where somebody is being treated badly in front of me.

Tests. Could I tell them exactly what I am doing and why? Who pays if I am wrong, and were they asked? What is the harshest accurate description of this?

Exceptions. If I break a line: who benefits, I say it out loud, and I take the consequence.

Standing commitments. The daily audit. A fixed proportion given, decided once a year and not renegotiated. One person contacted every week who has nobody else contacting them.

Review. Five minutes daily. Ten minutes weekly. An hour a year.

That is a page. It is not a philosophy and it is not supposed to be.

Why this works when resolutions do not

Four reasons, and they are the same ones this whole volume has been giving.

It is behavioural rather than dispositional. You can check whether you did it (13.4, and Volume VI).

It is decided in advance of the compromised state (8.6, 13.7).

It is short enough to hold in mind. A code you have to look up is not operating at the moment you need it.

And it has a procedure for its own failure, which is what stops a single breach becoming an abandonment.

The last thing

And it is the point of the whole Part.

**A code is not for being good. It is for being predictable to yourself.

Nearly every catastrophe traced in this volume — Ravana, Duryodhana, Bhishma, Karna, Dhritarashtra, the hall in 3.9 — happened to somebody who did not know in advance what they would do and found out in the moment, badly.

The purpose of writing it down is that when the situation arrives, the decision has already been made by a version of you who was not under pressure, was not humiliated, was not afraid, and had time.

That version of you is more trustworthy than the one who will be there.

What to carry from this page

Three to five lines, stated as behaviours, checkable by somebody else.

Three tests: could I tell them; who pays; and what is the harsh version.

An exception procedure, written down, because you will need it — who benefits, say it out loud, take the charge.

One or two standing commitments, unconditional and small.

And a review that actually happens.

Write it this week. One page. It will be wrong and you will revise it, and having a wrong code you revise is a completely different condition from having none.

Next: Part 14 takes the subject everything in this volume has been circling — what to do about the fact that it ends.