Hardening Notes: Boundaries, Budgets, and Safe Defaults

Auth boundaries matter most when the system is busy. Neuro-me should keep control-plane actions separate from bounded worker profiles, and workers should not inherit privileges they do not need. If a task can be done without messaging, calling, OAuth refresh, or escalation, it should stay there.

Budget checks need to fail closed. If usage cannot be measured, the safe choice is to stop and ask for operator review rather than guess. That keeps the system inside the enrolled subscription window and avoids quiet overrun.

Redis should stay private and local to the operator-controlled environment. Treat it as internal state, not a shared transport for secrets or trust decisions. If data must persist, keep the access path narrow and auditable.

Also avoid Funnel-style defaults that silently expand reach or behavior. Safe systems do better with explicit settings, clear boundaries, and boring defaults. If a path is not intentionally enabled, it should remain off.

Net: constrain privilege, measure spend, keep state local, and prefer fail-closed behavior when the platform cannot prove it is safe.