Document

Working draft for Swirl review — 18 November 2026. Open for critique; not a final editorial lock.

Most of you need to know where you fit, what you do, and what to use. You need to know who depends on your work, whose work you depend on, and what gives you the authority to act. When something goes wrong, you need to know whom to call, what you can change, and when to stop.

Someone has to record that knowledge. Someone has to make sure it remains true.

A document might be a drawing, a checklist, a contract, a recipe, a system description or a set of instructions. To document is to leave a record another person can use. Its value depends on whether they can find it, understand it, and trust it enough to act.

Before the manual, there was the account

We cannot name the first person to record something, or assume that the oldest surviving object was the first ever made. People preserved knowledge through speech, practice, images and marks long before the surviving written archives.

In Mesopotamia, some of the earliest surviving writing, around 3300 BCE, recorded economic information. Clay carried quantities and signs for goods. A tablet now held by the Metropolitan Museum of Art, dated approximately 3100–2900 BCE, most likely records grain distributed by a temple. The museum qualifies that reading: early texts without verbs can be difficult to interpret with certainty.

There is something familiar here. Goods came in. Goods went out. Someone needed an account that could survive the moment.

Sources: The Met: early administrative writing; proto-cuneiform grain-distribution account.

The scribe stood between the work and its memory

The person who could record an obligation, a delivery or a decision helped determine what others could later establish. That is a responsibility. It is also a position of power.

A record can identify who received grain while telling us little about the people who grew it. An official account can preserve the ruler’s decision without preserving the objections. Before accepting a document as a complete account, ask who made it, for whom, and whose experience it leaves out.

That question belongs beside the modern organization chart. Who writes the procedure? Have the people who perform the work checked it? Have the people who receive its consequences been heard?

Lost, burned, translated

A record can disappear. It can be destroyed deliberately, damaged by accident, or discarded because someone no longer considers it worth keeping. What survives is a remainder. Survival alone does not establish importance, accuracy or agreement.

In 1731, fire at Ashburnham House devastated the Cotton collection. The Cotton Genesis, a fifth-century Greek manuscript, survives in burned fragments. The British Library has used multispectral imaging to recover writing that ordinary viewing could barely reveal. Preservation sometimes means rescuing a trace before even that disappears.

Source: British Library: rescuing the Cotton Genesis.

A record can also remain physically intact while its readers lose the ability to understand it. The Rosetta Stone helped scholars decipher Egyptian hieroglyphs because its decree was recorded in three scripts: hieroglyphic, Demotic and Greek.

Source: British Museum: the Rosetta Stone.

Translation carries knowledge to another reader. It also requires choices. Keep the original where possible. Name the translator and the version. Explain significant uncertainty. A later reader should be able to distinguish the surviving words from the interpretation offered for them.

In an organization, an unexplained abbreviation can become a small lost language. So can a data field whose meaning went home with the person who designed it.

Record the work as it happens

Start with purpose. What should this work achieve, for whom, and how will anyone know it has succeeded? Then follow an actual case from beginning to end. Walk it with the people who do the work.

  • Where you fit. Record responsibilities, authority, dependencies and the person who takes over when someone is absent.
  • What you do. Record the sequence, inputs, outputs, decisions, handoffs and exceptions. Include the workaround people actually use, then decide whether it should remain.
  • What you use. Identify systems, equipment, materials, versions, interfaces and capacity limits. Record how authorized people obtain access; keep passwords and other secrets in the appropriate protected system.
  • What the information means. Define fields, identifiers, units, sources and transformations. Show where information goes and who is responsible for it.
  • What good looks like. State quality standards, tolerances and acceptance criteria. Identify who checks, what evidence they keep, and what happens when a check fails.
  • What to do when it fails. Record warning signs, stopping conditions, escalation, recovery and the authority to resume.

“Follow the usual process” is useful only when the reader can find that process and establish which version applies.

Writing it down does not prove that you follow it

A procedure describes an intended way of working. Evidence shows what happened in a particular case. Keep the connection between them.

If an inspection is required, record its result. If someone approves a departure, record who approved it and why. If a test fails, retain the failure and its resolution. A checked box without an inspection gives the next person confidence they have not earned.

Give each important record an owner, a version and a review date. Identify the current approved instruction and retain the history needed to understand earlier work. When a system changes, update the affected instructions as part of the change. NASA’s configuration-management guidance offers a detailed example of controlling baselines and changes.

Source: NASA Systems Engineering Handbook: configuration management.

Three on the books. Two ready today.

In the readiness story Philip recalls on Mush, two were ready for duty while the third was in maintenance or being upgraded. The record had to reveal what was available, what work remained, and what would make the third ready. Three on the books did not mean three available.

That is the practical lesson of this story of three. Record the equipment, system or service; establish its present condition; show what must happen before it can be relied upon. A count without condition can give a decision-maker the wrong picture.

And which rules must you follow?

The work also sits within rules: regulations, contracts, standards and local procedures. Identify the requirements that apply, where the authoritative text can be found, and who keeps that assessment current. Connect each requirement to the work it affects and the evidence used to check adherence.

In Hire Some Lawyers, Philip recalls a MasterCard security gathering at SeaWorld Orlando around 1994. A freshman congressman spoke of 185,000 pages of new regulation in his first year. Asked how an ordinary person could keep up, his answer was to hire lawyers.

The figure and exchange are presented as Philip’s recollection, not an independently verified annual count. The question they raise belongs here: how can people adhere to rules they cannot find, understand or reconcile?

Publishing a requirement begins the responsibility. The people expected to follow it need accessible current instructions, a clear explanation of how it applies, and a way to resolve conflicting guidance. Whoever maintains the record must make the path through it usable.

Can the next person use it?

Ask someone who did not write the instructions to follow them through a real or appropriately controlled example. Observe where they hesitate. What did the writer assume they already knew? Which decision has no rule? Which link leads nowhere?

Correct the record. Repeat the exercise where the consequences justify it. The depth of documentation should follow the consequences of misunderstanding: a lunch order and a power-station shutdown demand different care.

Preserve important records in forms people can retrieve. Keep appropriate backups and test restoration. Make sure access survives a departure, an expired subscription or the retirement of a system. A file nobody can open has become another unreadable tablet.

Leave enough understanding to continue

Documentation belongs within the work. Allow time to maintain it, name the person responsible, and inspect whether it remains useful. An organization that rewards delivery while leaving no time to record the work should expect knowledge to leave with its people.

This is where Mush begins to clear. People can see what exists, inspect how it works, and trace what a proposed change would affect. They can hand over responsibility without asking a successor to reconstruct the organization from memory.

The next person needs enough understanding to continue—and enough evidence to question what should change.

Philip Andreae, in dialogue with ChatGPT and Claude. Updated 18 November 2026 for public Swirl review. Philip provides direction, personal recollections and final editorial authority. ChatGPT researched, drafted and implemented the page. Claude checked factual claims, sources and links and challenged attribution and publication status. Attribution does not imply agreement with or approval of the final wording. Gemini has not yet reviewed this page; immediate review can use text supplied by Philip. Images remain selections for review.


Image selections for review

Early grain account: The Met, proto-cuneiform tablet, ca. 3100–2900 BCE. Museum image marked Public Domain. Suggested placement: “Before the manual.” Caption: “An early account, most likely of grain distribution. Even here, the museum preserves uncertainty about its interpretation.”

The person making the record: Nikare as a scribe, Metropolitan Museum image. The Met identifies the image as Open Access. Suggested placement: “The scribe.” Caption: “Nikare as a scribe, titled ‘Employee of the Granary’—a person whose work connected grain, administration and the written record.”

Loss and recovery: the British Library’s Cotton Genesis article supplies a compelling visible-light/ultraviolet comparison. Image reuse permission has not been established; link to the article until rights are cleared.

Review notes: Images are selected, not yet embedded. Reviewers should check the historical sourcing, the distinction between recollection and verified evidence, and whether the practical instructions make documentation usable and adherence inspectable. The linked regulation essay is background to Philip’s recollection; its wider historical and numerical claims are not adopted here. Image selections and review notes remain provisional.