JCEE Labs / Dallas, Texas
JCEE Labs is based in Dallas, Texas, and founded by Jonathan Chadbourne. We develop methods and software for AI-assisted operations where permissions, evidence, and human responsibility matter.
When software recommends an action, changes a record, or resumes after an interruption, someone still needs to answer practical questions:
We exist to make those questions easier to answer with evidence people can inspect.
Our direction
We begin with a specific workflow and the people doing the work. Our first industry focus is industrial distribution. The goal is to demonstrate measurable improvement alongside existing systems, then expand into more workflow ownership as evidence and economics justify it.
Read our approach →From the Founder · Jonathan Chadbourne
Why JCEE Labs starts with observation, evidence, and the workflows between systems. The thinking that connects our research to the work of ordinary businesses.
Read the founder essay →The wider company
Distribution is our first industry focus. JCEE Operating Cloud describes the longer-term platform direction. Howm.io is our separate personal-app suite in development, including Mirrored and MISE.
IMPLEMENTED CANDIDATE · NOT LAUNCHED
Eight routes built; 11/11 DOM interaction checks and 20/20 source-file readbacks matched.
Rendered browser/device acceptance, service integration, merge, deployment, and public launch remain open.
Full record →WEB MVP EVIDENCE RECOVERED · REPEATED USE NOT VALIDATED
The canonical source contains the September 12 build and test report and a preserved passing end-to-end receipt covering AI meal options, recipe steps, cooking recovery, a profile signal, and a saved recipe. The report records 24 passing tests plus type and build checks. These are historical receipts, not new runs.
A working test flow does not establish repeated cooking, retention, willingness to pay, or an advantage from personalization. The current hosted pilot and native iOS/TestFlight readiness remain unresolved; no production-readiness claim is made.
Full record →BACKEND AND IOS DEVELOPMENT
Backend and iOS repositories and application routes exist. The current review records prepared chat/check-in error-handling fixes.
Full builds, device acceptance, and current production validation remain to be established. This work is separate from VOW.
Full record →State what was tested, preserve the result, and keep failures visible.
A useful idea or recommendation does not create permission to act.
Keep versioned milestones and make the next decision understandable.
Support people making consequential decisions with evidence they can inspect.
The JCEE Assurance Method organizes the work around four steps: Observe, Judge, Authorize, and Record.
JCEE Distribution provides a concrete application. VOW and QCS address execution and authority questions. Operating Cloud describes the longer-term platform direction. Each program has its own evidence boundary. A result in one program does not establish every claim about another.
Explore the JCEE Assurance Method →We distinguish synthetic tests, reference implementations, research results, and observations from real operating environments.
A recorded milestone establishes only what its evidence supports under the stated conditions. Customer ROI and production readiness remain unestablished where the relevant evidence is missing.
Review published milestones and their boundaries →Companies can bring an operational problem. Researchers can bring a question, method, or reproduction proposal.
