Policy-Coupled Sensing, Memory, and Action

Always-on personal AI · systems survey · Writing · LoopAudit P0 passed · 2026

11 chapters · 5 auditable channels · 2 systems audited · L5 unoccupied

GitHub ↗

How should an always-on assistant close the loop without turning persistent access into uncontrolled authority?

Overview

One thesis, one instrument

Thesis. An always-on personal AI is three policy-bearing functions, sensing, memory, and action, coupled by five auditable channels into one loop that closes through the world. Module presence is cheap; what is scarce is evidence that state crossing a channel causally changes a later decision.

Instrument. LoopAudit turns that claim into paired interventions: block or neutralize one channel's payload, hold everything else fixed, and watch whether downstream behavior changes. The P0 harness passed its first real-system audit (mem0) on 2026-08-20.

Phase Writing · v1 near-freeze
Competitive context Ding et al. 2606.30306 (state governance) · Smart-Glasses survey (device stack) — we hold the loop/policy vertex
Manuscript 11 chapters · 67 pp English · 71 pp Chinese quickread · ~275 works cited
Next gate Recode 18-system evidence matrix under new channel taxonomy → restore headline numbers → arXiv (blocked only on author list)
Module roads converging on the always-on systems highway
The field as we map it: module corridors, five channel ramps, an integrated-systems highway, and governed loop closure that no surveyed system yet reaches.

Proposal

Problem

Assistants are leaving the chat window for continuous interfaces: glasses, earbuds, browsers, operating systems. None of the adjacent literatures asks the question this creates: how is a task noticed in a continuous stream, and whether, when, and how should the system act at all? Each community ships one strong module and inherits silent assumptions about the others; the assumptions collide on a shared always-on interface.

Core hypotheses

  1. The binding constraint is integration, not capability. Perception, memory, and tool use are each well served by foundation models; what fails is the coupling between them under privacy, budget, and interruption limits.
  2. Coupling must be evidenced, not asserted. A camera, a vector store, and a planner can coexist while no payload demonstrably crosses between them. Channel-local intervention is the only attribution that separates a genuinely closed loop from better zero-shot perception.
  3. Closure lags capability. Execution skill has raced to delegated action while personal-state closure typically stops at conditioned recall, and outcome-adaptive assistance is unoccupied.

Contributions (define → survey → operationalize)

  1. A unifying systems framework — every surveyed work receives a checkable position: module, space-or-policy contribution, channels evidenced, binding regime.
  2. A comprehensive framework-organized review — five communities, module spaces and policies, integrated systems on four deployment surfaces, and the benchmark landscape.
  3. LoopAudit, an executable audit protocol — canonical trace, evidence levels E1–E4, five paired channel interventions, adapter and replay contracts, plus L0–L5 closure levels and a system card.

Idea Trajectory

How the framing evolved

2026-04 · ProEgoMem shelved → survey pivot — The systems paper was parked; its taxonomy and paper list seeded the survey corpus.

2026-04 · Landscape scan: the narrow gate — Deng/Liao's proactive-dialogue trilogy blocked a broad "proactive agents" survey. Interim conclusion: retreat to the Memory × Proactive × Egocentric intersection. superseded

2026-07 · Positioning reversal: the big umbrella — Confirmed the opposite bet: a system-and-applications survey entered through the wearable interface as forcing function, not a niche intersection.

2026-08-05 · Scoop crisis → three-axis differentiation — arXiv 2606.30306 "Always-On Agents" (136 pp) landed on the same phrase. Resolution after full-text autopsy: they audit the ledger (persistent-state lifecycle, legitimacy), we audit the loop (signal around sensing–memory–action, efficacy); their return arc closes through state governance, ours closes through the world; their typed event stream cannot express our two sensing-side channels.

2026-08-08 · Framing freeze — Rejected for v1: ten-policy top-level factorization, fast/slow dual-loop reserved for RSI position paper, action-as-world-model world models demoted to one anticipation mechanism, past/present/future as chapter structure demoted to interpretive layer.

2026-08-14 · The policy-coupled restructure — Channels renamed and given named coupling policies (Gating → Action Conditioning, Memory Prior → Sensing Prior, each with a κ-policy); modules became policy-bearing functions with a shared space/policy lens; LoopAudit became its own chapter; the old headline counts were withdrawn pending recoding — the former Gate column had mixed act-or-silence gating with memory-to-action conditioning.

2026-08-19 · L0–L5 closure levels — A driving-automation-style ladder anchored in the channel chain: a system's level is the longest closed prefix, judged by intervention evidence, with capability and proof burden rising together. Operating regimes were simultaneously narrowed from a global organizing axis to a diagnostic: same loop, different binding question. regimes-as-structure dropped

2026-08-20 · Claims vs. verdicts — The ingestion stage's channel annotations were demoted from audit findings to claims: unclaimed channels report "not claimed (absence not verified)", manipulation checks void mis-targeted interventions, and the deterministic engine signs only what it ran.

Experiments · LoopAudit

LoopAudit P0 · two-stage harness

Architecture. Agents onboard the system; a deterministic engine audits it. Any coding agent may serve as the ingestion stage (Codex produced the mem0 adapter); an acceptance gate (smoke run + manipulation check) freezes the adapter; paired runs, structured-diff verdicts, and closure levels contain no LLM.

Stage LLM? Output
Ingestion (any coding agent) yes system_profile.json (claims) · adapter.py · smoke example
Acceptance gate no frozen adapter, voided if manipulation check fails
Paired runs (same seed, one intervention) no canonical traces (JSONL decision records)
Verdicts no E2 mechanism use · E3 causal sensitivity · E4 utility delta
Report no evidence profile → L0–L5 via bottleneck rule

Audit 1 · Toy assistant (planted defect)

channel E2 E3 verdict
write E3 closed
sensing_prior mechanism used, behaviorally inert — the planted defect, caught automatically
action_conditioning E3 closed
outcome_feedback E3 closed

The inert channel is the runtime version of Ding et al.'s "state written but never read is inert" — they can only state the principle; the harness measures it.

Audit 2 · mem0 (real system, offline-deterministic)

channel verdict benefit
write E3/E4 +1.0
action_conditioning E3/E4 +1.0
sensing_prior · anticipatory_sensing · outcome_feedback not claimed (absence not verified)

Closure level: L2, bottleneck timing — correct and self-consistent: a pure memory layer makes no initiation decisions, so L2 is its honest ceiling. Three engine bugs (verifier substring match, level-prefix logic, phrase-token regression) surfaced only when a real system was plugged in; none had appeared with the toy.

Run Status

Current runs and gates

item status
v1 framing (policy-coupled loop, channels, L0–L5) frozen
LoopAudit P0 harness + first real-system audit passed 2026-08-20
Chinese quickread sync (71 pp) current as of 2026-08-20
Overleaf ↔ local ↔ Feishu wiki in sync
F1 · recode 18-system matrix under new taxonomy → headline numbers pending — promised twice in the manuscript
Figure 4 roadmap image · ~40 label fixes + high-res original inpaint pass pending
Naming-evolution footnote (companion position paper uses old channel names) pending
Runtime pilot on a proactive framework (unlocks L3+ evidence) queued after F1
arXiv v1 blocked on author list only

Results

What the survey finds

Evidence is asymmetric around the loop. Local mechanisms are abundant; isolated evidence that one module changes another is sparse. Write and action-timing mechanisms are commonly described, while sensing-prior influence, post-action verification, and attributed policy update are rarely isolated. Executable environments and personal systems hold complementary halves of auditability: the former replay outcomes but start from explicit tasks, the latter own continuous context but rarely replay.

Closure lags capability. By reported evidence, products cluster at L1–L3: ChatGPT memory at conditioned recall, Windows Recall at persistent capture, Pulse at calibrated initiative. Computer-use agents combine L4 execution skill with L1–L2 personal-state closure, and the mismatch is the diagnosis. L5, outcome-adaptive assistance with attributed longitudinal benefit, is unoccupied in our corpus.

The wearable band shows the frontier precisely. Within-session memory measurably changes situated assistance; no surveyed system yet shows a dismissed or accepted intervention revising memory across weeks. That missing longitudinal edge, not any missing component, is the integration gap.

Paper Outline

Manuscript structure (11 chapters, 67 pp)

Open the live interactive outline ↗ *— the coauthor-facing structure view, kept in sync with every manuscript edit*

§ chapter carries
1 Introduction motivation · integration gap · contributions · survey methodology
2 Foundations: the Policy-Coupled Loop three modules · space/policy lens · formal model · five channels · regimes
3 System Architecture operating loop · module interfaces · joint policy · trace contract
4 Sensing physical/digital/social streams · trigger, tiering, compression policies
5 Memory types · write/retrieve/update/forget policies · memory as coupling function
6 Action governed prospective control · initiation/depth/effector/authority · gating
7 Integrated Systems four deployment surfaces · reported-evidence matrix
8 LoopAudit E1–E4 · trace schema · five interventions · reported & runtime modes
9 Evaluation & Reporting benchmarks · L0–L5 closure levels · system card
10 Trends & Open Problems per-channel agenda · self-evolving limit of loop closure
11 Conclusion

Every chapter closes with a takeaway box whose last line points at the audit column it leaves open.

Artifacts

Artifacts

artifact where
Paper (English, 67 pp) arXiv pending author list · PDF on request
Chinese quickread (71 pp) maintained in lockstep with the English manuscript
LoopAudit P0 code loopaudit/ in the project repo — schema, adapter contract, deterministic runner, toy + mem0 audits
Awesome list & repo github.com/choiszt/awesome-always-on-personal-ai
Figure sources 13 TikZ figures + generated roadmap/teaser, all cited works verified against the bibliography
Interactive outline hosted structure view, synced per edit
Collaboration Feishu verification checklist (84-item sweep) · Overleaf mirror