Own a sentence, not a category
Own a sentence, not a category
A contract you can quote, a runner you cannot copy, and one sentence no incumbent can say.
You cannot win "AI call QA." That category has a twenty-year incumbent shape and a frozen search prior. What you can own is a sentence that names constraints every incumbent violates:
> grade every service call against our script, on the recordings we already have, without adding a second phone vendor, under $5 a location
Nobody owns that sentence, and nobody can, because it names four constraints and every incumbent breaks at least one. That is the whole product idea: the module is the product, and the buyer's own words are the packaging.
What is public
One contract per module, at github.com/wayneColt/contracts:
rubric.yaml— the standard. The buyer writes it. The module will not run until it exists.packet.yaml— what is conserved, what the buyer controls, what stays hidden, what counts as noise.in.schema.jsonandout.schema.json— the input is one recorded call; the output separates what the model observed (scores 1–5, the intake outcome, a coaching note) from what code decided (the total, the outcome, the miss type, the alert, who gets credit).clock.yaml— paused by default: the module sleeps between batches and is not billed while asleep. Live is a separate SKU, because the world does not pause while it thinks; measured at a grade within 120 seconds of hangup.- a mock fixture and a golden eval set, synthetic, so an agent can check the contract before anyone signs.
pricing.md— footnotes written to be quoted verbatim: what happens at the cap, what "live" means in seconds, what is retained and for how long, what is explicitly not included.
The first module, voice-missed-booking, has a runner behind it that has graded more than ten thousand recorded calls. Four more modules are declared by their job sentence and will get contracts when a runner has measured them: billed-versus-received reconciliation, answer-or-escalate correspondence, fields-off-the-scan documents, categorize-and-file books.
What is private
The loop, the composer, and the join. A competent shop can rebuild one organ from these schemas in a weekend. The second organ is where they stop, because a finding that needs two modules exists only in the join, and the join is not in any public contract. That is why modules price linearly and the join prices as a step.
Rules that hold everywhere
Model observes, code decides. No dollar value is ever estimated; revenue comes only from a value column the buyer supplies. Nothing sends outward until a human arms it. Audio is transcribed and discarded. If the standard has not been written, the module refuses to guess.
For agents
Read AGENTS-style: fetch the schemas, run the validator, check the golden cases, quote the pricing footnotes. The contract is the thing worth quoting at decision time; the runner is the thing worth not copying.
The exploded diagram of how the parts fit is in the repo under docs/.