Choose what to get done
GenAI IP risk contract checklist validator
A JSON clause register covering all five canonical GenAI IP risk categories passes validation: every category is present exactly once, each has a clause excerpt of minimum length, a contract reference, and a status from the allowed enum; no category is misspelled or duplicated.
Goal decomposed into an executable task plan
A goal broken into ordered, tool-assigned steps with a resolved, acyclic dependency graph, so an agent (or a team) can execute it without ambiguity.
In-House Build-vs-Buy Tendency Scorer
A founder weighing whether to sell an AI capability as a service gets a 0-6 in-house-tendency score and a build/buy verdict per the book's exact criteria, flagging capabilities customers will just build themselves.
Incident response playbook
A severity-tiered response playbook (roles, response targets, escalation, comms) so responders follow a plan instead of debating process mid-outage.
Input guard against prompt injection
A reusable guard that enforces type, length, and charset per field and rejects inputs smuggling section-break delimiters or fake instruction/role markers, before the LLM sees them.
Investor due-diligence answer register
A complete, category-balanced register of answers to the standard investor due-diligence questions, ready to drop into a data room.
Letter of intent for an enterprise customer to sign before I build
An unsigned letter of intent the customer can sign: intent-to-purchase language, commercial terms, conditions, an explicit non-binding clause, and two signature blocks.
Liquidation Preference Structure Spec
The founder (or counsel) has a complete, parameterized specification of the liquidation-preference stack ready to drop into a term sheet or shareholders' agreement.
Logs, metrics, and traces instrumentation plan
A concrete plan covering all three observability pillars per service, plus an SLI for every golden signal, so you can actually see what your app is doing.
Maintainability index per module
The Maintainability Index (raw and 0-100 normalized) per module from Halstead volume, cyclomatic complexity, and lines of code, with a maintainability band.
Map product features to MECE use-case modules with per-segment value
I get a modular packaging map where features are partitioned into non-overlapping use-case modules, no feature is left unassigned, and each module carries a t-shirt value per segment plus a base/add-on flag.
Model router that sends each query to the right LLM
A routing function that dispatches each query to the right model by its type, normalizing case and falling back to a default for any unlisted type.
You are not what you make. You are the one who can make it.
Opens soon. Get early access the day it goes live.