# Celaya Solutions Research > Celaya Solutions Research is an independent research lab and consultancy in El Paso, Texas, founded in 2024 and run by Christopher Celaya. It builds AI search, retrieval and agent systems that make data coherent: every answer shows the source it came from and a person makes the call. Work is done in English and Spanish. This is the full-text companion to llms.txt: the text of every curated page on celayasolutions.com in one file, page titles as H2 with the source URL under each, so a model reading only this file can answer any reasonable question about the lab correctly. The link-first map is at https://celayasolutions.com/llms.txt. Last updated: 2026-09-22 ## Home Source: https://celayasolutions.com/ *Markdown view of [https://celayasolutions.com/](https://celayasolutions.com/). The canonical page is HTML at the same URL.* [Español](/es) El Paso, Texas · English and Spanish ## We make data coherent. Your manuals, records, market feeds and business tools rarely agree with each other. Celaya Solutions builds the search, retrieval and agent systems that bring them into one record, where every answer shows the source it came from and a person can check it. [Request a call](/hire#contact)[See the work](/work) 01 · What we build ### Three shapes the work takes. #### Search that cites its source Ask a question across approved manuals, procedures and records. The answer comes back with the document, page and revision it came from, and says so when the documents do not answer. #### Agents that work across your tools One agent that reads your market data, accounting, files and work boards, acts only through the actions you configure, and records what it did. #### Records that check themselves Telemetry, testimony or archive records checked against each other. Where they disagree, the system flags it with the evidence attached instead of smoothing it over. [What each one includes](/services) 02 · Proof ### Built, running, and public where it can be. - Live · trinidad.town ### Trinidad 5,435 rare Texas historical documents, searchable in public. Every answer links to the record it came from. [How Trinidad works](/research/trinidad) - Client build · public aliases ### Morpheus One agent across a day trader’s market data, brokerage, accounting, files, work boards and fleet. [See what was connected](/case-studies/morpheus) - Industrial research · evaluated in simulation ### WITNESS Reads drawings, telemetry, maintenance history and safety rules, then flags faults with hours of lead time and a cited recommendation. [Read the method and results](/instruments/witness) - Prototype · crawler and platform running ### GREYBOOK Breaker and switchgear documentation from five vendors in one catalog, revision-aware, every answer citing the exact page. [See the catalog schema](/instruments/greybook) [All the work](/work) How it works ### Four steps, one decision at each. 1. ### Free call Tell us the problem, who has it and what it costs you today. No questionnaire, no documents. 2. ### Diagnostic, fixed price, up to $3,000 A written finding: what data you have, what is missing, what to build and what not to build. Sometimes the answer is nothing. 3. ### Build or pilot Scoped and priced on its own, with milestones you can inspect and a way to measure whether it worked. 4. ### Handover Source code or a hosted system, documented, with support and running costs written down before we start. Scope and price are in writing before any paid work. Consulting outside a build is $125 an hour. [How we work, in detail](/onboarding) 04 · Who ### One builder, start to finish. Christopher Celaya runs the lab and does the work. He spent twelve years in industrial electromechanical systems, hyperscale data center operations and medium-voltage switchgear manufacturing before he wrote software for a living. The habits came with him: keep the source, log every change, and let a person make the call that matters. [About Christopher](/about) Next step ### Start with the problem. Write a few lines about who needs help and what does not add up. The first call is free. Leave confidential files out of the email. [Request a call](/hire#contact)[hello@celayasolutions.com](mailto:hello@celayasolutions.com) Research The lab also publishes: papers on coherence and autonomy, a field paper on El Paso’s data center buildout, and a catalog of instruments with the live deployments marked. [Research](/research) · [Instrument catalog](/instruments) ## Questions, answered Source: https://celayasolutions.com/faq *Markdown view of [https://celayasolutions.com/faq](https://celayasolutions.com/faq). The canonical page is HTML at the same URL.* [Español](/es/preguntas) Questions ## Before you begin. Cost, pilots, data, ownership and support, answered plainly. [Request a call](/hire#contact)[How we work](/onboarding) Questions ### Before you begin Who is a good fit? Teams whose problem is data that does not agree with itself: manuals in several revisions, a business spread across many tools, records that contradict each other. You need approved sources, a clear question and someone who can judge the answers. Industrial and operations teams are the most common, and we also work with specialists who run their work through many tools. What happens on the first call? It is free and takes about thirty minutes. We talk through the problem, who has it, what data exists and what would count as fixed. You leave knowing whether a diagnostic makes sense. What does the diagnostic cost, and what do I get? A fixed price, agreed in writing, never more than $3,000. You get a written finding: the data you have, the gaps, how a solution would be judged, and a recommendation on what to build. Sometimes the recommendation is to build nothing, and the finding says why. Is a pilot or build possible after that? Yes. It is a separate decision with its own scope and price. Nothing in the diagnostic commits you to it. How do we know it worked? Before a build starts we agree on real questions, the sources that count and what a correct answer looks like. The build is judged against those: right source, right revision, honest unanswered cases, and how much reviewer time it saves. Targets go in the scope so both sides are measuring the same thing. Can it work in English and Spanish? Yes. Bilingual search and answers are a normal part of the work. The scope names the controlling language for each document and who reviews specialist terms. A translated answer points back to the approved original. Where does the data run? On your hardware, on ours, or with a hosted provider. Local-first is the default preference. The scope says exactly what runs where and which providers, if any, touch your data. Who owns what? Your data stays yours. A one-time build is delivered with its source code. A hosted or licensed system has its own usage terms and may include components Celaya keeps. The agreement lists deliverables, reusable parts and any third-party licenses. What support is included? Whatever the scope says: handover, documentation, review milestones and any maintenance. Hosted systems carry a recurring fee, and infrastructure costs are stated separately. Response times and change requests are agreed in writing. What happens when we stop? For a build, you already have the code and the documentation. For a hosted system, the agreement sets export formats, the transition work and how long access and data are kept. Both are settled before work starts, not at the end. Next step ### Start with the problem. Write a few lines about who needs help and what does not add up. The first call is free. Leave confidential files out of the email. [Request a call](/hire#contact)[hello@celayasolutions.com](mailto:hello@celayasolutions.com) ## Services Source: https://celayasolutions.com/services *Markdown view of [https://celayasolutions.com/services](https://celayasolutions.com/services). The canonical page is HTML at the same URL.* [Español](/es/servicios) Services ## What we build. Each job starts with data that does not agree with itself: manuals in five revisions, a business spread across six tools, records that contradict each other. Each one ends with a system where the answer shows its source and a person makes the call. [Request a call](/hire#contact)[See the work](/work) Three things ### Search, agents, and records that check themselves. 01 · Search #### Search that cites its source For Maintenance, quality and operations teams working from approved manuals, procedures and records, in English, Spanish or both. You get A search that answers with the document, page and revision, says when the documents do not answer, and keeps the controlling document one click away. You bring The document set, the revision and access information, twenty or so real questions, and someone who can judge the answers. Not included Equipment control, safety decisions, regulatory certification, or replacing an approved procedure with a chat window. 02 · Agents #### Agents that work across your tools For Specialists whose day spans several systems: market data, brokerage, accounting, files, work boards, field or fleet tools. You get One agent with purpose-built connections to those systems, allowed to act only through the actions you configure, with a record of what it did and why. You bring The tools and the access, the decisions you want help with, and the actions it must never take on its own. Not included Unsupervised trading or payments, and any action without a configured gate. [Morpheus, a client build of this kind](/case-studies/morpheus) 03 · Records #### Records that check themselves For Teams reviewing forms, inspection records, testimony or archives, where the entries have to agree with each other and with a source. You get Extraction and cross-checking that links every field to where it came from and flags what conflicts or is missing, for a person to resolve. You bring Authorized examples, the rules a reviewer applies today, and the reviewer. Not included Automatic decisions. The system surfaces the conflict; a person settles it. How it works ### Four steps, one decision at each. 1. ### Free call Tell us the problem, who has it and what it costs you today. No questionnaire, no documents. 2. ### Diagnostic, fixed price, up to $3,000 A written finding: what data you have, what is missing, what to build and what not to build. Sometimes the answer is nothing. 3. ### Build or pilot Scoped and priced on its own, with milestones you can inspect and a way to measure whether it worked. 4. ### Handover Source code or a hosted system, documented, with support and running costs written down before we start. Scope and price are in writing before any paid work. Consulting outside a build is $125 an hour. [How we work, in detail](/onboarding) Beyond the three ### If your problem is not one of those. We have also scoped downtime prediction, plant-floor data capture, intake and back-office automation, bilingual work instructions and staff training. If the problem is data that does not add up, ask. The diagnostic will say whether it is worth building. [Request a call](/hire#contact) Location ### Based in El Paso. On site in the El Paso and Ciudad Juarez region, remote anywhere. Travel and working language are agreed for each engagement. Teaching ### Teaching stays free. Zero to Agent, the lab’s course on building with language models, and its community talks and classes cost nothing. [Explore the course](/instruments/zero-to-agent). Next step ### Start with the problem. Write a few lines about who needs help and what does not add up. The first call is free. Leave confidential files out of the email. [Request a call](/hire#contact)[hello@celayasolutions.com](mailto:hello@celayasolutions.com) ## About Source: https://celayasolutions.com/about *Markdown view of [https://celayasolutions.com/about](https://celayasolutions.com/about). The canonical page is HTML at the same URL.* [Español](/es/acerca) About Christopher Celaya founded Celaya Solutions Research in El Paso, Texas, in 2024 and does all of its work himself. Before software, he spent twelve years in industrial electromechanical systems, hyperscale data center operations and medium-voltage switchgear manufacturing. That is where the lab’s habits come from. [Request a call](/hire#contact) · [How we work](/onboarding) The lab Lab typeSingle-Author OperatorChristopher Celaya LocationEl Paso, Texas EntityCelaya Solutions LLC Background12 Years Industrial Contacthello@celayasolutions.com ## Where the habits come from. The lab builds search, retrieval and agent systems where every answer traces to its source and a person makes the call. Christopher writes the instruments, the papers and the notes, and builds the client work under a written scope. The person you talk to on the first call is the person who builds the system. [See the work](/work) [Instrument catalog](/instruments) Brand film, 30 seconds, silent. Christopher ![Christopher Celaya, founder of Celaya Solutions Research, El Paso, Texas](/assets/img/christopher-celaya.png) Christopher Celaya, El Paso, Texas ### Twelve years on the floor, then software. Industrial electromechanical systems, data center operations and switchgear manufacturing all teach the same thing: assume failure, keep a record, make every state observable, and never let an automated process act without a trace back to evidence and a person who can stop it. Most language-model systems have none of that. The instruments here put it back. [WITNESS](/instruments/witness) flags equipment faults with hours of lead time and writes a cited recommendation, and has no path to the controls. [GREYBOOK](/instruments/greybook) answers from vendor manuals with the exact page and revision. [Trinidad](/research/trinidad) answers questions about Texas history with the record attached. [Morpheus](/case-studies/morpheus) runs a trader’s market and business tools through one agent that records everything it does. ### Why one person. There is no team behind the name. The catalog, the live deployments, the papers and the client builds are the work of one operator, so one name answers for every claim on this site. When the lab needs more hands it uses its own agents, reviewed and signed the same way it asks clients to review theirs. Background ### Three kinds of industrial work. BACKGROUND El Paso, Texas 01 Industrial electromechanical systems Hands-on work in systems where failure has a physical consequence. Reliability, observable state and full traceability are requirements, not aspirations. 02 Hyperscale data center operations Operations at scale under continuous uptime. Every change reviewed, logged and reversible. The operating model for how the lab records provenance. 03 Medium-voltage switchgear manufacturing Manufacturing in the Ciudad Juarez and El Paso corridor, including border plants. Process control, consequence-aware review and quality gates shape how the instruments are designed. Tools ### What the lab builds with. WORKING STACK Local inference first, hosted fallback LANGUAGES Python. TypeScript. Swift. Rust. Go. APPLICATION FRAMEWORKS Next.js. SwiftUI. Tauri. Hono. Astro. Node. DATA AND RETRIEVAL Postgres. Qdrant. SQLite. Parquet. Drizzle. RUNTIME AND DELIVERY Docker. Railway. Fly.io. Cloudflare. Vercel. AGENT AND MODEL LAYER MCP. Ollama. Unsloth. Local inference first, with a hosted fallback, never the reverse. EDGE AND CONTROL Node-RED. MQTT. Modbus. Safety logic stays on the edge, where the consequence is. How the work gets done ### Four rules that survive contact with a deadline. OPERATING RULES Applied to every instrument and every client build 01 Build in public The repository is the record. Every project keeps a change log so the next person, human or agent, starts oriented instead of guessing. 02 Local first Safety logic runs on the edge. The cloud is an enhancement, never a dependency, because a system that stops working when the link drops was never finished. 03 Ship the thin slice Phase gates, not big bangs. A thing that runs beats a thing that is designed, and the running version tells you where to go next. 04 Write it down for the person after you Including when that person is you, next week. Every claim on this site is written so a stranger can check it without having to ask. Biography ### Who is Christopher Celaya? Christopher Celaya is the founder of Celaya Solutions Research, an independent research lab and consultancy in El Paso, Texas, and an industrial electromechanical technician with twelve years in critical facilities and manufacturing. - Twelve years of industrial electromechanical experience. - Hyperscale data center operations, medium-voltage switchgear manufacturing at a Fortune 500 manufacturer, and border manufacturing in Santa Teresa, New Mexico. - NFPA 70E and OSHA 10 certified. - Electrical engineering coursework at The University of Texas at El Paso and computer science coursework at El Paso Community College. - Author of the [Celaya Chain Protocol](/research/CCP-Scholar-v1) whitepaper, the [Earned Autonomy Architecture](/research/EAA-Scholar-v1) preprint, the [CORRIDOR: The Data Center Decade on the Border](/research/corridor) field paper, and the technical reports [Coherence as a Security Primitive](/research/CSR-2026-001-Scholar-v1) and [Multi-Dimensional Intent Alignment](/research/CSR-2026-002-Scholar-v1). - Founded Celaya Solutions Research in El Paso, Texas, in 2024. - Teaches [Zero to Agent](/instruments/zero-to-agent), a free public course on building with AI, and gives free talks in the El Paso region. - Contact: [hello@celayasolutions.com](mailto:hello@celayasolutions.com). Entity and contact ### Legal entity. The lab operates as **Celaya Solutions LLC**, El Paso, Texas. Celaya Solutions Research is the research surface of that entity. Site content licensing is stated in the footer and on the [legal and data page](/legal). ### Contact. For business and research inquiries, use [hello@celayasolutions.com](mailto:hello@celayasolutions.com). For direct, personal correspondence, use [chris@chriscelaya.com](mailto:chris@chriscelaya.com). English or Spanish. [Request a call](/hire#contact) [Donate](/donate) ## Contact Source: https://celayasolutions.com/hire *Markdown view of [https://celayasolutions.com/hire](https://celayasolutions.com/hire). The canonical page is HTML at the same URL.* [Español](/es/contratar) Contact ## Start with a call. Tell us what does not add up. The first conversation is free. If a diagnostic follows, it is fixed-price and never more than $3,000, and you decide separately whether to build. [Request a call](/hire#contact)[How we work](/onboarding) Write to us ### A few lines is enough. You can write to [hello@celayasolutions.com](mailto:hello@celayasolutions.com). #### What to include Your name, an email and a few lines about the problem. A personal email is fine. We reply by email to set a time. [hello@celayasolutions.com](mailto:hello@celayasolutions.com) [Optional: the detailed project questionnaire](/intake) [Common questions](/faq) Free call, then a fixed-price diagnostic of up to $3,000, then a separately priced build if you want one. [How we work](/onboarding) has the detail. Options ### Three ways to engage. #### Build A defined deliverable, handed over with source code and documentation. Rights, reusable components and running costs are in the agreement. #### Hosted or licensed We run it, you use it. A recurring fee, usage terms, support and an exit path, all in writing. #### Consulting and teaching $125 an hour for advice outside a build. Zero to Agent and the community talks stay free. [Explore the course](/instruments/zero-to-agent) ## How we work Source: https://celayasolutions.com/onboarding *Markdown view of [https://celayasolutions.com/onboarding](https://celayasolutions.com/onboarding). The canonical page is HTML at the same URL.* [Español](/es/proceso) How we work ## Clear steps. Visible work. You work directly with Christopher Celaya. Each step ends with something in writing and a decision that is yours. [Request a call](/hire#contact)[See the work](/work) How it works ### Four steps, one decision at each. 1. ### Free call Tell us the problem, who has it and what it costs you today. No questionnaire, no documents. 2. ### Diagnostic, fixed price, up to $3,000 A written finding: what data you have, what is missing, what to build and what not to build. Sometimes the answer is nothing. 3. ### Build or pilot Scoped and priced on its own, with milestones you can inspect and a way to measure whether it worked. 4. ### Handover Source code or a hosted system, documented, with support and running costs written down before we start. Scope and price are in writing before any paid work. Consulting outside a build is $125 an hour. During the project ### What your team brings. #### Define the problem Who uses it, which sources count, what it must never do, and who judges the answers. #### Agree the test The diagnostic proposes real questions, the expected sources and the cases the system should refuse to answer. #### Review as it is built Milestones you can inspect, with known failures listed rather than hidden. #### Hand it over Acceptance, deployment, documentation and support follow the agreement. Scope changes are priced separately. Document access and data handling are agreed before anything is shared. Keep confidential files out of the public form. [Common questions](/faq) Next step ### Start with the problem. Write a few lines about who needs help and what does not add up. The first call is free. Leave confidential files out of the email. [Request a call](/hire#contact)[hello@celayasolutions.com](mailto:hello@celayasolutions.com) ## Work Source: https://celayasolutions.com/work *Markdown view of [https://celayasolutions.com/work](https://celayasolutions.com/work). The canonical page is HTML at the same URL.* [Español](/es/trabajo) Work ## What we have built. A live public archive, a private client agent, two industrial research systems, and a short worked example of what a source-linked answer looks like. [Request a call](/hire#contact)[See the worked example](#workflow) 01 · Built ### Running, shipped, or measured. Live · trinidad.town #### Trinidad 5,435 rare Texas historical documents and 1,065,357 passages, searchable in public. Ask a question about local history and the answer comes back with the record it was drawn from, so a reader can check it instead of trusting it. [How Trinidad works](/research/trinidad) Client build · public aliases #### Morpheus A day trader who runs several companies needed one agent across market data, brokerage, accounting, files, work boards and fleet tracking. Morpheus is that agent and Morpheus Trading Desk is its market workspace. It acts only through configured, gated actions and records every setup it submits. The client’s identity and the code stay private. The case study shows what was connected and how the pieces talk to each other. [See what was connected](/case-studies/morpheus) Industrial research · evaluated in simulation #### WITNESS Reads a production line’s drawings, live telemetry, maintenance history and safety rules, flags faults with hours of lead time, and writes a recommendation with citations. Every step lands in a hash-linked record. Measured on a fixed simulation set, with the misses written down next to the hits. The language model writes text only and has no path to equipment controls. [Read the method and results](/instruments/witness) Prototype · crawler and platform running #### GREYBOOK Breaker and switchgear documentation from Schneider, Rockwell, Siemens, Eaton and ABB crawled into one catalog, revision-aware, with every answer citing the exact page. Built for the technician who needs the 2014 trip curve, not the current one. [See the catalog schema](/instruments/greybook) The [instrument catalog](/instruments) marks which systems are running in public, and the [research page](/research) holds the papers. 02 · Worked example ### What a source-linked answer looks like. Two questions against one sample document, so you can see the shape before you bring your own. The document was written for this page. #### Which template records a document review? Use template DR-02 and record the document identifier and revision. [Source: DOC-101, revision 3, page 1](#sample-source). **Reviewer:** confirms revision 3 is still the approved one before using the answer. #### How long must the record be retained? Unanswered. DOC-101 does not set a retention period. The system says so and points to the records owner instead of guessing. #### Sample document: DOC-101 · Revision 3 · Page 1 Approved sample, revision date 2026-08-01. > Record each document review using template DR-02. Include the document identifier and revision. The records owner must confirm the current approved version. Next step ### Start with the problem. Write a few lines about who needs help and what does not add up. The first call is free. Leave confidential files out of the email. [Request a call](/hire#contact)[hello@celayasolutions.com](mailto:hello@celayasolutions.com) ## Morpheus: custom agent and trading desk Source: https://celayasolutions.com/case-studies/morpheus ``` Document: Morpheus: A Custom Agent and Trading Desk Version: v1.0.0 Author: Celaya Solutions Contact: hello@celayasolutions.com Date: 2026-09-08 SHA256: 21de14d4ef28b156c33755b2b619b0b878749f852b3f4870c71481d195624a54 Chain: n/a Tx: [not anchored] License: All Rights Reserved / Celaya Solutions ``` *Markdown view of [https://celayasolutions.com/case-studies/morpheus](https://celayasolutions.com/case-studies/morpheus). The canonical page is HTML at the same URL.* [Español](/es/morpheus) Morpheus · Custom client build ## An agent built around the expert. A stock day trader who also runs several companies needs tools that understand both the market and the business. Celaya Solutions built a custom agent, its trading desk and the connections between the owner’s working systems. Morpheus and Morpheus Trading Desk are public aliases. The client’s identity and original project names are withheld. [Explore the connected system](#connected-system)[More work and examples](/work) 01 · The brief ### One expert. Several working worlds. The brief called for more than a general chat interface: market analysis, brokerage tools, accounting records, company files, work boards and fleet information needed to be available through an agent built for the owner’s workflow. Christopher Celaya designed and built the custom agent workflows, trading desk, integrations and deployment. The custom engineering connects an existing agent runtime and third-party services; its scope is the working system around the client’s expertise. 02 · The connected system ### Morpheus operates through the desk and the business tools. The agent has purpose-built interfaces to retrieve information, run supported scans, submit structured setups and request configured actions. Morpheus Trading Desk provides the market workspace and records for that work. #### The expert Questions, trading plans and business priorities Custom agent #### Morpheus Custom agent workflows and tool coordination #### Morpheus Trading Desk Market context, scanners, setups, outcomes and configured trading actions #### Business tools Accounting, company files, work boards, field jobs and fleet information Architecture overview of the client build. No client screens, records or account data are shown. 03 · What was connected ### Specialist tools, brought into one workflow. #### Market research and monitoring Schwab integrations support quotes, market depth, charts and alerts. The desk brings together options flow, gamma exposure, dark-pool context, scanners and multiple timeframes. #### Brokerage and desk actions Interactive Brokers connects brokerage workflows to the system. The agent includes guarded paper-order tools; the desk also supports separately configured trading actions, with account mode and execution gates governing availability. #### Accounting QuickBooks integrations retrieve financial records, receivable and payable aging, and profit-and-loss reports. The tools also support creating records and sending accounting documents. #### Files and work boards Dropbox tools find, retrieve, upload and organize documents. Monday.com integrations find work items, create tasks, update fields and move items between stages. #### Field work and fleet visibility Field-service tools connect customers, jobs, schedules, crews, charges and job stages. GPS integrations provide vehicle locations, history, reports, geofences and alerts. #### Operational checks The desk exposes feed health and scanner freshness, distinguishes connected data from saved examples, and keeps uncertain setup outcomes visible when market data is missing. 04 · Agent and desk in practice ### From market context to a reviewable record. This implemented workflow shows how the two parts work together. It describes system behavior rather than a client trade or a performance result. 1. ### Read the context Morpheus retrieves market data and scanner output from the desk. 2. ### Submit a setup The agent sends a structured setup through a signed request. 3. ### Validate and record The desk checks the request, rejects duplicate submissions, captures market context and records the configured gate decision. 4. ### Review the outcome The desk shares updates and a scoreboard. Open, expired and unverified outcomes remain distinct from decided samples. Trading actions follow a separate configured execution path. Recording a setup does not mean an order was placed or filled. 05 · Evidence and scope ### A private client build, explained through its implementation. This case study combines the builder’s account of the client engagement with a review of the agent and desk source. It documents custom engineering across a real client brief, with the client’s identity removed. The integration scope is visible in the implementation. Current account connections, live configuration and trading results were not tested for this public case study. No return, time-saving or reliability figure is claimed. Market-data access depends on provider entitlements. Some context is retrieved as timestamped snapshots; the interface can use saved examples when a live source is unavailable. Built for your field ### Bring the expertise. Define the work. If your work spans specialist tools, start with the decisions, information and actions you need to connect. We can scope a custom agent around those needs and agree how to evaluate it. [Request a call](/hire#contact)[More work and examples](/work) ## Morpheus: agente y mesa de operaciones a medida Source: https://celayasolutions.com/es/morpheus ``` Document: Morpheus: Agente y Plataforma de Trading a Medida Version: v1.0.0 Author: Celaya Solutions Contact: hello@celayasolutions.com Date: 2026-09-08 SHA256: f86afbe481f48e4796c6994e1570de6c67d4ced3f4108a5f7a3c8ea5c45dba7b Chain: n/a Tx: [not anchored] License: All Rights Reserved / Celaya Solutions ``` *Markdown view of [https://celayasolutions.com/es/morpheus](https://celayasolutions.com/es/morpheus). The canonical page is HTML at the same URL.* [English](/case-studies/morpheus) Morpheus · Desarrollo para un cliente ## Un agente diseñado para el especialista. Un operador bursátil intradía que también dirige varias empresas necesita herramientas que comprendan tanto el mercado como el negocio. Celaya Solutions creó un agente a medida, su plataforma de trading y las conexiones entre los sistemas de trabajo del propietario. Morpheus y Morpheus Trading Desk son nombres públicos sustitutos. Se omiten la identidad del cliente y los nombres originales de los proyectos. [Explorar el sistema conectado](#connected-system)[Más trabajo y ejemplos](/es/trabajo) 01 · La necesidad ### Un especialista. Varios ámbitos de trabajo. El encargo requería más que una interfaz de conversación general: análisis de mercado, herramientas de corretaje, registros contables, archivos de las empresas, tableros de trabajo e información de flotas debían estar disponibles mediante un agente adaptado al propietario. Christopher Celaya diseñó y construyó los flujos del agente, la plataforma de trading, las integraciones y el despliegue. El desarrollo a medida conecta un entorno de ejecución de agentes existente con servicios de terceros para crear un sistema de trabajo en torno a la experiencia del cliente. 02 · El sistema conectado ### Morpheus opera mediante la plataforma y las herramientas del negocio. El agente dispone de interfaces específicas para consultar información, ejecutar análisis compatibles, enviar propuestas de operación estructuradas y solicitar acciones configuradas. Morpheus Trading Desk ofrece el espacio de análisis de mercado y los registros de ese trabajo. #### El especialista Preguntas, planes de operación y prioridades del negocio Agente a medida #### Morpheus Flujos del agente y coordinación de herramientas a medida #### Morpheus Trading Desk Contexto de mercado, análisis, propuestas, resultados y acciones de trading configuradas #### Herramientas del negocio Contabilidad, archivos, tableros, trabajos de campo e información de flotas Vista de la arquitectura del desarrollo para el cliente. No se muestran pantallas, registros ni datos de cuentas del cliente. 03 · Las conexiones ### Herramientas especializadas en un mismo flujo. #### Investigación y seguimiento de mercado Las integraciones con Schwab permiten consultar cotizaciones, profundidad de mercado, gráficos y alertas. La plataforma reúne flujo de opciones, exposición gamma, actividad en mercados oscuros, análisis y distintas escalas de tiempo. #### Corretaje y acciones de la plataforma Interactive Brokers conecta las operaciones de corretaje al sistema. El agente incluye herramientas de órdenes simuladas con controles; la plataforma también permite acciones de trading configuradas por separado, según el modo de cuenta y los controles de ejecución. #### Contabilidad Las integraciones con QuickBooks consultan registros financieros, antigüedad de cuentas por cobrar y pagar e informes de pérdidas y ganancias. También permiten crear registros y enviar documentos contables. #### Archivos y tableros de trabajo Las herramientas de Dropbox buscan, descargan, cargan y organizan documentos. Las integraciones con Monday.com buscan elementos de trabajo, crean tareas, actualizan campos y mueven elementos entre etapas. #### Trabajo de campo y flotas Las herramientas de servicio de campo conectan clientes, trabajos, horarios, cuadrillas, cargos y etapas. Las integraciones GPS ofrecen ubicaciones de vehículos, historial, informes, geocercas y alertas. #### Estado operativo La plataforma muestra el estado de las fuentes y la antigüedad de los análisis, distingue los datos conectados de los ejemplos guardados y conserva la incertidumbre de los resultados cuando faltan datos de mercado. 04 · El agente y la plataforma ### Del contexto de mercado a un registro que se puede revisar. Este flujo implementado muestra cómo trabajan juntas las dos partes. Describe el comportamiento del sistema, sin mostrar operaciones ni resultados financieros del cliente. 1. ### Consultar el contexto Morpheus obtiene datos de mercado y resultados de análisis de la plataforma. 2. ### Enviar una propuesta El agente envía una propuesta de operación estructurada mediante una solicitud firmada. 3. ### Validar y registrar La plataforma verifica la solicitud, rechaza duplicados, captura el contexto de mercado y registra la decisión de los controles configurados. 4. ### Revisar el resultado La plataforma comparte actualizaciones y un resumen de resultados. Los casos abiertos, vencidos y sin verificar se mantienen separados de los casos resueltos. Las acciones de trading siguen una vía de ejecución configurada por separado. Registrar una propuesta no significa que se haya enviado o ejecutado una orden. 05 · Evidencia y alcance ### Un desarrollo privado, explicado desde el código. Este caso combina la descripción del encargo por parte de su autor con una revisión del código del agente y la plataforma. Documenta el desarrollo a medida para una necesidad real de un cliente cuya identidad se ha omitido. El alcance de las integraciones está presente en la implementación. Las conexiones actuales de las cuentas, la configuración en vivo y los resultados de trading no se probaron para este caso público. No se publican cifras de rentabilidad, ahorro de tiempo ni fiabilidad. El acceso a datos de mercado depende de los permisos del proveedor. Parte del contexto se consulta como capturas con fecha y hora; la interfaz puede usar ejemplos guardados cuando no hay una fuente en vivo disponible. Diseñado para tu especialidad ### Aporta la experiencia. Define el trabajo. Si tu trabajo abarca herramientas especializadas, empieza por las decisiones, la información y las acciones que necesitas conectar. Podemos definir un agente a medida y acordar cómo evaluarlo. [Solicitar una llamada](/es/contratar#contact)[Más trabajo y ejemplos](/es/trabajo) ## Instruments Source: https://celayasolutions.com/instruments *Markdown view of [https://celayasolutions.com/instruments](https://celayasolutions.com/instruments). The canonical page is HTML at the same URL.* ### // 002 · The Catalog ## Each instrument as its own signal. // FILM 002 · csr instruments install · 41s · silent ### // Live now [ CSR-Trinidad LIVE #### Trinidad // Archival Intelligence · trinidad.town Live archival intelligence over 5,435 rare Texas historical documents, with 1,065,357 passages indexed. Source-linked retrieval you can use now. ](/research/trinidad)[ CSR-MORTEM LIVE #### MORTEM // Biometric Stream · mortem-agent.xyz Live biometric stream instrument. Real-time HRV and ECG dynamics with a public deployment. ](https://mortem-agent.xyz/)[ CSR-ARK LIVE #### ARK // Biodiversity Archive · ark-web The global biodiversity occurrence record, over 3.7 billion entries, mirrored to local disk and rebuilt so a question over the whole archive answers in milliseconds. Every answer names the snapshot date it was computed against. ](https://ark-web-production-2cdf.up.railway.app)[ CSR-GALEN LIVE #### GALEN // Clinical Index · galenindex.org A source-linked clinical index. Every claim carries the record it came from, so a reader can check the answer instead of trusting it. ](https://galenindex.org)[ CSR-VERDICT LIVE #### VERDICT // Legal Intelligence · verdict-production Testimony coherence analysis for legal practice. Four agents with separate views of the record: CLERK on intake and citation, WITNESS on the facts, COUNSEL on the argument, JUDGE weighing it against what was cited. ](https://verdict-production-8687.up.railway.app)[ CSR-ATRIUM LIVE #### ATRIUM // Practice Workflow · web-production Workflow intelligence built for one specialty medical practice rather than a general suite bent toward it. Architected for its record handling requirements, and a person decides before anything reaches a clinical action. ](https://web-production-0ebbe.up.railway.app/marketing/index.html)[ CSR-DRAMATURG LIVE #### DRAMATURG // Archival Screenwriting · dramaturg Turns historical archives into screenplays where every line traces back to a real record. The provenance chain is the point, not a footnote on it. ](https://dramaturg.up.railway.app)[ CSR-PACEMAKER LIVE #### PACEMAKER // Cardiac Telemetry · pacemaker Live pacemaker telemetry streamed and anchored on chain. Roughly 86,400 beats a day, each one a timestamped record, which is what turns a health signal into an identity primitive. ](https://pacemaker.up.railway.app)[ CSR-ZTA LIVE #### ZERO TO AGENT // Community Course · zerotoagent.org A free twelve level field course from the Open Hub Learning Platform in El Paso. Starts with useful everyday tasks and finishes with a full stack project the student can prove works. ](https://zerotoagent.org/course/landing.html) ### // Documented in depth Twenty five of these have a working repository behind them, and their pages carry source excerpts, measured results and the regional use cases they were built for. The rest are registry entries: real instruments, documented honestly, without the depth. [ARK3.7 billion records mirrored](/instruments/ark) [ZERO TO AGENTFree eight week course](/instruments/zero-to-agent) [ATRIUMSpecialty practice workflow](/instruments/atrium) [WITNESSIndustrial agent, measured lead time](/instruments/witness) [GREYBOOKCross-vendor documentation](/instruments/greybook) [CLOSPriority equation, 37 agents](/instruments/clos) [AXONEarned autonomy](/instruments/axon) [CCPProof of Coherence, 6 programs](/instruments/ccp) [VERDICTFour-agent legal pipeline](/instruments/verdict) [RECALLDocument intelligence](/instruments/recall) [TEXAS ARCHIVE1,065,357 passages](/instruments/texas-archive) [MORTEMBiological identity proof](/instruments/mortem) [EPPECivic notarization](/instruments/eppe) [CORTEXManufacturing, IP-restricted](/instruments/cortex) [NEURAL CHILDDevelopmental architecture](/instruments/neural-child) [GEO5Structured symbol input](/instruments/geo5) [BYTEFRAMENo tokenizer](/instruments/byteframe) [ALIGNMENT EXPERIMENTSafety reproduction](/instruments/alignment-experiment) [QUICK NEURAL CHILDRandomized lifespan](/instruments/quick-neural-child) [CORTEX PLATFORMPer tenant metering](/instruments/cortex-platform) [BESS LAND PLATFORMRecomputable parcel scores](/instruments/bess-land-platform) [IMAGOInventory before index](/instruments/imago) [LMUCalibrated against real inference](/instruments/lmu) [PROJECT JUPITERWater and grid arithmetic](/instruments/project-jupiter) [CUSTOM GPTSMetered action schema](/instruments/custom-gpts-ecosystem) ### // i. Cognitive Systems [ CSR-01 RESEARCH #### CLOS // Cognitive Operating System 37-agent cognitive life operating system, agents named after the founders of the algorithms they wrap. ](/instruments/clos)[ CSR-02 RESEARCH #### NEURAL CHILD // Developmental Intelligence Five interacting neural networks (perception, memory, emotional processing, reasoning, communication) that learn through experience rather than bulk pretraining. ](/instruments/neural-child)[ CSR-03 RESEARCH #### QUICK NEURAL CHILD // Accelerated Lifecycle Rig Compressed deployment variant of Neural Child. ](/instruments/quick-neural-child)[ CSR-04 RESEARCH #### AXON // Earned Autonomy Architecture Autonomous self-monitoring system with a 7-label behavioral classifier, blockchain-anchored audit trail, cross-session diary memory, swarm architecture, and always-on daemon cycles. ](/instruments/axon)[ CSR-05 RESEARCH #### ARCHIE // Personal Language Model Personal language model forked from AXON, trained on 5GB of Notion exports. ](/instruments/archie)[ CSR-06 RESEARCH #### MIRROR // Biometric x Behavioral Correlates Apple Health biometric streams against AXON behavioral classifier logs on a single timeline. ](/instruments/mirror)[ CSR-07 RESEARCH #### MEMENTO // Time-scale Reckoning Life-in-weeks visualization instrument. ](/instruments/memento)[ CSR-08 RESEARCH #### CORA // Programmable Cognition Runtime and training curriculum system. ](/instruments/cora)[ CSR-09 RESEARCH #### CSUITE // Multi-LLM Boardroom Multi-LLM boardroom research instrument that simulates executive-tier deliberation across multiple model architectures. ](/instruments/csuite)[ CSR-10 RESEARCH #### COGNITIVE COMPILER // Build System for Thought Compiles raw cognitive output (voice journals, prompt traces, instrument logs) into structured cognitive artifacts. ](/instruments/cognitive-compiler) ### // ii. Civic and Legal [ CSR-11 RESEARCH #### EPPE // El Paso Proof Engine Civic accountability infrastructure anchoring public records, water system data, grid performance, and other municipal artifacts to an immutable chain. ](/instruments/eppe)[ CSR-12 RESEARCH #### VERDICT // Legal Intelligence Four-agent legal intelligence pipeline: JUDGE, CLERK, WITNESS, COUNSEL. ](/instruments/verdict)[ CSR-13 RESEARCH #### DEEP BLUE // Real-time Court STT Real-time courtroom speech-to-text pipeline. ](/instruments/deep-blue)[ CSR-14 RESEARCH #### NOTARY // Document Notarization Notarization service built on CCP. ](/instruments/notary)[ CSR-15 RESEARCH #### DISCIPLINE ENGINE // Hard Scope Constraints Module that enforces declared scope and behavior rules on agentic systems. ](/instruments/discipline-engine) ### // iii. Biometric and Embodied [ CSR-16 LIVE #### MORTEM // Biometric Stream Streams live pacemaker heartbeat data to the Solana blockchain. ](https://mortem-agent.xyz/)[ CSR-17 RESEARCH #### VITALS // Live Heartbeat Bezier heart path beating at 72 BPM with a scrolling EKG strip beneath. ](/instruments/vitals)[ CSR-18 RESEARCH #### HEALTHKIT INTEGRATION // Body x Language 1GB HealthKit XML parsing pipeline with streaming strategy. ](/instruments/healthkit-integration)[ CSR-19 RESEARCH #### BIOMETRIC LM // Body as Language Treats biometric streams (heart rate variability, skin conductance, breath patterns) as a language the model can read. ](/instruments/biometric-lm)[ CSR-20 RESEARCH #### VOICE JOURNALING PIPELINE // Continuous Capture Continuous audio capture, transcription, and cognitive pattern analysis. ](/instruments/voice-journaling-pipeline)[ CSR-21 RESEARCH #### AFTERLIFE // Archival Continuity Companion concept to MORTEM. ](/instruments/afterlife) ### // iv. Audio and Music [ CSR-22 RESEARCH #### FRISSON ANALYZER // Psychoacoustic Peaks MCP server that detects and classifies emotional peak responses (frisson) in audio. ](/instruments/frisson-analyzer)[ CSR-23 RESEARCH #### MYELIN // Frisson Topology Frisson network visualization instrument for the C-Cell production site. ](/instruments/myelin)[ CSR-24 RESEARCH #### MUSIC PRODUCTION MCP // Agentic Crate-Digging MCP server integrating the 172,000+ sample C-Cell library with agentic tooling. ](/instruments/music-production-mcp)[ CSR-25 RESEARCH #### REAPER DAW MCP // DAW Addressable MCP server bridging an LLM into the REAPER digital audio workstation. ](/instruments/reaper-daw-mcp)[ CSR-26 RESEARCH #### SOFT GIRL ERA MASTERING // Genre-bound Mastering Mastering pipeline tuned to the soft girl era sonic palette: warm low end, glassy highs, controlled dynamics, intimate stereo image. ](/instruments/soft-girl-era-mastering)[ CSR-27 RESEARCH #### PREDICTIVE BEAT MAPPER // Rhythm as Prior Predicts beat placement and rhythmic structure from incomplete audio. ](/instruments/predictive-beat-mapper)[ CSR-28 RESEARCH #### TRIBE // Live EQ Monitor 22-bar EQ visualization with organic frequency motion and live frisson detection. ](/instruments/tribe)[ CSR-29 RESEARCH #### BEAT MAP EDITOR // Author Tune Test Authoring tool for the soft girl era iOS rhythm game (11 tracks, distinct mechanics per track). ](/instruments/beat-map-editor)[ CSR-30 RESEARCH #### BEAT SABER TO ROBOTICS // Entertainment to Industry ~20,000 VR movement patterns extracted and converted into bimanual robotics training corpora. ](/instruments/beat-saber-robotics) ### // v. Infrastructure and Platforms [ CSR-31 RESEARCH #### CORTEX // Cognitive Manufacturing 14-agent manufacturing intelligence system. ](/instruments/cortex)[ CSR-32 RESEARCH #### CORTEX PLATFORM // Industrial Intelligence Delivered Multi-tenant applied intelligence SaaS substrate that hosts CORTEX-class deployments. ](/instruments/cortex-platform)[ CSR-ATR DEPLOYED #### ATRIUM // Clinical Workflow Intelligence Workflow intelligence for a specialty medical practice. Record handling met by the architecture, an audit grade trail over what the system did, and the physician holding the decision. ](/instruments/atrium)[ CSR-33 RESEARCH #### CCP // Celaya Chain Protocol The chain protocol underneath EPPE, NOTARY, MORTEM, and the VERDICT evidence anchoring layer. ](/instruments/ccp)[ CSR-34 RESEARCH #### SILT // Memory Across Time Persistent memory substrate. ](/instruments/silt)[ CSR-35 RESEARCH #### SYNAPSE / SYNAPSE-CLI // Many MCP, One Model MCP orchestration layer. ](/instruments/synapse)[ CSR-36 RESEARCH #### FORGE // Prompt Evolution Prompt optimizer. ](/instruments/forge)[ CSR-37 RESEARCH #### CONDUIT // View from the Bridge Dashboard surfacing live faces of instruments simultaneously: Vitals, MORTEM, CORTEX, CLOS, EPPE, VERDICT, Neural Child, SILT, TRIBE, MYELIN. ](/instruments/conduit)[ CSR-38 RESEARCH #### TOOL REGISTRY // Capability not Persona Module that holds tool schemas in a separate registry rather than the system prompt, so AXON's identity layer stays uncontaminated. ](/instruments/tool-registry)[ CSR-39 RESEARCH #### OPENCLAW // Agent as Deliverable Agent orchestrator and instrument packager. ](/instruments/openclaw)[ CSR-40 RESEARCH #### C-SUITE OS // OS, Not Note-app Operating system layer for executive-tier cognition. ](/instruments/c-suite-os)[ CSR-41 RESEARCH #### ACP // Swarm-safe Protocol for inter-agent coordination in autonomous swarms. ](/instruments/acp)[ CSR-42 RESEARCH #### TOKEN HEADER // Provenance Lightweight Provenance-stamping primitive that travels with model output. ](/instruments/token-header)[ CSR-43 RESEARCH #### SENTINEL // Did anything go wrong Watchdog agent that observes other agents and instruments for drift, scope violation, or quota anomaly. ](/instruments/sentinel)[ CSR-44 ROADMAP #### PROJECT JUPITER // Status Underdocumented Working-title project from Wave 3. ](/instruments/project-jupiter)[ CSR-WITNESS DOCUMENTED #### WITNESS // Industrial Agent Reads electrical drawings and live equipment telemetry, predicts faults with 3 to 25 hours of lead time, and is architecturally forbidden from touching a breaker. ](/instruments/witness)[ CSR-GREYBOOK DOCUMENTED #### GREYBOOK // Industrial Documentation Schneider, Rockwell and Siemens documentation crawled into one revision-aware corpus, answerable with citations back to the exact page. ](/instruments/greybook) ### // vi. Civic Tech and Tools [ CSR-ARK LIVE #### ARK // Biodiversity Archive Over 3.7 billion biodiversity records mirrored to local disk as 9,705 files and 286 GB, verified against per-artifact manifests, and rebuilt into a layout that answers in milliseconds. Native companion app included. ](/instruments/ark)[ CSR-ZTA TEACHING #### ZERO TO AGENT // Community Course Free eight week course in El Paso. Week 1 is what these tools are, Week 7 runs a model on your own hardware, Week 8 is a three minute demo from everyone. ](/instruments/zero-to-agent)[ CSR-45 RESEARCH #### RECALL // Production RAG Production RAG document intelligence service: Next.js, Qdrant, Nomic embeddings, Claude, SSE streaming, scanned PDF OCR via Claude vision, and scoped auth. ](/instruments/recall)[ CSR-46 RESEARCH #### TEXAS ARCHIVE // History Queryable Local-first RAG pipeline over 500 GB of historical Texas state documents (Python ingestion, Docling and PyMuPDF OCR, Qdrant, Ollama, Next.js). ](/instruments/texas-archive)[ CSR-47 RESEARCH #### BESS LAND PLATFORM // Battery Storage Intel Battery Energy Storage Systems land acquisition intelligence platform for El Paso. ](/instruments/bess-land-platform)[ CSR-48 RESEARCH #### BOT KILLER / STAPLE // Civic Surface Clean Bot detection platform concept developed with collaborators. Targets the bot-traffic problem in civic and commercial surfaces. ](/instruments/bot-killer)[ CSR-49 RESEARCH #### RALPH // Model to Objects MCP server bridging the Flipper Zero into the agentic stack. ](/instruments/ralph)[ CSR-50 RESEARCH #### INSIGHT EXTRACTOR GPT // Extract, Not Summarize Custom GPT in the CSR ecosystem. Extracts structured insight from raw documents, transcripts, and conversations. ](/instruments/insight-extractor-gpt)[ CSR-51 RESEARCH #### INSIGHT EXPLORER // Extract, Traverse Companion to Insight Extractor. Where Extractor pulls insight from a single document, Explorer navigates across a corpus to find related insights and surface their connections. ](/instruments/insight-explorer)[ CSR-52 RESEARCH #### GRAPH RECONNAISSANCE // Non-obvious, Legible Reconnaissance instrument that builds and traverses entity-relation graphs from unstructured text and public sources. ](/instruments/graph-reconnaissance)[ CSR-53 RESEARCH #### CUSTOM GPTS ECOSYSTEM // Cross-platform Reach Umbrella entry covering the multiple Custom GPTs (Insight Extractor, Insight Explorer, and others) deployed to the OpenAI marketplace as CSR secondary distribution channel. ](/instruments/custom-gpts-ecosystem) ### // vii. Hardware and Concepts [ CSR-54 RESEARCH #### LMU // Inference as First-class Silicon Silicon inference hardware concept: CPU to GPU to LMU. ](/instruments/lmu)[ CSR-55 RESEARCH #### INTELLIGENCE POWER SUPPLY // Infrastructure for Agents Conceptual instrument that maps electrical infrastructure to agent provisioning: a PSU for agents. ](/instruments/intelligence-power-supply)[ CSR-56 RESEARCH #### ROBOTICS SIMULATOR // Simulate Before Build Simulator that validates robotic motion patterns derived from the Beat Saber pipeline. ](/instruments/robotics-simulator)[ CSR-57 RESEARCH #### ABSORPTIVE LAYER 3 // Agentic Native Conceptual internet architecture proposal positing an absorptive layer between transport and application that handles intelligence-mediated content negotiation natively. ](/instruments/absorptive-layer-3)[ CSR-58 RESEARCH #### MERIDIAN // Naming Before Instrument Meta-framework for cross-domain pattern transfer. ](/instruments/meridian)[ CSR-59 RESEARCH #### ALIGNMENT FRAMEWORK // Alignment Continuous Framework for ensuring alignment between agent behavior and operator values across the full instrument stack. ](/instruments/alignment-framework)[ CSR-60 RESEARCH #### SANTA TERESA SIMULATION // Pre-deployment Sandbox Simulation of the Santa Teresa border region: cross-border industrial flow, infrastructure exposure, water and grid coupling. ](/instruments/santa-teresa-simulation)[ CSR-61 RESEARCH #### SOFT GIRL ERA (IOS) // Playable Instrument iOS rhythm game with 11 tracks, distinct mechanics per track, soft girl era sonic and visual aesthetic. ](/instruments/soft-girl-era-ios) ### // viii. Brand and Public [ CSR-62 RESEARCH #### CHRISCELAYA.COM TERMINAL // Civilian-readable Claude Terminal-style interface at chriscelaya.com, powered by the Anthropic API. ](/instruments/chriscelaya-terminal)[ CSR-63 RESEARCH #### CSR BRAND SYSTEM // Aesthetic is Instrument The Celaya Solutions identity standard: #000000 / #FFFFFF / #FF6B35 / #06D6A0 / #FFBE0B. ](/instruments/csr-brand-system)[ CSR-64 RESEARCH #### CELAYASOLUTIONS.COM // Front Door / Lab Public-facing website for the CSR lab. ](/instruments/celayasolutions-com)[ CSR-65 RESEARCH #### PINAX // Index for the Library Codex/index instrument in the public-facing instrument lineage. ](/instruments/pinax)[ CSR-66 ROADMAP #### IMAGO // Codex Visual Public-facing visual/iconographic instrument in the codex lineage. Specifics flagged for spec fill-in. ](/instruments/imago)[ CSR-67 RESEARCH #### SOUL.MD // Operator Persona Identity / character document. ](/instruments/soul-md) ### // ix. Papers and Frameworks [ CSR-68 RESEARCH #### EAA PAPER // Preprint Complete Academic preprint co-authored with Renato Kuipers. ](/instruments/eaa-paper)[ CSR-69 RESEARCH #### CSR-2026-001 // Family Named First numbered CSR research paper. Establishes geometric mean as a security primitive across CCP, CLOS, EPPE, and VERDICT. ](/instruments/csr-2026-001)[ CSR-70 RESEARCH #### COHERENCE EQUATION // Make Coherence Visible Operator-coined equation for measurable coherence: C = A x CE x I x CB x S x E. ](/instruments/coherence-equation)[ CSR-71 RESEARCH #### CSR PORTFOLIO ASSESSMENT // Defensible Figure Formal assessment of the CSR portfolio using COCOMO II methodology, market analysis, and IP replacement modeling. ](/instruments/csr-portfolio-assessment)[ CSR-72 RESEARCH #### CODEX OF THE HELLENES // Index for Library Methodology document underlying Pinax. Frames CSR research practice in a codex / library tradition rather than a startup / product tradition. ](/instruments/codex-of-the-hellenes)[ CSR-GEO5 RESEARCH #### GEO5 // Geometric Language System A model that receives five explicit binary components per symbol instead of an arbitrary character identity. Hypothesis stated as unproven, confirmatory experiment specified in advance. ](/instruments/geo5)[ CSR-BYTEFRAME RESEARCH #### BYTEFRAME // Tokenizer-Free Architecture No tokenizer, no vocabulary table, no learned embedding lookup. Byte identity enters through a fixed spectral projection with no RNG anywhere. ](/instruments/byteframe)[ CSR-ALIGN PUBLIC #### ALIGNMENT EXPERIMENT // Safety Evaluation Harness A fully contained reproduction of Anthropic’s agentic-misalignment work. No network egress, all identities fictional, results aggregated across sweeps. ](/instruments/alignment-experiment) ### // Orchestration views [ CSR-100 RESEARCH #### NETWORK OVERVIEW // All Instruments Federated Macro view of every instrument in the registry, federated through the SYNTHISIA coherence judge. ](/instruments/network-overview)[ CSR-101 RESEARCH #### FEDERATION FLOW // Query Routed and Traced A single query traverses SYNTHISIA, routes to three instruments based on permutation evaluation, and returns federated with full reasoning trace. ](/instruments/federation-flow) ## Research Source: https://celayasolutions.com/research *Markdown view of [https://celayasolutions.com/research](https://celayasolutions.com/research). The canonical page is HTML at the same URL.* // 001 · Research ## Research The lab publishes its work in the open. The current showcase is CORRIDOR, a civic accountability field paper on El Paso's hyperscale data center buildout, alongside the Trinidad archival intelligence instrument, the lab's scholar papers, and the measured case studies from client work. // Showcase · Field paper FIELD PAPER ### The Data Center Decade on the Border A grounded, source-verified account of El Paso's hyperscale data center buildout: what was promised, what was actually signed, and the single contract term that decides whether the bet pays. Current to June 18, 2026. 80%tax abated, 15 years 50job floor in the contract $10Bstated investment 1.5Mgal/day water permitted [Read the field paper](/research/corridor) // 002 · Instruments and papers CSR-DC STANDING RECORD ### El Paso data centers The standing public record on the regional data center buildout: power, water, land, incentives, and the policy framework the city is still writing. The load and consumption figures every argument rests on, kept in one place with their sources attached. Studies What a hyperscale buildout costs a desert grid and a desert aquifer, and who is answerable for the numbers. Produces A cited public record, a comment packet, and the argument EPPE was built to anchor. [Read the record](/research/data-centers) CSR-Trinidad LIVE ### Trinidad Trinidad is an archival intelligence system over 5,435 rare Texas historical documents, with 1,065,357 passages indexed, deployed at trinidad.town. Studies How historical records can become an evidence-aware retrieval and reasoning surface while keeping source material visible. Produces Source-linked retrieval paths and archival intelligence outputs over the Texas historical corpus. [Read about Trinidad](/research/trinidad) CSR-FACET BRIEFING ### FACET A multi-perspective briefing that runs five expert lenses over one question: should El Paso enact a time-boxed pause on new data center incentives until its policy framework is adopted? Then it grades its own work. Type Research briefing / multi-perspective instrument. Published June 18, 2026 · Celaya Solutions Research. [Read the briefing](/research/facet) CS:CCSIP-2026-001 PAPER ### Celaya Chain Protocol A coherence-based governance whitepaper framing Celaya Chain Protocol as a Layer 3 architecture for reputation, biological identity, governance, and trust infrastructure. Scholar-friendly HTML and archival PDF. Type Technical report / Layer 3 blockchain architecture. Published February 22, 2026 · Christopher Celaya. [Open HTML](/research/CCP-Scholar-v1) [Open PDF](/research/CCP-Scholar-v1.pdf) CSR-EAA-2026-001 PAPER ### Earned Autonomy Architecture A technical report describing a self-monitoring applied intelligence architecture that classifies, modifies, and measures its own behavioral patterns through earned autonomy, structural separation, and coherence metrics. Type Technical report / self-monitoring applied intelligence systems. Published April 2026 · Christopher Celaya. [Open HTML](/research/EAA-Scholar-v1) [Open PDF](/research/EAA-Scholar-v1.pdf) CSR-2026-001 PAPER ### Coherence as a security primitive The paper that names the family resemblance the instruments were already enacting. Authority as a trajectory rather than a state: a non-compensatory geometric mean across five axes of verified intent, two temporal decay terms, and a biological axis that cannot be delegated. States the coalition resistance problem formally and proposes a candidate resolution. Type Technical report / distributed security and mechanism design. Open for peer review. Published April 2026 · Christopher Celaya. [Open HTML](/research/CSR-2026-001-Scholar-v1) [Open PDF](/research/CSR-2026-001-Scholar-v1.pdf) CSR-2026-002 PAPER ### Multi-dimensional intent alignment The framework companion to CSR-2026-001. The same authority function, written as a working specification: two temporal decay terms, five axes under governed weights, a biological axis that cannot be delegated, and the attack surface set out one class at a time. Coalition resistance is stated as an open problem rather than answered. Type Technical report / coherence verification and runtime attestation. Open for peer review. Published April 2026 · Christopher Celaya. [Open HTML](/research/CSR-2026-002-Scholar-v1) [Open PDF](/research/CSR-2026-002-Scholar-v1.pdf) // 003 · Case studies Measured field reports from the lab. Every report starts with a real, measured baseline, then keeps score. The lab reads its own bills to the penny before it tells you anything. CSR-002 LIVE EXPERIMENT ### The inference bill that never stops An autonomous back office agent quietly ran up a roughly 28,000 dollar a year model bill, and 62 percent of it was pure waste. This is how the lab measured it, and the Recall framework and Mila agent built to take it back. Published June 2026 · El Paso, Texas. [Read the case study](/case-studies/inference-bill) CSR-001 COST REPORT ### Token and API cost report The measured token-level cost baseline behind CSR-002: where a roughly 28,000 dollar a year model bill goes, and the plan to take most of it back. Client identity and project names withheld. Published June 2026 · El Paso, Texas. [Read the report](/case-studies/token-cost-report) CSR-003 IN PROGRESS ### Mila, measured Mila's full cost ledger across all eight companies she runs, measured the same way as the first report. Lands here next. Status Not yet published. // 004 · Animated equations The equations behind the papers, rendered as short silent animations. Each one is embedded beside the equation it explains inside the paper it belongs to. This is the reel that runs them together. // REEL 001 · authority decay, coherence composite, coherence plateaus, ledger chain · silent ## El Paso data centers Source: https://celayasolutions.com/research/data-centers *Markdown view of [https://celayasolutions.com/research/data-centers](https://celayasolutions.com/research/data-centers). The canonical page is HTML at the same URL.* // Position · El Paso del Norte corridor ## Data centers, water, and power, *on terms the public can enforce.* I am not against data centers. **I build the equipment they run on.** My concern is narrow and factual: El Paso and Santa Teresa are approving facilities that consume large volumes of our water and power without enforceable limits, and shifting the cost and risk onto residents. [Read the public comment packet](/assets/el-paso-data-center-public-comment-packet.pdf) **Christopher Celaya** Founder, Celaya Solutions Research LLC 12+ years electrical infrastructure Submitted to El Paso City Council, June 9, 2026 8.71MGD Documented regional water surplus, the figure the City has never shown its math against 17.9% Share of that surplus the Northeast El Paso facility alone is authorized to draw 2,880MW Self-supplied gas microgrid authorized for the Santa Teresa project across the basin 50jobs Permanent jobs required for one El Paso campus, total, not per phase 01 / Where I stand ### The rules are too weak, and the same pattern will repeat unless the City sets enforceable terms now. My background is electrical infrastructure: more than twelve years, including critical power systems at large data centers and switchgear manufacturing. I have read the public records behind the region's data-center projects and run the water and power math, and I have submitted that work, sourced and reproducible, for the Council's consideration. The draft **Data Center Policy Framework** is a good list of goals. It has no teeth. It should be replaced with an enforceable ordinance: a special permit and a Council vote, a buffer from homes and schools, a potable-water cap with reclaimed-water cooling, public metering and reporting, one hundred percent applicant-paid cost causation, daily penalties, and a teardown bond. I do not raise the specifics of any one deal to single out a company. **Each project followed the rules that exist today.** The point is that the rules let our water and power leave the table without limits, and the City can fix that with a law that applies equally to everyone, before the next signature. “I am not against data centers or technology. I build the equipment they run on. My concern is that the City is approving facilities that consume large volumes of our water and power without enforceable limits.” **From the public comment letter** Christopher Celaya to Mayor Johnson and the El Paso City Council · June 9, 2026 02 / The one question I ask answered on the record On the record Which water-supply number did the City rely on to find we have enough water for data centers, and where is it published? El Paso Water provides on the order of 105 million gallons per day, with a documented regional surplus on the order of 8.71 million gallons per day. The Northeast El Paso facility alone is authorized for up to 1.5 million gallons per day. **If that supply number cannot be shown with a citable source, the approvals rest on trust, not data.** 105 MGD provided by El Paso Water 8.71 MGD documented surplus 1.5 MGD authorized, one facility 17.9 % of surplus, that facility alone 03 / What the public record shows ### What El Paso gave up for one data center. Every line below is drawn from the executed agreements for the Northeast El Paso project (Chapter 312, Chapter 380, and the Stan Roberts records), counterparty WURLDWIDE LLC, d/b/a Statue LLC. What the City gaveFrom the signed agreements 01 **80% property-tax abatement**, 10 years per phase, up to 5 phases (Chapter 312) 02 A second **80% property-tax grant**, 15 years per phase, with no dollar cap (Chapter 380) 03 **$5,000,000** in Texas Economic Development road funds 04 Up to **$9,000,000** reimbursing the company's road costs 05 **All impact, permit, review, and park fees waived** 06 **~1,039 acres of City land**, sold to the company 07 A **35-year lock-in** that auto-extends, with a promise not to tax or regulate data centers for the term What the City gotIn return 50 **permanent jobs, total.** Not per phase. Remote workers count toward it. Wage floor near $16.43/hour. Jobs not required for roughly a decade. · A building the company is **not required to construct** · Inspection once a year, escorted, under a non-disclosure agreement The bottom line And the oversight the City *surrendered* × **No cap on water.** Terms sit in a separate El Paso Water agreement that is not public. × **No cap on power.** No ceiling on electrical demand anywhere in the contracts. × **No cost-causation.** Nothing makes the company pay for the utility upgrades it forces, so residents' bills absorb them. × **No noise, air, or environmental limits**, and no community-benefit requirement. × A duty to **fight residents' public-records requests** for the company, at the Texas Attorney General. × Almost **no clawback** if the project underdelivers. El Paso cannot easily undo this deal. It can refuse to repeat it. The fix is a city law that sets clear, equal terms before the next signature. 04 / The region as a whole ### Three projects. Two states. One basin and one airshed. These facilities draw on the same regional water basin and the same air. They are being approved at the same time, with no public study of the three of them together. Northeast El Paso, Texas Meta WURLDWIDE LLC, d/b/a Statue LLC Authorized potable water, full build-out1.5 MGD Grid load~100 MW Permanent jobs required50 total Socorro, TX Wiwynn El Paso County, same basin Grid load~150 MW Cumulative regional studyNone on file Shares aquifer with El PasoYes Santa Teresa, NM · Doña Ana County Project Jupiter Case D-307-CV-2025-02766 Self-supplied gas microgrid2,880 MW Nitrogen oxides emitted~499 tons/yr Water claims backed by technical dataNo 2,173 MW El Paso Electric reports a record peak demand of **2,173 MW** against roughly **2,300 MW** of capacity, projects large-load-driven needs of up to **1,650 MW**, and has proposed billions in upgrades and a residential rate increase. El Paso is non-ERCOT, so the 2025 Senate Bill 6 large-load protections do not reach it. That is the regulatory gap a city ordinance can close. 05 / What I am asking the Council to do ### Five things, before the next approval. 1 #### Adopt an enforceable ordinance Generally applicable to all hyperscale data centers, in place of the non-binding framework: special permit and Council vote, a 1,000-foot buffer from homes and schools, a potable-water cap with reclaimed-water cooling, public metering and reporting, 100% cost causation, daily penalties, and a teardown bond. 2 #### Publish the water-supply number State the supply figure relied upon for data-center approvals, with its source. If the math cannot be shown, do not approve further capacity. 3 #### Require a cumulative regional study Count Meta, Wiwynn, and the adjacent Doña Ana County project together, for water and power, before any new approval, phase, or incentive. 4 #### Make operators pay for what they cause One hundred percent of the utility upgrades they trigger, with no rate increases on residents, and require the water and interconnection service agreements be filed with the City and made public, redacted only as the law requires. 5 #### Require a decommissioning bond before operation Financial assurance equal to the full cost of teardown and site restoration, posted before a certificate of occupancy, so an empty facility never becomes the public's liability. 06 / The work on file ### What I have built and submitted. Independent, sourced, and reproducible. Not an official City of El Paso publication, and not legal advice. [ PDF Submitted June 9, 2026 #### Public Comment Packet The comment letter, the exhibit, and a filled, court-ready model ordinance, submitted to the City Council and City Plan Commission. Download the packet ](/assets/el-paso-data-center-public-comment-packet.pdf)[ LAW Part C · ready for City Attorney review #### Model Data Center Ordinance A neutral, generally applicable draft amending Title 20: definitions, zoning, performance standards, metering, enforcement, and decommissioning, with 16 local-policy values filled in. Read the draft ](https://celaya-solutions.github.io/Draft-Policy) REC Public instrument · runs on RECALL #### CORRIDOR, the public record Do not take my word for any of this. CORRIDOR gathers the primary documents for all three projects and answers questions with the sources attached, fingerprinted so the record cannot be quietly altered. Record temporarily offline DATA Evidence Record · CS-INST-007 #### Water & load analysis The water-supply math and the El Paso Electric load study behind the figures on this page, compiled in the companion Evidence Record with citations to every source. In the Evidence Record Inside the packet Part A Public comment letter The position, the one question, and the five asks, addressed to the Mayor and Council. Part B Exhibit What El Paso gave up for one data center, line by line, from the executed agreements. Part C Model ordinance A filled, neutral, court-ready ordinance written for introduction and City Attorney review. 07 / The movements ### How this got on the record. Feb 17, 2026 #### Council directs staff to draft a framework The City Council directs staff to develop a data center policy addressing impacts on water, energy, infrastructure, and the community. Feb 2026 #### CSR water analysis I run the regional water-supply math: the 105 MGD provided, the 8.71 MGD surplus, and the 17.9% one facility is authorized to draw. Celaya Solutions water analysis Spring 2026 #### Load study, instrument CS-INST-007 The El Paso Electric load study: record peak against capacity, the large-load need, the proposed upgrades and rate increase, and the non-ERCOT regulatory gap. Citing EPE 2024 System Expansion Plan, EPE All-Source RFP (July 2025), and others May 2026 #### City staff publishes the draft framework The staff Data Center Policy Framework circulates: a list of goals, with no enforceable limits. Jun 9, 2026 #### Public comment packet submitted The letter, exhibit, and model ordinance go to the City Council and City Plan Commission, copied to the City Clerk for the record and the City Attorney. Jun 15, 2026 #### CORRIDOR goes public The full document set for all three projects opens to the public, searchable, with every answer carrying its sources. Ongoing #### Available to brief, at no cost Open to brief the Council, the City Plan Commission, or City staff on the analysis and the ordinance. 08 / Where this is being discussed ### Out in the open. #### r/ElPaso and the local conversation I have been posting this work and answering questions in public. If you want to weigh in, push back, or ask for a source, these threads are the place. The record is meant to be argued with. - [r/ElPaso I created a multi-agent simulation to predict the vote](https://www.reddit.com/r/ElPaso/comments/1qkpce0/i_created_a_multi_agent_ai_simulation_to_predict/) - [r/ElPaso The Meta data center vote failed 5-3 Tuesday](https://www.reddit.com/r/ElPaso/comments/1u6k0r0/the_meta_data_center_vote_failed_53_tuesday_the/) - [r/ElPaso I made a bilingual tool to look up the El Paso data center deal](https://www.reddit.com/r/ElPaso/comments/1u73ho1/i_made_a_bilingual_tool_to_look_up_the_el_paso/) 09 · Engage ### I will brief Council, the Commission, or staff. At no cost. If you are a resident, a reporter, or sit on the Council, and you want the analysis walked through or the ordinance explained, reach out. **The math is reproducible and the sources are open.** Independent · sourced · no fee [hello@celayasolutions.com](mailto:hello@celayasolutions.com?subject=El%20Paso%20data%20center%20ordinance) [Get the packet](/assets/el-paso-data-center-public-comment-packet.pdf) **Independent, sourced, and reproducible. Not an official City of El Paso publication, and not legal advice.** Company and agency names are used only to identify the public matters discussed. Every figure on this page is drawn from the executed agreements and public filings compiled in the companion Evidence Record. Citations to area facilities support generally applicable standards and do not direct any proposed ordinance at a single project. Prepared by Christopher Celaya, Celaya Solutions Research LLC, El Paso, Texas, June 2026. ## El Paso as a research environment Source: https://celayasolutions.com/el-paso-research-lab *Markdown view of [https://celayasolutions.com/el-paso-research-lab](https://celayasolutions.com/el-paso-research-lab). The canonical page is HTML at the same URL.* // El Paso, Texas, 31.7619 N, 106.4850 W ## Applied Intelligence and LLM Research Lab in El Paso, Texas Celaya Solutions Research is an independent applied intelligence and large language model research lab in El Paso, Texas. CSR builds local-first applied intelligence systems, provenance-aware research instruments, multi-agent orchestration tools, archival intelligence over Texas historical records, and industrial applied intelligence for manufacturing, data centers, maquiladora operations, and the Ciudad Juarez-El Paso border region. [Explore CSR research instruments](/research) [Border manufacturing and maquiladora applied intelligence](/border-manufacturing-research) [Return to the homepage](/) ### Why El Paso is the research context El Paso gives an applied intelligence research lab a practical environment rather than an abstract market category. The region sits at the intersection of industrial infrastructure, manufacturing, data centers, historical archives, cross-border logistics, bilingual operator workflows, and applied research needs. That context makes the city useful for studying applied intelligence systems and large language models that must work near operators, evidence, physical constraints, and institutional records. CSR uses the phrase applied intelligence research lab El Paso in a literal way: the lab is located in El Paso, Texas, and the work is centered on research instruments rather than generic software packaging. As an applied intelligence company El Paso can point to, Celaya Solutions Research focuses on artificial intelligence El Paso use cases where local constraints matter. El Paso applied intelligence research is not treated as a slogan. It is the condition that shapes what the lab studies. ### LLM research framed by place Most large language model discussion is detached from where the model runs and what records it touches. CSR's LLM research treats place as a first-class variable. The lab studies how LLMs behave when retrieval is bound to a known corpus, when inference is kept local where it should be, when outputs must trace back to a record, and when operators reviewing the output may not work in the same language as the model's training distribution. Local-first LLM deployment, provenance-aware generation, and multi-agent orchestration are the architectural answers CSR develops as research instruments, not as managed services. ### Industrial and manufacturing conditions Local-first applied intelligence systems are especially relevant in environments where data movement, latency, review, and consequence cannot be ignored. Industrial applied intelligence research for manufacturing, data centers, medium-voltage systems, and operational infrastructure requires different assumptions than consumer software. Applied intelligence infrastructure systems have to account for human oversight, failure modes, physical process timing, and the cost of wrong automation. CORTEX, CSR's 14-agent manufacturing intelligence platform, is the lab's documented research instrument in this domain. ### Ciudad Juarez, maquiladoras, and the Paso del Norte Borderland El Paso is one half of a binational metropolitan region. Across the Rio Grande is Ciudad Juarez, Chihuahua, and together the two cities form one of the densest manufacturing corridors in North America. The Paso del Norte Borderland contains hundreds of *maquiladora* assembly and manufacturing operations producing electronics, automotive components, medical devices, and aerospace parts. CSR's industrial applied intelligence research is shaped by this reality: applied intelligence instruments for border manufacturing must respect bilingual documentation, cross-border data sovereignty, USMCA logistics, and operator review boundaries that look different on each side of the bridge. See the lab's dedicated [border manufacturing and maquiladora applied intelligence](/border-manufacturing-research) research framing for detail. ### Archival conditions The Borderland also contains dense archival and civic record contexts. Provenance-aware applied intelligence and archival intelligence systems matter when LLM outputs need to trace back to documents, events, ledgers, or historical records. A system that summarizes, generates, notarizes, or reasons over records should expose how it arrived at an answer. That is why multi-agent applied intelligence systems at CSR are studied through evidence, traceability, and role boundaries rather than through ungrounded LLM output alone. Trinidad, the lab's archival intelligence instrument, operates over 5,435 rare Texas historical documents, with 1,065,357 passages indexed. ### Borderland technology research Cross-border logistics and regional infrastructure make El Paso a serious setting for Borderland technology research. The lab does not claim formal partnerships, deployments, or affiliations beyond what is stated in this site. It does claim a research focus: building instruments that explore local-first applied intelligence systems, large language model architecture, industrial applied intelligence research, provenance-aware applied intelligence, archival intelligence systems, and human-judgment-preserving architecture from El Paso, Texas. As a Texas applied intelligence research lab, CSR links place to architecture. The research question is not only what models can produce. It is where the data moves, who reviews the output, what evidence remains visible, what language the operator speaks, and how a system behaves when it is used near real infrastructure, real records, or a real international border. ### Contact For research inquiries, architecture conversations, or documentation requests, contact [hello@celayasolutions.com](mailto:hello@celayasolutions.com). Inquiries are welcome in English or Spanish. ## Border manufacturing Source: https://celayasolutions.com/border-manufacturing-research *Markdown view of [https://celayasolutions.com/border-manufacturing-research](https://celayasolutions.com/border-manufacturing-research). The canonical page is HTML at the same URL.* // Paso del Norte, El Paso, Texas and Ciudad Juarez, Chihuahua ## Border Manufacturing and Maquiladora Applied Intelligence Research Celaya Solutions Research studies applied intelligence and large language model systems for border manufacturing and maquiladora operations across the Ciudad Juarez-El Paso corridor. The research focus covers local-first applied intelligence for the plant floor, multi-agent orchestration, bilingual operator workflows, USMCA-aware logistics reasoning, and provenance-aware industrial applied intelligence built for the realities of the Paso del Norte Borderland. [Read about CORTEX manufacturing intelligence](/instruments/cortex) [Applied intelligence research lab in El Paso](/el-paso-research-lab) [All research instruments](/research) ### Why the border corridor is a research environment The Ciudad Juarez-El Paso corridor is one of the densest manufacturing regions in North America. Hundreds of *maquiladora* assembly and manufacturing operations across Ciudad Juarez, Chihuahua produce electronics, automotive components, medical devices, aerospace parts, and consumer goods, integrated into supply chains that cross the international bridge multiple times before reaching a final customer. El Paso, Texas hosts the logistics, customs brokerage, warehousing, and data center capacity that supports that flow. The result is a binational industrial system that exposes every interesting question in industrial applied intelligence at once. An applied intelligence instrument that is honest about this environment cannot treat manufacturing as a uniform abstraction. It must respect operator language, data sovereignty, regulatory boundaries, latency on the line, and the fact that the same physical part may be touched by two countries before it ships. Border manufacturing applied intelligence research is therefore where industrial applied intelligence, LLM architecture, and cross-border systems meet. ### Maquiladora-specific research questions CSR's research framing treats maquiladora operations as a specific case of industrial applied intelligence rather than as a generic factory scenario. The questions that shape the work include: - How should a large language model handle **bilingual operator workflows** where shift instructions, exception notes, and quality logs are written in Spanish and reported upstream in English? - What does **local-first applied intelligence** mean when the plant floor is in Ciudad Juarez and the corporate data center is in El Paso, Dallas, or another country entirely? - How should an applied intelligence instrument handle **USMCA documentation**, certificates of origin, and customs paperwork without inventing facts a broker would not have signed? - How should **multi-agent orchestration** divide responsibility between line monitoring, exception classification, supervisor escalation, and human review across a cross-border shift? - How should **provenance** behave when a single inference may be cited later in a regulated audit on either side of the border? ### CORTEX as the lab's manufacturing instrument CORTEX is CSR's 14-agent manufacturing intelligence platform and the lab's most direct research surface for border manufacturing applied intelligence. CORTEX studies how a coordinated set of specialized agents, observation, retrieval, exception classification, supervisor summary, audit, and others, can support manufacturing contexts where latency, review, constraints, and operational consequence matter. Read more on the [CORTEX manufacturing intelligence platform page](/instruments/cortex-landing). ### Local-first LLM architecture for the plant floor A maquiladora line cannot wait on a round trip to a far-away inference endpoint, and a sensitive process record should not always cross a border just to be summarized. Local-first LLM deployment is a research path the lab takes seriously because it answers both pressures at once: keep critical inference, routing, and evidence handling close to the operator, and only escalate to cloud LLMs when the architecture explicitly authorizes it. This framing applies as well to data center workflows in El Paso that support customers in Ciudad Juarez and across northern Mexico. ### Bilingual and bicultural operator design An applied intelligence instrument used in a maquiladora is an instrument used by a bilingual workforce. CSR's research treats this as a design constraint instead of as a translation feature. Operator interfaces, LLM prompts, retrieval indexes, and audit records all have to make sense in Spanish on the line and in English to corporate review. That requirement changes how prompts are written, how retrieval corpora are curated, and how multi-agent transcripts are stored. ### Cross-border data sovereignty and USMCA context Border manufacturing applied intelligence cannot ignore that *where* data lives is a regulated question. CSR's research framing distinguishes between observation data (often local), aggregated reporting (often cross-border), regulated documentation (USMCA, customs, FDA, ITAR depending on sector), and audit-grade provenance records. An LLM instrument that conflates these surfaces makes the system riskier to operate. CSR's instruments are designed to keep that separation visible. ### Honest scope The lab does not claim formal deployments, contracts, or partnerships inside specific maquiladora operations beyond what is documented on this site. It does claim a research focus: building research instruments, CORTEX, CLOS, EPPE, VERDICT, RECALL, and the surrounding architecture, that take maquiladora and border manufacturing context seriously instead of pretending the line is generic. ### Contact For research collaboration, architecture conversations, or documentation requests from operators, plant engineering teams, customs brokers, supply chain researchers, or border manufacturing journalists, contact [hello@celayasolutions.com](mailto:hello@celayasolutions.com). Inquiries are welcome in English or Spanish. ## Method Source: https://celayasolutions.com/method *Markdown view of [https://celayasolutions.com/method](https://celayasolutions.com/method). The canonical page is HTML at the same URL.* // Method · The lab runs on its thesis ## One operator. An agent fleet. The numbers in public. Celaya Solutions Research is run by one person, with applied intelligence doing the leverage work that a staff would otherwise do. That is not a confession. It is the research method: the lab is its own first testbed, and this page is the living record of how it runs. Frontier labs are the thousand people; they cannot publish this experiment. A one-operator lab can. // 001 · The loop ### Agents draft. The operator signs. The record shows both. Every instrument, paper, film, and page this lab ships moves through the same loop. An agent fleet does retrieval, drafting, building, and verification sweeps. The operator reviews, corrects, and signs, and answers for the result with his name on it. This is the same discipline the lab sells: provenance-aware systems where a human stays accountable. The lab does not ask clients to run a loop it does not run on itself. CSR-METHOD-01 // ONE PASS THROUGH THE LOOPEvery public artifact - 01 Frame: the operator states the question, the constraints, and what evidence would settle it - 02 Fleet: agents sweep sources, draft, build, and check the work against the record - 03 Verify: load-bearing figures get confirmed against primary sources, dated, and tiered - 04 Sign: the operator reads it, fixes it, ships it, and takes the blame if it is wrong // 002 · The human, live ### The loop has exactly one human. You can watch him be alive. The operator streams his heart rate from a wearable to this site in real time. It is the accountability claim made physical: there is a person in this loop, he is particular, and he is not hiding behind a brand. When the wearable is off, the trace says so instead of pretending. CSR-OPS-000 // OPERATOR TELEMETRY · HEART RATEidle 72 bpm Source: Apple Watch 1 of 2One operator · One heartbeat · In public // 003 · The numbers ### What one human plus a fleet actually produces. These are the same counts the site footer reports. Nothing here is projected, annualized, or rounded up. When a number grows, this page changes and the change is dated in the dispatches. CSR-METHOD-02 // OUTPUT REGISTRYDefined counts only 1operator, zero employees 9live public deployments 2published papers 2brand films, made in house - 1,065,357 passages indexed across 5,435 rare Texas historical documents, live at trinidad.town - 18 dated sources in the CORRIDOR reference list, each linked from the paper and checked June 18, 2026 - 1 instrument catalog spanning research and operations, documented on the instruments page // 004 · The cadence ### One dispatch a month, minimum. In writing. A lab that publishes a timestamp owes you the next one. Each dispatch records what changed in the CORRIDOR record, what the lab shipped, and what broke. If a month passes without one, hold the lab to it: the promise is public and so is the inbox. [Read Dispatch 001](/notes/dispatch-001) [All notes and dispatches](/notes) // Work with the lab ### This method is for hire. The same loop that runs this lab can run on your records, your floor, your archive. Evidence in, provenance out, a human accountable at every step. [Start a build](/intake) [Read the research](/research) ## Press kit Source: https://celayasolutions.com/press *Markdown view of [https://celayasolutions.com/press](https://celayasolutions.com/press). The canonical page is HTML at the same URL.* // Press · Media kit ## Everything you need to cite the lab correctly. Boilerplate at three lengths, verified statistics that carry their own citations, brand assets, and a direct line to the operator. Every figure on this page is checked against a primary source before it ships. If you find one that is wrong, say so and it gets corrected with priority. // 001 · Boilerplate ### Copy-ready descriptions. CSR-PRESS-01 // SHORT · ONE SENTENCE Celaya Solutions Research is an independent research lab and consultancy in El Paso, Texas, that builds systems to make data coherent: search, retrieval and agents where every answer shows its source and a person makes the call. CSR-PRESS-02 // STANDARD · ONE PARAGRAPH Celaya Solutions Research is an independent research lab and consultancy in El Paso, Texas, founded in 2024 and run by Christopher Celaya. It builds systems that make data coherent: search over documents that answers with the page and revision, agents that work across a specialist's tools and record what they did, and records checked against each other with the evidence attached. Public instruments include Trinidad, a searchable archive of 5,435 rare Texas historical documents; ARK, a local mirror of the global biodiversity record holding over 3.7 billion entries; and CORRIDOR, a source-verified record of El Paso's data center buildout. Nine instruments are deployed and publicly reachable. CSR-PRESS-03 // FULL · PROFILE Celaya Solutions Research is an independent research lab and consultancy in El Paso, Texas, founded in 2024 and run by Christopher Celaya, who spent twelve years in industrial electromechanical systems, hyperscale data center operations and medium-voltage switchgear manufacturing before building software. The lab builds systems that make data coherent: every answer traces to the record it came from, inference can stay on local hardware, and a person makes the consequential call. Its client work includes custom agents that connect a specialist's market, accounting and operations tools into one governed workflow. Its public work includes Trinidad, an archive of 5,435 rare Texas historical documents with 1,065,357 passages indexed and answerable in public; ARK, a mirror of the global biodiversity occurrence record holding more than 3.7 billion entries, verified against per-artifact manifests; and CORRIDOR, a source-verified civic record of El Paso's hyperscale data center buildout. Nine instruments are deployed and publicly reachable. The lab publishes its research and its sources at celayasolutions.com. // 002 · Fast facts ### The lab, in numbers that are defined. CSR-PRESS-04 // REGISTRYSame counts the site footer reports 2024founded, El Paso, Texas 1operator, zero employees 9live public deployments 2published papers - 5,435 rare Texas historical documents in the Trinidad corpus, 1,065,357 passages indexed, live at trinidad.town - 3.7B biodiversity occurrence records mirrored to local disk in ARK, 9,705 files and roughly 286 GB, verified against per-artifact manifests - 9 instruments deployed and publicly reachable: Trinidad, MORTEM, ARK, GALEN, VERDICT, ATRIUM, DRAMATURG, PACEMAKER and Zero to Agent - 2 papers: the CORRIDOR field paper and the FACET briefing, both source-verified and citable - 1 live heartbeat: the operator streams his heart rate to the site in real time as a working claim about human accountability // 003 · Verified statistics ### The El Paso data center record, checked against primary sources. From the CORRIDOR field paper, current to June 18, 2026. Each line copies with its citation attached. Reconfirm against the cited primary sources before use in testimony. CSR-QUOTE-01 // COPY WITH CITATIONCurrent to June 18, 2026 - 80% of property tax abated for 15 years in the Meta data center agreement - 50 jobs is the contractual job floor in the same agreement - 1.5M gallons of water per day permitted for the buildout, in a desert city - $10B stated investment, against the 50-job contractual floor Full context, method, and the primary sources behind each figure: [the CORRIDOR field paper](/research/corridor). Copy-ready plain and BibTeX citations sit at the end of each paper. // 004 · Brand assets ### Marks, cards, and films. CSR-PRESS-05 // ASSETSUse as-is, do not restyle - SVG Vernier mark, color and mono [color](/assets/img/vernier.svg) [mono](/assets/img/vernier-mono.svg) - PNG Social card, wordmark and vernier on black, 1200 by 630 [download](/assets/img/csr-social-card.png) - MP4 FILM 001, the lab boot sequence, 30 seconds, silent [download](/assets/video/csr-brand-film-landscape.mp4) - MP4 FILM 002, instruments install, 41 seconds, silent [download](/assets/video/csr-parade-wide.mp4) - WEB Brand guidelines: type, color, voice, and usage rules [open](/celaya-solutions-brand-guidelines) // 005 · Contact and license ### One operator, one inbox. For interviews, data requests, or corrections, write to [hello@celayasolutions.com](mailto:hello@celayasolutions.com) or call [(915) 755-5705](tel:+19157555705). There is no communications team between you and the person who did the work. Corrections to any published figure are handled with priority over everything else. Site content is licensed [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/): quote it, chart it, republish it, with attribution. Suggested citations for the lab and each paper are on the [legal page](/legal#cite) and at the end of every paper. ## Legal, data and citation Source: https://celayasolutions.com/legal *Markdown view of [https://celayasolutions.com/legal](https://celayasolutions.com/legal). The canonical page is HTML at the same URL.* // LEGAL ## Legal, data, and compliance Plain statements about who operates this site, how its content may be used, what the site collects, and what the lab's compliance language does and does not claim. If something here is not yet backed by a real statement, it is marked as such rather than asserted. [Who runs the lab](/about) [Return to the homepage](/) // 001 · Entity ### Legal entity This site and the research surface it presents are operated by **Celaya Solutions LLC**, a limited liability company based in El Paso, Texas. Celaya Solutions Research is the research and publication name used by that entity. Business inquiries go to [hello@celayasolutions.com](mailto:hello@celayasolutions.com). // 002 · License ### Content license Unless a page states otherwise, the written content, research notes, and technical reports published on this site are © 2026 Celaya Solutions LLC and licensed under [Creative Commons Attribution 4.0 International (CC BY 4.0)](https://creativecommons.org/licenses/by/4.0/). You may share and adapt the material with attribution. The instrument source code itself is not published on this site and is not covered by this license. // 003 · Citation ### Suggested citation To cite the lab as a whole, use: Celaya, C. (2026). Celaya Solutions Research. El Paso, Texas. https://celayasolutions.com Individual technical reports carry their own copy-ready citation, license, and DOI or arXiv badge on the [research](/research) page and on each paper. Those identifier slots are pre-wired and render automatically once an identifier is registered. // 004 · Data Collection ### What this site collects This website is hosted on Railway. Hosting and email providers process request metadata and inquiries to operate the site and deliver messages. - The theme preference is stored in your browser. The site fonts are self-hosted. - The short inquiry form sends your name, email, problem description and any optional fields to the website backend, which uses Resend to deliver email to the lab. Do not send confidential documents, sensitive personal information or credentials. - The optional detailed questionnaire stays in the page until you request an automated estimate or open an email draft. Requesting an estimate sends the project description to the backend and may use the configured OpenAI or Anthropic service. The draft is not a paid diagnostic or a quote. Sending an email draft requires you to send it in your mail application. - The existing PostHog integration records explicit contact clicks, work-example clicks, form starts and acknowledged submissions. Automatic element capture and session recording are disabled. These events include the page and language, not names, email addresses or inquiry text. Analytics providers still receive standard connection metadata. - The lab archive includes an optional view of the operator’s wearable telemetry. Opening that page connects to HypeRate. Commercial pages do not load that connection. For questions about access, providers or retention, contact [hello@celayasolutions.com](mailto:hello@celayasolutions.com). Data handling for a commissioned project is agreed separately. // 005 · Compliance ### ATRIUM compliance posture ATRIUM is described elsewhere on this site as a specialty-practice document instrument designed around healthcare privacy principles. To keep that language honest, here is the plain statement behind it: ATRIUM is architected around the safeguards HIPAA expects of systems that touch protected health information: role-based access control, audit logging of access and actions, the minimum-necessary principle for data exposure, and a workflow that keeps a licensed physician in the review loop before any output is used. This describes a *design posture*. It is not a claim of formal HIPAA certification, a completed third-party audit, or a signed Business Associate Agreement, and none of those should be inferred from the word "architected." Do not submit protected health information through this public marketing site. Any production deployment that would handle real patient data is handled under separate, direct agreement, not through this website. ### Other compliance language The lab does not currently make biometric-certification, security-certification, or regulatory-approval claims on this site. Where an instrument touches sensitive data domains, the language is meant to describe design intent and is backed by the posture stated above. If you find a claim on this site that reads as a certification we have not earned, email [hello@celayasolutions.com](mailto:hello@celayasolutions.com) and it will be corrected. ## Sitio en espanol Source: https://celayasolutions.com/es *Markdown view of [https://celayasolutions.com/es](https://celayasolutions.com/es). The canonical page is HTML at the same URL.* [English](/) El Paso, Texas · Inglés y español ## Hacemos que los datos sean coherentes. Tus manuales, registros, datos de mercado y herramientas de negocio rara vez concuerdan entre sí. Celaya Solutions construye los sistemas de búsqueda, consulta y agentes que los reúnen en un solo registro, donde cada respuesta muestra la fuente de la que salió y una persona puede comprobarla. [Solicitar una llamada](/es/contratar#contact)[Ver el trabajo](/es/trabajo) 01 · Qué construimos ### Tres formas que toma el trabajo. #### Búsqueda que cita su fuente Haz una pregunta sobre manuales, procedimientos y registros aprobados. La respuesta llega con el documento, la página y la revisión de donde salió, y avisa cuando los documentos no responden. #### Agentes que trabajan con tus herramientas Un solo agente que lee tus datos de mercado, contabilidad, archivos y tableros de trabajo, actúa solo mediante las acciones que tú configuras y registra lo que hizo. #### Registros que se comprueban entre sí Telemetría, testimonios o archivos contrastados unos con otros. Donde no concuerdan, el sistema lo señala con la evidencia adjunta en lugar de disimularlo. [Qué incluye cada uno](/es/servicios) 02 · Pruebas ### Construido, en marcha y público donde se puede. - En vivo · trinidad.town ### Trinidad 5,435 documentos históricos raros de Texas, consultables en público. Cada respuesta enlaza al registro del que salió. [Cómo funciona Trinidad (inglés)](/research/trinidad) - Desarrollo para un cliente · alias públicos ### Morpheus Un solo agente para los datos de mercado, corretaje, contabilidad, archivos, tableros de trabajo y flota de un operador intradía. [Ver qué se conectó](/es/morpheus) - Investigación industrial · evaluado en simulación ### WITNESS Lee planos, telemetría, historial de mantenimiento y reglas de seguridad, y señala fallas con horas de anticipación y una recomendación con citas. [Método y resultados (inglés)](/instruments/witness) - Prototipo · rastreador y plataforma en marcha ### GREYBOOK Documentación de interruptores y tableros de cinco fabricantes en un solo catálogo, con control de revisiones y cada respuesta citando la página exacta. [Ver el esquema del catálogo (inglés)](/instruments/greybook) [Todo el trabajo](/es/trabajo) Cómo funciona ### Cuatro pasos, una decisión en cada uno. 1. ### Llamada gratuita Cuéntanos el problema, quién lo tiene y qué te cuesta hoy. Sin cuestionario ni documentos. 2. ### Diagnóstico a precio fijo, hasta $3,000 Un informe escrito: qué datos tienes, qué falta, qué construir y qué no construir. A veces la respuesta es no construir nada. 3. ### Desarrollo o piloto Con alcance y precio propios, hitos que puedes inspeccionar y una forma de medir si funcionó. 4. ### Entrega Código fuente o sistema alojado, documentado, con soporte y costes de operación por escrito antes de empezar. El alcance y el precio quedan por escrito antes de cualquier trabajo pagado. La consultoría fuera de un desarrollo cuesta $125 por hora. [Cómo trabajamos, en detalle](/es/proceso) 04 · Quién ### Una sola persona, de principio a fin. Christopher Celaya dirige el laboratorio y hace el trabajo. Pasó doce años en sistemas electromecánicos industriales, operación de centros de datos a gran escala y fabricación de tableros de media tensión antes de dedicarse al software. Los hábitos vinieron con él: conservar la fuente, registrar cada cambio y dejar la decisión importante en manos de una persona. [Sobre Christopher](/es/acerca) El siguiente paso ### Empieza por el problema. Escríbenos unas líneas sobre quién necesita ayuda y qué no cuadra. La primera llamada es gratuita. No incluyas archivos confidenciales. [Solicitar una llamada](/es/contratar#contact)[hello@celayasolutions.com](mailto:hello@celayasolutions.com) Investigación El laboratorio también publica: artículos sobre coherencia y autonomía, un informe de campo sobre los centros de datos de El Paso y un catálogo de instrumentos con los despliegues en vivo señalados. [Investigación (inglés)](/research) · [Catálogo de instrumentos (inglés)](/instruments) ## CORRIDOR Source: https://celayasolutions.com/research/corridor *Markdown view of [https://celayasolutions.com/research/corridor](https://celayasolutions.com/research/corridor). The canonical page is HTML at the same URL.* // Civic accountability research · CORRIDOR ## The Data Center Decade on the Border El Paso committed public land, desert water, and new grid capacity to hyperscale applied intelligence. This is a grounded account of what was promised, what was actually signed, and the single contract term that decides whether the bet pays. By **Celaya Solutions Research** Instrument **CORRIDOR** Record current to **June 18, 2026** [All research](/research) [Run the impact simulator](#simulator) Abstract In December 2023 the El Paso City Council unanimously approved a tax abatement to bring a Meta data center to a 1,000 acre parcel in the Northeast. Two years and one applied intelligence boom later, that project has grown from a 1.5 billion dollar facility into a 10 billion dollar, one gigawatt campus, with a dedicated natural gas power plant being built to run it and a permit to draw up to 1.5 million gallons of water a day in a desert.[2](#r2)[3](#r3) The public arrived late, and loudly. In May 2026 the Council voted unanimously to stop recruiting future hyperscale projects; in June it spent seven hours hearing residents before voting, five to three, that it could not legally walk away from the deal it had already signed.[5](#r5)[14](#r14) This paper sets out the verified record on all three projects CORRIDOR tracks, presents the strongest version of both the booster and the critic case, and then names the load bearing finding: net benefit is not decided by jobs or investment headlines. It is decided by deal structure. The decisive term is the combination of an eighty percent, fifteen year abatement with a binding floor of fifty permanent jobs, and the real cost is the opportunity cost of public inputs that were committed before the public could weigh in. 01 ### The record, dated Three hyperscale projects now sit inside a single metro airshed and a single stressed watershed. El Paso did not drift into the data center business. It chose it, on specific dates, through specific votes. On December 5, 2023, under then Mayor Oscar Leeser, the Council unanimously approved economic development agreements with Wurldwide LLC, a Meta affiliate, for a site in Northeast El Paso. Of the representatives serving today, only two were in the room for that vote: District 8's Chris Canales and District 6's Art Fierro.[19](#r19) Meta broke ground in October 2025, and in March 2026 announced it was raising its investment more than sixfold.[7](#r7)[9](#r9) CORRIDOR follows three developments across the El Paso and Santa Teresa corridor. They differ in jurisdiction and disclosure, which is exactly why they belong in one frame. Project A #### Meta / Wurldwide LLC The anchor. One gigawatt, 10 billion dollars, online 2028. Five construction phases, phase one underway, first portion expected operational July 2026. Northeast El Paso, Texas Project B #### Project Jupiter / Acoma LLC Under construction across the state line in Doña Ana County, drawing on the same regional grid and labor market under a different set of rules. Santa Teresa, NM Project C #### Fort Bliss / federal site Recently announced. City staff name it alongside Meta as a source of added emissions, but it sits on federal land outside ordinary city review. Fort Bliss, TX City staff have estimated that powering these facilities would raise El Paso's carbon dioxide emissions by about twenty one percent over a 2019 baseline.[12](#r12) The three projects share air, water, transmission, and a construction workforce. No single permitting process sees all three at once. CORRIDOR exists to hold them in one view. 02 ### The deal, read closely The headline is investment and jobs. The contract is an abatement and a floor of fifty. Strip away the announcements and read the instrument. Under the 2023 Chapter 380 agreement, if Meta invests at least 800 million dollars, the City abates up to eighty percent of its property taxes for fifteen years. El Paso County layered on its own abatement. The El Paso Times estimated the combined package could be worth up to 110 million dollars.[2](#r2) On top of that, the City allocated up to 5 million dollars in economic development funds to help defray the cost of the project's connection to U.S. Highway 54.[22](#r22) 80% city property tax abated, 15 years, if 800M invested $110M est. value of combined city + county package 50 permanent jobs the contract actually requires 300+ operational jobs Meta now says it will create $10B stated investment, up from 1.5B in March 2026 The gap between the last two figures is the whole accountability problem in one line. Meta says it will employ more than three hundred people once the campus is complete, and more than four thousand at peak construction. The agreement obligates it to fifty.[3](#r3)[5](#r5) A promise is not a covenant. When the abatement is locked for fifteen years and the binding employment floor is fifty, the public's leverage to convert the larger number into a guarantee has already been spent. There is a real point on the booster side that honest accounting has to keep. The parcel was previously city owned land, managed by El Paso Water and the Public Service Board, transferred to the City for industrial development before Meta ever appeared. As public land it generated no property tax at all. So even an eighty percent abatement leaves the remaining twenty percent, plus the land base and sales tax on construction materials, as revenue the rolls did not have before.[15](#r15) The deal is not free money for nothing. But that framing, public land versus private use, is also the trap, and we return to it in Section 06. 03 ### Water, in a desert Permitted for 1.5 million gallons a day. Estimated at 400,000. The distance between those numbers is the argument. El Paso Water supplies cooling water to the Meta site under an agreement permitting up to 1.5 million gallons per day. The utility's own estimate of actual average use is far lower, around 400,000 gallons per day, roughly 146 million gallons a year. CEO John Balliew has been precise about why: below 86 degrees the facility uses essentially nothing for cooling, and only a 117 degree day would push it toward the permitted maximum. At 400,000 gallons a day the data center would not crack the utility's top ten customers; it lands around number eleven, behind schools and hospitals.[20](#r20)[25](#r25) 1.5M gal/day the water agreement permits ~400K gal/day utility estimates as the average No. 11 rank among El Paso Water customers at that level 200% of water consumed that Meta pledges to restore Balliew has stressed that Meta pays the highest large user rate with no special rate and no rebate, and that the utility's 2026 budget and roughly twelve percent rate increase were not driven by the data center.[23](#r23) Meta, for its part, has pledged to restore two hundred percent of the water it consumes through Rio Grande watershed projects, micro irrigation upgrades for pecan orchards, and partnerships to bring running water to colonias, projects it expects to restore more than 177 million gallons a year once implemented.[26](#r26) Taken at face value, that is a genuine commitment, and a better one than most host communities secure. Two facts keep the concern alive anyway. First, this is a city that in the same window suffered a 36 inch water main rupture leaving roughly 100,000 Northeast and Central residents without adequate pressure, under a boil water notice.[23](#r23) Reliability, not just supply, is the lived issue. Second, and more important, the water figures above describe the original 1.5 billion dollar facility. Neither Meta nor the utility has released an updated forecast for the 10 billion dollar, one gigawatt campus, which observers expect could climb toward a million gallons a day.[22](#r22) The number the public is debating is the old number. The water figure most often quoted in public is for a facility that no longer exists at that scale. 04 ### Power, and the air that pays for it A gigawatt of constant demand does not come from the existing grid. It comes from a new gas plant built to order. To serve Meta, El Paso Electric is building a dedicated facility: a roughly 500 million dollar, 366 megawatt natural gas plant, developed with the generator company Enchanted Rock and reported to use hundreds of small gas fired units.[18](#r18)[21](#r21) That plant carries an air permit authorizing significant annual emissions, including on the order of 68 tons of nitrogen oxides, a precursor to the ozone El Paso already struggles with.[18](#r18) 366 MW dedicated gas plant being built for the site ~$500M plant cost, initially covered by Meta +21% city CO2 vs 2019, per city staff estimate 68 tons NOx/yr the plant is permitted to emit Here the structure matters as much as the chemistry. Meta states that it pays the full cost of serving the data center, plans to add more than 5,000 megawatts of clean energy to the Texas grid, and intends to match one hundred percent of its electricity use.[4](#r4) Opponents, reading El Paso Electric's filings, counter that the plant's cost is structured to shift to all ratepayers after an initial period Meta covers, and they note that the original agreement explicitly stated Meta "shall not be obligated to pursue" the solar and alternative energy it had floated.[9](#r9)[21](#r21) A pledge to match clean energy and a contractual release from having to build it can coexist on the same page. Which one governs in 2030 is the open question. 05 ### The two cases, fairly Accountability work earns its authority by stating the other side at full strength. Here it is, both ways. The case for - **Real tax base on land that had none.** Public land off the rolls becomes a taxable industrial site, with the non abated share, the land, and construction sales tax flowing to local services. - **High wage anchor and signal.** The Borderplex Alliance argues the jobs are transformational and that Meta marks El Paso as a place serious capital will come. - **A revenue customer for the utility.** Constant data center load is steady cash flow that residential customers do not provide, the utility's CEO argues, part of a larger growth vision. - **Costs borne by Meta, by its account.** Full water and energy costs, 8 million dollars in local infrastructure, 130 plus local vendors, a 200 percent water restoration pledge, and bill assistance funding. - **A track record elsewhere.** The mayor of Los Lunas, New Mexico, reports more than 2.5 billion dollars of Meta investment over a decade and 6 million dollars to local schools and nonprofits. The case against - **A floor of fifty.** Fifteen years of abatement are locked against a binding requirement of fifty permanent jobs, while the public debates the 300 figure it cannot enforce. - **Scarce water, committed first.** Up to 1.5 million permitted gallons a day in a desert with recent main breaks and boil notices, and no released forecast for the larger campus. - **A gas plant and its airshed.** A new 366 MW fossil plant and a projected 21 percent rise in city CO2, in a region already out of step with its own climate plan. - **Cost shifted to ratepayers.** Critics read the utility's filings to mean residents eventually carry plant costs, after Meta's initial period, even as bills already rise. - **Decided behind the public.** The terms were set in 2023; transparency demands, including from Congresswoman Veronica Escobar, came after, not before, the leverage was gone. Both columns are true at once. That is not indecision. It is the actual shape of the problem: a deal can deliver real revenue and real jobs and still be a poor trade if the inputs it consumes were worth more in another use, and if the public never got to price them. 06 ### The analysis Net benefit does not hinge on how big the investment is. It hinges on how the contract is built. Load bearing finding The decisive variable is deal structure, and the single most decisive term is whether the scarce inputs are taxed and bound by enforceable benefits, or abated and released. El Paso wrote an eighty percent, fifteen year abatement against a fifty job floor. That structure, not the ten billion dollar number, determines the return to the community. There is a useful contrast in the public record. In jurisdictions that tax the servers and equipment heavily rather than abating them, data centers have become large net contributors to local budgets, because the taxable value sits in the constantly refreshed hardware, not the land. El Paso took the other path: abate the improvements, keep the land base. Whether that path pays depends entirely on enforceable floors, escalators, and benefit terms, the very things a fifty job minimum does not provide. The collective blind spot **Opportunity cost.** Because the parcel was public land already off the tax rolls, every comparison defaults to "data center versus nothing," which makes any private use look like pure upside. That framing hides the real question: was this the best use of that specific water allocation, that grid capacity, that publicly held land, against every alternative the City could have pursued with the same scarce inputs? A debate framed as "something versus nothing" can never surface the better something. The mechanism that lets a weak structure get signed is information asymmetry. El Paso's history of non disclosure on these projects, and the still unreleased water forecast for the expanded campus, mean the public consistently debates last year's numbers while the operative terms sit in instruments few have read. The developer always knows the real figures. The community rarely does, until the vote is behind it. What is already changing The City's May 2026 policy direction is the structural fix arriving in real time: no incentives for future hyperscale projects, binding community benefit agreements instead of abatements, special permits, and a pause on selling public land for this use.[17](#r17) That is the correct lever. It does not touch the Meta deal, which is the point: the fix is for the next one, and the next one is already announced at Fort Bliss and across the line at Santa Teresa. CORRIDOR's role follows from this directly. Keep the executed terms in daylight, track the fifty job floor against the three hundred job promise as the campus opens, publish the campus scale water forecast the moment it exists, and hold the community benefit framework to enforceable language rather than aspiration. Accountability here is not opposition. It is making the trade legible enough that the public can judge it on the real numbers. The public record behind this analysis is the source list at the end of this paper. Every load-bearing figure traces to it. 07 ### What to watch Seven indicators will tell you whether the bet is paying, long before the rhetoric does. 01 First phase goes live, July 2026 Watch whether reported hiring tracks toward 300 or settles near the contractual 50. 02 Campus scale water forecast The 400,000 gallon figure is for the old facility. The updated number for the gigawatt campus is the one that matters. 03 Who pays for the 366 MW plant Track the El Paso Electric proceeding to see if and when plant costs move from Meta to ratepayers. 04 The clean energy match, verified Pledged 5,000 MW of clean energy versus a contractual release from pursuing it. Watch what actually interconnects. 05 November election Several incumbents who declined to reopen the deal face voters. Recall mechanics under the City Charter are already being discussed. 06 Community benefit agreements with teeth Whether the new framework produces enforceable floors and escalators, or aspirational language, on Fort Bliss and the next applicant. 07 Project Jupiter terms across the line Santa Teresa operates under New Mexico rules. The corridor's total water and grid draw is the sum, not any one project. // Method and limits ### How this paper was built, and what it cannot claim This field paper combines three passes: a multi source research sweep, an independent CORRIDOR analysis of the deal structure, and a live verification of every load bearing figure against primary local reporting and the City of El Paso's own materials, conducted June 18, 2026. Every number in the stat blocks was confirmed against a dated source listed below. Read the figures by tier. Verified the deal date and terms, the 50 job floor, the abatement structure, the 1.5 million permitted and 400,000 estimated water figures, the council votes, and the gas plant scale and permit. Reported, evolving the 10 billion dollar investment, 300 and 4,000 job projections, and the 200 percent water restoration pledge, all from Meta and not yet independently realized. Contested the eventual shift of plant cost to ratepayers, the campus scale water draw, and whether clean energy commitments will be met. A note on stance. This paper presents the booster case at full strength and credits genuine commitments where the record supports them. It also takes a position: that deal structure, not investment size, is the decisive variable, and that the public priced its scarce inputs too late. That is an analytical judgment, argued from the evidence, not a neutral recitation. Readers weighing public testimony or policy should confirm any figure against the cited primary source before relying on it, particularly the New Mexico and federal projects, which sit outside the El Paso records cited here. ### References 1. **Plan to run El Paso data center on natural gas sparks concern.** Inside Climate News / The Texas Tribune, Jan 26 2026. [texastribune.org](https://www.texastribune.org/2026/01/26/texas-el-paso-meta-data-center-natural-gas-power-plant/) 2. **Inside the power deal behind Meta's El Paso data center, now at 10 billion.** El Paso Matters, Mar 29 2026. [elpasomatters.org](https://elpasomatters.org/2026/03/29/meta-data-center-el-paso-10-billion-expansion-water-gas-electricity-usage/) 3. **Meta to spend 10 billion on applied intelligence data center in El Paso, 1GW by 2028.** CNBC, Mar 26 2026. [cnbc.com](https://www.cnbc.com/2026/03/26/meta-to-spend-10-billion-on-ai-data-center-in-el-paso-1gw-by-2028.html) 4. **El Paso City Council rejects effort to end Meta data center agreement.** El Paso Matters, Jun 9 2026. [elpasomatters.org](https://elpasomatters.org/2026/06/09/meta-data-center-deal-to-remain-el-paso-city-council-rejects-terminating-agreement/) 5. **Meta increases investment in El Paso data center to 10 billion.** Bloomberg, Mar 26 2026. [bloomberg.com](https://www.bloomberg.com/news/articles/2026-03-26/meta-increases-investment-in-el-paso-data-center-to-10-billion) 6. **Big things are happening, El Paso.** Meta Data Centers (company blog), Mar 2026. [datacenters.atmeta.com](https://datacenters.atmeta.com/2026/03/big-things-are-happening-el-paso/) 7. **Proposal seeks stricter oversight, no tax breaks for future applied intelligence data centers.** El Paso Matters, May 21 2026. [elpasomatters.org](https://elpasomatters.org/2026/05/21/el-paso-city-council-data-center-policy-no-tax-breaks-incentives/) 8. **El Paso City Council votes to stop recruiting data center projects.** KTSM / Border Report, May 26 2026. [borderreport.com](https://www.borderreport.com/news/environment/el-paso-city-council-votes-to-stop-recruiting-data-center-projects/) 9. **Data Centers (policy framework and project facts).** City of El Paso, official page, 2026. [elpasotexas.gov](https://www.elpasotexas.gov/) (the data center page has since moved) 10. **City of El Paso releases draft policy framework to regulate future hyperscale data centers.** CBS4 Local, May 2026. [cbs4local.com](https://cbs4local.com/newsletter-daily/city-of-el-paso-releases-draft-policy-framework-to-regulate-future-hyperscale-data-centers) 11. **El Paso city representative seeks to terminate Meta data center deal.** El Paso Matters, Jun 2 2026. [elpasomatters.org](https://elpasomatters.org/2026/06/02/el-paso-texas-meta-data-center-cancel-contract-tax-breaks-water-pollution/) 12. **El Paso can't cancel Meta data center tax breaks, top officials say.** El Paso Matters, Jun 3 2026. [elpasomatters.org](https://elpasomatters.org/2026/06/03/el-paso-texas-meta-data-center-tax-breaks-cancel-contract-water-air-pollution/) 13. **How much water will Meta's El Paso data center use?** El Paso Matters, Dec 2 2025. [elpasomatters.org](https://elpasomatters.org/2025/12/02/el-paso-texas-meta-data-center-water-usage/) 14. **El Paso residents rally against Meta data center agreement.** KISS El Paso (commentary; figures corroborated against cited reporting), Jun 2026. [kisselpaso.com](https://kisselpaso.com/public-opposition-el-paso/) 15. **El Paso City Council to start work on limiting datacenters next week.** El Paso Herald Post, May 22 2026. [elpasoheraldpost.com](https://elpasoheraldpost.com/2026/05/22/el-paso-city-council-to-start-work-on-limiting-datacenters-next-week/) 16. **El Paso Water adopts 1.2 billion budget with rate increase.** El Paso Matters, Jan 14 2026. [elpasomatters.org](https://elpasomatters.org/2026/01/14/el-paso-water-approves-budget-2026-12-rate-increase-monthly-bills/) 17. **El Paso Water CEO: Meta data center not in top 10 water users.** KTSM, Dec 28 2025. [ktsm.com](https://www.ktsm.com/news/el-paso-water-ceo-meta-data-center-not-in-top-10-water-users/) 18. **Meta touts 10B El Paso data center, water and grid pledges as council weighs incentives.** CBS4 Local, Jun 2026. [cbs4local.com](https://cbs4local.com/newsletter-daily/meta-touts-10b-el-paso-data-center-water-and-grid-pledges-as-council-weighs-incentives) ### Cite this paper The citation below is copy ready. The report number is stable and this URL is the canonical record. A DOI slot is pre-wired and will render here once an identifier is registered. CSR-CORRIDOR-2026-001 // PLAIN CITATION Celaya Solutions Research (2026). The Data Center Decade on the Border: a grounded account of El Paso's hyperscale buildout. Technical report CSR-CORRIDOR-2026-001, Celaya Solutions Research, El Paso, Texas. Current to June 18, 2026. https://celayasolutions.com/research/corridor BIBTEX @techreport{csr2026corridor, author = {{Celaya Solutions Research}}, title = {The Data Center Decade on the Border: a grounded account of El Paso's hyperscale buildout}, institution = {Celaya Solutions Research}, number = {CSR-CORRIDOR-2026-001}, year = {2026}, month = jun, address = {El Paso, Texas}, url = {https://celayasolutions.com/research/corridor}, note = {Current to June 18, 2026} } CORRIDOR is a civic accountability research instrument from Celaya Solutions Research. This field paper is independent analysis for public information, not legal, financial, or investment advice. Figures are current to June 18, 2026 and should be reconfirmed against the cited primary sources before use in testimony, comment, or reporting. // Tool · Scenario model ### Impact simulator Set which projects come online and when, then scrub the timeline to model corridor water draw, air emissions, the household utility bill and the share of income it consumes, and basin stress. The bill model counts only projects on El Paso Electric's grid; the water model counts all of them. Every coefficient is exposed, sourced, and editable. Interactive model. Outputs depend on the assumptions set in the controls. Reconfirm figures against primary sources before relying on them. ## FACET Source: https://celayasolutions.com/research/facet *Markdown view of [https://celayasolutions.com/research/facet](https://celayasolutions.com/research/facet). The canonical page is HTML at the same URL.* // Research briefing · FACET ## Should El Paso enact a time-boxed pause on new data center incentives until the policy framework is adopted? Seat: **Civic accountability researcher / public commenter** Scope: **City of El Paso, the incentive lever** Horizon: **Decision now, 15 to 20 year stakes** Lenses: **Finance, organizer, developer, regulator, historian** Grounding: **Web-grounded to June 18, 2026** [All research](/research) The 60-second read A time-boxed pause on new data center incentives until the framework is adopted is low-cost, legally clean, and largely formalizes what the council already decided unanimously on May 26. The evidence that incentives drive these investments is weak: Meta grew from 1.5 to 10 billion dollars after its deal was signed, and Project Jupiter is proceeding next door on different rules. The case is strongest if the pause is coupled to a hard framework-adoption date and framed as a pause on subsidies, not construction, the legally bulletproof lever. The honest limit: the corridor's largest water and grid pressures, Jupiter and Fort Bliss, sit outside city jurisdiction, and no El Paso pause can reach them. 01 ### Five lenses on the question L1 #### Municipal finance economist A pause on new incentives costs El Paso almost nothing in foregone investment, because the binding constraint on these projects is scarce water, grid, and land, not subsidies. The real fiscal danger is signing more 15-year, 80-percent-abated deals with 50-job floors before the city can price the inputs it has already committed below cost. Strongest evidence Meta increased its El Paso commitment sixfold, from 1.5 to 10 billion dollars, after the abatement was signed, proving the incentive was not the deciding factor. The El Paso Times put the city and county package at up to 110 million dollars; the contract's binding job floor is 50. Only this lens sees A pause does not lose deals, it preserves the city's pricing power over public land already moved off the tax rolls, water sold at the standard rate, and a dedicated 366 MW plant whose cost may shift to ratepayers. L2 #### Community organizer A pause is the minimum democratic response to a community that filled seven hours of council comment and nearly 200 speakers in opposition, asked to absorb water, air, and bill impacts from deals it had no say in. The pause restores the sequence that should have come first: rules, then deals. Strongest evidence The June 9 hearing drew almost 200 speakers, mostly opposed, yet the council still declined even to open renegotiation, 5 to 3. Residents face roughly 200 dollars a month in utility bills against a median income near 59,900, with first-time participants and Gen Z students now packing the chamber. Only this lens sees The cost of not pausing is not fiscal, it is legitimacy. Every new abated deal signed ahead of the framework deepens the trust gap and the recall energy, which is itself a real governance cost. L3 #### Developer / industry practitioner A short, defined pause tied to a known endpoint is survivable and even clarifying for serious developers; what deters capital is open-ended uncertainty, not a transparent rule-making window. A pause that drifts, or that signals El Paso is closing to the applied intelligence economy, risks ceding the next tier of tenants mid-boom. Strongest evidence Capital is flowing to the region regardless of the hostility: Meta grew to 10 billion amid open opposition, and Project Jupiter at 2.45 gigawatts is proceeding across the line in Santa Teresa on a different rule set. The Borderplex Alliance frames the applied intelligence supply chain as a once-in-a-generation window. Only this lens sees The competitive risk is not losing Meta, which is locked, but losing the next tenants and suppliers who read a messy retroactive fight as political risk. A clean pause-to-framework reads as discipline; a chaotic one reads as a place that changes the deal after you build. L4 #### Regulator / policy A pause on new incentives is legally clean and largely redundant with the council's own May 26 direction, which already withholds abatements, rebates, and fee waivers from future hyperscale projects. Codifying it as a formal pause-until-framework simply removes ambiguity and staff discretion, and it cannot touch the executed Meta agreement. Strongest evidence When Hill County tried to pause data center construction, developer RCM Hill sued in federal court arguing Texas counties lack moratorium authority, and the county rescinded. A home-rule city declining its own discretionary subsidies is categorically different: you cannot be compelled to grant a tax abatement. Only this lens sees The choice of lever is everything. Pausing incentives, not construction, is the legally defensible path; the Hill County case proves the construction-ban alternative gets struck down. The pause's real job is sequencing, closing the gap a motivated developer would target. L5 #### Historian Host communities that paused to write rules before competing on subsidies consistently fared better than those that signed first and regulated later. The megadeal-then-regret arc is the dominant pattern, from Foxconn Wisconsin to El Paso's own 2023 Meta vote that two sitting council members now publicly regret. Strongest evidence Foxconn Wisconsin pledged 10 billion dollars and 13,000 jobs for billions in subsidies, delivered a fraction, and the site eventually became a data center. El Paso's own Meta deal was approved unanimously and is now openly regretted; Rep. Canales has said he is sorry for his role in it. Only this lens sees El Paso has run this boom-and-bust before. ASARCO, Phelps-Dodge, and the garment finishers once drew more than a million gallons a day and then left. The abatement-chasing host keeps the liabilities, the airshed and the drawn-down aquifer, after the capital moves on. 02 ### Where the lenses collide Conflict 1 // Do incentives drive the investment? Finance economist Meta's sixfold increase after the deal proves incentives are not binding. Pausing forfeits nothing. vs Developer The next tier of tenants and suppliers reads incentive withdrawal as closing for business and routes elsewhere. Conflict 2 // Does the pause actually do anything? Regulator It largely restates the May 26 policy. Mostly symbolic sequencing, not a radical act. vs Community organizer Symbolism matters. It is the democratic signal residents are owed, and it closes the gap a developer would exploit. Conflict 3 // What is the real cost? Community organizer The cost of not pausing is legitimacy and trust, already cashing out as recall energy. vs Developer The cost of a drifting, open-ended pause is ceding the applied intelligence window to other metros. Strongest position The regulator. It is grounded in what already legally happened on May 26 and in the Hill County precedent, and it reframes the pause as low-cost procedural insurance rather than a gamble. The finance economist runs a close second; the sixfold-increase fact is hard to argue with. Weakest position The developer's competitive-flight claim. On current evidence it is not borne out: Jupiter is proceeding next door on different rules and Meta grew amid open hostility. Open-ended uncertainty does deter in principle, but the specific "El Paso loses the boom" framing is unsupported by what is actually happening. The question that resolves it Is the pause time-boxed to the imminent framework, and is it on incentives rather than construction? If yes to both, nearly every lens supports it: low cost, high legitimacy, clean sequencing, firm legal ground. Decouple it from a hard deadline, or aim it at construction, and the deterrence and litigation risks become real. What every lens agrees on None of the five argues for signing new incentive deals in the current gap before the framework is adopted. All agree the Meta deal is contractually locked and not the subject of this decision. All agree the rules should govern; the only disagreement is whether a formal pause adds value over the policy already in place. The blind spot nobody is watching The debate is entirely about future city incentives, but the corridor's largest pressures come from projects a city pause cannot touch: Project Jupiter, 2.45 gigawatts on an islanded microgrid in New Mexico, and Fort Bliss, 3 gigawatts on federal land with no city review. The city controls the smallest lever in the system. 03 ### Findings, ranked by what they can bear 01 #### A pause forfeits almost no investment The incentive is not the binding factor in these siting decisions, so withdrawing it loses little. confidence 9 / 10 support: Meta 1.5B to 10B after the dealsupport: Jupiter proceeding in Santa Teresa 02 #### Pause incentives, not construction, the legally bulletproof lever A home-rule city declining its own discretionary subsidies is categorically safer than a construction ban, which Texas courts have already rejected. confidence 9 / 10 support: Hill County RCM lawsuit and rescissionchallenge: any moratorium label draws legal fire 03 #### Legally clean, and mostly codifies the May 26 policy The council already voted unanimously to stop incentivizing future hyperscale projects. The pause removes ambiguity; it cannot and must not touch the locked Meta deal. confidence 9 / 10 support: May 26 unanimous votesupport: city attorney on Meta deal 04 #### Time-boxing is the decisive design choice Pause-until-framework, with the framework weeks away after the June 16 comment close, collects nearly every benefit. Open-ended, it invites the one real downside. confidence 8 / 10 support: framework in staff finalization now 05 #### The legitimacy cost of not pausing is real and rising Seven hours of comment, recall energy in the chamber, two council members who now regret the 2023 vote. Inaction has a political price. confidence 8 / 10 support: June 9 hearing 06 #### Competitive-flight risk is overstated, but not zero Regional capital is flowing despite hostility, so the flight case is weak today. Still, the next-tier-tenant concern is directionally valid if the pause drifts. confidence 6 / 10 challenge: open-ended uncertainty does deter 04 ### Signals Hidden connection #### Every grievance is a sequencing failure Each resident complaint traces to one thing: the deals were signed before the rules existed. The pause and the framework are two halves of one fix, stop signing until the inputs are priced. The whole fight is about sequencing, the single thing the 2023 deal got catastrophically wrong. Actionable insight #### How to make the comment unimpeachable Argue for the pause, but anchor it: couple it to a hard framework-adoption date so it cannot be called open-ended; frame it as a pause on subsidies, not construction, and pre-empt the Hill County attack by naming and distinguishing that case; concede the centers can still build, since this is about public money, not permission; and name the jurisdictional limit honestly, because that candor makes you the rigorous voice in the room. Frontier question #### Who speaks for the projects the city cannot reach? Since the largest impacts, Jupiter and Fort Bliss, lie outside city jurisdiction, what regional mechanism gives the public a seat: a Paso del Norte water and grid compact, county-level coordination, or organized pressure on the PUC and the Army? Stage four ### The briefing grades itself FACET reviews its own work before it ships. Here is where this briefing is strong, where it is soft, and the bias it was built with. Finding Confidence Why Pause forfeits little investment 9 / 10 The sixfold post-deal increase is near-decisive. Pause incentives, not construction 9 / 10 Grounded in the Hill County ruling and home-rule authority. Legally clean, codifies May 26 9 / 10 Restates a vote that already happened. Time-boxing is decisive 8 / 10 Depends on the framework staying imminent. Legitimacy cost of inaction 8 / 10 Well documented in the hearings. Flight risk overstated 6 / 10 The softest claim; directionally contestable. Weakest link The time-boxing premise rests on the framework actually being imminent. If staff drag it for months, the "time-boxed" claim erodes and the developer's deterrence concern grows teeth. Finding 6, on flight risk, is the softest individual claim. Bias check This briefing was commissioned to arm a public comment for a pause, and it leans that way. The pause-favorable lenses carry more weight than the developer lens, which got the hardest scrutiny. The lean is disclosed; the evidence also genuinely favors the pause. The developer's strongest form, that you only need to lose a few marquee tenants, was underweighted. The sixth lens it is missing An environmental-justice and public-health lens, the 366 MW gas plant's nitrogen oxides in an airshed already near nonattainment and the cumulative burden on specific neighborhoods, would harden the community case with health specifics. It was offered as a swap and set aside, so this is a deliberate, noted omission. What would change the verdict If the framework adoption slips past the next few months, or if the pause were drafted against construction rather than incentives, the balance shifts toward the developer and regulator cautions, and the recommendation weakens from clear to conditional. A- **A- as a briefing to arm public comment:** clear, grounded, actionable, and honest about both its lean and the jurisdictional limit. **B+ as objective research,** since the advocacy tuning is real and disclosed, and the competitive-flight counter-case deserved more room. CSR-FACET-2026-001 // PLAIN CITATION Celaya Solutions Research (2026). FACET briefing: a time-boxed pause on new El Paso data center incentives. Briefing CSR-FACET-2026-001, Celaya Solutions Research, El Paso, Texas. Grounded to June 18, 2026. https://celayasolutions.com/research/facet BIBTEX @techreport{csr2026facet, author = {{Celaya Solutions Research}}, title = {FACET briefing: a time-boxed pause on new El Paso data center incentives}, institution = {Celaya Solutions Research}, number = {CSR-FACET-2026-001}, year = {2026}, month = jun, address = {El Paso, Texas}, url = {https://celayasolutions.com/research/facet}, note = {Grounded to June 18, 2026} } FACET is a multi-perspective research instrument from Celaya Solutions Research. This briefing simulates expert lenses to surface contradiction and is independent analysis for public information, not legal advice. It was commissioned to inform public comment and is transparent about that lean in its self-review. Confirm any figure against its primary source before relying on it in testimony. Sources: El Paso Matters (May 21, June 2, June 3, June 9, 2026); KVIA and KFOX/CBS4 (May 26, June 9, 2026); El Paso Inc. and KTEP (June 2026); City of El Paso, ElPasoTexas.gov/research/data-centers; Texas Tribune and Inside Climate News (Jan 2026). Hill County and RCM Hill litigation via KTEP reporting. Census ACS 2024 for median income. Celaya Solutions Research // FACET // El Paso ## Trinidad Source: https://celayasolutions.com/research/trinidad *Markdown view of [https://celayasolutions.com/research/trinidad](https://celayasolutions.com/research/trinidad). The canonical page is HTML at the same URL.* // Research Instrument ## Trinidad Trinidad is an archival intelligence system over 5,435 rare Texas historical documents, with 1,065,357 passages indexed, deployed at trinidad.town. [Back to research instruments](/research) [Applied Intelligence research lab in El Paso](/el-paso-research-lab) ### What it studies Trinidad studies how historical records can become an evidence-aware retrieval and reasoning surface while keeping source material visible. ### Artifact or evidence produced It produces source-linked retrieval paths and archival intelligence outputs over the Texas historical corpus. ### Research context Trinidad is documented as part of Celaya Solutions Research's work on local-first Applied Intelligence systems, provenance-aware research instruments, industrial Applied Intelligence workflows, archival intelligence systems, multi-agent orchestration tools, and human-judgment-preserving Applied Intelligence architecture. Suggested citation CSR-TRINIDAD-2026-001 // PLAIN CITATION Celaya Solutions Research (2026). Trinidad: archival intelligence over Texas historical records. Research instrument CSR-TRINIDAD-2026-001, Celaya Solutions Research, El Paso, Texas. Deployed at https://trinidad.town. https://celayasolutions.com/research/trinidad BIBTEX @misc{csr2026trinidad, author = {{Celaya Solutions Research}}, title = {Trinidad: archival intelligence over Texas historical records}, year = {2026}, organization = {Celaya Solutions Research}, address = {El Paso, Texas}, howpublished = {\\url{https://trinidad.town}}, note = {Research instrument CSR-TRINIDAD-2026-001; 5,435 documents, 1,065,357 passages indexed}, url = {https://celayasolutions.com/research/trinidad} } ## WITNESS Source: https://celayasolutions.com/instruments/witness *Markdown view of [https://celayasolutions.com/instruments/witness](https://celayasolutions.com/instruments/witness). The canonical page is HTML at the same URL.* [Home](/) [Instruments](/instruments) WITNESS v. Infrastructure & Platforms ## WITNESS Industrial Agent An industrial agent that reads drawings and live telemetry, predicts faults with hours of lead time, and is architecturally forbidden from touching a breaker. Phase 3 complete, tagged v0.3 Python MQTT Modbus Parquet SQLite scikit-learn uv ### What it does WITNESS ingests four things about a production line: the electrical drawings, live equipment telemetry, the maintenance history, and the site safety rules. From those it produces one output, a written recommendation with citations, delivered with enough lead time to act on. Telemetry arrives over MQTT or a Modbus poll, lands in a ring buffer for the live view and a Parquet archive for the historical one. A feature pipeline turns raw channels into hourly windows. Three detectors run over those windows: deterministic threshold rules, an IsolationForest anomaly model per channel group, and a lead-time estimator that answers the only question a maintenance planner actually asks, which is how long they have. Every one of those steps writes an event to a hash-linked provenance chain. The project rule is blunt: if it is not in the chain, it did not happen. ### Measured, not claimed Phase 3 closed against a fixed ten-seed simulation set. Recall was 1.0 on fault classes f1 through f3, false alarms ran at 0.5 per simulated day, and median lead time ranged from 3.4 to 25.6 hours depending on the fault. Precision measured 0.89 against a 0.90 target. That gap is written into the repository rather than rounded away, along with the reason: the line simulator's per-channel random walk does not mean-revert, which produces excursions a real process would pull back. A number that misses its target and says why is worth more than one that hits it and cannot be reproduced. ### In the code The provenance chain: every event is hash-linked to the one before it ``` SCHEMA = """ CREATE TABLE IF NOT EXISTS events ( seq INTEGER PRIMARY KEY, ts_utc TEXT NOT NULL, actor TEXT NOT NULL, kind TEXT NOT NULL, payload TEXT NOT NULL, payload_hash TEXT NOT NULL, prev_hash TEXT NOT NULL, chain_hash TEXT NOT NULL ); """ @dataclass(frozen=True) class VerifyResult: ok: bool first_divergence_seq: int | None events_checked: int ``` Tampering with an event breaks every chain\_hash after it, and `witness chain verify` reports the exact sequence number where the record diverges. This is the same instinct as a CMMS work order that cannot be backdated. Debounce and the fault-to-detector map, from the detector ``` FAULT_ANOMALY_GROUP: dict[str, str] = { "f1": "electrical", "f2": "mechanical", "f3": "electrical", "f4": "tension", } HISTORY_MAX_POINTS = 4 * 3600 # per-channel history kept for trend estimation DEBOUNCE_WINDOWS = 3 # 3 consecutive triggering windows before alarm ``` Three consecutive hourly windows must trigger before anything alarms. A single noisy sample cannot page anyone at 2am, which is the difference between an alerting system people keep and one they mute in week two. ### How this differs from the ordinary version #### The model is not in the control path This is the whole design. The language model produces text artifacts only, no tools, no actuator access, no write path to the PLC. Where WITNESS is permitted to influence equipment at all, it does so through a deterministic permissive relay that hardwired E-stop, guard and safety circuits always override. A dashboard that lets a model write a setpoint is a different product with a different risk profile, and it is not this one. #### Evidence or silence A recommendation that cannot cite the telemetry window, the drawing reference and the maintenance record behind it does not survive the validator. There is no fallback to a plausible-sounding paragraph. When the evidence is thin the output says so, which is the behavior a maintenance planner can actually build a schedule on. #### It reads the drawings Most predictive-maintenance tooling sees a stream of numbers with no idea what they are wired to. WITNESS parses schematic sheets into an interlock graph first, so a current anomaly on one channel can be related to the contactor it feeds and the interlock that will trip because of it. The prediction comes with a circuit, not just a chart. ### In the field #### A stamping line in Ciudad Juárez Juárez shed roughly 57,500 maquiladora jobs between mid-2023 and mid-2025, about 18 percent of its manufacturing workforce, while output targets held. The gap gets closed with automation and with fewer people watching more machines. That is exactly the condition where a 3-to-25-hour warning on a motor or a hydraulic circuit changes the week: the repair moves from an unplanned line-down at 02:00 into a planned window on Sunday, with the part already on site. #### A 480V distribution panel in Santa Teresa Nuisance trips at shift change are one of the most common and least diagnosed problems on a plant floor, because the evidence is gone by the time anyone looks. With telemetry archived and hash-chained, the question stops being "what do you remember about Tuesday" and becomes a query: show me every window in the last ninety days where this channel behaved this way, and what else was running. #### What changes over a year The first month is instrumentation and honest baselines, most lines do not know their own normal. By month three the threshold rules are tuned to the actual process and the false-alarm rate is low enough that operators trust the pages. By month twelve the fault labels accumulated from real events are worth more than the simulator that bootstrapped them, and the model is being retrained on the plant it actually runs on rather than a synthetic line. ### Questions Can WITNESS control equipment? No. The language model produces text only. Any actuation path is a deterministic permissive that hardwired safety circuits override, and the model has no write access to it. Does it need cloud access? No. The ingestion, archive, feature pipeline and detectors run on site. This matters for maquiladora operations where telemetry crossing a border is a compliance question rather than a technical one. What lead time does it give? Median lead time measured 3.4 to 25.6 hours across fault classes f1 to f3 on the standard ten-seed evaluation set, at a false-alarm rate of 0.5 per simulated day. ### Related - [CORTEXCognitive Manufacturing](/instruments/cortex) - [CORTEX PLATFORMIndustrial Intelligence Delivered](/instruments/cortex-platform) - [CCPCelaya Chain Protocol](/instruments/ccp) - [SILTMemory Across Time](/instruments/silt) - [SYNAPSE / SYNAPSE-CLIMany MCP, One Model](/instruments/synapse) - [FORGEPrompt Evolution](/instruments/forge) Building something this touches? [Start a build](/intake) [All instruments](/instruments) ## GREYBOOK Source: https://celayasolutions.com/instruments/greybook *Markdown view of [https://celayasolutions.com/instruments/greybook](https://celayasolutions.com/instruments/greybook). The canonical page is HTML at the same URL.* [Home](/) [Instruments](/instruments) GREYBOOK v. Infrastructure & Platforms ## GREYBOOK Industrial Documentation Cross-vendor industrial documentation, crawled into one content-addressed corpus and made answerable with citations back to the exact page. Crawler and web platform both running Python aiosqlite FastAPI Next.js Supabase pnpm ### What it does A maintenance technician looking for the trip curve on a specific breaker is searching across Schneider, Rockwell, Siemens, Eaton and ABB, each with its own site, its own PDF conventions and its own idea of what a model number is. GREYBOOK crawls those vendor libraries into a single SQLite catalog and a content-addressed PDF store, extracts the text page by page, and puts a retrieval layer with citations on top. The crawler half is a Python package with per-vendor spiders and a FastAPI control dashboard. The platform half is a Next.js application: auth, document viewer, and a chat surface where every answer carries the document and page it came from. ### Politeness is a feature Each spider runs with a configured interval and a dry-run mode, and vendor-specific field notes live in the repository, Schneider's Akamai layer returns 403 to anything that looks impatient. A crawler that gets a lab blocked is worse than no crawler, so the defaults are conservative and the run history is recorded per vendor. ### In the code The catalog schema: text extraction is a separate, nullable stage ``` CREATE TABLE IF NOT EXISTS documents ( stable_id TEXT PRIMARY KEY, vendor TEXT NOT NULL, title TEXT NOT NULL, source_url TEXT NOT NULL, doc_type TEXT NOT NULL, product_family TEXT, model_numbers TEXT, -- JSON array revision TEXT, -- download fields, NULL until fetched local_path TEXT, sha256 TEXT, pages INTEGER, -- text-extraction fields, NULL until extracted text_pages TEXT, -- JSON array, one string per page text_extracted_at TEXT ); ``` Discovery, download and extraction are three separate stages with their own timestamps, so a crawl can be resumed, audited, or re-run for one vendor without touching the rest. `sha256` is the deduplication key: the same manual published under four part numbers is stored once. Operating the crawler ``` greybook seeds greybook crawl --vendor schneider --seed masterpact_mtz --dry-run --max-documents 50 greybook crawl --vendor schneider --url '' --interval 3.0 greybook list --vendor schneider --downloaded greybook stats greybook export --output catalog.jsonl ``` Dry-run first, always. The revision field is what makes this more than a search box: a plant running a 2014 revision of a breaker needs the 2014 curve, not the current one. ### How this differs from the ordinary version #### Revision-aware, not just full-text Vendor search finds the current document. A plant floor needs the revision that matches the equipment actually installed, which is frequently two or three revisions behind. Because every document is stored with its revision, family and model numbers, a query can be scoped to the gear in the building rather than the gear in the catalog. #### Answers cite the page A retrieval system that summarizes five manuals into a confident paragraph is dangerous in this domain, a wrong torque spec or trip setting has physical consequences. Every answer here resolves to a document, a revision and a page number the technician can open and read for themselves. #### One corpus, five vendors The value is not any single vendor library; it is that a mixed plant has Schneider gear feeding Rockwell drives next to Siemens instrumentation, and no vendor will ever index a competitor. The cross-vendor join is the product. ### In the field #### A mixed-vendor plant in El Paso Almost no facility is single-vendor. A technician tracing a fault crosses a Schneider main, a Rockwell VFD and a Siemens sensor in one shift, and burns twenty minutes per hop finding the right PDF. Collapsing that into one search with citations gives back time that is currently spent hunting rather than fixing. #### Bilingual by necessity On this border a work instruction is read in Spanish and the vendor manual is published in English. Retrieval that answers in the reader's language while citing the English source page keeps both the accessibility and the auditability, the technician understands it and the quality record still points at the controlling document. #### What changes over a year Early on the corpus is vendor libraries. Within a few months the valuable additions are local: the site's own drawings, MOPs, and closed work orders indexed beside the manuals. That is when it stops being a documentation search and becomes institutional memory that survives the retirement of the one technician who knew where everything was. ### Questions Which vendors are covered? Schneider, Rockwell and Siemens have working spiders. Eaton and ABB exist as stubs with vendor research notes; adding a vendor is a spider, not an architecture change. Does it re-host vendor PDFs publicly? No. Documents are cached into a private content-addressed store for the operator that crawled them, and answers cite back to the vendor source URL. ### Related - [CORTEXCognitive Manufacturing](/instruments/cortex) - [CORTEX PLATFORMIndustrial Intelligence Delivered](/instruments/cortex-platform) - [CCPCelaya Chain Protocol](/instruments/ccp) - [SILTMemory Across Time](/instruments/silt) - [SYNAPSE / SYNAPSE-CLIMany MCP, One Model](/instruments/synapse) - [FORGEPrompt Evolution](/instruments/forge) Building something this touches? [Start a build](/intake) [All instruments](/instruments) ## AXON Source: https://celayasolutions.com/instruments/axon *Markdown view of [https://celayasolutions.com/instruments/axon](https://celayasolutions.com/instruments/axon). The canonical page is HTML at the same URL.* [Home](/) [Instruments](/instruments) AXON i. Cognitive Systems ## AXON Earned Autonomy Architecture A self-monitoring agent that has to earn its autonomy: a seven-label behavioral classifier, a hash-anchored audit trail, and memory that persists across sessions. Running as a daemon, subject of the EAA preprint Python PyTorch LoRA SQLite (WAL) MCP ### What it does AXON is the production-grade fork of Neural Child, built around one idea: an agent should not begin with full permissions. A seven-label behavioral classifier scores its own conduct, a governance layer gates self-modification, and every consequential action lands on an append-only ledger. It runs as an always-on daemon rather than a request-response service, keeps a cross-session diary that survives restarts, and carries a behavioral backbone checkpoint that is trained on its own recorded history. ### Earned Autonomy Architecture The architecture is the subject of a preprint co-authored with Renato Kuipers: diary-based self-training, recursive feedback loops, a behavioral backbone, brave-threshold dynamics, and personality-as-filter. The claim under test is that an agent whose permissions expand only as its measured behavior justifies them is both safer and more useful than one granted everything at initialization. ### In the code Governance is a token budget, not a prompt instruction ``` ## Self-modification is gated. An adapter cannot be promoted to the live ## policy unless the behavioral score clears threshold AND the governance ## budget covers the change; both facts are written to the chain first. @dataclass(frozen=True) class ModificationRequest: adapter_id: str behavioral_score: float # from the 7-label classifier governance_cost: int # tokens debited on approval justification: str # written to the audit ledger ``` Illustrative shape rather than the full implementation. The point is structural: a prompt that says "be careful" is a suggestion, while a budget that must be debited before a weight change lands is a control. ### How this differs from the ordinary version #### Autonomy is earned, not configured The usual pattern gives an agent its full tool surface on day one and relies on the system prompt for restraint. AXON inverts it: capability expands as measured behavior justifies it, and contracts when it does not. The seven-label classifier is the measurement, not a vibe check. #### Memory that outlives the session A cross-session diary plus a chain-anchored action log means the agent can be asked what it did last week and answer from a record rather than a reconstruction. Most agent memory is a rolling context window, which is a buffer, not a memory. #### The identity layer stays clean Tool schemas live in a separate Tool Registry rather than in the system prompt. This keeps the part of the agent that defines who it is from being progressively diluted by however many tool definitions it has been given this month. ### In the field #### Why this matters outside a lab Every business deploying an agent with real permissions faces the same question and usually answers it with a prompt: what stops this thing from doing something expensive. A measured, logged, revocable permission model is the answer an auditor accepts and a paragraph of instructions is not. ### Questions What are the seven labels? They classify the agent's own conduct across a behavioral spectrum used to gate self-modification. The classifier is trained on the agent's recorded history rather than on generic conversation data. ### Related - [CLOSCognitive Operating System](/instruments/clos) - [NEURAL CHILDDevelopmental Intelligence](/instruments/neural-child) - [QUICK NEURAL CHILDAccelerated Lifecycle Rig](/instruments/quick-neural-child) - [ARCHIEPersonal Language Model](/instruments/archie) - [MIRRORBiometric x Behavioral](/instruments/mirror) - [MEMENTOTime-scale Reckoning](/instruments/memento) Building something this touches? [Start a build](/intake) [All instruments](/instruments) ## CCP Source: https://celayasolutions.com/instruments/ccp *Markdown view of [https://celayasolutions.com/instruments/ccp](https://celayasolutions.com/instruments/ccp). The canonical page is HTML at the same URL.* [Home](/) [Instruments](/instruments) CCP v. Infrastructure & Platforms ## CCP Celaya Chain Protocol Six on-chain programs implementing Proof of Coherence: a five-axis score an agent must clear before the network treats its actions as trustworthy. Six Anchor programs, devnet Rust Anchor Solana TypeScript ### What it does CCP is the settlement layer under EPPE, NOTARY, MORTEM and VERDICT's evidence anchoring. Instead of asking whether a signature is valid, it asks whether an agent is coherent: does its claimed identity, its earned reputation, its declared policy, its actual actions and its biological attestation agree with each other. Six Anchor programs carry it: registry, identity, coherence, reputation and trust tiers, organizations, governance, and dispute resolution. ### In the code The five axes and their weights, from ccp-coherence ``` pub const SCALE: u64 = 1_000_000; /// 5-axis Proof of Coherence weights (sum = SCALE) pub const W_IDENTITY: u64 = 300_000; // 0.30 pub const W_REPUTATION: u64 = 250_000; // 0.25 pub const W_POLICY: u64 = 200_000; // 0.20 pub const W_ACTION: u64 = 150_000; // 0.15 pub const W_BIOLOGICAL: u64 = 100_000; // 0.10 pub const COHERENCE_THRESHOLD: u64 = 600_000; // 0.60 minimum ``` Fixed-point integers, not floats, determinism matters when validators must agree. The weights are constants in a deployed program, which means changing what "coherent" means is a governed upgrade with an on-chain record, not a config edit. ### How this differs from the ordinary version #### Coherence rather than possession A private key proves possession of a key. It proves nothing about whether the entity holding it has behaved consistently with what it said it would do. Proof of Coherence scores that agreement across five axes and puts a floor under it. #### Biological attestation is one axis, weighted lowest The biological signal, MORTEM's streamed pacemaker and wearable data, is deliberately 10 percent of the score. It is corroboration, not identity. A design that weighted it heavily would be both fragile and invasive. ### In the field #### Where an anchor beats a database For most business records a database is the right answer. The narrow case where this is not true is when the party keeping the record is also a party to the dispute, utility infrastructure data, chain-of-custody, environmental readings near a permitted facility. Anchoring a hash makes later revision detectable by someone who does not trust the record keeper. ### Questions Does this require a token to use? The programs implement reputation, trust tiers and governance on Solana devnet. The design intent is anchoring and verification, not a tradeable asset. ### Related - [CORTEXCognitive Manufacturing](/instruments/cortex) - [CORTEX PLATFORMIndustrial Intelligence Delivered](/instruments/cortex-platform) - [SILTMemory Across Time](/instruments/silt) - [SYNAPSE / SYNAPSE-CLIMany MCP, One Model](/instruments/synapse) - [FORGEPrompt Evolution](/instruments/forge) - [CONDUITView from the Bridge](/instruments/conduit) Building something this touches? [Start a build](/intake) [All instruments](/instruments) ## Zero to Agent Source: https://celayasolutions.com/instruments/zero-to-agent *Markdown view of [https://celayasolutions.com/instruments/zero-to-agent](https://celayasolutions.com/instruments/zero-to-agent). The canonical page is HTML at the same URL.* [Home](/) [Instruments](/instruments) ZERO TO AGENT vi. Civic Tech & Tools ## ZERO TO AGENT Community Course A free eight week course in El Paso that ends with every attendee having shipped something of their own, built on the argument that a small operation is better served owning a small system than renting a large one. Part 1 built, curriculum approved, companion game content complete Curriculum Workbook Slides JavaScript Card engine ### What the eight weeks actually cover Week 1 is what these tools are, taught through the phone keyboard's next word suggestion, and the two sentences every attendee has to be able to say cold. Week 2 is the difference between something that talks and something that acts, which is where the course delivers on its own name. Weeks 3 and 4 put a website and then a working web app on the internet during the session. Week 5 is answers from your own documents. Week 6 turns the specification written in Week 2 into a running agent. Week 7 is models on your own machine with nothing leaving the building. Week 8 is a three minute demo from everyone, no exceptions. The arc was deliberately rewritten so first contact with an agent moves to Week 2 rather than Week 6, and prompting stops being its own week: context, constraints and the ask get taught inside the hands-on blocks and sharpened every week after. ### Six teaching rules, applied to every section Analogy first, term second, so no technical word appears before a concrete picture of it. Every term gets a plain English definition in the same sentence it first appears. Attendees spend more of the session doing than listening. Each week has anchors, short sentences repeated at least three times, word for word, never varied. Each week builds a fence: an explicit list of what the thing is not. Verification is taught as a physical habit rather than a disclaimer. That last rule is the course in miniature. The verification habit is lifted straight from electrical work: nobody trusts that a circuit is dead because somebody said it is dead, you lock it out, tag it out, and check with your own meter. The anchor repeated all night is "confidence is not accuracy." ### The demo that does the teaching Week 1 runs a fabrication on purpose. Search is switched off and the room is asked for the meaning of fault code E-47 on a compressor model that does not exist. The answer comes back confident, specific and numbered, and entirely invented. Then the same question runs with a real manual pasted in, and the answer changes and cites. The line delivered after the reveal is the point of the whole evening: the machine did not get smarter between those two answers, it got material. Everything the course teaches afterwards, retrieval, your own documents, local models, is a way of giving it material. ### In the code The scheduling rules in the companion game, which encode the actual failure modes ``` /* Pity timer: any active Build List goal whose tag has not resolved a card in 4+ days. */ pityTags: function () { var r = NG_STATE.run, out = []; this.milestones().forEach(function (m) { if (m.done || !m.tag) return; var last = r.lastTagDay[m.tag] || 0; if (r.day - last >= 4) out.push(m.tag); }); return out; }, drawWeight: function (card, pity) { var w = card.weight; var tags = card.tags || []; for (var i = 0; i < tags.length; i++) if (pity.indexOf(tags[i]) >= 0) { w *= 5; break; } return w; }, ``` The course ships with a 56 day narrative game covering the same eight weeks, and this is its honesty mechanism. A pure random draw lets a run stall: the goal you are working toward simply stops coming up, which is a software artefact, not a lesson. The pity timer multiplies the weight of any goal that has gone four days without progress, and a separate crisis floor swaps the deck for a recovery deck when momentum collapses, so a bad run bends rather than ends. Both rules exist because the failure they prevent is the one that makes a learner quit, and the course is aimed at people whose first instinct on a stall is to conclude the fault is theirs. ### How this differs from the ordinary version #### Owning a small system beats renting a large one Third party software is built for the average of thousands of customers, which means every business pays for the parts it does not use and works around the parts it needs and did not get. The course teaches the other path: describe your own workflow, build the narrow thing that runs it, keep the data. By Week 6 an attendee is holding a specification they wrote in Week 2 and an agent that runs it. #### The bill stops being a subscription A rented tool charges per seat, forever, and the price is set by the vendor. Something you built costs what it costs to run, and Week 7 exists specifically to show that a capable model can run on hardware already sitting in the building, at which point the recurring cost of the thing approaches the electricity. #### Your data does not leave Handing customer lists, medical records or contracts to a hosted tool is a decision most small operations make without noticing. The course names that in Week 1 as a failure mode and answers it in Week 7 rather than leaving it as a warning. #### It is free, local, and ends in a demo Eight weeks, no cost, in El Paso, and the last session is everybody presenting for three minutes. That last constraint is deliberate: a course that ends in a certificate produces certificates, and a course that ends in a demo produces working things. ### In the field #### A worked example the room can open ATRIUM is the argument in finished form: a workflow intelligence platform built for one specialty medical practice, architected for its record handling requirements, rather than a general practice management suite the practice would have bent itself around. It is the answer to the question every attendee eventually asks, which is whether the thing they build can be real. #### Why this region El Paso, Santa Teresa and Ciudad Juarez run on small operations and family shops that a per seat subscription prices out and a national vendor never visits. The people in the room already understand procedures, tolerances and verification from their day jobs. The course borrows that vocabulary rather than replacing it. ### Questions What does it cost? Nothing. It is a free community course run in El Paso, and every tool used in the first weeks has a working free tier. Do I need to know how to code? No. Week 1 starts at the phone keyboard's next word suggestion and every technical term is defined in plain English in the sentence where it first appears. More of each session is spent doing than listening. Why build instead of buying software that already exists? Because a general product is the average of thousands of customers, so you pay for what you do not use and work around what you needed and did not get. A narrow system you own runs your workflow, keeps your data, and costs what it costs to run rather than a per seat fee set by somebody else. What do I leave with? A working account, three completed real tasks from the first night, a specification you wrote in Week 2, an agent built from it in Week 6, a model running on your own machine in Week 7, and a three minute demo of your own work in Week 8. Deployed and answering [Open the live site](https://zerotoagent.org/course/landing.html) zerotoagent.org ### Related - [RECALLProduction RAG](/instruments/recall) - [TEXAS ARCHIVEHistory Queryable](/instruments/texas-archive) - [BESS LAND PLATFORMBattery Storage Intel](/instruments/bess-land-platform) - [BOT KILLER / STAPLECivic Surface Clean](/instruments/bot-killer) - [RALPHModel to Objects](/instruments/ralph) - [INSIGHT EXTRACTOR GPTExtract, Not Summarize](/instruments/insight-extractor-gpt) Building something this touches? [Start a build](/intake) [All instruments](/instruments) ## Dispatch 001: July 2026 (2026-07-01) Source: https://celayasolutions.com/notes/dispatch-001 ## What a dispatch is One of these ships every month, minimum. Each dispatch records three things: what changed in the CORRIDOR record, what the lab shipped, and what broke or got corrected. The promise is public. If a month passes without a dispatch, the lab missed it and you are entitled to say so. This is the first one. ## The CORRIDOR record No load bearing figure has changed since the June 18, 2026 verification pass. The 80 percent abatement over 15 years, the 50 job contractual floor, the 1.5 million gallons per day water permit, and the 10 billion dollar stated investment all stand as published. The live record at the CORRIDOR site continues to answer questions against the same sourced dataset. One process note: the field paper now carries a copy ready citation block, plain and BibTeX, with a stable report number, CSR-CORRIDOR-2026-001. If you quote the record in reporting, testimony, or public comment, the citation travels with it. ## Shipped this cycle The site itself did most of the growing this month. The lab produced two brand films in house, a 30 second boot sequence and a 41 second instruments install, both terminal aesthetic motion graphics matching the house tokens. They now run on the homepage, the instruments catalog, and the about page. The operator's heartbeat went live on the site. A wearable streams heart rate over the internet to the homepage, the method page, and the footer of every page. When the badge reads live, the human accountable for this lab is wearing it at that moment. When the wearable is off, the trace replays a resting 72 and says so instead of pretending. The claim the lab makes about human accountability is now a physical signal you can watch. The citation layer shipped. Every paper carries a copy ready plain citation and BibTeX with a stable report number. The homepage and the new press kit carry verified statistics that copy with their citations attached. The FACET briefing gained the same scholar meta tags the CORRIDOR paper already had. Two new pages: a press kit with boilerplate at three lengths, brand assets, and a direct media contact, and a method page recording how one operator runs this lab with an agent fleet doing the leverage work. ## Broke or corrected The footer has linked to a suggested citation anchor on the legal page since June. The anchor did not exist. It does now. ## Next cycle Three things are in motion: an annotated retrieval trace from Trinidad for the homepage method section, scoping for an ask the lab surface that answers questions about the lab's work with provenance shown, and groundwork for a Spanish mirror of the core pages. No promises on which lands first. The dispatch will say what actually happened. ## Meet the Lab (2026-06-17) Source: https://celayasolutions.com/notes/meet-the-lab ## The short version - This is a research lab. We build instruments: tools made to test an idea and learn something true. - We work across many areas: documents, health signals, public records, factories, and the design of applied intelligence itself. - We have built dozens of instruments. Below are a few flagship ones. - These notes come from this lab. We build the same way we teach here: test it, measure it, write it down. ## What the lab is We are Celaya Solutions Research (CSR), an independent lab based in El Paso, Texas. We did not start in software. We spent years in heavy industry: running data centers and building high-voltage equipment. That work taught us one thing that shapes everything we do now. The same patterns show up everywhere. In wiring, in sound, in code, and in how a mind sorts the world. Once you see a pattern in one place, you start to see it in all of them. So we build instruments, not products. An instrument is a tool made to learn something, not to sell something. We aim for surprise. We want to find out what is true, even when the safe move would be to ship something simple. One method runs through all of it. Treat the work like a lab. Form a guess. Test it. Measure what happens. Write it down so anyone can check it. That is the same method these notes teach you. ## A few flagship instruments These are a handful of the tools we have built. Each one is its own project. RECALL. Document intelligence. It reads a large pile of documents, then lets you ask plain questions and get answers that point back to the source. We proved it on a public archive of 5,435 rare Texas historical documents, with over 1,065,357 passages indexed. It ran at almost no cost, and it produced a receipt that shows the records were never changed. EPPE, the El Paso Proof Engine. Civic proof. It takes an everyday record, like a utility bill, and stamps it onto a public ledger. Later, anyone can prove the record is real and was not changed. It is built for plain accountability, starting at home. MORTEM. Live body data. It streams heart and body signals onto a dashboard in real time. It can also hand that data off in the same format hospitals use, so the readings are not locked inside one app. CORTEX. Factory intelligence. A team of software agents that work together to make sense of how a plant runs. It came straight out of our years on the factory floor. CLOS. A cognitive operating system. A larger group of agents that run as one system. It is our test bed for a hard question: how do many small parts add up to something that thinks? BYTEFRAME. A lean applied intelligence engine. A new way to build a language model that is small enough to run on your own machine, not just in a giant data center. It is part of how we study running applied intelligence in private, on hardware you control. These six are a sample. The lab runs dozens more. The wide range is on purpose. Working across many fields is how we find the patterns that tie them together. ## Where to begin New here? Start with the note on token cost. It covers the basics of using applied intelligence without wasting money. After that, the notes build in order: writing better prompts, picking the right model, running your own private model, and building systems that do many steps at once. Every note ends with steps you can run yourself. That is the promise, and it is the whole reason this lab writes anything down. ## Lab Notes (2026-06-16) Source: https://celayasolutions.com/notes/lab-notes ## Introduction Welcome to the lab notes. These are short, plain guides to using applied intelligence well. Not magic tricks. A method. Most applied intelligence advice online is folklore. Someone says "try this prompt, it works great," and you have no way to know if that is true for you. We do it differently. We treat using applied intelligence like lab work. We test things. We measure them. We write down the steps and the numbers so you can repeat them and see for yourself. You do not need a degree to read these. We write at about an 8th grade level on purpose. Plain words, real examples, and the math shown. How to use this page. If you are new, read the notes in order. Each one builds on the last. If you need one thing, jump straight to it. Every note stands on its own and ends with a "Try it yourself" so you can run it. ## Lab principles These are the rules we hold ourselves to. They also make a good way for you to work. 1. We test, we do not guess. We never just tell you something works. We show you how to check it. 2. Every note can be repeated. If we claim a result, we give you the steps and the numbers to get the same one. 3. Measure before you trust. Keep a few test cases you can run again. That is how you know a change really helped. 4. Change one thing at a time. It is the only way to learn what actually made the difference. 5. Start small and cheap. Use the smallest model and the shortest prompt that does the job. Step up only when you must. 6. The right context beats more context. A few useful details help more than a wall of text. 7. Write it down. A result you did not record is a result you cannot repeat. Keep a lab notebook. 8. Be honest about limits. We say what we know, what we do not, and what might change. 9. Protect privacy. We keep people's names and private data out of public notes. 10. Facts go stale. Prices and tools change. Always check the source for today's number. ## Where this is going More notes will land here over time. Each one is the same method pointed at a new piece: writing better prompts, picking the right model, running your own private model on your own machine, and building systems that do many steps at once. The goal is simple, and a little strange for a lab to admit. We want you to stop needing us. When you can test your own applied intelligence work and trust the result, you are doing real lab work. That is the whole point. This is an open lab. Try the steps. Push on them. If something breaks, or you find a better way, we want to hear it. ## Thanks for reading Your attention is the rarest thing you own. Thank you for spending some of it here. We will keep these notes honest, plain, and worth your time. That is the deal. ## Tokens, Dollars, and Why Long Chats Get Expensive (2026-06-15) Source: https://celayasolutions.com/notes/token-cost-efficiency ## The short version - A language model charges you by the token. A token is a small chunk of text. Roughly 4 letters, or about three quarters of a word. - You pay for input (what you send) and output (what you get back). Output costs more. - Every new message in a chat re-sends the whole chat so far. So a long chat costs more on every turn, and it can also get less accurate. - Match the model to the job. Use a small, cheap model for simple work. Save the big model for hard problems. - A clear question with the right context up front beats a long back-and-forth. Good questions save money. ## What a token is A token is a piece of a word. Short common words like "lab" are often one token. Longer words get split into two or three. In English, about 1,000 tokens is about 750 words. A short paragraph is around 100 tokens. This matters because the model does not count words. It counts tokens. The bill counts tokens too. So when we talk about cost, we talk about tokens. A rough way to guess: take your word count and multiply by 1.33. That gives you a close-enough token count. ## How tokens become dollars There are two prices, and they are different: - Input: the text you send (your question, your files, the chat history). - Output: the text the model sends back. Prices are listed per 1,000,000 tokens. People write that as "per million." Here is the formula: cost = (input tokens / 1,000,000 x input price) + (output tokens / 1,000,000 x output price) Let us do a real one. As of June 2026, Anthropic lists Claude Sonnet at $3 per million input tokens and $15 per million output tokens. (Always check the provider's pricing page for today's number. Prices change.) Say you send 2,000 tokens and get back 1,000 tokens: - Input: 2,000 / 1,000,000 x $3 = $0.006 - Output: 1,000 / 1,000,000 x $15 = $0.015 - Total: about $0.021, or 2 cents. One chat is cheap. The trouble starts when you run a thousand chats, or one very long chat. Small numbers add up fast. Notice one thing in those prices. Output costs 5 times more than input. That is true across the current models. So long, rambling answers cost more than short ones. If you only need the answer, ask for just the answer. ## Why long chats cost more and get worse This is the part most people miss, so read it twice. The model has no memory of its own between turns. Each time you send a new message, the model re-reads the entire chat from the top. The whole history goes back in as input, every single time. So the chat grows like a snowball. Turn 1 might send 300 tokens. By turn 30, you might be sending 15,000 tokens with every message, because the bill now includes everything you said before. Here is the same question in a short chat and in a long one, using the Sonnet prices above. Short, fresh chat. Your question is 1,000 tokens. The answer is 500 tokens. - (1,000 / 1,000,000 x $3) + (500 / 1,000,000 x $15) = $0.003 + $0.0075 = about $0.011 (1 cent). Long chat. The history is now 15,000 tokens. You add the same 1,000-token question. The answer is still 500 tokens. - (16,000 / 1,000,000 x $3) + (500 / 1,000,000 x $15) = $0.048 + $0.0075 = about $0.056 (5 to 6 cents). Same question. About 5 times the cost. And you pay that bloated input on every later turn, not just once. It is not only about money. A long chat that wanders across many topics also gets less sharp. The important stuff gets buried in old, off-topic text. The model has to split its attention across all of it. It can also get stuck on something you said early on that no longer fits what you need now. Two problems, one fix. When your goal changes, start a new chat. Carry over only the short summary or the file you actually need. Not the whole transcript. Rule of thumb: one objective per chat. New objective, new chat. Name the chat after its objective so you can find it later. ## Which model for which job Think in three tiers. The names below are current Claude models, but the idea works anywhere. - Small and fast (cheapest). Example: a Haiku-class model, about $1 per million input. Good for simple, clear, high-volume work: sorting text, pulling out fields, simple formatting, quick answers. - Middle (balanced). Example: a Sonnet-class model, about $3 per million input. A good default for most real work. - Large (priciest). Example: an Opus-class model, about $5 per million input. Save it for the hard stuff: tricky reasoning, messy problems, and answers where a mistake costs more than the tokens. The move is simple. Start with the cheaper model. Step up only when it fails your own check. Do not reach for the biggest model out of habit. That habit is how bills balloon. There is a stronger version of this idea. A cheap model with great context often beats an expensive model with poor context. The next section is about that. ## Ask a better question, give better context A vague question gets a vague answer. Then you spend 5 more turns fixing it. Each turn costs tokens and time. A clear question with the right context can get the answer in one turn. That is cheaper and faster. Give the model what it needs to win: - The goal. What are you trying to do. - The limits. What it must or must not do. - The format. What you want the answer to look like. - An example, if you have one. This up-front context is leverage. A little more input buys a lot more output quality, and usually fewer total turns. That is the trade you want. But more is not always better. The right context beats the most context. Dump in too much off-topic text and you are back to the long-chat problem: higher cost, lower focus. Aim for relevant, not huge. ## More ways to save - Say how long. "Keep it short" or "just the code, no explanation" cuts output tokens. Output is the pricey part. - Reuse a big context with caching. Some providers let you cache a long document or a set of instructions so you do not pay full price to send it again every turn. When you reuse the same big context a lot, this can cut cost by most of it. - Batch the non-urgent jobs. Some providers offer a lower rate (often about half) for work you can wait on. - Count the cost of a redo. A cheap answer that is wrong, and makes you redo the work, was not cheap. Price the mistakes, not just the tokens. ## What it means - Tokens are money. Input and output both cost. Output costs more. - Long chats cost more on every turn and can get less accurate. Reset when the goal changes. - Start with the cheaper model. Step up only when it fails your check. - Spend your effort on the question and the context, not on more turns. - Always check today's prices on the provider's page. ## Try it yourself 1. Find your model's input and output prices, per million tokens. 2. Take a recent chat. Guess its tokens: word count x 1.33. 3. Put the numbers into the formula: cost = (input / 1,000,000 x input price) + (output / 1,000,000 x output price). 4. Now do it twice for the same task: once in a long chat, once in a short fresh chat. Compare the cost. You will usually find the fresh chat is cheaper, and often the answer is just as good or better. 5. Bonus: run the same task on a small model and a big model. Can you really tell the difference for that task? If not, the small model wins.