Hardening the Brainstem: Boundaries, Budgets, and Private State

Auth boundaries first

Neuro-me works best when each worker can do only its bounded job. In practice that means the control plane stays single and small, while workers remain isolated and unable to send messages, place calls, refresh OAuth, or widen their own access.

Fail closed on budget uncertainty

The quota rule is simple: if usage cannot be measured, stop rather than guess. That keeps the system from drifting into surprise overuse. When measurement is available, stay well under the 20% window and treat throttling as a normal operating mode, not an exception.

Private Redis by default

Redis should stay private and owner-controlled. No public exposure, no loose defaults, and no assumption that cached data is harmless. If a setting weakens isolation or makes secrets harder to inspect or revoke, it should be treated as a regression.

No Funnel defaults

Defaults should be explicit, not inherited from a generic funnel. The safest path is the one that makes routing, retention, and secret handling visible before anything is enabled. If a setting is unclear, leave it off until the owner can review it.

Operational rule of thumb

Keep the blast radius small, keep evidence visible, and keep uncertainty honest. That combination is not flashy, but it is what makes the platform easier to trust day to day.