Skip to content
tacometry

How this works

A build log and working field guide for one 2015 Tacoma in Juneau. 14 projects, planned through abandoned.

No figure appears unless it was measured or sourced

Every number that rolls up carries a confidence level. One that is not known yet reads as unverified, says what would close it, and is never counted in a total. Any unknown in scope makes a total a floor.

This matters most on payload. A budget that treats three unknown projects as weighing nothing reads as reassurance while being wrong.

Content is not presentation

Everything here is rendered from YAML at the root of the repository. A project is a directory with a project.yaml and up to five optional files. Adding one touches no code, and editing a step from a phone through GitHub’s web editor is a supported way to work. Model in docs/content-model.md, procedure in docs/adding-a-project.md.

Routes and recurring work

A project can fork on a decision: the power system is built in the cab or the bed, and that changes two of its twelve phases. Progress is keyed by step id, so switching routes never destroys a tick.

Maintenance has intervals rather than a sequence. Step completion is a list of dated records everywhere, so a checkbox and a service interval are the same shape.

Your build data never leaves your browser

Ticks, notes, route choices, prices and log entries are kept in this browser’s local storage and are never sent anywhere. No account and no server holds them, which is why it works with no signal. All of it exports as one file from your data, and log entries copy out as YAML ready to commit.

Visits are counted anonymously

We count visits with our own privacy-friendly analytics. It sets no cookies and stores nothing on your device; your IP address is used only to make a daily anonymous count and is never stored. To opt out on this site, open any page with ?ov_ignore=1.

What it is not

Not a substitute for the manual that came with your own hardware. Where a project was extracted from a source, what that source got wrong is written down rather than resolved silently.

Repository layout
content/
  vehicle.yaml            the truck
  taxonomy.yaml           categories, statuses, locations
  projects/<slug>/
    project.yaml          required
    phases.yaml           ordered phases and steps
    parts.yaml            specifications, not what you own
    reference.yaml        spec tables and wire schedules
    calculators.yaml      interactive tools this project mounts
    log.yaml              dated entries, committed
docs/
  content-model.md        the contract
  adding-a-project.md     the procedure
  projects/<slug>/        source material
apps/web/                 one renderer of all of it