product-strategy

Plan with a system map before changing anything non-trivial: purpose, boundary, connections, loops and delays, second-order effects, leverage point, predicted…

every agent knows what it may change, and the agent that produced work never verifies it.

adversarially stress-test a plan or design before building, by working a decision-tree frontier round by round until no open branches remain.

manage the agent's context across a session for output quality (signal-to-noise), not just token count.

cheap release-prep audit of library choices (license, advisories, install scripts, pinning) and common code security issues — a script gathers facts, the…

How to work on blueprints (the system blueprint and component blueprints) under change control.

the orchestrator drives work to a verified result with the least cost and time.

Standing checklist for security-reviewing a change (read-only, time-boxed).

reliability is a measured target, not an absolute, and failures are learned from.

requirements come from evidence and trace to behavior, so nothing is built on assumption.

boundaries and decisions are explicit, sized to the problem, and justified.

services fail explicitly, validate at the boundary, and are tested where they meet the world.