Menu

Individual skill

Statvs

0upvotes

Front door to STATVS (said status), the one append-only record of what happened across LifeOS and every app it runs: checks the record's health, says whether a system, app or site reports into it, writes rows, answers what happened, rebuilds and drills views, rewinds and replays past turns, and onboards a system through the five-step migration. USE WHEN statvs, status logging, status record, the record, is X logging to status, is my site reporting into status, full status logging, log this to status, write a status row, what happened, status tail, verify the record, status counters, drill, restore drill, rebuild a view, compare a view, rewind a turn, replay a miss, onboard X into status, migrate X to statvs, dual-write, register a stream. NOT FOR session status or why is this slow (the s shortcut), posting Vigil events or deciding what to text the principal (Vigil), complaints (Errata), memory recall (Cortex).

LifeOS/install/skills/Statvs/SKILL.md

Read pinned source

Source commit f6ab5e0228bfb356c82edbf52b69344dbd585486

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
19,782
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Statvs

STATVS (Roman spelling, said "status") is the one record of what happened across LifeOS and every app it runs. Things that happened are appended once as rows and never rewritten; every other piece of state is a view folded from those rows that can be deleted and rebuilt. When the principal says "status logging", "the record" or "is X reporting into status", this skill is what they mean, and every intent here answers from the record and its CLI, never from a system's private log. Shared facts the intents rely on:

- **Concept:** `LIFEOS/DOCUMENTATION/Statvs/StatvsSystem.md`. **Criteria and build state:** `LIFEOS/STATVS/ISA.md` (maintainer-side; may be absent on an install). **Engine:** `LIFEOS/STATVS/` with CLI `Statvs.ts`, `Rewind.ts`, and the stream registry `streams.ts`.
- **Row shape:** one envelope (`id`, `seq`, `hlc`, `ts`, `writer`, `stream`, `class`, `app`, `kind`, `severity`, `title`, `session`, `ref`, `data`, chain fields). An append to a stream not in `streams.ts` is refused.
- **Privacy classes** (`public`, `system`, `personal`, `customer`) are the first directory of every segment and never share a file. Secret-shaped values are refused at the writer; tenant content never enters the record.
- **Reporting in** means rows from that system are landing in the record under its own `writer`, on registered streams, today. A system that only writes its own log, or only reaches Vigil through an adapter, is not reporting in.
- **Migration** happens one system at a time in five steps: dual-write, build the view from each store, compare until equal, switch every reader, delete the old store. A system has moved only when its old store is gone.
- **Neighbors:** Vigil is the advocate that reads the record and decides what to tell the principal; its `writeEvent` path also lands rows in the `event` stream, so posting a notice-worthy event stays a Vigil job. Cortex curates what is worth remembering. The bare `s` / "status" shortcut is session status, not STATVS.

## Ideal State

- Every answer about the record, a system's coverage or what happened is grounded in output from `Statvs.ts` or `Rewind.ts` run this turn, and names the command it came from.
Back to top