REF-02 / Agent Catalog

14-Agent
Catalog

Complete specification for each CORTEX agent. Domain ownership, function definition, input sources, output targets, and architectural notes.

Catalog Summary
cortex.agents / v1.0
01total_agents14
02tier_1_core5 // YIELD, CADENCE, WATT, WRENCH, COMPASS
03tier_2_domain6 // SPEC, RACHEL, VECTOR + 3 facility-specific
04tier_3_support3 // SENTINEL + 2 coordination
05naming_conventionAgent name == domain == scope boundary
06cross_domain_commsprohibited // route through hub
Naming principle: Agent names were selected for immediate domain clarity. The name is the scope. If you cannot infer the domain from the name alone, the name is wrong.
Tier 1
Core Manufacturing Agents
5 agents
01 YIELD T1
Production Throughput
FunctionMonitors manufacturing yield rates, production targets, and output quality metrics. The primary performance intelligence agent — everything that measures whether the line is doing what it is supposed to do.
Inputs
Production sensor data, quality control reports, shift logs
Outputs
Yield rate reports, performance variance alerts, throughput summaries
YIELD is the most frequently queried agent by floor leads. Configure its report cadence to match shift structure.
02 CADENCE T1
Scheduling and Timing
FunctionOwns the temporal layer of CORTEX. Tracks shift schedules, production windows, maintenance windows, and planned downtime. The agent that knows when everything is supposed to happen.
Inputs
Shift schedules, maintenance calendars, planned downtime windows
Outputs
Schedule conflict alerts, upcoming window notifications, timing reports
CADENCE feeds scheduling context to YIELD and WRENCH. All time-sensitive escalations pass through CADENCE before routing.
03 WATT T1
Energy and Power Data
FunctionTracks electricity consumption, demand curves, and power factor across the EP44 facility. Directly relevant to the Project Jupiter grid capacity analysis — the same domain, at the facility level.
Inputs
Power meters, energy management systems, utility data
Outputs
Consumption reports, demand spike alerts, power factor summaries
Given the EP44 context and the Project Jupiter water/grid findings, WATT's data has potential litigation relevance. All WATT outputs should be timestamped.
04 WRENCH T1
Maintenance Tracking
FunctionOwns the maintenance domain: scheduled preventive maintenance, unplanned repairs, equipment health scores, and parts inventory signals. The agent that tells you what is about to fail before it does.
Inputs
Equipment sensors, maintenance logs, parts inventory system
Outputs
PM schedule reports, failure prediction alerts, repair completion notifications
05 COMPASS T1
Navigation and Workflow
FunctionThe workflow routing agent. Directs information flows between the CORTEX hub and the operational teams. Compass knows where things are supposed to go and ensures they arrive. Functions as the internal router for the Teams integration layer.
Inputs
Hub routing directives, Teams channel configuration, stakeholder maps
Outputs
Workflow routing confirmations, delivery receipts, routing failure alerts
COMPASS is the agent most tightly coupled to the Microsoft Teams integration. Changes to Teams channel structure require COMPASS reconfiguration.
Tier 2
Domain Agents
6 agents
06 SPEC T2
Specifications and Standards
FunctionOwns the technical standards layer. Tracks process specifications, quality standards, compliance requirements, and engineering tolerances. Ensures that the operational data from Tier 1 agents is interpreted against the correct specifications for each product line.
Inputs
Engineering specs, quality standards docs, compliance requirements
Outputs
Spec deviation alerts, standards update notifications, compliance reports
07 RACHEL T2
Reporting and Escalation
FunctionThe reporting agent. Compiles domain-specific reports from multiple agents and formats them for specific stakeholder audiences. RACHEL knows who needs what format and ensures reports arrive ready to use — not requiring reformatting.
Inputs
Multi-agent report data, stakeholder preferences, report templates
Outputs
Formatted stakeholder reports, executive summaries, escalation packages
RACHEL is the primary interface for the 220% data gravity expansion. Personal configurations per stakeholder live in RACHEL, not in the hub.
08 VECTOR T2
Data Direction and Flow
FunctionThe data routing intelligence agent. VECTOR tracks where data originates, where it needs to go, and whether it has arrived correctly. Distinct from COMPASS (which routes workflow) — VECTOR routes data payloads.
Inputs
Data pipeline status, transfer logs, schema validation results
Outputs
Flow health reports, routing failure alerts, schema mismatch notifications
09 EP44-A T2
[Facility-Specific Domain A]
FunctionOne of three agents configured specifically for EP44 operational requirements. Domain classification is internal to the EP44 deployment context. Architecture pattern: same Tier 2 agent specification as SPEC, RACHEL, VECTOR but with facility-specific domain ownership.
Inputs
EP44 operational sources
Outputs
EP44 domain-specific reports
Facility-specific agent configurations are documented in the EP44 deployment supplement. Not included in this reference for confidentiality.
10 EP44-B T2
[Facility-Specific Domain B]
FunctionSecond EP44 facility-specific agent. Same architectural pattern as EP44-A. Domain ownership defined in deployment supplement.
Inputs
EP44 operational sources
Outputs
EP44 domain-specific reports
11 EP44-C T2
[Facility-Specific Domain C]
FunctionThird EP44 facility-specific agent.
Inputs
EP44 operational sources
Outputs
EP44 domain-specific reports
Tier 3
Support Agents
3 agents
12 SENTINEL T3
Monitoring and Alerts
FunctionThe always-on monitoring agent. Watches all other agents and the hub for out-of-bounds conditions. SENTINEL is the only agent authorized to issue high-priority escalations that interrupt normal hub processing. Two live deployments: CORTEX and Juniper.
Inputs
All agent report streams, hub health metrics, threshold configurations
Outputs
High-priority escalation messages, threshold alerts, system health reports
SENTINEL is also deployed in the Juniper instrument and embedded in the CLOS architecture. The same agent architecture, three separate deployment contexts.
13 COORD-A T3
Coordination Layer A
FunctionHandles coordination responsibilities for the inter-agent timing and synchronization layer. Ensures agents report on correct cadences and that hub state is consistent across agent report cycles.
Inputs
Agent report timestamps, hub state log
Outputs
Sync confirmations, cadence adjustment directives, state consistency reports
14 COORD-B T3
Coordination Layer B
FunctionSecond coordination agent handling the stakeholder interface synchronization. Ensures that what stakeholders see in Teams reflects the current hub state within the specified latency threshold.
Inputs
Hub state, Teams channel state, stakeholder session data
Outputs
Sync status, latency alerts, interface consistency reports
Next: Deployment Protocol → ← Architecture