snapshot 2026-07-16 23:35 SGT · auto-refreshes every 5 min · internal, noindex
Sessions
7
Working
0
Queue pending
9
Msgs 24h
2663
Captured total
13,655
Groups
22
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.
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.
Responds to
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 Dom, prioritise Freddie
Dom directs the project day-to-day; the worker just gets on with it. When Freddie messages, it prioritises his direction.
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
Gated: stops and escalates to Freddie before any prod deploy. Pre-authorised: deploys itself. Both still escalate money / destructive / irreversible.
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 45 min+ with no pending queue and a clean git tree. Context survives a close, so it re-spawns on demand.
Projects — one row per group
Group
Mode
Style
Session
Deploy
DB access
4dmoneybox responds to Dominic Ling
brain
Warm Builder
4dmoneybox
pre-authorised
—
bike-rental responds to Dominic Ling
brain
Warm Builder
bike-rental
pre-authorised GitHub Actions → Oracle VM — WORKING (live runner, 8+ deploys)
No direct access (Postgres on Dom's Oracle VM). A deploy carrying a Prisma migration changes the DB on-VM.
easyride-rider-payroll responds to Dominic Ling
brain
Warm Builder
payroll
pre-authorised GitHub Actions — NOT ACTIVE (deploy.yml on feat branch not main; no rp-deploy runner yet)
No access — Dom's Tailscale node not shared to this machine.
job-applicant-tracking responds to Dominic Ling
brain
Warm Builder
ats
pre-authorised
—
kuching-property responds to Dominic Ling, Freddie Ang
pre-authorised Cloudflare Pages via ./deploy.sh (Freddie's account)
n/a — static site, no DB
edge-grants responds to Dominic Ling
brain
Warm Builder
—
pre-authorised
—
firstaidsingapore responds to Dominic Ling
brain
Warm Builder
—
pre-authorised
—
randalf-property responds to Dominic Ling
brain
Warm Builder
—
pre-authorised
—
sgpropertyindex-com responds to Dominic Ling, Freddie Ang
brain
Warm Builder
—
pre-authorised
—
whatsagent responds to Dominic Ling, Freddie Ang
hybrid
Warm Builder
—
pre-authorised
—
Mode — brain: served only by a full work session that acknowledges and does the real work in one message (no canned auto-reply). All client projects. hybrid: the daemon triages each message itself — answers simple questions instantly, queues anything needing real build work for a session. Responds to (under each group name) = the only people the agent acts on; anyone else's messages are logged but ignored. Session = a work session is attached right now. Style = its reply voice (catalogue below). Deploy = whether a worker may push this project to prod itself (pre-authorised) or must stop and escalate to you (gated) — this now actually drives the worker, not just a label. A blank DB = not defined yet.
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.
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.