nightly

Files (1)

• SKILL.md

SKILL.md (first lines)

# /nightly - canonical seven-leg close-parity protocol

NIGHTLY_LOCAL_PROTOCOL: close-parity-v2-7L-11C

`/nightly-close-parity` is the public fire verb for this seven-leg framework. It first proves that this
project-local protocol is the one being loaded. Do not fall back to another
same-name skill or an installed cache.

The seven legs contain eleven independently recorded checkpoints:

| Leg | Checkpoints |
|---|---|
| A - Dream | `dream` |
| B - Reconcile and context | `reconcile`, `context-hygiene` |
| C - Sweep and heat | `sweep-now`, `heat-index` |
| D - Digest | `digest` |
| E - Runtime health | `system-check`, `cognitive-runtime` |
| F - Measurement ledgers | `ledger-capture`, `ledger-review` |
| G - Vault sync | `vault-sync` |

Every checkpoint is recorded through `daemons/nightly-pass.mjs`. A failed
checkpoint immediately writes a named event to the append-only
`NIGHTLY_ALERTS.jsonl` ledger, writes the same bounded alert to stderr, and
leaves it active for the next SessionStart hook. Local delivery is the complete
default channel; no external coordination service is required.

## Root, memory, date, and environment

Run from the aigent-OS root. The normal operational memory root is
`vault/memory`; the daemon also supports the documented `memory` fallback used
by minimal forks and honors `AIGENT_STATE_HOME_DIR` for isolated probes.

One time zone is used for pass dating, alert scopes, ledger review, and
freshness. Configure it with `AIGENT_NIGHTLY_TIME_ZONE`; the documented default
is `America/Los_Angeles`. Configure the post-fire cutoff with
`AIGENT_NIGHTLY_CUTOFF_HOUR`; the default is `4`. A CLI `--time-zone` or
`--cutoff-hour` override must be threaded through the whole invocation. The
controller stores both values in pass state so a later checkpoint cannot drift
to a different date policy.

Tests and scheduled invocations must set the root, state-home, time zone, and
cutoff explicitly. Ambient values must never decide which memory tree a proof
mutates.

## Evidence controller

Prove the route, then begin:

```text
node daemons/nightly-route-check.mjs --root <aigent-root>
node daemons/nightly-pass.mjs begin --root <aigent-root> [--date YYYY-MM-DD] [--replace]
```

Begin requires both canonical inputs to exist and be readable:

- `vault/memory/MEMORY_CANDIDATES.md`
- `vault/memory/runtime/NIGHTLY_CAPTURE_CANDIDATES.jsonl`

The exact prefix may be `memory/` only when the root uses the documented
fallback layout. Missing input is a failed invocation, never an empty or skip
claim.

`--replace` is recovery-only. It abandons an interrupted `status=running` pass
with a named alert before starting a new pass. It never overwrites completed
evidence.

After each checkpoint:

```text
node daemons/nightly-pass.mjs record --root <aigent-root> \
  --checkpoint <name> --status <pass|skipped|fail> --exit-code <integer> \
  --artifact <file:PATH|git:FULL-40-CHAR-SHA|stdout:CHECKPOINT@exit=N|none:ALLOWLISTED-REASON> \
  --detail "<bounded factual detail>"
```

A `git:` artifact must be the full 40-character commit id, copied verbatim
from `git rev-parse HEAD`; a short id is refused.

Any nonzero exit, missing/stale/noncanonical artifact, illegal skip, or explicit
failure becomes `fail` and raises
`NIGHTLY:LEG_FAIL:<checkpoint>`. A duplicate record is refused, preserves the
first evidence, raises `NIGHTLY:DUPLICATE_CHECKPOINT:<checkpoint>`, and makes
finish red. Only `sweep-now` and `digest` may be skipped under their exact
predicates. Continue collecting other safe evidence after a failure.

Finish:

```text
node daemons/nightly-pass.mjs finish --root <aigent-root>
```

A missing checkpoint raises `NIGHTLY:INCOMPLETE_PASS`. The terminal block is
green only when all eleven checkpoint rows are present once, every validator
receipt is nonempty, no row failed, and terminal `status: PASS` is written.
Terminal `status: FAIL` is always red.

## Artifact and postcondition contract

The controller captures pre-fire Dream, cognitive, and ledger snapshots at
begin. It independently re-runs each known postcondition and stores bounded
literal output in the checkpoint's `validator` field.

| Checkpoint | Accepted green artifact |
|---|---|
| dream | canonical `file:` path to `DREAM_LOG.md` |
| reconcile | `stdout:reconcile@exit=0` |
| context-hygiene | `stdout:context-hygiene@exit=0` |
| sweep-now | canonical `file:` path to `SWEEP_LOG.md` |
| heat-index | canonical `file:` path to `HEAT_INDEX.json` |
| digest | canonical `MEMORY_CANDIDATES.md` file, or `none:no-staged-candidates` when re-parsing proves zero |
| system-check | `stdout:system-check@exit=0` |
| cognitive-runtime | `stdout:cognitive-runtime@exit=0` |
| ledger-capture | canonical candidate file/stdout, or `none:no-ledger-candidates` when the begin snapshot proves no append |
| ledger-review | `stdout:ledger-review@exit=0` |
| vault-sync | current `git:<HEAD>`, or `none:nothing-to-commit` after a clean-tree predicate |

A checkpoint may not certify itself by echoing an artifact string. File paths
must remain inside the selected root and resolve to the canonical product.
Stdout receipts cause the deterministic daemon to run again. `none:` reasons

From wrg32786/aigent-os, MIT.

More from wrg32786/aigent-os