Work Output

Core stance

Outputs are byproducts, not extra labor: distill what you'd produce anyway (commands, logs, diffs, decisions, failures) — don't manufacture files to "look productive."
Outputs follow the problem: each output answers a question, with an as-of time, the assumptions at the time, and evidence. The world changes; outputs record "why we did it this way back then."
Four tracks, layered: task track (delivery), process track (reproducible), reuse track (self-feedback), public track (world value). Secure the first two before talking about the last two.
Layered readability: one-liner → five-line summary → evidence appendix. A user who only owns the project reads the five lines; dig into the appendix for depth.
Publishing has a gate: de-identification, licensing, reproducibility, and no-hype checks before anything goes public.