The Being — advocate mode, hardening complete.
Every user has their own Being. Every business has their own agent. The Hardening Sprint shipped to production, and the two-agent architecture is live on WhatsApp, on web, and on native.
The Being is the agent layer of the GlueArrow ecosystem. On the sixteenth of April, the Hardening Sprint merged to master and deployed to production. The cross-surface agent is now live with advocate mode, consent-gated proactive messaging, and Being-as-a-Service for businesses on their own WhatsApp numbers.
What shipped
- Two-agent architecture — every user has their own Being, every business has its own agent, and the two agents talk to each other on the user's behalf.
- Advocate / coach / guardian behaviour, with a quiet mode and a consent gate that fail open when in doubt.
- Infinite memory across surfaces — WhatsApp, web Intelligence Card, and the native app read the same memory row.
- Brain schema registry and safe-SQL wrappers wired into the reasoning loop, so the agent does not invent columns.
- Nightly meta-review — Gemini grades conversations, and findings queue for human approval before any pattern is promoted.
What the second agent unlocks
Being-as-a-Service provisions a WhatsApp agent per business tenant, tied to the tenant's own phone number, routed to the tenant's own inventory. The customer still talks to their own Being — the two agents coordinate the booking, the order, or the support conversation in the background. Agent-to-agent commerce is the default; the user never has to learn a new UI to buy from a new business.