AITraining2U
Single Unit · Service Point Co-pilot · Live Demo

Single Unit — one COUNTER-PILOT agent in the service point lead’s pocket.

The portfolio demo shows what the CEO sees every morning. This page is the other end of the same operating model: the daily ranked checklist that the service point lead at Pejabat Tanah #1 sees on their phone every morning. One agent, push-only, no dashboard. Most Malaysian government operators should start here.

Portfolio (CEO) Single Unit (Service Point)
The Service Point

Loading…

Loading…
Format
—
Staff (FTE)
—
Tier
—
Single-Unit Architecture for Government — one agent, push-only Show diagram ▾ Counter queue system MyGovUC + service desk Officer roster COUNTER-PILOT Counter Action Agent Reads signals · ranks tasks · pushes to phone DAILY CHECKLIST Ranked, dated, dismissible on the service point lead’s phone
Three local signals → one agent → one ranked checklist. No dashboard, no chart. Push-only means the service point lead never opens an app — the next task is just there. This is the entry-bar version of the operating model for government: the other specialist agents are switched off until Phase 2.

Data inputs COUNTER-PILOT subscribes to

Twelve live feeds across operational systems, IoT, roster, vendor, weather, regulator, comms and competitor signals. The COUNTER-PILOT agent re-reads everything every 60 minutes and re-ranks the action list before the next push.

Today's service-point signals

Six derived signals the COUNTER-PILOT agent uses to score every candidate action. These are what the agent saw at 06:00 this morning, on the day selected in the tab strip.

Daily action checklist

Push-only. The service point lead doesn’t pull a dashboard — these tasks land on their phone in this order. Mark them off as you go to feel the loop.
0%
0 of 0 tasks complete
Today’s shift

Today’s COUNTER-PILOT run log

The agent runs on a fixed schedule, not on demand. Each entry is a re-rank pass: inputs refreshed, signals recomputed, checklist re-ordered. Greyed rows are the rest of the day still to come.

How this was built

The agent reads three files of mock service point telemetry — the same files that drive the portfolio demo. We filter to a single sp_id (SP-0001), pick the latest three operating days, and let the agent generate its checklist deterministically from the day’s signals.

This page is intentionally tiny: about 200 lines of JavaScript, zero frameworks, one HTTP fetch per data file. The point is the operating model, not the chrome.

Source data: entities.csv · daily_signals.csv · agent_writebacks.jsonl