Skip to content
DoculateBack to home

Writing

Notes on building Doculate

Design decisions behind an engine that has to show its working. Mostly about provenance, versioning, and the places where a shortcut would quietly cost you the ability to prove anything.

  1. 01How do I tailor my CV to a job description?Match the job’s requirements to your actual experience, bring relevant evidence forward and save a separate CV for the application.6 min read
  2. 02Why a citation should point at a rectangle, not a documentA useful citation identifies the exact page and rectangle that supports a claim, while the original source stays unchanged.5 min read
  3. 03A document version that changed without the text changingStable block identity and source-aware diffs expose evidence changes that a content hash alone cannot see.5 min read
  4. 04The wall between what you cite and what you claimReference material can be cited for what it says, and still never become evidence about the person using it.5 min read
  5. 05A guard that rejects its own model’s outputDoculate checks drafted claims against cited evidence and rejects unsupported numbers, dates, quantities, and proper nouns.5 min read