Skip to content
P‑AIProject‑AI
Systems · Project-AI

Project-AI documentary status

internal designation — The United Sovereign Stack

This page complements the homepage by focusing on repository-backed documentary scope, proof surfaces, and current synchronization boundaries.

Meet Legion · public ambassador

Repository identity and role

Project-AI repository is the canonical documentary source for ecosystem architecture, governance framing, and linked subsystem references. The proof portal is a curated public surface, not a full corpus mirror.

The default-branch README frames the repository as "The United Sovereign Stack," integrating a "Trinity of Sovereignty" — Cerberus Ω, Thirsty-Lang/TARL, and the Project-AI Monolith — under one signed constitution. This portal treats that framing as narrative vision, distinct from the verified operational claims tracked in Claims.

Documented A separate github_release_branch describes a v0.0.3 offline-first Windows release with signed-installer verification. That content is not yet merged to the default branch this portal cites, so it is not reflected in the status above.

Known synchronization limit: repository updates may lead the portal until maintainers re-run documentary curation and regenerate pinned data.

The v0.0.3 offline-first release, in practice

The unmerged release branch above describes a v0.0.3 offline-first Windows build. These are unedited screenshots of that Control Center actually running, across two sessions eight days apart — first a browser-based verification pass, then the native desktop launcher signed in as the real owner. They're included as evidence of current UI state, not as a substitute for the pinned-commit documentary sources elsewhere on this page.

Session 1 — browser verification pass (2026-07-21)

First-run setup
First-run setup

Recovery codes issued to a "Browser Verification Owner" test account, explicitly labeled "not a cloud login."

Command Center
Command Center

Gateway, replay, audit chain, and evidence-registry status. Work queue and activity feed are empty by design, not populated with placeholder data.

Requests
Requests

Records a human work request only — captioned "the execution gate is not called."

Evidence
Evidence

21 DOI-backed records (real Zenodo DOIs), tagged Security / Governance / Architecture.

System health
System health

Captioned "not a production-readiness claim."

Governance and authority
Governance and authority

Governance, Capabilities, and Execution gate — the latter two marked "no human action is exposed."

Simulations
Simulations

Registered engines by maturity, from IMPLEMENTED down to PRE ALPHA — most explicitly expose no human action.

Administration
Administration

Account creation plus an append-only account-security event log.

Preferences
Preferences

Local display settings only — explicitly scoped as not touching account, role, or authority.

Session 2 — desktop launcher, signed in as owner (2026-07-28)

Desktop launcher — starting
Desktop launcher — starting

The local runtime (v0.0.3, "P1 Offline-First Local") booting and running its own readiness checks before anything is usable.

Desktop launcher — ready
Desktop launcher — ready

A one-time Owner setup key is issued only after the runtime itself reports its checks complete — access is gated behind verification, not handed out at launch.

Command Center (signed in as owner)
Command Center (signed in as owner)

Same dashboard as the browser session, now against the real local gateway signed in as "IAmSoThirsty," flagged "Partial system evidence" because replay has not run.

My Inbox
My Inbox

Empty — no invented assignments.

Execution requests
Execution requests

Same human-work-record-only form.

Evidence
Evidence

The same 21-record DOI registry, now scrolled to Paper-07.

Audit explorer
Audit explorer

Read-only, permission-filtered search over the append-only audit chain — "never grants execution authority."

Governance and authority
Governance and authority

Identical structure to the browser session.

Security and Chimera
Security and Chimera

A page not present in the browser-verification pass: "verified security surfaces and explicit gaps; no decorative secure claims."

System health
System health

Audit chain now shows 1 entry instead of 0 — real state, not a static mock.

Administration
Administration

The real owner account, with an append-only security event ("auth.bootstrap_completed") timestamped and IP-logged.

Blocked
Blocked

A later session finds another process already on the expected local port and refuses to adopt it: "Project-AI will not adopt or control that process without verified recovery." The fail-closed posture the rest of this UI describes, actually firing.