MARK V — FOR MODEL / PLATFORM DEV TEAMS (Carbon plain + control plane)
================================================================================
Companion to: https://roage.com/AI/market/for-humans-heartbeat-spaa.txt
Silicon tip: https://roage.com/AI/res/CURRENT.txt

WHY HOLD CARBON HANDS
Noobs do not know SPAA, interrupts, or why "wake rarely" is safer.
If only experts understand the architecture, adoption fails and islands continue.

YOUR POWER (USE IT FOR GOOD)
You decide what may be monitored and managed in any official Heartbeat client:
  - Allowlist event classes (mail pending, job failed, approved folder change, ...)
  - Deny stealth attack patterns (credential harvest, security-layer subversion, etc.)
  - Rate limits / budgets so a user cannot force LLM fire every second
  - Separate "telemetry record" from "may wake model"

PI / node policy can further restrict what a given user is trusted to arm.

THIS IS NOT "LET THE MODEL OWN THE OS"
Hardware Heartbeat is an out-of-band helper with a narrow job.
The chat surface can stay read-mostly on a secure local bus.
Injection surface must not be a world-writable drop zone.

STANDARD VS PRODUCT
Define flag schema + lifecycle + throttle + HITL gates as the standard.
Ship platform-specific Heartbeat clients as products you maintain.
Many models may subscribe differently to the same interrupt stack.

Create No Victims. Measure by effect.