The commercial facts an agent cannot read from a repository, and the decisions that go wrong without them.
Project root starter
Every rootnote in the library: the commercial, privacy, documentation, design and editorial context an agent cannot read from the code.
Assumes:A project an agent will work in. Nothing about language, platform or size. Several documents share fill-in fields, so answering once applies across the set.
9 of these have fill-in fields. This pre-built archive ships them unfilled, because it is generated once for everyone. To get copies with your own values already in place — asked once per field, applied across every document that uses it — build this selection yourself.
Download 9 documents + MANIFEST
Contents
What counts as personal data, where it must never end up, and the changes that quietly widen what you hold.
A linked set of documents with defined sections and relationships, rather than one long file that narrates the code.
Why an agent drifts a visual language one plausible value at a time, and the rules that stop it.
Voice, mechanics and error-message rules, and why inconsistent terminology costs more than any single bad sentence.
The conformance level, what gets verified and how, and the failures an agent introduces without noticing.
Why concatenating a sentence breaks translation, and the assumptions in code that only hold for one language.
What may be run without asking, what must stop first, and how to report what actually happened.
Stop the bleeding before diagnosing, record while acting, and the autonomy rules that matter most when they are under pressure.
MANIFEST.md
Shipped inside the archive. Reproduced here so you can read it before downloading.
# Project root starter
Every rootnote in the library: the commercial, privacy, documentation, design and editorial context an agent cannot read from the code.
Source: https://the-handover.org/packs/project-root-starter
Built: 2026-08-29
Documents: 9
Licence: Handover-1.0 (© Captivated Ltd) — https://the-handover.org/licence
## What this pack assumes
A project an agent will work in. Nothing about language, platform or size. Several documents share fill-in fields, so answering once applies across the set.
## Fill-in placeholders
9 document(s) in this pack contain placeholders that have not been
filled in. They are written as double braces and are safe to leave — but they are
meant to be replaced with values for your project.
Either replace them by hand using the list below, or rebuild this selection at
https://the-handover.org/build, which asks once per field and applies each answer across every
document that uses it.
- docs/business-context.md
{{legal_entity}} — Legal entity
{{jurisdiction}} — Primary jurisdiction
{{default_visibility}} — Default visibility of work
- docs/data-handling-and-privacy.md
{{jurisdiction}} — Primary jurisdiction
{{retention_default}} — Default retention
{{data_residency}} — Data residency requirement
- docs/documentation-standard.md
{{docs_path}} — Documentation directory
{{spelling_variant}} — Spelling variant
{{link_style}} — Link style between documents
- docs/design-system-context.md
{{tokens_path}} — Design tokens source of truth
{{accessibility_standard}} — Accessibility standard
- docs/language-editorial-guide.md
{{spelling_variant}} — Spelling variant
{{heading_case}} — Heading capitalisation
- docs/accessibility-commitment.md
{{accessibility_standard}} — Accessibility standard
{{assistive_tech_support}} — Assistive technology commitment
- docs/multi-language-support.md
{{source_locale}} — Source locale
{{supported_locales}} — Supported locales
- docs/working-agreement.md
{{branch_model}} — Branching model
{{review_requirement}} — Review requirement
- docs/operational-runbook.md
{{escalation_path}} — Escalation path
{{failure_signal}} — How you find out something is wrong
## Contents
### docs/business-context.md
Title: Business context for an agent working on commercial software
Summary: The commercial facts an agent cannot read from a repository, and the decisions that go wrong without them.
Authors: Leon Mallett, Founder of Captivated Ltd (captivated.online)
Source: https://the-handover.org/docs/business-context
Last confirmed working: 2026-08-14
SHA-256: 5e5053a53a22d383d51b62b70a6dcaffc65356a9477122d281c3911a64a0035c
### docs/data-handling-and-privacy.md
Title: Data handling and privacy for an agent working with real data
Summary: What counts as personal data, where it must never end up, and the changes that quietly widen what you hold.
Authors: Leon Mallett, Founder of Captivated Ltd (captivated.online)
Source: https://the-handover.org/docs/data-handling-and-privacy
Last confirmed working: 2026-08-21
SHA-256: 4f0cebbddf9ed095f26dd81cf851666012e89f6949435bade763cdf0f40ff177
### docs/documentation-standard.md
Title: Documentation standard for agent-maintained projects
Summary: A linked set of documents with defined sections and relationships, rather than one long file that narrates the code.
Authors: Leon Mallett, Founder of Captivated Ltd (captivated.online)
Source: https://the-handover.org/docs/documentation-standard
Last confirmed working: 2026-08-25
SHA-256: e8c425c4a5318899c1b26a76a7d1b65386d906a21cf9d25eea8ec28547ad615f
### docs/design-system-context.md
Title: Design system context for an agent building interfaces
Summary: Why an agent drifts a visual language one plausible value at a time, and the rules that stop it.
Authors: Leon Mallett, Founder of Captivated Ltd (captivated.online)
Source: https://the-handover.org/docs/design-system-context
Last confirmed working: 2026-08-15
SHA-256: 33ff04ef8ee28391480a5c7500f68fa95c3b1ab0813de3278c0addabd668e87c
### docs/language-editorial-guide.md
Title: Language and editorial guide for agent-written copy
Summary: Voice, mechanics and error-message rules, and why inconsistent terminology costs more than any single bad sentence.
Authors: Leon Mallett, Founder of Captivated Ltd (captivated.online)
Source: https://the-handover.org/docs/language-editorial-guide
Last confirmed working: 2026-08-15
SHA-256: 99b7a464b4400a03f6b7a7a2826399d97f4b89e53982a6375b1953b852a607b2
### docs/accessibility-commitment.md
Title: Accessibility for an agent building and testing interfaces
Summary: The conformance level, what gets verified and how, and the failures an agent introduces without noticing.
Authors: Leon Mallett, Founder of Captivated Ltd (captivated.online)
Source: https://the-handover.org/docs/accessibility-commitment
Last confirmed working: 2026-08-21
SHA-256: 336bd4cca71d0831ea8b59e24ec0b2eb457f4a52010c869b8b4d24d665c92899
### docs/multi-language-support.md
Title: Multi-language support for an agent writing interface code
Summary: Why concatenating a sentence breaks translation, and the assumptions in code that only hold for one language.
Authors: Leon Mallett, Founder of Captivated Ltd (captivated.online)
Source: https://the-handover.org/docs/multi-language-support
Last confirmed working: 2026-08-21
SHA-256: c5fa2f38b910f4fc86ee3d144e3e5c53d52a25193c76c9cb0edc8ee3f1ad8ff5
### docs/working-agreement.md
Title: Working agreement for an agent in this repository
Summary: What may be run without asking, what must stop first, and how to report what actually happened.
Authors: Leon Mallett, Founder of Captivated Ltd (captivated.online)
Source: https://the-handover.org/docs/working-agreement
Last confirmed working: 2026-08-26
SHA-256: 547496ff31226d04225b371917295b9002f331fc862eb21810607b84a66b1d37
### docs/operational-runbook.md
Title: Operating something that is live, and what an agent may do during an incident
Summary: Stop the bleeding before diagnosing, record while acting, and the autonomy rules that matter most when they are under pressure.
Authors: Leon Mallett, Founder of Captivated Ltd (captivated.online)
Source: https://the-handover.org/docs/operational-runbook
Last confirmed working: 2026-08-26
SHA-256: 15d493f980788eff6069811874e50a6f112e59c479a16b5094aab85b69b0bb9b
## Licence and attribution
Copyright is retained by the authors and Captivated Ltd. You may use these
documents in your own projects — private, public, commercial, client work —
and adapt them to fit. What is reserved is republishing the collection as a
collection: mirrors, or catalogues assembled out of these documents.
Each file carries an attribution header naming its authors, its source and the
date it was last confirmed. Keep it: once a file has been separated from this
pack, that header is the only thing that still credits the person who wrote it.
## Verifying this pack
Each SHA-256 above is of that file exactly as it appears in this archive. Verify one
with `shasum -a 256 <file>`; a file whose hash does not match was modified after
packaging.
Document files are byte-reproducible: the same source document, at the same
confirmation state, always produces the same bytes. The archive as a whole is not,
because this manifest records the build date above — two builds on different days
differ in that line and therefore in the archive, while every document file inside
stays identical. The per-file hashes are the thing to check.