Integration release 0.1.0-alpha.6

One reviewed action, authorized once

The user wanted one bounded result: create an absent local result.txt containing 38 reviewed bytes. The qualified occurrence acquired evidence, retained an independent review, required explicit operator acceptance, spent one exact authorization, executed once under Docket custody, settled successfully, and then required fresh observation before any continuation.

What happened

1. Observe: NQ admitted one bounded host observation; Pulse supplied currentness support for that exact observation.
2. Propose: Maude compiled the exact local-copy plan and Nightshift admitted the occurrence.
3. Review: Switchyard retained one bounded OpenAI review. The enrolled verifier accepted its exact result.
4. Accept and judge: an operator accepted the exact candidate digest. AG checked the accepted review and standing; provider completion alone did neither.
5. Authorize once: AG issued and spent authority for the exact work. Docket resolved one operator-owned local permission snapshot.
6. Execute under custody: Docket dispatched Maude's authority-neutral exclusive-create executor and retained one attempt.
7. Settle and inspect: Docket settled the attempt as successful. A later no-follow read observed the exact 38-byte regular file.
8. Stop: AG ended at settled_observation_required. Another action needs fresh observation, judgment, and authority.

Verify from public-only inputs

These commands clone the immutable release and the exact public checker revision into a fresh directory. They verify every released evidence digest, reproduce the objective/occurrence check, and confirm that a mismatched plan identity refuses.

SETUP=$(mktemp -d /tmp/constellation-alpha6.XXXXXX)
cd "$SETUP"
git clone https://github.com/unpingable/unpingable-site.git site
git -C site checkout --detach constellation-v0.1.0-alpha.6
git clone https://github.com/unpingable/constellation-ag.git ag
git -C ag checkout --detach e0f30de668234935cdbc4b0bd04f5dc13838411d
python3 site/constellation/releases/0.1.0-alpha.6/verify-evidence.py \
  --ag-checkout "$SETUP/ag"

Expected output is one compact constellation.recipe-b-public-evidence-check/v1 object with result: passed, projection_correspondence: exact, objective_completion: not_determined, authority_for_another_action: none, and mismatched_plan_digest: refused.

Inspect progressively

• Readable action summary: review, proposal, authorization, attempt, settlement, effect digest, claims, and nonclaims.
• Post-effect observation: what the later local read established at one time.
• Objective check: exact cross-owner identity match and deliberately unknown objective completion.
• Full Phosphor objective projection: detailed public record for drill-down.
• Release manifest: exact runtime and evidence-reader source pins.
• Qualification record: successful, refusal, uncertainty, response-loss, and newcomer scopes.

Refusal, uncertainty, and recovery

The successful occurrence is not the only evidence used for this profile. A mismatched Docket-standing operator refuses before review or authority. The pinned Maude/Docket qualification retains an indeterminate attempt at a deterministic post-sync/pre-success-record transition and reconciles that same attempt without another execution. A retained-success response-loss case likewise reconciles the original successful attempt rather than creating another grant or copy. These are targeted qualification cases, not additional provider-reviewed occurrences.

If an installed run loses a response, preserve its AG, Docket, executor, review, and manager records together. Inspect the original identities before doing anything else. Do not submit a replacement occurrence merely because the caller lacks a terminal response.

Run it yourself versus adapt it

The commands above are the supported public newcomer path for this release: read and verify the qualified occurrence. Adapting an external caller to perform a new effect additionally requires its own enrolled reviewer route, current evidence, exact standing inputs, operator-owned Docket grant, executor closure, durable state, and authority. The candidate glue is documented in the reviewed local-copy integration example; it is not a secretless one-command installer and does not grant the reader authority to contact a provider or perform work.

Lifecycle and retention

The public evidence reader starts no services and creates no state beyond its temporary clones. For an operational installation, preserve Plan Core, NQ, Nightshift/Foreman, Switchyard, AG, Docket, executor journals, manager checkpoints, configuration identities, and exact source/artifact pins as one recovery set. Stop writers before a consistent backup. Restart only the original durable owner; inspect before considering another submission. State migration, restore across changed component revisions, and rollback are not qualified by alpha.6.

Live Slack, Discord, or PagerDuty delivery was not performed. Deterministic/local notification adapters are documented separately; message delivery or acknowledgment would not establish execution success or authority.