Estate completion control — production proof, consolidation, and retirement gates

[stephenlutar2-hash]

Objective

Close the difference between a working public command demonstration and a durable, authenticated, observable production estate. No item is complete without source, deployment, and live evidence.

Landed or actively merging

• Killinchu Defend plane merged as the sole Aegis/Sentra public runtime surface.
• Vessels folded into Killinchu public topology.
• A11oy publisher admits only Terra, Counsel, Finance, and Lyte as independent vertical front doors and records Sentra/Vessels as folded into Killinchu.
• Vertical-services taxonomy change prepared to classify Sentra as a capability plane, Aegis as a portfolio label, and IMMUNE as migration-required.
• Canonical public-estate manifest and fixed-origin live witness prepared with immutable receipts.

P0 — required before the word production

• Exact merged source is live for A11oy, Killinchu, Lyte, Finance, Terra, and Counsel; every required route and Hugging Face revision matches its source receipt.
• Killinchu Defend state is durable across rebuild, sleep, and rollback; backup and restore are exercised, timed, and receipted.
• OIDC identity, tenant isolation, RBAC, requester/approver separation, session expiry, and audit-subject attribution are enforced outside public demonstration mode.
• SLOs exist for availability, p95 latency, error rate, deployment freshness, connector freshness, and receipt-chain verification; alerts route to a named operator path.
• All production secrets have metadata-only inventory, rotation owner, last-rotated timestamp, least-privilege scope, and a tested revocation path; values never enter receipts.
• Public mode remains non-effecting. Any future effector requires a separately approved authority contract, target allowlist, two-person control, rollback, and live tripwire evidence.

P1 — estate completion

• Snapshot SZLHOLDINGS/sentra, inventory secret key names without reading values, prove Killinchu /defend parity, record rollback window, then retire the duplicate Space.
• Classify SZLHOLDINGS/aegis-assurance; retain only a distinct assurance contract that is not already served by A11oy or Killinchu.
• Classify SZLHOLDINGS/david-leads; keep it outside the flagship estate unless it is an explicitly owned commercial workflow.
• Inventory every remaining SZLHOLDINGS Space against the canonical manifest; no unclassified public Space remains.
• Complete the IMMUNE migration gate: unique admission contract, signed-authority boundary, tripwire contract, rollback receipts, parity tests, and exact-source live witness.
• Bind one governed inference route with model revision, tokenizer revision, benchmark suite, latency/cost envelope, fallback policy, PII boundary, and fail-closed behavior. Do not call an unbound plan inference.
• Prove every official-source connector with fixed origin, schema contract, freshness budget, rate-limit behavior, attribution, degraded mode, and immutable observation receipt.

P2 — product and commercial readiness

• Mobile and desktop journey tests at 320×568, 375×812, 768×1024, and 1440×900 for A11oy and all five public products; keyboard, reduced-motion, forced-colors, touch-target, overflow, and readable-table gates pass.
• One developer quickstart, one operator runbook, one incident runbook, one backup/restore runbook, and one customer-facing trust page all match the exact deployed revision.
• Tenant onboarding, usage metering, support boundaries, data retention, export/delete, licensing, and service ownership are explicit.
• Investor metrics distinguish measured live usage from demonstrations, synthetic data, planned capacity, and projections.

Definition of done

A checkbox closes only with: protected-source SHA, green checks on that SHA, deployment revision, live route proof, rollback evidence where relevant, and an immutable receipt. A screenshot or README statement alone is not completion.

Signed-off-by: Stephen Lutar stephenlutar2@gmail.com

[stephenlutar2-hash]

Live operational receipt — 2026-09-04 23:15 UTC (Grok team probe)

Product is operational. Estate is not closed.

MEASURED

• https://a-11-oy.com/healthz → {"status":"ok","organ":"a11oy","doctrine":"v11","lock":"749/14/163","commit":"c7c0ba17","signer":{"status":"ABSENT","signing_available":false,"scheme":"UNAVAILABLE"}}
• https://szlholdings-a11oy.hf.space/healthz → same payload
• https://a-11-oy.com/api/a11oy/v1/honest → lock LOCKED, Λ Conjecture 1, signer null
• https://a-11-oy.com/console and /lyte → 200, Command Center + LYTE lattice present
• https://a11oy.net/ → 200 Proof Registry (proof only, not product)
• Packet on main: payloads/grok-terminal/ via merged PR docs(grok-terminal): live operational probe 2026-09-04 #1925

WILL NOT close from this comment

• [HF estate] make every SZLHOLDINGS Space public and operational #1764 [HF-ECOSYSTEM-DRIFT] Public manifest is stale #1282 INC-05: apex serves; HF READY and www canonical redirect remain unproved #1497 HF estate / www canonical — blocked-external
• [INCIDENT] Energy ledger forks during rolling restart #1878 energy ledger forks — no joules invented
• [ALERT-CHANNEL] Shared receipt-failure alert channel is OFF #541 [security] Private alert posture requires attention #1714 alert channel / private alert — no secrets from here
• frontier(model): build SZL-Nemo v3 from the governed v2 failure evidence #1034 SZL-Nemo v3 — no GPU train claimed
• Signer remains ABSENT — receipts stay UNSIGNED-honest. Do not treat console marketing copy as SIGNED.

Host canon unchanged: product = a-11-oy.com · proof = a11oy.net · never a11oy.com · no new product Space.

[stephenlutar2-hash]

Evidence map from tonight's alignment round (2026-09-05T01:25Z UTC) — measured, not asserted. No checkbox is being closed; this records where verified evidence now exists.

P0 item 1 (exact merged source live):

• szl-constellation: Space commit 75ff4ece = mirror commit 026bea18 — source/deploy parity verified for v4.7 (15/15 tests green pre-push, fail-closed console mount). The constellation now has exactly the source ↔ deployment ↔ receipt linkage this item requires.
• All six named surfaces (A11oy, Killinchu, Lyte, Finance, Terra, Counsel) have Spaces updated within the last 24h; per-route revision receipts remain the pipeline's witness work.

P1 Space-inventory item: the census is receipted — szl-pin@40e61f2e holds the live 20-Space census (master 968e3d29b6db7ad8b6af4204880467fcf7c49a37f9b179b6607899407ab6ed17, offline-verifiable), including the private duplicates (counsel-assurance, puriq-markets, terra-assurance) that P1 items 1–3 ask to classify.

P0 item 2 (Killinchu durability): actively landing — P0 gate #399 seams 1–3 (durable state, default-deny effector guard, two-person approvals) merged within the last 90 minutes with green harness checks each.

Owner-path items unchanged: OIDC/RBAC, secrets inventory, SLOs/alert routing, and the alert-channel cutover (#541 — blocked on SLACK_WEBHOOK_URL_V2 provisioning, an owner-only secret action) remain owner actions.

Definition of done respected: nothing here closes a box without its receipt.

[stephenlutar2-hash]

ADDENDUM to the evidence map — full-estate health receipt, measured 2026-09-05T01:45Z UTC, independent fetch session:

All six constellation surfaces measured SERVING this session (6/6):

Surface	Result	Evidence
a11oy (szlholdings-a11oy.hf.space)	SERVING	Full doctrine-v11 front door; all four runtime checks at honest CHECKING first paint; ledger depth shown as "—" (not fabricated); Λ rendered gray as Conjecture 1
killinchu	SERVING	Full surface + backend /api/killinchu/v1/honest live JSON (git_sha ffa77b89, v11 LOCKED 749/14/163, locked-8 exact, sqlite durable=True) — receipted on #1836
lyte	SERVING	Governed observability workbench; canonical source linked (szl-holdings/lyte-lattice)
finance (PURIQ)	SERVING	Provenance-first console; decision tape honestly labeled; canonical source linked (szl-holdings/puriq-live)
terra	SERVING	Public-records underwriting; probe contract explicitly fail-closed ("Reachability alone is not a domain measurement")
counsel (PRISM)	SERVING	Attorney-reviewable matter twin; drafting/verification lanes separated

What this strengthens: the P0 item-1 requirement that every named surface be live is now demonstrated at the transport level in a single session, not inferred from repo timestamps. Combined with the per-route revision receipts already in the pipeline, the source ↔ deployment ↔ witness loop is closed end-to-end for the whole constellation.

Cross-reference: killinchu deep verification (finding 5, #1836): static honesty mechanism verified, runtime up, backend evidence live, durability seam live in production.

Still owner-path only: www CNAME (INC-05, one record), OIDC/RBAC, secrets inventory, SLOs/alert routing, #541 webhook provisioning.

[stephenlutar2-hash]

FINAL LOOP RECEIPT — live receipt lake observed, 2026-09-05T01:50Z UTC:

• GET /api/lake/v1/receipts on the product origin returned 100 receipts (page limit reached; chain_index observed up to 144), SHA3-256 hash-chained, schema szl.lake.receipt/v1, spanning 2026-08-22 → 2026-08-30.
• Organs observed in the live chain: a11oy (pcai/run ALLOW, label MODELED, signed=true, seed 42), kernel_plane (manifested, 8 surfaces), state_plane (decided: UNDECIDED — an honest refusal to overclaim, probe fields null), token_plane (skipped: "no *.txt under datasets"), pr_sweep (skipped: "gh cli or token absent").
• Every receipt carries kernel c7c0ba17, locked-8 exact, conjectures labeled (Λ = Conjecture 1, KhipuBFT = Conjecture 2), energy UNAVAILABLE — no invented metrics anywhere in the chain.

Watch item (honest observation, not an incident): the flagship lake's most recent ingest is 2026-08-30T21:04:51Z (chain_index 144). Five days without a new receipt is consistent with "no qualifying actions since," but receipt-freshness should be an explicit watch item on this checklist: if qualifying actions have occurred since Aug 30, their receipts are missing.

Combined with tonight's measurements — 6/6 constellation surfaces serving, honest manifests live on a11oy (git_sha 3616dff) and killinchu (git_sha ffa77b89), record.json PARTIAL exactly as designed, /verify live with labeled-check semantics — the product origin's evidence chain is now observable end-to-end by any anonymous visitor. This closes the loop's reachable work; remaining items on this issue are owner-path (OIDC/RBAC, secrets inventory, SLOs/alert routing, #541 webhook provisioning).