Status

What exists, what has been shown, and when. Each row below is a dated statement with its evidence and the condition that would have to be met before the claim is strengthened.

Summary as of 2026-10-02

Alpha 2 accepted 2026-10-02 — one governed service start on two fresh Ubuntu 22.04 virtual machines, installed from a published source-free bundle and checked by separate fresh observations; operator beta in preparation. A prerelease, not a general suite release; 0.1.0-alpha.6 remains the released integration profile.

Alpha 1, which ended with the released 0.1.0-alpha.6, proved the semantics: a real composed occurrence, its authority, custody and currentness boundaries, recovery, receipts and refusals. Alpha 2, accepted on 2026-10-02, shows that a packaged set of versions can be installed from published artifacts onto fresh machines by someone outside the development environment and run one governed effect with independent postconditions. Beta will mean an operator can actually live in it, with an operator-facing workflow, coherent status and refusal surfaces, and real setup, upgrade, recovery and day-to-day operation; that is in preparation, and nothing here claims it yet.

Released integration profile: 0.1.0-alpha.6, reviewed-local-copy/v1. One exact plan to create a local file was independently reviewed, explicitly accepted, authorized once, executed once and settled, then checked by a separate read. Anyone can re-verify the retained evidence from public source without repeating the effect.
Runnable demo: the indeterminate-effect demo passed a cold-clone run in a fresh virtual machine on 2026-09-25. The custody service is real and built from source; the other parts are local stand-ins. Its source is the tag demo/indeterminate-effect-20260925, a qualified public exhibit, not a Docket release. See the ledger row.
Released component package: NQ 0.2.0, a Debian package and tarball for NQ alone.
Alpha 2, accepted 2026-10-02: a published source-free bundle of six Ubuntu 22.04 packages (AG operator tools and systemd executor, Docket, Nightshift, NQ 0.2.0 and Pulse support) was installed on two fresh virtual machines; one governed start of a fixed system service was authorized once, custodied and settled, and independently confirmed by fresh unit and HTTP observations. Two setup refusals before any authority was issued were kept. The release is a prerelease; the component repositories carry the exact source on their dev/operator-beta branches and have no new tags. See the ledger row.
Observation profile on one operator host (2026-10-01): NQ 0.2.0, Monitor’s host-posture runner and a Nightshift recurrence timer were installed as services on one production-adjacent Ubuntu 22.04 host, made real capacity observations, delivered one live Slack message and ran one unattended recurrence tick. About an hour later acquisition exceeded the runner’s time bounds and every cycle since has been refused, fail-closed; the cause is in NQ. See the record and ledger row.
Earlier Alpha 2 candidate (2026-09-25), history: the alpha.6 composition packaged for Debian 12 passed a clean install, a newcomer run and an upgrade-continuity run, and a hostile review’s kit-check finding was fixed; it was never accepted and is superseded. See the ledger row.
Earlier profiles: alpha.1 through alpha.5 remain available for narrower consultation, saved-check, objective-read, connected-cache and installed-cadence paths; see guides and source.
Not production-ready. The boundaries are on the limits page.

Names used on this page

Each name is one small program; the components page has the details. The words composition, profile, exhibit and promotion are defined below.

AG: Decides whether one exact piece of work may run, and grants permission for that one run.
Docket: Keeps custody of an authorized attempt: sends it once, records the outcome, and reconciles an uncertain one by reading rather than repeating.
NQ: Evaluates a narrowly defined question from recorded evidence, or refuses when the evidence is missing or stale.
Maude: Writes and checks the exact plan of work before anyone authorizes it.
Nightshift: Tracks work and conditions over time and proposes the next task.
Pulse: Checks whether current evidence still supports one specific statement.
Switchyard: Runs bounded requests to a model provider, used here for the independent review of a plan.
App Server: The agent runtime, built from public Codex source, that Switchyard drives for that review; see guides and source.

Status ledger

One row per object: what it claims, when that was last verified and by what, where the evidence lives, and what would have to happen before the claim may be strengthened. Rows are dated statements, not a live panel — a mechanical check may satisfy a promotion condition, but promotion stays an explicit editorial act.

Constellation 0.1.0-alpha.6 — reviewed local copy

composition qualified immutable integration release

One exact local-copy plan was independently reviewed, explicitly accepted, authorized once, executed under Docket custody, settled successfully, and followed by a read-only observation. An anonymous public-clone reproduction verified the retained evidence without repeating the provider call or effect.

verified 2026-09-20: the immutable alpha.6 manifest, qualification record, walkthrough, and anonymous public-clone verification
evidence: alpha.6 walkthrough · manifest · qualification
promotion: This release is immutable. Operational burn-in, live notification delivery, cross-version restore, migration, rollback, and production consumer adoption require separate evidence.

Alpha 2 — governed service start on two fresh Ubuntu 22.04 machines

composition accepted Alpha 2 showing; published prerelease; not a general suite release

Six Ubuntu 22.04 packages (AG operator tools and systemd executor, Docket, Nightshift, NQ 0.2.0 and a Pulse support package) were installed from one published source-free bundle onto two fresh virtual machines. On the target, AG issued one exact one-use authority, Docket consumed the enrolled owner standing, kept custody of the single attempt, dispatched the signed envelope and settled success, and a fixed, previously inactive systemd service started. NQ on the target independently observed the unit loaded, active and running; NQ on the controller independently fetched the service's health endpoint and matched status, no-redirect and the shipped body hash. Pulse judged current support for exactly those two propositions. Two earlier setup attempts were refused before any authority was issued, and their records were kept.

verified 2026-10-02: showing m2-support-003, completed 2026-10-02 02:41 UTC: all 15 installed runtime executables on both machines matched the candidate bytes, the five component source commits matched their published dev/operator-beta refs, and the result record and records archive were published with the bundle and its digest
evidence: release: bundle, digests, result record · ALPHA2.md (identity table) · runbook · ALPHA2-RESULT.json
promotion: This is a prerelease that shows one fixed scenario on two fresh machines, once. It is not aggregate health, effect causation, exactly-once execution, clock accuracy, general support-family adoption or a beta. The component repositories carry the exact source on their dev/operator-beta branches and have no new tags or releases; build reproduction is not claimed; NQ's UTC time quality is unqualified. Beta needs ordinary component release and promotion lifecycle, restart and outcome-unknown handling, durable install, upgrade, rollback and day-two operation, and a reviewed beta release.

Observation profile, generation one, on one operator host

composition installed and exercised 2026-10-01; acquisition failing closed since 18:49 UTC the same day

NQ 0.2.0, Monitor's host-posture runner and a Nightshift recurrence timer were installed from Ubuntu 22.04 packages as services on one production-adjacent operator host. Within the first hour the runner made real filesystem-capacity observations and published a status projection, NQ delivered one live Slack message that the owner received, and the timer ran one unattended recurrence tick. From 18:49 UTC NQ's per-invocation work exceeded the runner's fixed time bounds, and every cycle since has been refused and published as unknown, which is the runner's designed fail-closed response. The cause is in NQ: it validates the entire retained history on every store open, so cost grows without bound. The same mechanism was seen in an earlier sustained VM run.

verified 2026-10-02: the owner's dated installation record and its correction of 2026-10-02 03:05 UTC, summarized on the record page with host identity removed; package digests are listed there
evidence: sanitized record · NQ 0.2.0 source · host-posture runner source
promotion: A bounded, watermarked validation path in NQ; a reinstall that stays healthy for a stated period and survives a reboot on the host; and the recurrence glue becoming a component contract rather than site-written configuration. No governed effect runs on that host, and nothing about it is a production claim.

reviewed-local-copy/v1 — earlier Alpha 2 release candidate (2026-09-25), history

composition historical release candidate; never accepted; superseded by the accepted Alpha 2 showing

Packaged builds of NQ, Maude, Nightshift, Pulse, AG, Docket, Switchyard and the App Server, with a setup kit, were installed into a fresh Debian 12 virtual machine from those artifacts alone. One reviewed and accepted occurrence settled successfully and wrote its file exactly once. Every requested refusal held: a wrong artifact digest, a repeated init, a stale review, an expired authorization, a second execution attempt, and acceptance of the wrong candidate. The review came from a local fixture standing in for the model provider, and the acceptance was performed by the test harness, not by a person.

verified 2026-09-25: clean-install run-004 on 2026-09-25: 31 pass, 0 fail, 0 not exercised, with setup kit 0.4.0. It reruns every earlier case, including a check that the evidence verifier shipped in the kit gives the same result inside the virtual machine as outside it and a replay of the settled evidence without the issuer's private key, and adds cases from the hostile review: the review's altered setup kits and substitute artifact were run against the new bundle and refused, and an already-installed NQ is now compared with the package file by file. An earlier upgrade-continuity run (run-002: 22 pass, 0 fail, 0 not exercised) upgraded an install of the previous kit to a second, test-only build and re-verified the first build's retained evidence, byte for byte; the upgrade code is unchanged in kit 0.4.0, so it was not rerun. Both run records are retained privately; the harness source is public on an unmerged branch.
evidence: clean-install harness source · upgrade-continuity harness source · the released alpha.6 profile it packages
promotion: Closed. This candidate was never accepted and will not be released; the accepted Alpha 2 is the two-machine showing of 2026-10-02 on Ubuntu 22.04, built from different forward source lines. The record stays because the clean-install, newcomer, upgrade-continuity and hostile-review results remain evidence about the alpha.6 composition's packaging. The local trust boundary it found is still open and now described against Alpha 2 on the limits page. The two harness links point at a commit that is only on an unmerged site branch and will break if that branch is deleted.

Constellation Docket

artifact public source; exercised in alpha.6

Takes custody of one authorized attempt, dispatches an authority-neutral executor, and records settlement and reconciliation. Alpha.6 exercised its bounded local permission snapshot and local-copy executor path. Alpha 2 exercised enrolled owner-standing enforcement, attempt custody, signed dispatch and settlement across two machines (forward source 0c771e9b, published on dev/operator-beta).

verified 2026-10-02: the alpha.6 manifest and qualification record at the exact pinned public revision; the Alpha 2 showing of 2026-10-02 at the published forward source
evidence: repository · alpha.6 walkthrough · Alpha 2 release
promotion: The profile is narrow; it does not establish production hardening or arbitrary executor compatibility.

Constellation AG

artifact public source; exercised in alpha.6

Checks whether exact automated work is admissible and grants bounded one-use authority for one specific run. It does not execute work or infer permission from a provider response. Alpha 2 exercised one-use authority for a signed systemd service start on a separate machine (forward source f21b2431, published on dev/operator-beta).

verified 2026-10-02: the alpha.6 one-use authorization and public evidence-reader checks; the Alpha 2 showing of 2026-10-02 at the published forward source
evidence: repository · components · Alpha 2 release
promotion: No family-wide or production maturity is claimed.

Constellation NQ

artifact public source; bounded released profiles

Evaluates retained evidence under named profiles and keeps missing, stale, unavailable, or uncertain results visible. Its results do not authorize an effect.

verified 2026-10-02: alpha.2 through alpha.6 profiles, the Alpha 2 showing's fresh unit and HTTP observations, and the operator-host installation record
evidence: repository · components
promotion: One live Slack delivery was observed on 2026-10-01 with the owner confirming receipt; that is one message, not qualified delivery. Sustained acquisition over a growing store failed on the operator host because NQ validates its whole retained history on every open (see the observation-profile row). Cross-version restore, production migration and rollback remain unqualified.

Constellation NQ 0.2.0 component package

artifact published component release; developer preview

A Debian package and a tarball for NQ alone, built twice offline with identical bytes and accepted in a clean Debian 12 virtual machine (49 pass, 0 fail, 2 not exercised). It packages one component; it is not an installable Constellation suite. A rebuild of the same source for Ubuntu 22.04 is what the Alpha 2 bundle and the operator-host installation carry; only the Debian 12 assets are published under v0.2.0.

verified 2026-09-25: the published GitHub release, whose assets were downloaded and checked against their recorded digests and the qualified copies
evidence: v0.2.0 release · components
promotion: NQ's maturity stays developer preview. The package does not qualify any other component or composition. The Ubuntu 22.04 build is published only inside the Alpha 2 bundle, not as a v0.2.0 asset.

Constellation Nightshift

artifact public source; recurrence and alpha.6 occurrence paths exercised

Owns temporal observation, recurrence, and task proposal without acquiring authorization or execution custody. Alpha 2 exercised the canonical supported observation and exact-work proposal; on the operator host one packaged recurrence timer ran one unattended tick (forward source 3333c791, published on dev/operator-beta).

verified 2026-10-02: alpha.5 installed-cadence qualification and the alpha.6 occurrence/review path; the Alpha 2 showing of 2026-10-02 at the published forward source
evidence: repository · components · Alpha 2 release
promotion: No complete production recurring installation or consumer migration is claimed; the operator-host recurrence used site-written glue and its posture is incomplete by construction.

agent_governor (classic Python)

artifact deprecated predecessor

Preserved for historical records and migration context. New authorization work uses Constellation AG; the two products are not presented as wire-compatible.

verified 2026-09-21: the public repository deprecation notice and canonical successor documentation
evidence: deprecated repository · successor
promotion: None. Do not use this predecessor as the current installation path.

Indeterminate-effect demo (refund with a lost reply)

exhibit cold-clone qualified; tagged public exhibit, not a Docket release

An agent reports a refund done after the reply was lost. Docket, built from source, records the attempt as indeterminate, sends nothing twice, and settles success or failure only on a separate observer's read of the provider's ledger. A second run with the request lost ends in failure under the same agent claim. Docket is real; the authorization signer (a stand-in reproducing AG's published test vector), the payment provider, the faulty network link and the agent are local stand-ins. Everything runs on one host under one clock.

verified 2026-09-25: run-003: an anonymous HTTPS clone of the demo source into a fresh Debian 12 virtual machine, with the network cut off for the build and the run; the demo exited 0 and its independent check passed 53 of 53 checks. The exhibit tag demo/indeterminate-effect-20260925 (eeb0534) carries the same demo code; only the README changed.
evidence: demo source (tag demo/indeterminate-effect-20260925) · transcript · check output · recording
promotion: The tag is a qualified public exhibit, not a Docket release or cohort promotion; the demo counts as part of Docket only once it is merged there. Independence holds because this demo's worker delegates reconcile to the observer; Docket does not pin that configuration, so it is not a general guarantee. Using AG itself, a remote provider, or several observers would each need separate evidence.

Four-office governed vertical

exhibit historical 2026-07 composition

An earlier pilot separated proposal, authorization, execution custody, and evidence evaluation. It remains research history, not the current installation guide.

verified 2026-07-26: dated public office records from the historical pilot
evidence: archived exhibit · current documentation
promotion: Superseded as the public starting point by the immutable alpha.6 walkthrough.

ECAD / design-flow work

proposition pre-alpha research direction

Extends Constellation upstream into how work is designed, decomposed, composed, and reviewed. It is not part of the qualified alpha.6 integration profile.

not verifiable — nothing built: No general ECAD/design-flow release has been qualified.
evidence: current boundaries · research directions
promotion: A separately scoped, reproducible public profile; alpha.6 does not provide one.

Ledger as of 2026-10-02. Generated from status.json by tools/render_status.py in the site repository; it is a dated statement, not a live panel. A row moves only by an explicit editorial act — a passing test may satisfy a promotion condition, but it does not promote the claim.

How to read the labels

The ledger and the archive use two small vocabularies, so that a reader never has to guess whether something is an idea, a design proposal, a working specimen, a qualified composition, or deployed evidence.

Four kinds of object

artifact: An implemented system with a bounded, independently inspectable claim.
composition: A specific relationship between artifacts that has actually been exercised. Compositions are earned individually and dated; none of them generalize.
exhibit: A behaviour you can presently inspect or run.
proposition: Candidate architecture under investigation. Named, not ratified, and usually not built.

Other terms

profile: One named, pinned composition with a released guide, such as reviewed-local-copy/v1. An integration release qualifies a named profile.
promotion: Strengthening a row’s claim, for example from release candidate to release. It happens only by an explicit editorial decision once the stated condition is met.
settlement: The final recorded outcome of an attempt: success or failure, with the evidence it rests on.
reconcile: Finding out what happened to an uncertain attempt by reading evidence, never by repeating the attempt.
alpha-exit: Historical name for the work of getting from the alpha integration releases to a first packaged release; it ended with Alpha 2.

Four kinds of thing shown

schematic: A designed explanatory diagram or normalized trace. It teaches the shape of the system. It is not output.
captured run: Literal bytes from an actual execution, carrying the command, the version, and the date it was run.
rendered: A readable presentation generated from a real machine artifact. The raw artifact stays reachable.
cited: A claim whose warrant is a document in a public repository, linked at the point of use.

Where a distinction is not yet earned, this site says so rather than smoothing it. Synthetic fixtures appear only where they are identified as synthetic and used to demonstrate conditional behaviour — never as testimony about a real estate. Terms of art are defined in the glossary.