State assumptions
Name the environment, actors, data classes, volume, consequence, and operating boundary. A diagram without assumptions is decoration.
PUBLICATION METHOD
Trace the system. Force the failure.
Every technical note begins with a bounded job and follows data, authority, state, evidence, failure, and recovery through the system.
Show the contract
Identify typed input, structured output, authorization, idempotency, audit, retention, and the interface where a failure becomes visible.
Test the edges
Use invalid, missing, contradictory, repeated, unavailable, unauthorized, and rollback cases before treating the happy path as evidence.
Separate fact from judgment
Product behavior and primary documentation are dated. Design choices are identified as recommendations with their tradeoffs.