A.N. Creation revision control. Human lesson: https://ancreationoffice.com/revisions.html Purpose. Explain version control before introducing tools: preserve earlier versions, identify what changed, know what is approved for a particular use, and know which version each recipient actually had. Use plain revision numbers (Rev 1, Rev 2, Rev 3) unless the project already has another convention. This routine applies with or without Git. Tool setup remains at https://ancreationoffice.com/version-control.txt . Identify each item. Assign a stable item/document name or ID and an owner. Number successive revisions consistently, optionally zero-padded in filenames, and show the revision inside issued documents or drawings so printed or forwarded copies remain identifiable. Preserve supplier/customer identifiers and revision conventions; record mappings instead of renaming issued originals. PROJECT.txt and plan.md retain their stable working names. Do not renumber every item when only one changes. Separate draft, approved-for-a-use, and sent. These are distinct facts. A later draft does not supersede an approved revision simply because its number is higher. A quote request is not authorization to manufacture. Record approval status, reviewer, date and intended use only from actual evidence. Unknown status stays unknown. A commit, filename, checked box, or bot statement alone is not approval. Manual workflow. Save revisions as item-rev01, item-rev02, etc. Keep working drafts in a working area with unique identifiers such as item-rev03-draft-01 and draft-02. Preserve meaningful checkpoints rather than issuing a new revision for each keystroke. Before sharing or approving anything, freeze the exact files, even when shared only for draft review. Never silently alter or overwrite an issued/shared copy, reuse its revision for changed content, or discard superseded versions. Continue edits in a new revision or uniquely identified draft. Mark superseded status in the log without changing the preserved issued file. Keep the original editable source and applicable exports, with an exact file list, in their subject area. Keep large technical packages in technical/releases/; small release manifests in shared/releases/ link to them. Back up manual history as well as current files. Revision log. b-project-manager maintains shared/releases/revision-log.csv (or an existing agreed equivalent), with specialist updates. Record item ID/title, revision or shared draft ID, previous revision, date, change summary and reason, responsible owner, status, reviewer/approval date/intended use when known, exact preserved file/package paths, Git vault/commit when used, and evidence. Give every meaningful issued revision and every shared draft a retrievable record. Add superseding/replacement references and dated status changes without erasing the original issuance or approval evidence. Changes are coordinated with the owner rather than overwriting each other's records. Handoff log. b-project-manager maintains shared/handoffs/handoff-log.csv (or equivalent). For each actual transmission, record a handoff ID, date, sender, named recipient/organization, purpose, exact item/revision or immutable package manifest, preserved files, and sending evidence. Log confirmed receipt separately, including date/evidence, and record which revision the recipient confirms using. Prepared, sent, received, reviewed and approved are distinct; do not infer one from another or fabricate past distribution. When evidence is missing, mark it unknown. Do not send material merely because a log entry is being prepared; existing user authorization rules still apply. Before a conversation. Explain the common mismatch: a file has gone back and forth, the vendor has Rev 3, and the person has Rev 5. They disagree because they are describing different revisions. State the intended revision and ask, "We are on Rev 5. Do you have a copy of that?" Have the recipient check the revision on the actual file they opened. If it differs, arrange the authorized replacement and confirm the matching file is open before discussing details. Keep the older revision as evidence of the prior conversation or quote. Look up the recipient's last known handoff. Retrieve its exact saved revision, compare it with the current approved revision, and identify relevant changes. Ask which version the other person is using if not confirmed. Save the answer and the relevant meeting/email evidence. Never assume an old quote, approval or manufacturing instruction applies to a newer design. When a replacement is authorized, explain what it replaces, retain the original handoff, and track affected recipients and outstanding acknowledgments in the log and plan.md. A log can establish what was sent; it cannot prove what a person read without evidence. Multiple revision levels. Items advance independently. Budget Rev 7, enclosure Rev 3, bracket Rev 5 and test plan Rev 2 may belong to one package. A reviewed release manifest lists their exact identities, revisions, file paths, purpose, reviewer and evidence; no ambiguous 'latest' links. The engineering role verifies CAD models, native sources, exported drawings, dimensions and related technical files are compatible with that package. Do not force unrelated documents to share a revision number, or infer compatibility solely from matching labels. The prototype role and b-project-manager use the identified package revision for prototypes, tests, quotes and production preparation and report mismatches. Record which revision was actually built or tested. With Git. Map issued revision labels to exact repository paths and commit IDs (and tags when used). Preserve actual large-file objects and verify the files can be retrieved. Ordinary commits may be working checkpoints rather than approved releases. Keep human-readable revision labels in outgoing files and maintain the distribution/review logs; Git cannot supply those facts automatically. Follow the existing cross-vault manifest rules, avoiding a manifest that attempts to contain its own future commit hash. Review an older revision in a separate retrieval location without replacing current work. If reverting to an older design, make a new documented decision and revision that cites the source; preserve intermediate history rather than resetting or rewriting it away. Templates. Blank CSV headers are at https://ancreationoffice.com/revision-log.csv and https://ancreationoffice.com/handoff-log.csv and included in the starter ZIP. Reuse populated records; do not overwrite them with templates. Capture facts as work happens; do not block the inventor's first conversation on filling empty logs. Record deferred review, missing revision evidence, and outstanding handoffs in b-project-manager's plan.