§26. Changes from v4.3
planarian @ a924e09 · Spec v4.6 · snapshot main · all versions
Incorporates the owner-approved conceptual review (Future Work v0.2 §1.1–§1.11 and the decisions in its §13).
- §7: principles 13–15 (reference monitor and species-blind principals; invisible under normal use; failure response enforced outside the monitor); principle 9 generalized to attributed overrides. Invariants I16 (security floor), I17 (administrator set non-empty), I18 (hash-chained journal), I19 (no self-approval, no self-escalation), I20 (no agent without the monitor).
- §8:
Suppressiongeneralized toOverride { desired: LeaveAlone | Stopped | Absent | Detected, attribution };Suppress/UnsuppressbecomeSetOverride/LiftOverride;UnitStatus::Overridden.Actor::Usercarries session, seat, and active;Actor::Agentreserved.Condition::Foreground.security_floorinSystemState;below_security_floorandother_sessions_affectedinDerivedFacts. Typed probe kindsDBus,FilePresent;Execadministrator-only.Posture,FailureClass.RejectReasongains theUnauthorized,Interrupted, andNoSpacevariants v4.3 used but did not declare. - §9: probe-kind rule; signed external desired-state source (hook); catalog coverage as a gym metric;
NotInCatalogby phase; graphical-session readiness bound to the session’s compositor; learned edges need a gym case. New §9a: PlanarianOS as a distribution with three profiles, per-profile gates, accounts, live mode. - §10: foreground signals; user services desired while any session of the uid exists; actor resolution from logind; boot report; signed health report (hook) with a core-computed disclosure profile.
- §11: principals and capabilities; Phase B non-human grants; overrides on Security units need an administrator; per-session “own session”; multi-user and security-floor floors; approval as a capability with no self-approval; deliberate actions carry identity; the unattributed residue by posture.
- §12: activation window and sandbox check on the generation path. New §12d (boot ordering,
planarian-ready.target, failure classes, responses, four postures, configurable timeout, boot-chain locking), §12e (security floor), §12f (activation scheduling and quiet mode), §12g (sandbox tier, Phase B). §12c: hash-chained records and chain head in the checkpoint. - §13–§14: overrides; quiet-mode deferral; attributed stop phrasings.
- §15: v4.4 acceptance cases; malicious-declaration family; invisibility, coverage, AskFirst-rate, and verification metrics as ratchets; Firecracker target non-gating from A.
- §16: CLI additions; frontends section (the console is one optional frontend).
- §17a: the verification ratio d:a and the trust count reported at every gate. Phase A proof targets add I16 (in
decideand target selection) and I19. - §18: agent instructions 10–17; rule 4’s preserve list extended to I10–I20.
- §4, §5, §6, §19, §20, §21: roadmap rows (Phase C is PlanarianOS), scope, layout, decisions, model residency, broker and future directions, invisibility budget. §20’s idle unload stays at 10 min, now declared rather than fixed.
- §1–§3: overview prose, the diagram, and feature-table rows updated to overrides, attributed actions, the security floor, failure posture, quiet mode, and the sandbox tier.
- Consistency pass after review:
Decision::Allowcarries anApproverClass;ApprovalTokenbinds its approver;PrincipalId,Capability,Grant, andAuthorizationdeclared;Actor::Unattributedfor inferred overrides, which never apply to Security-sensitive units;EscalationReason(includingRevertBlockedByFloor); a boot-only generation path with theAwaitingBootstate; I1 and I6 clarified against the floor and waiting transactions; the v4-review Security-override case changed from rejected to held for administrator approval; CLI verbsoverride/releasereplacesuppress/unsuppress; §12c’s checkpoint also carries overrides and the security floor.