Technical notes that preserve primitives and assumptions

Mechanism

Useful notes explain why a technique works and what conditions make it applicable. A command list without input context, version assumptions, or observed output is difficult to reuse. Separate the underlying primitive from a complete exploit chain and identify what remains unproven so later work does not inherit false certainty.

Practical method

For each experiment, record the hypothesis, environment, exact input, observation, and interpretation. Keep contradictory results rather than deleting them. Link claims to artifacts or primary documentation and note changes made to imported examples. Summarize reusable mechanisms after the experiment is verified.

primitive: what capability was demonstrated?
preconditions: versions, state, access, alignment
evidence: input and observable result
next step: what missing capability is needed?

Interpreting evidence

A good note lets someone decide applicability before running commands. Include the failed prerequisite as prominently as the successful demonstration when it limits reuse.

Pitfalls and limits

A complete challenge solve can obscure the transferable idea. Source licenses apply to copied material. Similarity of names or examples does not establish equivalence across different versions.