Documentation you can hand over.It stays in the repository.

Charter writes architecture, decisions, API, and security notes from the code, in the standards a client already expects.

I already looked.
0:00 / 0:00

An ADR, ready to send.

One decision, the options, and why this one won. It is a file in the project, so the handoff is the repository.

docs/adr/0014-session-store.md

Decision

Sessions live in the Postgres database the deployment already runs.

Options

Postgres, or a separate Redis. Redis lost because a client handoff should not add a second store to back up.

Status

Accepted. The note at the bottom was written by the team, and it stays when the page is updated.

Every codebase keeps its own documents.

  • docs/architecture.mdarc42, taken from the modules that are there.
  • docs/api.mdThe routes the code actually registers.
  • docs/security.mdThe controls the repository can show, including the compliance notes you keep beside them.
  • docs/onboarding.mdHow a new person, or a client, starts.

A later change marks the pages that depend on it. The others are left alone. A draft is built from the evidence for that page, so the model is not sent the rest of the repository.