Vigil

Vigil is the log every part of LifeOS writes to when something happens, and the reader that decides whether you need to hear about it. Subsystems (standing questions, app health, vulnerabilities, background services, complaints, the news reader) post events in one schema to a local outbox; a forwarder ships them to the store; a five-minute tick routes new events by severity: critical and high become a text to your phone, medium waits for the digest, low and info land on the dashboard only. Every notification is itself an event, so the log can count how often it interrupted.

Ideal State

• Every answer about what is going on comes from the Vigil log and opens with the tick's health, because a quiet log and a dead reader look identical.
• An event is reported as routed only on evidence (a fresh heartbeat, the notification row after the next tick), never on an exit code that proves only a write.
• No event carries a value, a name or a credential; the emitter's refusal is reported as the right outcome, never worked around.
• The skill reads and feeds the log without changing what the tick owns: no digest line deleted or the digest file moved, no plist edited, no tick installed unasked.

Intent Routing

Intent	Trigger	File
Status	"what is going on", "anything I should know", "vigil status", "is the tick alive"	Intents/Status.md
Emit	"log this to vigil", "post an event", "emit an event", a job that needs to report something	Intents/Emit.md
Digest	"pending digest", "what got held", "what was medium today"	Intents/Digest.md
Install	"install vigil", "start the tick", "register the monitor"	Intents/Install.md

File	Read when
Setup.md	first-time setup, writing your own policy, monitor workflow or adapter, or standing up the optional store

Data & Config