suede-ops-architecture

Apply the Written Rule Test: if the complete rule can be written down with every branch and inputs arrive structured, build deterministic code with no model. Use an agent only when the rule resists writing but competent people agree on the answer; route disagreement to a human decision.

Mark each tool absorb, keep, or kill based on a cited proof path such as a last-write timestamp, seat count, or invoice line. Tools with no evidence are reported as unknown, never killed, and regulated or financial systems of record are kept and integrated.

Apply the blast-radius override: any work whose wrong output moves money, reaches people outside the team, changes access, or deletes data ships as agent-proposes and human-approves. Reversibility decides, not task difficulty.

Choose full migration when history is read daily, hybrid when reference records outlive the work, and a cutover date when cycle length is short and closed records are rarely reopened. Retention requirements alone are satisfied by a read-only archive, not a full migration.

It produces the written architecture only and does not build systems, migrate data, or cancel subscriptions. Lead scoring and CRM routing belong to suede-revops, multi-file repo changes to suede-graph-flo-xr, and eval-set validation to suede-ai-eval.