CODITECT - the AI operations layer
Adopt AI across the enterprise with compliance, risk, and audit built in.
CODITECT records every AI-touched change against an approved task and a regulatory control. Compliance posture is current at all times because it is produced by the work itself, not assembled before an audit. Below: a 3-minute demo of one engineering use case. The same model applies across the application stack.
Sign in to watch the 3-minute demoWho this is for
ICP
High-growth software companies doing agentic coding.
Mark recommended two ICPs - high-growth software companies and regulated industries - and added: “I don’t think you need to solve both of them.” This demo covers the first.
The problem - in Mark’s words
“We can code faster than we can test… there is no system for determining which tests needed to be run for any particular release or checking whether they were run or recording what the outcome was.”
Mark reframed this in the same conversation: it’s a code quality problem, not an engineering problem. The faster a team moves - especially agentically - the harder it is to know whether quality best practices are being followed, including by the agents themselves.
“Are the agents themselves following the quality rules?” [00:55:16]
The solution - what the demo shows
- An agent writes the new code - five files in a single burst.
- The system selects the four tests affected by the change, with a written reason for each.
- The system writes four more tests for situations the engineers did not write, including one designed to fail.
- All sixteen tests run. The deliberately failing test does fail, with the exact test, line, and change reported.
- Every change is recorded with the approving engineer’s name and a timestamp. Human or agent - same record, same review.
- The four audit documents an auditor would normally request are produced as a byproduct of the run. Each is timestamped and signed.
- Everything packages into one audit bundle.
Product - in Mark’s framing
CODITECT runs as “a quality management system for a software company that was doing agentic coding.” [00:46:36]
The system handles the work that nobody is doing today:
- Determining which tests need to run for any particular change or release.
- Checking whether they were actually run.
- Recording what the outcome was - in an immutable audit trail.
- Producing the IQ, PQ, and traceability documentation as a byproduct, not as paperwork on top.
“It just has to be a quality process that goes really fast.”
Velocity is the gate. The demo is built to show the QMS layer keeping pace with the agent - not bottlenecking it.