Start one change
Tranche
Connect scope, lane, authority, completion criteria, and proof.
The toolkit / canon v1.11.0
Make the standard usable.
Start with one bounded change. Copy the records you need, fill them with project evidence, and keep authority clear.
Download the full reference ↓Capture evidence
Issue record
Preserve the observation, expected behavior, evidence, and unknowns.
Preserve decisions
Architecture decision record
Record context, alternatives, rationale, acceptance, consequences, and supersession.
Enforce decisions
ADR enforcement field
Connect each load-bearing invariant to its actual enforcing mechanism.
Track invariants
System invariant register
Keep current enforcement and open obligations visible across changes.
Transfer ownership
Handoff packet
Give the next role current state, evidence, boundaries, and acceptance conditions.
Prepare acceptance
Review pack
Present the outcome, exact revision, proof, limits, and requested promotion authority.
Keep the operator current
Executive check-in desk
One standing page of every open ask to the operator: decide, do, decided by the team, already answered. Built from a data file by a dependency-free renderer that checks it against the contract and computes the totals, so every project's desk reads the same. A broken file still shows every ask, with the repairs listed. Silence is never consent.
Start a role
Role brief
Onboard a role through authoritative references and living project state.
Connect a project
Agent entry fragment
Point a consuming project at Velocity and its local overlay.
Evolve the method
Process change proposal
Route a reusable process improvement with its evidence and authority owner.
Optional / v1.4
Agent evaluation pack
Qualify agent configuration changes against protected expected outcomes.
Optional / v1.4
Automation transition contract
Bind accepted artifacts and existing authorization to a bounded next action.
Optional / v1.4
Measured automation pilot
Compare delivery time, human effort, quality, and resource use.
Experimental / Entity
Work board
A living page of a project's active work for teams without a tracker: in motion, waiting, backlog, recurring controls, done with proof. Built from a data file by a dependency-free renderer, piloted on real work. Operator decisions stay on the check-in desk.
Experimental / Entity
Work management
The shared meaning of work states, so a board, a TODO file, or an existing tracker all say the same thing by “blocked” or “done.”
Experimental / Entity
Markdown work tracker
Keep a plain TODO file as the authoritative queue, under the same work contract.
Experimental / Entity
Project records file support
Guarded, recoverable updates to desk and board data by authorized agents, with views and complete export.
Experimental / Automation
Portable project records
Continue a project across agents, tools, and vendors: records the project owns, not an assistant's memory.
Experimental / Automation
Artifact index
One shared index of where each record lives, who owns it, and how it is updated.
Experimental / Portfolio, emerging
Decision levels
An optional tag for work, initiative, and portfolio decisions, on one desk.
Experimental / Portfolio, emerging
Decision and management records
Inherited context, opportunities, initiatives, and gates, used only where a decision needs them.
Experimental / Portfolio, emerging
Tracker binding and handoff
Move work between trackers without losing its meaning or its authority.
Adopt through your project.
Pin a Velocity release and define a thin local overlay. These are empty templates, not completed evidence or permission to act. Preserve links to the governing rules when adapting them.
One source of authority.
The downloads are convenience copies. Individual files resolve their canon links to v1.11.0; the full reference includes Markdown documents with their relative structure preserved. Read the standard before applying a template.
The three v1.4 automation templates are optional and informed by the credited playbook review. ADR recordkeeping builds on established practice. The automation example contains synthetic cases, not measured results.