Absolute mandate as precondition for transformation

Before any AI-transformation technical work, the operating co-owner secures explicit, unilateral authority from the other co-owners to tear down the existing org without consensus, feature-by-feature debates, or department-level vetoes. This is a single one-time conversation that replaces "let me build a business case for each change" with "we just do; we report progress; we don't ask permission per move."

A mid-size cosmetics R&D + production company ran a >50% office FTE cut in three months without weeks of approval cycles per role. The operator explicitly: "without the absolute mandate, every microservice would be a 4-week political negotiation. With it, we just shipped." Cases A-038 (4-phase maturity) and A-040 (4-week launch plan) implicitly assume this authority exists; this case makes the precondition explicit.

1. Articulate the end-state for the co-owners in two sentences: "we're going to halve office headcount, replace task-tracker with microservices, and stop seeking buy-in per-department for the next 6 months."
2. Name a hard cutover date (calendar date, not "Q3-ish").
3. Get explicit, in-writing agreement: "you have authority to act without my sign-off for the duration."
4. Communicate to the org once, honestly. Pair with [new-N14-03] (elite framing). Don't soften.
5. Set a single weekly check-in with co-owners — outcome reporting, not approval.
6. The first time someone tries to escalate around you, refer them to the agreement publicly and politely. Once.
7. At end of cutover window, return to consensus governance — the mandate is bounded in time.

• Don't try this without genuine co-owner alignment; a mandate that gets revoked mid-stream is worse than no mandate. Get the written sign-off before the kickoff conversation.