);
}
/* =====================================================
§6 — CORTEXA SAFE
===================================================== */
const SAFE_CAPABILITIES = [
{ icon: 'permit', title: 'Permit-to-Work compliance', body: 'Detects when permits are issued, modified, or breached in radio traffic; flags missing watchers, conflicting permits, or violations.' },
{ icon: 'confined', title: 'Confined-space risk', body: 'Recognises confined-space entry mentions and verifies the required communications were made.' },
{ icon: 'hotwork', title: 'Hot work & ignition risk', body: 'Detects hot-work activity adjacent to flammable operations or unauthorised areas.' },
{ icon: 'hazard', title: 'Hazardous-substance mentions', body: 'H₂S, hydrogen sulfide, chlorine, ammonia, and other hazard keywords trigger immediate escalation.' },
{ icon: 'incident', title: 'Incidents in progress', body: 'Identifies the language of an incident as it unfolds — "I need medical", "shut down the line", "evacuate" — and routes it.' },
{ icon: 'nearmiss', title: 'Near-misses', body: 'Captures and structures the conversational signals of near-misses that today often go unreported.' },
];
function SafePage() {
useReveal();
return (
<>
Every conversation, watched for the things that put your people at risk.}
subhead="Cortexa Safe listens to every radio transmission, every PTT exchange, every submitted report — and flags the safety events that matter: permit-to-work breaches, confined-space risks, hot-work conflicts, gas and fire mentions, hazard escalations, near-misses, incidents in progress. Every alert is backed by playable evidence and routed to the right person within seconds."
ctaPrimary={{ label: 'Request a Pilot', to: '/demo' }}
ctaSecondary={{ label: 'See use cases', to: '/solutions/permit-to-work' }}
photoSrc="assets/safe-hero.png"
photoAlt="Refinery operator in full PPE walking a process unit at golden hour, radio in hand."
photoTag="HERO · REFINERY WALK, GOLDEN HOUR"
photoCorner={['', 'SAFE / HERO']}
/>
{/* §6.2 — Capability grid 2×3 */}
Six categories of safety event, watched continuously, across every channel.}
sideNote="Each category arrives with the audio, transcript, entities involved, and a precision score tuned to your site over time."
/>
{SAFE_CAPABILITIES.map((c, i) => (
{String(i+1).padStart(2,'0')}
{c.title}
{c.body}
))}
{/* §6.3 — Scenario */}
A field operator on Channel 7 mentions a strong smell of gas near tank farm B. Within four seconds, Cortexa Safe has flagged the transmission, identified Tank Farm B as a known asset, paired it to the live permit-to-work record showing that hot work is in progress 80 metres away, and pushed an alert to the night supervisor's screen with the original audio and a transcribed and translated summary. By 02:14:12, the supervisor has paused the hot-work permit. By 02:15, two additional team members have been dispatched to investigate. The system files an activity record with full evidence chain for the post-shift review.}
photoSrc="assets/safe-scenario.png"
photoAlt="Tank farm at night, low ambient light, faint cooling tower silhouettes."
photoCorner={['', 'SCENARIO']}
/>
{/* §6.4 — Outputs */}
);
}
/* =====================================================
§7 — CORTEXA OPS
===================================================== */
const OPS_CAPABILITIES = [
{
icon: 'rounds', n: '01', title: 'Operator rounds.',
body: 'Define what should be said at each checkpoint of a round — equipment IDs, observations, value thresholds. Cortexa Ops verifies each checkpoint was visited, what was observed, and whether anything fell outside the expected range.',
tag: 'OPERATOR ON A UNIT WALK', src: 'assets/ops-cap-round.png',
},
{
icon: 'switching', n: '02', title: 'Startup / shutdown procedures.',
body: 'Verify the required communications happen in the required order during plant or equipment startup, shutdown, switching, and emergency drills. Closure produces a pass / partial / not-completed verdict with attached transcripts.',
tag: 'CONTROL-PANEL SWITCHOVER', src: 'assets/ops-cap-switch.png',
},
{
icon: 'handover', n: '03', title: 'Shift handover integrity.',
body: "Cortexa Ops generates a structured handover summary at the end of each shift — open permits, in-progress work, unresolved incidents — and verifies the incoming crew acknowledged it. Nothing falls between shifts.",
tag: 'SHIFT-CHANGE BOARD', src: 'assets/ops-cap-handover.png',
},
];
function OpsPage() {
useReveal();
return (
<>
The right communications, in the right order, at the right time.}
subhead="Cortexa Ops verifies that operator rounds, startup and shutdown procedures, equipment handovers, and shift transitions actually happen the way your operating procedures say they should. When they don't, you know within minutes — not at the end of the quarter."
ctaPrimary={{ label: 'Request a Pilot', to: '/demo' }}
ctaSecondary={{ label: 'See use cases', to: '/solutions/procedural-compliance' }}
photoSrc="assets/ops-hero.png"
photoAlt="Control-room supervisor reviewing a paper procedure binder, wall of screens behind showing abstracted operations dashboards."
photoTag="HERO · CONTROL ROOM, PROCEDURE BINDER"
photoCorner={['', 'OPS / HERO']}
/>
{/* §7.2 — Three capability blocks (text + small photo each) */}
Three procedural moments where slips matter most.}
sideNote="Define the procedure once. Cortexa watches every instance of it across every channel, in every supported language."
/>
{OPS_CAPABILITIES.map((c, i) => (
{c.n}
{c.title}
{c.body}
))}
A daily operator round on Unit 4 is scheduled for 06:00. By 06:35, Cortexa Ops sees that the operator on Channel 3 has acknowledged seven of the eight required checkpoints — but Pump P-406 has not been mentioned. Ops opens a partial-completion record, attaches the call audio that did happen, and notifies the day-shift supervisor before the round closes. The supervisor either confirms the operator visited P-406 silently (manual override, logged) or dispatches them back. Either way, the audit trail is complete.}
photoSrc="assets/ops-scenario.png"
photoAlt="Dawn-shift industrial unit in low light, low opacity."
photoCorner={['', 'SCENARIO']}
/>
);
}
/* =====================================================
§8 — CORTEXA SIGNAL
===================================================== */
const SIGNAL_STEPS = [
{
icon: 'define', n: '01', title: 'Define a concept the way you describe it.',
body: 'Operators tell the system, in plain language, what they want to detect — the words that anchor it, the signals that confirm it, the things that should rule it out. No code, no model training, no data science team.',
},
{
icon: 'evaluate', n: '02', title: 'See precision and recall before you save.',
body: "Every concept is evaluated live against your historical conversations so your team can see how often it would have fired, on what, and how confidently — before it goes live. Adjust until it's right.",
},
{
icon: 'improve', n: '03', title: 'Improve it continuously.',
body: "Every supervisor review of a Signal-driven detection tunes the precision automatically. A concept that's noisy on day one is sharp on day thirty.",
},
];
const SIGNAL_USECASES = [
'Detecting every permit-to-work issuance and verifying the named watcher.',
'Tracking contractor arrival and departure on radio across multi-tenant sites.',
'Flagging foreign-object-debris reports on aviation ramps.',
'Identifying gas-alarm acknowledgement delays across upstream facilities.',
'Capturing tool-and-equipment handovers between shifts on construction sites.',
'Detecting any operational event for which your team has a clear definition and an existing manual review process.',
];
function SignalPage() {
useReveal();
return (
<>
You define what matters. Cortexa finds it.}
subhead={<>Cortexa Signal lets your team define any concept your operation cares about — "permit-to-work issuance", "watcher named", "gas alarm acknowledged", "foreign-object debris reported", "contractor arrival" — and have it detected across every conversation, in any supported language, with verifiable evidence and continuous tuning. No engineering work. No retraining cycles.}
ctaPrimary={{ label: 'Request a Pilot', to: '/demo' }}
ctaSecondary={{ label: 'See use cases', to: '/solutions/custom-detection' }}
photoSrc="assets/signal-hero.png"
photoAlt="Operations engineer and HSE manager at a whiteboard with hand-drawn flow diagrams of an operational procedure."
photoTag="HERO · WHITEBOARD WORKING SESSION"
photoCorner={['', 'SIGNAL / HERO']}
/>
{/* §8.2 — Three steps */}
Three steps. No engineering work.}
sideNote="The same workflow you'd use to brief a new analyst. Signal is built so your operations team — not ours — defines what gets watched for."
/>
{SIGNAL_STEPS.map((s, i) => (
{s.n}
{s.title}
{s.body}
))}
{/* §8.3 — Use cases list */}
The shape of what teams have asked it to watch for.