Introduction
CODITECT is the system that addresses the three deficiencies Mark named.
Read his framing of the universal problem. Every page on this site shows one specific way CODITECT addresses the three deficiencies Mark named - deciding which tests run, running them, recording the outcome - across software, AI use cases, and regulatory regimes.
"We and every other software company in the world are outstripping our ability to test what we're building."
Why now: the velocity of agentic coding has decoupled from the velocity of testing, auditing, and validation - the knowledge and proof that AI agents did what they were tasked to perform, i.e. testing, in this case. An AI agent can produce more code in a day than a team used to write in a sprint. The test, audit, and compliance layers did not get faster at the same rate. The gap is structural and widens with every model release.
Three deficiencies - in every company today - that no software addresses:
- determining which tests need to run for a particular release
- checking whether they ran
- recording the outcome
Mark Walker, nue.io - meeting transcript [00:46:36]
Every page on this site shows one specific way CODITECT addresses the three deficiencies Mark named.
Every page on this site is a way CODITECT addresses the three deficiencies
Each section of the site addresses Mark's universal problem from a specific angle: tests, audits, compliance, memory, ITIL, deployment. The threading is consistent: which tests run, that they ran, the outcome recorded.
Use the left navigation to jump to the angle relevant to your current question. The 3-minute demo at the top shows all three deficiencies addressed in a single run.
Foundation-model-agnostic, IDE-independent
The platform runs underneath the IDE and routes to the model best suited per task: Anthropic Claude, Gemini, Codex, Kimi, or a local open-source model. Switching IDE or model does not change the audit record. The recorded outcome follows the work.
Deployment is local AI workstation, Google Cloud Workstations, or hybrid. Same primitives, different lane.
Compliance built in, not bolted on
Each record carries a regulatory framework tag where one applies: NIST AI RMF, EU AI Act, NAIC, NYDFS Part 500, FDA 21 CFR Part 11, ISO 42001, sector-specific obligations. The control-to-clause mapping is documented in the SaMD-Validated Testing Framework per ADR-292.
There is no separate compliance phase - compliance evidence is the work product. Tracked issues open when CI hooks detect a violation today; broader risk-monitoring is part of the Universal Quality Development Harness per ADR-320.
In summary - the problem and what CODITECT solves
The problem. Agentic coding has outpaced testing, auditing, and record-keeping. Three deficiencies result, and no software available today addresses them - nobody decides which tests must run for a particular release, nobody checks whether they ran, nobody records the outcome.
What CODITECT solves. The platform addresses all three deficiencies by construction. Per change, the platform selects the relevant tests, runs them, and records the outcome - signed, immutable, queryable. The same record satisfies the engineering leader, the auditor, and the regulator.
The scope of this site. This site shows the core flow and the adjacent surfaces - architecture decisions, compliance frameworks, memory, ITIL, model routing. The platform addresses many surfaces this site only summarises.
"This is only a portion of what CODITECT can do for you."
Mike Smith - May 1, 2026