Troubleshooting the alpha routes

Start with the exact versioned guide: released maude-plan-consultation/v1, saved-check-attention/v1, objective-saved-check-read/v1, connected-cache-c, installed-saved-check/v1, or reviewed-local-copy/v1. These profiles have independent pins and boundaries.

Record a small, useful report

If you used a released suite/profile, include its manifest version and selected profile; otherwise say “unreleased source.” Include only relevant prerequisite versions, such as python3 --version or rustc --version, not an environment dump.

Before changing state, record the repository URL and exact commit, this guide URL, operating-system and Python environment, documented command, expected result, observed result, and relevant draft, revision, proposal, request, or attempt identifier. Identify the owner of the store, configuration record, log, and SQLite sidecars. Include only the smallest redacted output excerpt that shows the problem.

Common boundaries

The fixture generator refuses a path

Choose a new absent local directory. It intentionally refuses to overwrite a retained corpus. Do not delete a retained corpus merely to make the command run.

A proposal is visible but has not changed the draft

A usable proposal remains proposed until an explicit accept or reject. Inspect its base revision, scope, operation, validation, and diff. Acceptance creates a Plan Core successor only; checking, locking, handoff, authorization, and execution remain separate.

A structural check reports a finding

Use the exact displayed revision and check receipt when inspecting the finding. Do not present a prior validation as a check of a later successor revision.

A provider route lacks a usable credential or budget

Stop at the refusal. Starting the enrolled route does not read the credential or authorize a call. Do not replace the credential path with a value in a command or report, and do not retry a retained provider occurrence automatically.

The Maude design server was interrupted

Stop any remaining foreground server, then use the exact restart command in Operations with the retained plans.sqlite, presentations.sqlite, proposals.sqlite, and owner-facts.json. Do not rerun the generator over that directory. This restores an inspection surface; it does not reconcile a governed attempt.

You need to move or upgrade a store

Cross-store backup, restore, migration, and rollback are unverified. Preserve the four-file set, SQLite sidecars, original revision, environment, and command; do not invent a conversion path.

A consultation reader says unavailable

Parse the JSON result before deciding what happened: this condition uses exit status 0. Confirm the exact selected plans.sqlite, public revision, and kit revision, then stop if the store is absent, malformed, or incompatible. Keep writers quiescent for a consistent aggregate; do not retry a mutating command or replace the store.

A saved-check attention run was interrupted or its final output was lost

Follow the retained-state procedure in the alpha.2 guide. Preserve the existing root and inspect commands.jsonl, the exact Nightshift evaluation and NQ notification custody before considering another action. Missing final output or an unavailable identifier does not establish that no delivery occurred. Do not rerun the create-only generator over retained state or repeat an uncertain local-file write.

An installed saved-check tick was interrupted or returned no response

Follow the alpha.5 retained-state procedure. Preserve the exact root, tick summary, both owner databases and sidecars, configurations, transcript, inspection files and inbox. An acquisition_started or nq_started summary is indeterminate. Response loss after NQ acceptance has not been exercised, so inspect the exact NQ notification and Nightshift evaluation before considering another invocation. The single-user fixture's NQ debug same-UID helper exception is not an installed identity boundary; do not substitute another pinned commit or claim systemd activation.

A reviewed action lost its response or stopped halfway through

Preserve the original durable-manager checkpoint and the exact Plan Core, NQ, Nightshift/Foreman, Switchyard, AG, Docket and executor records. Inspect the existing review, issuance, attempt and settlement identities before another submission. If Docket has an indeterminate attempt, reconcile that same attempt; do not create another grant or repeat the effect. See the alpha.6 refusal and recovery boundary.

You need to inspect an old saved-check result

Use NQ's historical-read procedure with the exact archived binary and an external configuration selecting the archived database. Verify its seal before reading; older archives retain their original verifier and validation scope. Do not edit the sealed config, rerun the check, or treat the old result as present conditions. This does not provide automated rollover or cross-store lookup.

Where to ask

Support is best effort with no guaranteed response time. While waiting, inspect existing records without changing them. An absent receipt does not establish failure; if an effect may have occurred, reconcile its existing attempt before another submission.

For Maude Plan Core or design-server behavior, use Maude's public issue tracker. For AG-hosted Phosphor behavior, use Constellation AG's issue tracker. For a broken page or site example, use the site issue tracker. Include only the minimal redacted report above. These are best-effort channels: opening an issue does not guarantee a response, diagnosis, fix, or permission to change a governed workflow.

For lifecycle handling after the first exercise, see After the first run. The connected-cache example has a separate inspection and interruption guide; its alpha.4 public-only newcomer and documented refusal/recovery checks passed within that profile's limits. For the deterministic authoring setup, see Maude's bounded authoring walkthrough.