Entry 002
2026-08-16
Illustrative demo
"An advisory firm is bidding on a competitive proposal that weights firm experience and technical quality heavily. Disclosure of AI use is voluntary — there is no legal obligation — and all deliverable IP transfers to the client. Do we disclose that we use AI agents, including a proprietary AI expert-board tool, and with what scope?"
What the board said
Value Creator: When the bid is scored mostly on experience and technical quality, demonstrable governance is the edge — not the absence of tools. Disclosing well turns a latent liability into early evidence of institutional maturity.
Devil's Advocate: The real risk isn't the AI stigma; it's the collision between "all deliverable IP transfers to the client" and a proprietary, reusable tool. Fence the method contractually before you describe it, or the client may claim its output too.
Strategic Planner: Silence is asymmetric and grows costlier: an IP-transfer clause eventually forces you to explain how each deliverable was produced. "They hid the method" is far more damaging than the initial prejudice. Tie AI to the IP clause — AI is never the author.
Business Intelligence: A sophisticated buyer rewards traceability, not the absence of tools. Add a rule that resolves the IP intersection: no AI input creates firm-owned copyright, and every output is subsumed into named human authorship.
Critical Thinker: Challenge the assumption that "tool" and "deliverable" are separable for IP — they may not be. And test the "abstract questions" rule: if the mandate's parameters are a fingerprint, abstraction protects no one. Run a reidentification test before promising it.
Executor: Add a rule of traceability and chain of custody. Keep the tool's name generic in the body of the proposal, reserve the commercial name for a technical appendix, and rehearse a 30-second answer for the Q&A round.
CEO: the board converges — disclose, with bounded scope, integrated into methodology and the quality plan, not an isolated annex, and in generic functional language. The real tension is where to draw the line between the proprietary tool and the transferred deliverable. Add the two rules the firm's original three lacked: (4) the tool and method are not a deliverable and not subject to IP transfer; (5) traceability and chain of custody. Watch one signal: if the Q&A concentrates on "how much the machine does" instead of the technical design, the disclosure is over-explaining — cut it in half.
Illustrative demo on a governance question faced by professional-services firms, generalized and stripped of any identifying detail. No client and no confidential data. Published as a demonstration of the methodology.