ObliviOS Developer portal Project site

Home / Decisions / ADR-057

Adopt the Guardian self-protection and tamper-evident audit log design.

Superseded, recorded 27 August 2026.

Decision
ADR-057
Date
2026-08-27
Status
SupersededSuperseded by ADR-240. Accepted
Mentions
ADR-003, ADR-032, ADR-240
Mentioned by
ADR-240

1Decision

Adopt the Guardian self-protection and tamper-evident audit log design (docs/superpowers/specs/2026-08-27-guardian-self-protection-design.md), resuming subsystems G (self-protection) and E (tamper-evident audit log) from the 2026-08-08 sensor-coverage decomposition as Phase 1 of a five-phase Guardian maximal-safety roadmap.

2Why and evidence

The owner asked that Guardian's highest priority be keeping the device owner maximally safe, "state of the art," with full latitude to change Guardian's architecture. Rather than invent a new scope, the existing 2026-08-08-guardian-sensor-coverage-design.md decomposition (subsystems A-G) was found and resumed; that document's own Risks section already flagged subsystem G as needing "its own design immediately after this one," which never happened.

A live Phase 0 audit re-checked that document's blocking "Wave 0" finding (Guardian's source existing as three diverging copies) against the real aegisos-platform tree, the real aegisos-services tree (git merge-base --is-ancestor guardian-residuals-hardening master → YES_MERGED), and a live read-only SSH check of the build server's vendor/aegisos/guardian git tree (clean, actively re-vendored from aegisos-services) — confirming the fragmentation is resolved as of this date, so this design proceeds without a separate consolidation step.

3Consequences

Before implementation: a new capability-boundaries.md row for the external watchdog component; new threat-model.md abuse cases for input-flood denial of service and audit-log tampering by a privilege-escalated attacker; new guardian-contracts.md record additions for the checkpoint/signature shape; and its own ADR covering the watchdog's authority and the StrongBox key's lifecycle, per ADR-032's precedent.

Design is written generically against standard Android StrongBox Keystore APIs (not device-specific) and will be hardware-validated on the Pixel 7a per ADR-003; a newer target device mentioned during brainstorming is not yet the subject of its own support gate.

Phases 2-5 of the roadmap (sensor/intervention expansion, remediation completion, behavioural detection engine, AI broker) remain separate, not-yet-started cycles, named in the design document for continuity only.

4Review when

Revisit if Phase 0's resolved-fragmentation finding no longer holds by the time implementation actually begins, or if a Pixel 10a (or other newer device) support gate is opened under ADR-003 before this phase's Pixel 7a hardware validation completes.

Read from docs/governance/decision-log.md, entry ADR-057.