stack/docs/architecture/lease-broker-security.md

WI-1 lease broker security notes

• Trusted identity comes only from Linux SO_PEERCRED plus /proc starttime, never request identity fields.
• Descendant authorization is anchored to (pid,starttime) and uses a complete second starttime pass to fail closed on disappearance or PID-reuse races.
• Runtime generations are monotonic per anchor; a bump revokes prior-incarnation tokens before persistence commits. WI-3 stores the live generation in an owner-only locked file so same-PID Pi reload/new/resume/fork and Claude resume/clear transitions cannot inherit a VERIFIED lease.
• Session IDs and cycle tokens use the OS cryptographic RNG. Math.random and model output are not token sources.
• Framing and persistence failures fail closed. Sensitive tokens are not logged.
• Built-in 0700/0600 filesystem modes provide same-principal hardening only, not socket authenticity against the same UID. WI-1 provides no distinct-principal isolation. That stronger deployment requires an external protected proxy, ACL, or service boundary, and the boundary must preserve authenticated client identity for the broker's SO_PEERCRED and ancestry authorization rather than substituting a shared proxy identity.
• WI-2 whole-class authorization denies every consequential, unknown, and custom tool while UNVERIFIED; it does not inspect shell strings or trust wrapper selection. First-class Claude/Pi, both Claudex dispatch modes, PRDY, QA remediation, coord, orchestrator, and fleet starts converge on broker register-before-exec; Claudex additionally installs the mandatory all-tools hook inside its preserved isolated config and fails closed on unsafe settings.
• The permanent check-runtime-launches.py suite/CI guard scans production source for direct literal, absolute-path, process-API, command-array, and dynamic Claude/Pi launches. It has no bypass allowlist: an unrecognized launch form fails CI until routed through the common boundary.
• WI-2 promotion consumes a WI-1 cycle token before VERIFIED becomes visible. Observer revocation, runtime-generation replacement, broker restart, and monotonic TTL expiry remove authority.
• WI-3 wires redundant Claude PreCompact/SessionStart(compact) and Pi session_before_compact/post-session_compact context observers to that same revoke action. If broker confirmation fails after an observer fires, the revoker advances the private generation as a local fence; subsequent authorization revokes the stale broker incarnation before any consequential allow.
• Dual observer absence while a lease remains live is the named bounded residual stale window: consequential tools remain allowed until monotonic expiry, with no claimed within-window action bound. After expiry they are denied. Total observer-plus-gate absence remains T-C.
• Receipt observation, payload construction, and constrained recovery implementation remain later surfaces. A receipt can become a promotion prerequisite but is never the safety mechanism.

Coordinator security review must rerun the real socket/peercred and mutator-gate acceptance suites on an unrestricted Linux runner and obtain the mandated independent Opus-SECREV review before integration.