Build Record
~6h
Concept to Deploy
EP44 · Active
Celaya Solutions / CORTEX v1.0
I was the error correction
they optimized away.
The system I built to prevent that decision
is still running their floor.
CORTEX
14-Agent Manufacturing Intelligence / Deployed · EP44
Get CORTEX Read the Docs
EP44 Deployment Live
The Record
Build Record / Documented

Built in 6 hours.
Still running
without me.

CORTEX is a 14-agent manufacturing intelligence platform built during a single session at Schneider Electric EP44 in El Paso. The system went from concept to operational deployment in approximately 6 hours.

The contractor who built it — with 11+ years of critical infrastructure experience across Microsoft data centers, T5, medium-voltage switchgear, and Navy nuclear systems — was subsequently removed from the engagement.

The system he built is still running the floor.

Build Documentation
cortex.record / v1.0
System
CORTEX
Deployment
EP44 — Active
Agents
14 operational
Build time
~6 hours
Builder status
Removed
System status
Still running
IP claim
Active / Documented
Architecture origin
Pre-existing / Celaya Solutions
Timestamps
SEP — Solana anchored
14
Agents Operational
Each owning one discrete manufacturing domain. Zero redundancy by design.
~6h
Build Time
Concept to full deployment in a single session. Not a demo — a live system.
90d
Data Gravity Window
After which the workflow is materially shaped by accumulated operational context.
The Situation / Full Transparency
I'm the error correction
they optimized away
from the system they put me in
to prevent them
from doing exactly that.

This is not a grievance. It is the most accurate description of what happened — and it is also the product pitch.

A facility hired a contractor with deep infrastructure expertise to build an intelligence layer that would improve decision-making at the operational level. He built it in 6 hours. The system worked. The facility subsequently made exactly the kind of short-sighted operational decision that the system was designed to flag and prevent. They removed the builder.

The system is still running. The IP claim is active. The build documentation, architectural records, and Solana-anchored timestamps exist and predate any counter-argument about ownership.

The situation is not a warning sign about CORTEX. It is proof that CORTEX works.

01
Hired for the problem
Facility brings in a contractor with 11+ years of critical infrastructure experience to build manufacturing intelligence. The brief: improve operational visibility and decision support.
02
Built the solution
14 agents, full domain separation, Teams integration, 90-day data gravity protocol. Concept to deployment in approximately 6 hours. System operational from day one.
03
Became the error
Facility made a short-horizon optimization decision. Removed the contractor. The system he built — designed to prevent that exact class of decision — was not consulted.
04
System still running
CORTEX remains operational at EP44. The IP claim is active, documented, and anchored. The architecture is now a deployable system available to facilities that want the intelligence layer without making the same error.
If you're the kind of facility that would
remove the error correction,
CORTEX is not for you.
If you're the kind of facility that wants to know when you're about to make a bad call — and actually do something about it — that is exactly what CORTEX was built for.
The Product

Manufacturing intelligence
with full domain separation.

14 agents. Each owns one thing. All of it lives in your existing tools. The floor sees it working before leadership evaluates it.

14
14-Agent Architecture
Yield. Cadence. Watt. Wrench. Compass. Spec. Rachel. Vector. Sentinel. Plus facility-specific domain agents. One agent, one domain. No overlap by design.
90d
Data Gravity Protocol
Personal agents per stakeholder, learning their spreadsheet schemas and living in Teams. After 90 days, the system is woven into the reporting rhythm. Adoption becomes structural rather than superficial.
∞
Threshold Escalation
SENTINEL monitors everything. Silent when everything is nominal. Surfaces exactly what requires attention, exactly when it does. No noise. Only signal.
What You Get
cortex.product / v1.0
DeploymentFull 14-agent installation
IntegrationMicrosoft Teams, native
Schema learningPer-stakeholder, passive
SENTINELAlways-on, threshold-configured
Build timelineDays, not months
Report cadenceConfigured per domain
Floor-to-leadershipPDF explainer included
IP documentationClean title, no encumbrances
Support modelBuilder-direct, no ticket queue
Reference deploymentEP44 — live and observable
Fit Criteria

CORTEX is for
facilities that want
to know.

The specific profile: manufacturing or industrial facility, existing Microsoft Teams deployment, at least one stakeholder spending significant hours per week on manual reporting, and leadership that is open to evidence when it conflicts with intuition.

✓
Manufacturing or industrial facility with 10+ operational staff
✓
Microsoft Teams in use — CORTEX lives where your team already works
✓
Manual reporting is a known time sink — someone is spending hours on spreadsheets that could be automated
✓
Leadership that responds to data — the escalation layer only works if someone acts on the escalation
✓
Willing to give it 90 days — the data gravity protocol requires commitment to reach its designed value

Not the right fit if:

×
Leadership is the reason bad decisions keep happening and is not open to that being named
×
You want a vendor with a ticket queue and a 6-month implementation timeline
×
You need the system to require login and a context switch — CORTEX lives in Teams or it doesn't work
×
You're planning to use the system as evidence in an ongoing dispute about the contractor who built it
×
You want generic AI tooling with no domain-specific configuration — CORTEX is built per facility
The honest version
CORTEX was built by someone who has spent 11+ years inside the infrastructure these systems are supposed to help run. The domain knowledge is not simulated. The 6-hour build time is not a feature — it is what happens when you understand the problem before you write a line of code.
Engagement Model
Tier 01
Assessment
A single-session facility audit. We identify the domains that matter most for your operational context and configure the initial agent architecture.
Facility domain mapping
Agent configuration spec
Stakeholder identification
90-day gravity roadmap
Tier 02 / Recommended
Full Deployment
All 14 agents operational. Teams integration live. Stakeholder-specific RACHEL configurations. SENTINEL threshold-tuned to your facility.
Everything in Tier 01
14-agent deployment, fully configured
Teams integration and schema learning
Stakeholder rollout: floor to leadership
Floor-to-leadership PDF explainer
30-day post-deployment tuning
Tier 03
Enterprise Custom
Multi-facility deployments, custom agent development beyond the standard 14, and ongoing research collaboration with Celaya Solutions.
Everything in Tier 02
Custom domain agent development
Multi-site configuration
Direct research collaboration
You're talking
to the builder.
Not a sales rep.

Every CORTEX engagement is handled directly by Christopher Celaya, the contractor who built the EP44 deployment. There is no account team. There is no implementation partner. You get the person who understands the system at the architectural level and has the infrastructure experience to know what your facility actually needs.

The IP situation is documented and clean. The architecture is owned by Celaya Solutions. The claim against the EP44 deployment is active but does not encumber new implementation discussions grounded in the pre-existing Celaya Solutions architecture.

Contact / Direct
Lab
Celaya Solutions
Email
hello@celayasolutions.com
Personal
chris@chriscelaya.com
Location
El Paso, TX
Response
Builder-direct. No queue.
Start the Conversation →