Tony, this isn't a critique. It's a mirror. Pulled from your Drive: handoff docs, system protocols, brand briefs, the queso run, the soaking essay reviews. A few signatures repeat enough to count as a voice. Here they are.
You write like a systems architect with a poet's ear — the prose is technical, terse, bullet-forward, and metadata-aware, but the framing, naming, and metaphors betray someone who treats infrastructure as a creative medium and language as load-bearing material.
Almost every doc opens with a structured header: Status, Owner, Version, Created, Last Reviewed. You don't begin with a sentence; you begin with a schema. The reader is oriented before the prose starts.
You don't explain what something is; you state what it does and what it forbids. "The missing modern layer is not more buckets; it is a routing protocol." Short. Declarative. Built to be quoted back.
You don't bullet *after* writing — you bullet *instead of* writing. Paragraphs appear only to set frame; the work happens in lists, tables, and short imperative lines. Density without thickness.
You name things with weight: TOEKS NAS, STROKE_BOT, ANCHOR_BOT, SEMISTRY, K|A System, SETT.LIFE, 24W.IN. Capitalizations, separators, and orthography all carry signal. The name is the brand is the spec.
System voice: sysadmin, no hand-holding, "Lock the doors," "Protect the data." Brand voice: tender, intentional, philosophical — "consent-forward," "people who take connection seriously." You don't blend them; you switch them.
You don't use semicolons. You don't use parentheses much. You use the em-dash — to define, to pivot, to interrupt — and you use it more than most writers do. It's the printed equivalent of voice memo cadence: thinking out loud, on the move.
You frame what something isn't before you say what it is. It's a rhetorical move that earns trust by clearing space.
Phases get sticky two-word titles. Not "Phase 1" — "Lock the doors." Not "Phase 2" — "Protect the data." Memorable, kinesthetic, slightly cinematic.
When you list, you don't just list. You add a target column. "Should be zero." "Should be rare." "Should be flagged." Every line is a check, not a note.
Some lines you decide not to vary again. "Outside of my nonprofit work…" You mark these as canonical, set them once, defend them after. Brand as version control.
Materially unique outputs end with a one-line origin stamp — date, system, source, attribution. It's not a footer. It's a chain-of-custody.
Soaking is not a metaphor for connection; it's the practice. SETT.LIFE isn't *like* a settlement; it's the architecture. You don't dress ideas in figurative language — the figure is the spec.
Tap to check. These are diagnostic, not commandments. Some pieces should fail some of them on purpose.