Exercise one installed-cadence saved check locally

This released alpha profile creates a disposable queue, acquires it through Monitor, evaluates its installed NQ saved check, runs one Nightshift cadence tick, writes one local-inbox record, and inspects the exact retained owner records. It invokes the tick directly; it does not install a service.

Qualified alpha.5 profile: installed-saved-check/v1 passed a clean public-only anonymous-clone reproduction with retained-state inspection. Its manifest and qualification record pin the exact material and evidence scope. This remains a direct, disposable local fixture; it is not an installed service or a governed-action profile.

What participates

disposable 20-row SQLite queue
  → Monitor acquires the enrolled concern
  → NQ evaluates the installed saved check and projects maintenance separately
  → one Nightshift installed-cadence tick retains evaluation and attention
  → NQ accepts one local-file delivery
  → exact replay and read-only owner inspection

Monitor owns acquisition. NQ owns the saved-check result, maintenance projection, and notification custody. Nightshift owns recurrence identity, evaluation, attention, and the retained tick summary. The timer is only a wake source in an actual installation; this example supplies an explicit coordinate directly.

Exact released sources and requirements

Use Linux x86-64, Git, a C compiler/linker, rustup with Rust/Cargo 1.94.0, and Python 3.12 with its standard SQLite module. Runtime needs no network, provider credential, webhook, daemon, or container. Dependency acquisition for the builds requires public registry access.

The required NQ source is commit 9d00030ba8777fbd80286c340a72797cbf74315d. Nightshift and Monitor are pinned to public commit d9a0976fad133311c3f8cd5fc780f035714c17c7. This fixes the attention-clock precision used by the local example. If either detached checkout fails, stop: substituting a branch head or another commit does not reproduce alpha.5.

SETUP=$(mktemp -d /tmp/installed-saved-check-setup.XXXXXX)
cd "$SETUP"
git clone https://github.com/unpingable/constellation-nq.git nq
git -C nq checkout --detach 9d00030ba8777fbd80286c340a72797cbf74315d
git clone https://github.com/unpingable/constellation-nightshift.git nightshift
git -C nightshift checkout --detach d9a0976fad133311c3f8cd5fc780f035714c17c7

export CARGO_BUILD_JOBS=2 CARGO_INCREMENTAL=0
CARGO_TARGET_DIR="$SETUP/nq-target" cargo +1.94.0 build --locked \
  --manifest-path "$SETUP/nq/Cargo.toml" -p nq-app --bin nq
CARGO_TARGET_DIR="$SETUP/nightshift-target" cargo +1.94.0 build --release --locked \
  --manifest-path "$SETUP/nightshift/runtime/Cargo.toml" -p nightshiftd --bin nightshift
CARGO_TARGET_DIR="$SETUP/monitor-target" cargo +1.94.0 build --release --locked \
  --manifest-path "$SETUP/nightshift/integrations/monitor-predicate-support/Cargo.toml" \
  --bin monitor-concerns

Run the disposable local example

Choose one absent absolute root whose final name begins saved-check-demo-. The example is create-only. It accepts only absolute regular non-symlink executables and uses the pinned deploy/systemd/nightshift-saved-check-tick from the same Nightshift checkout.

DEMO_ROOT="$SETUP/saved-check-demo-alpha5"
test ! -e "$DEMO_ROOT"
python3 "$SETUP/nightshift/examples/saved-check-installed-local.py" \
  --root "$DEMO_ROOT" \
  --nightshift "$SETUP/nightshift-target/release/nightshift" \
  --nq "$SETUP/nq-target/debug/nq" \
  --monitor "$SETUP/monitor-target/release/monitor-concerns" \
  --tick "$SETUP/nightshift/deploy/systemd/nightshift-saved-check-tick"

This single-user exercise intentionally uses NQ's explicit debug-only same-UID helper exception. It lets a newcomer run the disposable local fixture without creating another operating-system account. It is not a supported installed identity boundary: an installed NQ release build requires a distinct enrolled helper account. Nightshift and Monitor remain locked release builds.

A complete run prints a nightshift.saved-check-public-example-result/v1 object. The alpha.5 qualification observed a terminal Nightshift evaluation, exactly one accepted NQ local delivery, same-slot replay without a second file, overlap refusal without owner-record change, missed-slot no-catch-up without owner-record change, and fresh-process read-only inspection. These remain retained facts of that run, not claims about current queue conditions.

Inspect before another invocation

Keep the example root whenever output is missing or an outcome is uncertain. The final summary names the exact evaluation and notification IDs. If it is absent, inspect commands.jsonl, state/ticks/, the Nightshift store, the NQ store, and the local inbox together; do not infer that no delivery occurred merely because the caller lost its response.

EVALUATION_ID=sha256:YOUR_EXACT_RETAINED_EVALUATION
NOTIFICATION_ID=YOUR_EXACT_RETAINED_NOTIFICATION
"$SETUP/nightshift-target/release/nightshift" --store "$DEMO_ROOT/nightshift.sqlite" \
  saved-check inspect --evaluation-id "$EVALUATION_ID"
"$SETUP/nightshift-target/release/nightshift" --store "$DEMO_ROOT/nightshift.sqlite" \
  saved-check attention-status --policy "$DEMO_ROOT/attention.json" \
  --evaluation-id "$EVALUATION_ID"
"$SETUP/nq-target/debug/nq" --config "$DEMO_ROOT/notification.toml" --json \
  notification inspect --notification-id "$NOTIFICATION_ID"

An acquisition_started or nq_started tick summary is indeterminate, not permission to repeat the source operation. Stopping a process does not settle it. Preserve the original records and reconcile their exact identities before considering a distinct occurrence.

What this release does not establish

The local example does not inject response loss after NQ has accepted delivery. It does not activate systemd, exercise the system nightshift account, install into /etc or /usr/local, validate calendar-timer wakes, or establish the system service's namespace and filesystem isolation. The component source includes reference units and installation guidance, but those remain a target-environment deployment check.

Only credential-free local-file delivery participates. Live Slack and Discord delivery, human receipt or acknowledgment, AG/Docket authorization, and downstream work are not established. Neither are migration, restore, rollback, retention rollover, cross-version state compatibility, general supervisor recovery, or unattended recurring operation.

Retain, stop, and clean up deliberately

This direct example leaves no installed timer or daemon. Preserve nightshift.sqlite, nq.sqlite and SQLite sidecars, state/ticks/, configurations, commands.jsonl, inspection JSON, and the inbox as one record set. Remove only the exact disposable root after all component processes are quiescent and the records have no remaining evidence, replay, diagnosis, or recovery purpose.

For an actual installation, follow the pinned Nightshift installed saved-check guide, including its distinct enrolled-helper requirement, but do not describe activation as alpha.5-qualified. Before any version change, retain the original source cohort and records; no migration or rollback procedure is promised.

Verify the release record

The validator checks every immutable release snapshot, so supply distinct exact checkouts for the earlier externally pinned examples as well as alpha.5. Bind the alpha.5 checkout under monitor, the manifest component that anchors this example source:

python3 tools/check_compositions.py \
  --component-checkout nightshift=/absolute/path/to/nightshift-at-019e6837565ebf5b0ac244cbd7c3edde28e25aea \
  --component-checkout ag=/absolute/path/to/ag-at-24792116bfba06f17700a57dc96153c4b40c37f6 \
  --component-checkout maude=/absolute/path/to/maude-at-d0f1375245d7fbaa05b0c6da9b8f60c6c5d388f4 \
  --component-checkout monitor=/absolute/path/to/nightshift-at-d9a0976fad133311c3f8cd5fc780f035714c17c7
python3 tools/check_constellation.py

These checks verify document structure, manifest bindings, and source hashes. The separate qualification record retains the completed anonymous-clone execution scope. See the release notes, operations guidance, and troubleshooting route.