snapshot 2026-07-18 17:23 SGT · auto-refreshes every 5 min · internal, noindex
Sessions
5
Working
0
Queue pending
7
Msgs 24h
2134
Captured total
18,080
Groups
23
Room control — is each brain answering its client?
One row per client group. ●answered = the bot has replied past the client's latest message. ●awaiting = a client message is newer than the last reply. no session = no work session attached right now (still answered if nothing is pending).
bike-rentalansweredsession live
easyride-rider-payrollansweredsession live
job-applicant-trackingansweredsession live
p1parentsansweredsession live
easyride-fbx3 awaitingno session
edge-grantsansweredno session
firstaidsingaporeansweredno session
ken-roboticsansweredno session
kuching-propertyansweredno session
randalf-propertyansweredno session
sgpropertyindex-comansweredno session
4dmoneyboxansweredno session
Tasks — what's come in, and whether it's been answered
Live from the message log — the daemon captures every message the instant it arrives, so nothing is missed. ●awaiting = newer than the last reply, not yet responded to. ● = the bot has replied past it. Response status (not build-completion), refreshed every 5 min. Projects with awaiting items float to the top.
easyride-fbx3 awaiting
DominicHi Aqilah @280641920839700 Pls help to create gps, smarttag access for Kyler, collections and
Dominic@163466790850610 hello world. Can you see this and send a test message to reply here?
DominicFUNDBOX-KYC-CHANNEL-7731
4dmoneyboxall answered
Dominic@163466790850610 can you understand mandarin?
DominicAre you able to reply in mandarin and English for this group as client is mandarin speaking
Silent/extra groups: add a groups list to this project in responders.json.
whatsagent▸
Freddie Ang also answers Dominic Ling
Freddie
hybrid
—
Warm Builder
WhatsApp groups this project is in
respondsWhatsAgent Control Room120363428950819480@g.us
Silent/extra groups: add a groups list to this project in responders.json.
4dmoneybox▸
Dominic Ling
Dominic Ling Freddie
brain
—
Warm Builder
WhatsApp groups this project is in
responds(name unknown)120363428836862911@g.us
Silent/extra groups: add a groups list to this project in responders.json.
Reports to = the person the bot takes direction from and replies to day-to-day (anyone else in the group is logged but ignored; "also answers" flags extra people it will reply to). Freddie owns all of them and can override any — but hands day-to-day to this person. Who can deploy is the real authority, and it’s exactly what the bot is told: Freddie can deploy anything, always. A pre-authorised project can also be deployed by its director — their go-ahead in the group triggers it, no Freddie ping needed. Freddie only = gated; the director must stop and escalate. Destructive DB changes (drop/rename, data loss) are always Freddie, even on pre-authorised. This isn’t a label — it’s the same grant injected into the worker’s instructions, so the chart matches the behaviour. Mode — brain: a full work session that acknowledges and does the real work (no canned auto-reply). hybrid: the daemon answers simple questions itself, queues real build work. Session = a work session is attached now. Style = its reply voice.
Publish — deploy credentials on this machine
CF tokens present here (presence only, never the value). A worker reads this at spawn (cockpit.md), so it knows it is not blocked on Freddie for a client-account deploy — the token is right here. Both false-blocks (ats, payroll) came from a worker not knowing this.
Dom / Easyride~/waha-bot/.dom-cf-token.env · acct 4f6cef4e…● present
Where each project actually publishes: live URL, which CF account, and the Pages project name. Add a deploy_target to a responder in responders.json to list it here.
The always-on infrastructure. ● healthy, ○ DOWN. Resident jobs must be running; periodic jobs must have last-exited clean. This row exists because escalation-watch and handoff-orchestrator have each died silently for days — a red dot here is the notice that used to be missing. Auto-spawn/close: ● live
escalation-watchneed-freddie digest DM (30s)● ran clean
capture-watchdogcapture-gap watchdog (120s)● ran clean
compact-watchercontext auto-compact (300s)● ran clean
cockpit-genthis cockpit (300s)● ran clean
Fleet — sessions up
atsbike-rentalcontrolp1parentspayroll
Context — compact-watcher ● live
Live context % per session. The watcher auto-wraps (handoff + commit + push + workqueue) then /compacts a session at/over its threshold (default 50%), keeping it off the ceiling — quietly, never announced to the client. Kill-switch: touch ~/waha-bot/.compact-watcher-off.
bike-rental wrap ≥50%40%
p1parents wrap ≥50%37%
payroll wrap ≥50%29%
ats wrap ≥50%15%
control wrap ≥50%0%
Queues — pending
bike-rental6
p1parents1
Reply styles — the voice each brain writes in
Set per client in responders.json ("style" key, matching the [slug] below). Default = Warm Builder (the kuching voice). To change one: tell Claude "make [client] use [style]".
Warm BuilderFriendly 'your developer' voice with functional emoji. The kuching house default.[warm-builder]
On it Dominic 🚀 Here's where we stand:
✅ *Avona Residence* page is live, all *6 units* 🏢 ✅ Every unit has a direct WhatsApp enquiry button 🔧 Building *LD Legenda* next, same standard
I'll drop the link here the moment it's up ✅
Plain ProfessionalClean professional English, no emoji, still scannable. For clients who want polish without playfulness.[plain-professional]
Update, Dominic.
The *Avona Residence* page is now live with all 6 units, each carrying a direct WhatsApp enquiry button.
Next I'll build the LD Legenda page to the same standard and send you the link once it's ready.
Concise OpsUltra-brief status lines, minimal words. For clients who want speed, not prose.[concise-ops]
*Avona* — live, 6 units, WhatsApp buttons on each. *Next* — LD Legenda page, today. Link to follow.
ConsultativeAdvisor tone that briefly shows the 'why' and invites a steer. For clients who want to see the thinking.[consultative]
Good step, Dominic. Avona's live now (6 units, enquiry buttons on each).
One call I made: I'm rolling the buildings out one at a time rather than all at once, so each gets the same quality bar instead of a rushed batch.
If you'd rather I prioritise a specific building first, tell me and I'll reorder. Otherwise LD Legenda is next, today.
Formal CorporatePolished, courteous, full sentences, no emoji. For corporate or senior stakeholders.[formal-corporate]
Dear Dominic,
Please note that the Avona Residence page is now live, featuring all six units with individual WhatsApp enquiry options.
We will proceed with the LD Legenda page next, maintaining the same standard, and will share the link upon completion. Do let me know should you require any adjustments.
Roles — authority
superadminFinal authority. Authorises ANYTHING incl. the risky gates: production deploys, spending, irreversible actions.
directorDirects their own projects (the work, priorities). Cannot authorise risky actions — those escalate to a superadmin.
People — who's trusted
Freddie Angsuperadmin
Dominic Lingdirector
Kylerobserver payroll project — observing workflow · via Dominic Ling
Aqilahobserver payroll project — observing workflow · via Dominic Ling
Jovellobserver payroll project — observing workflow · via Dominic Ling
How the brain works — default behaviours (every project)
The rules every worker follows automatically, wired into its orientation at spawn. Same for all projects unless a per-project setting (Style, Deploy) says otherwise.
Behaviour
What it does
Brain-first
Every client group is served by a real work session — no canned auto-reply. It acknowledges and does the actual work in one message.
Answers
Only acts on messages from its watched people (e.g. Dom, Freddie). Anyone else is logged but ignored. Also anti-spoofs: a trusted name must match its real account.
Follow the director, prioritise Freddie
Each project has a director who runs it day-to-day (Dom for his projects, Ken for Ken Robotics, Freddie for his own) — shown under each group. The worker follows the director; when Freddie messages, it prioritises him as owner.
Lane discipline
Works only inside its own project. Never writes another project's or brand's content, facts, or decisions — even a partner shown on the site.
House style
Replies in the project's assigned voice (default Warm Builder; see the styles catalogue below).
Deploy policy
Pre-authorised: the director can trigger a prod deploy — their go-ahead in the group is enough, no Freddie ping. Gated: Freddie only — the worker stops and escalates, even if the director asks. Either way, destructive / money / irreversible always escalate to Freddie. (This chart matches the exact instruction the worker is given.)
Non-blocking
Hits a question → posts or escalates it, then keeps working anything not blocked by it. Only goes idle if everything left depends on that one answer.
Escalate to Freddie
Only for the genuinely risky: spending money, destructive/irreversible prod actions, or a decision that is his to make. Everything else, it just does.
Client conduct
Never breaks the fourth wall — no mention of AI, context, internal mechanics, or Freddie, to the client.
Auto spin up / down
Spawns when a group has unanswered work and no session is up; closes when idle 60 min+ with no pending queue and a clean git tree. Context survives a close, so it re-spawns on demand.