{{ screenTitle }}
{{ screenSub }}
⌕
🔔
{{ notifCount }}
Notifications
{{ nf.title }}
{{ nf.detail }}
{{ nf.time }}
VI
Vektra Instruments
{{ greeting }}
Agents handled 31 items overnight - {{ needsYouCount }} need you now.
{{ a.pill }} {{ a.title }} {{ a.meta }} Open →
{{ k.label }}
{{ k.value }}
{{ k.delta }}
Systemic exceptions - todayAll exceptions →
{{ r.id }} {{ r.title }} {{ r.sla }}
Agent network - todayActivity →
{{ g.name }}
{{ g.autonomy }}
{{ g.done }}
actions
{{ g.waiting }}
waiting
Est. employee time saved this week: 142 h · human interventions: 9 roadmap metric · directional
← Exceptions OP-2026-0418 Deuterium lamp fails to ignite - error E-217 {{ heroStatus }} S2 · core function impaired Warranty active · 24 mo
Created Jul 16, 09:12 · updated {{ heroUpdated }}
Operation summary
{{ s.k }}{{ s.v }}
SLA & risk{{ slaChip }}
Resolution plan due{{ slaRemaining }}
{{ s.k }}{{ s.v }}
Recommended intervention: {{ slaIntervention }}
{{ t.label }}
AIMost likely cause - lamp power-supply board (PSU-D2) failure87% confidence
Deuterium lamp fails to strike with error E-217. Replacement lamp shows the same failure, ruling out the lamp itself. Instrument log shows the D2 anode rail collapsing to 41 V during ignition (spec ≥ 85 V) - consistent with a degraded PSU-D2 board. Not remotely repairable.
Recommended:Open RMA - depot repairalternatives considered: remote fix (ruled out) · escalate to engineering (not needed)
Possible causes
{{ c.name }}{{ c.p }}
Diagnostic steps performed
{{ d.mark }}{{ d.text }}
Supporting evidence
{{ e.src }}{{ e.text }}
Knowledge sources · similar cases
📄 SM-VX4200 §6.3 - D2 ignition circuit diagnostics 📄 KB-1182 - E-217 fault tree (updated May 2026) ⟲ CS-2025-2291 - same fault · PSU-D2 replaced · 9 days ⟲ OP-2026-0102 - same fault · depot repair · 8 days
Information collected: serial ✓ · firmware v4.2.1 ✓ · instrument log ✓ · error photo ✓ · usage hours ✓  Missing: none
AI summary: Customer reported total D2 lamp failure during method validation. Guided diagnostics ruled out the lamp; log analysis points to the PSU-D2 board. Customer has a regulatory deadline Aug 3 - repair turnaround matters.
{{ m.channel }} {{ m.who }} AI {{ m.time }}
👍👎💬
{{ m.body }}
{{ transcriptLabel }}
recording ref REC-8837 · 07:42 duration · consent logged
{{ t.who }}{{ t.text }}
Every action is logged with actor, permission and timestamp. Open in audit trail →
{{ e.actor }} {{ e.title }} {{ e.tag }} {{ e.time }}
{{ e.detail }}
✓ chain verifiedHash-chained ledger · {{ caseAuditCount }} entries for this operation · tamper-evident
{{ a.actor }} {{ a.action }} {{ a.ts }}
Permission {{ a.permission }} · policy {{ a.policy }} · accessed {{ a.accessed }} · outcome {{ a.outcome }}
Approval requiredAPR-0142 · due 17:00
Create RMA & send customer return instructions
Agent recommendation: depot repair under warranty. Confirmed hardware fault (PSU-D2), not remotely repairable, entitlement verified.
Why approvalPolicy RMA-01: RMA creation requires human sign-off
RiskLow - standard covered defect
Business impact~€1,240 vs on-site visit · protects Aug 3 deadline
Evidencelog excerpt · KB-1182 · warranty record
ApproverA. Moreau (you)
Your role ({{ roleLabel }}) cannot approve RMA creation. Ask an Approver - A. Moreau or S. Weber.
{{ approvalResultTitle }}
{{ approvalResultBody }}
RMA-2026-0097Depot repair · stage 4 of 17Open →
Next actions
{{ n.group }}
·{{ i }}
RMACustomer · ReasonTypeStageCase
{{ r.id }} {{ r.customer }} · {{ r.reason }} {{ r.type }} {{ r.stageLabel }} {{ r.caseId }}
The AI agent coordinates, monitors, reminds, documents and escalates - receiving, repair, inspection and shipping are performed by people. Physical steps below always name a human owner.
{{ rmaHead }}↳ {{ rmaLink }}
{{ m.k }}{{ m.v }}
Next required action: {{ rmaNext }}
⚠ Exception: {{ rmaException }}
Process stages
{{ s.mark }} {{ s.name }}
IDRMADirCarrierRouteStatusETA
{{ s.id }} {{ s.rma }} {{ s.dir }} {{ s.carrier }} {{ s.from }} → {{ s.to }} {{ s.status }} {{ s.eta }}
Logistics & Customs Agent tracks progress, detects delays and holds, prepares documentation, and escalates - it never books or changes carriers itself.
{{ shipHead }}
{{ d.k }}{{ d.v }}
{{ g.name }}AI
{{ g.type }} · {{ g.dept }}
{{ g.drift }}owner {{ g.sup }}
{{ g.ver }}
config version
{{ g.uptime }}
uptime 30d
{{ g.err }}
errors 30d
Model {{ g.model }} · last deploy {{ g.deploy }} · {{ g.deleg }}
Configuration & lifecycle events
DateAgentEventVersionActorStatus
{{ f.t }} {{ f.agent }} {{ f.event }} {{ f.ver }} {{ f.actor }} {{ f.result }}
{{ f.label }}
✓ hash chain verified · 4,812 entries Export bundle (ISO audit) →
TimestampActorAction · data accessedPermissionPolicy · refOutcomeCost · durHashRate
{{ a.ts }} {{ a.actor }} {{ a.action }} · {{ a.accessed }} {{ a.permission }} {{ a.policy }} · {{ a.caseId }} {{ a.outcome }} {{ a.cost }} {{ a.hash }}
👍👎💬
{{ g.name }}
{{ g.type }}
{{ g.autonomy }}
{{ agName }}{{ agType }}Owner: A. Moreau · no orphan agents
Authority per capability
{{ c.cap }}Approver: {{ c.approver }} ▾{{ c.authority }}
{{ u.name }}
The approving authority must be a system user - gated actions route to them as decisions.
Authority is granted per capability and per action - no blanket autonomy. Changes are versioned, staged for confirmation, and written to the activity ledger. Owner: A. Moreau.
{{ k.k }}
{{ k.v }}
Scope & limits
{{ c.k }}{{ c.v }}
Budget controlsstaged · versioned · enforced at runtime
{{ b.k }}
{{ b.sub }}
€
{{ budgetExample }}
Decisions are checked against these limits at runtime - an over-limit action is denied and converted into a decision for the approving authority.
{{ rolesCount }}
{{ c.label }} {{ c.label }}
Permission registeragents and humans in one place - every action records the permission that allowed it
PrincipalTypePermissionAccessApprover
{{ p.who }} {{ p.kind }} {{ p.tool }} {{ p.access }} {{ p.approver }}
Approvers for gated actions are assigned per capability in Policies & autonomy. Humans get permissions through roles - assign users to roles, not permissions to users.
{{ t.label }}
SLA policies · Technical Support & RMA
First response
S1: 15 min · S2: 1 h · S3: 4 h · S4: next business day
Source: Service SLA Policy · v3.2 · QMS
Resolution plan
S1: 4 h · S2: 8 business hours · S3: 3 days
Source: Service SLA Policy · v3.2 · QMS
RMA timers
Return window 30 days · repair 10 business days from receipt · return shipment 5 business days
Source: RMA Procedure · v4.1 · QMS
Shipment monitoring
Carrier poll every 4 h · hold > 24 h escalates · missing docs drafted by agent + human confirm
Source: Logistics Monitoring SOP · v2.0 · QMS
Policies are synced from their source documents in QMS - the system enforces the released version. Editing happens in QMS, not here.
RMA eligibility decision matrix
Condition
Outcome
Approval
In warranty + covered defect
Approve - depot repair / replace
Human sign-off
+ business-critical downtime (S1)
Approve + advance replacement
Support Mgr + Finance
Excluded damage (liquid / drop)
Convert to paid-repair quote
Support Mgr
Out of warranty
Paid-repair quote or decline
Support Mgr
Serial not found
Reject - route to records team
Auto
Source: RMA Procedure · v4.1 · QMS
Escalation ladder (per topic, per department)
Agent
0 min - retries, reminders, drafts
→
Supervisor
+10 min (S1) / +2 h (S2)
→
Ops Manager
+20 min (S1) / next day (S2)
→
VP Service
+40 min (S1) - breach review
Source: Escalation Policy · v1.8 · QMS
Fired escalations appear on the case timeline and in the audit ledger with the ladder step that triggered them.
{{ x.type }}
{{ x.desc }}
{{ x.ref }}
Owner: {{ x.owner }} {{ x.goLabel }}
Exceptions are raised by the platform runtime - permission denials, low-confidence recommendations, SLA risk, failed system actions and cost anomalies all land here with an accountable owner.
{{ t.k }}
{{ t.v }}
Cost & time saved by agent (30d)value estimates · directional
{{ c.name }}
{{ c.cost }} {{ c.saved }}
Cost is metered per action from the ledger; value connects completed operations, saved human time and SLA performance to each agent.
Prototype previewAgent creation is unavailable in this prototype - templates shown for orientation.
Diagnosis agent
Triage, guided diagnostics, evidence-backed recommendations. Starts at Recommend authority.
Coordination agent
Runs playbooks across departments - reminders, documentation, hand-offs, approvals.
Monitoring agent
Watches external systems, detects delays and anomalies, escalates per ladder.
Technical diagnosis to product returnActive · 2 live runsView live run →
Agents coordinate, monitor, remind, document and escalate - receiving, repair and shipping are performed by named humans at each physical stage.
{{ s.n }}{{ s.name }}
Remote resolution
Intake → identify → guided diagnostics → remote fix → verification → close & survey. Fully agent-run below S2; human gate on config changes.
Escalation handling
Detect breach risk → notify accountable owner → escalate per ladder → track to resolution. Eligibility rules and ladders live in Administration.
SystemGranted scopesStatusLast event
{{ c.sys }} {{ c.scopes }} {{ c.status }} {{ c.last }}
Agents reach systems only through governed tools with the scopes above - every invocation is metered and written to the activity ledger.
{{ k.k }}
{{ k.v }}
{{ k.s }}
Denied & gated actions per dayJul 6-19
{{ b.d }}
Converted to decisionHard-denied
Error rate by weekthreshold 0.5%
{{ b.v }}
{{ b.w }}
Spike in W3 traces to a KB indexing fault, since patched - see Activity ledger.
Denials by policy30 days
{{ c.name }}
{{ c.n }}
RMA-01 gates every rma.create by design - volume there is expected, not an anomaly.
Agent runtime cost per dayJul 6-19 · €
{{ b.d }}
Metered per action from the activity ledger · ≈ €0.16 per action · connected to outcomes in Value & cost.
Feedback to agent team
{{ fbcContext }}
Sent to the agent's supervisor and training queue · logged in the activity ledger with your name.
✦
Console assistant
manage the platform by chat · actions are logged
✕
{{ m.text }}
{{ c.label }}
✦Assistant
{{ t }}