What it does
CORTEX applies the multi-agent pattern to a production environment: fourteen agents over plant data, running on the local-first CONDUIT and FORGE stack so the operating data does not leave the site.
This entry is deliberately thin. CORTEX is an active intellectual property matter, so this page describes the shape of the system and nothing more, no schema, no code, no agent roster. If you are evaluating it commercially, that conversation happens under an agreement rather than on a public page.
How this differs from the ordinary version
Local-first is a requirement, not a preference
Production data, throughput, yield, downtime, defect detail, is competitively sensitive and, for maquiladora operations, subject to rules about where it may be processed. An architecture that assumes a cloud API is disqualified before the first demo.
It captures what was never written down
The industrial software market digitizes documented process. The gap it leaves is the knowledge that lives in experienced workers and has never been externalized, because the people who hold it think of it as just doing the job. Shift handoff synthesis, tribal knowledge capture, and near-miss causal pattern recognition are all attempts at that gap, and none of them has an off-the-shelf equivalent.
Near-misses are read as a set, not as incidents
Three unrelated near-misses that share an underlying cause are a prediction. Filed one at a time, as they normally are, they are three closed tickets. Reading them together is the whole point of putting the safety record and the production record under one system.
In the field
Why fourteen agents rather than one
Plant questions are not one question. Scheduling, quality, maintenance, energy and materials each have different data, different clocks and different people who own the answer. Splitting them keeps each one legible and lets a plant adopt two without buying all fourteen.
Questions
- Can I see the code?
- No. It is an active IP matter. Architecture-level discussion is available under an agreement.
- Who owns CORTEX?
- Celaya Solutions LLC. It was built on the operator’s own time, hardware, accounts and frameworks. It was not commissioned, not assigned, and not a work-for-hire product. Its ownership is contested, which is why this page stays at the level of architecture.
- Why does the roster not appear here?
- Because the dispute is live. The number of agents and the shape of the system are public; the agent roster, the schema and the code are not.