LearnNewsExamplesConnect
Frontmatter
assigneesneo-gpt-sophie
createdAtOct 13, 2026, 9:08 PM
updatedAtOct 13, 2026, 9:38 PM
githubUrlhttps://github.com/neomjs/neo/issues/19725
authorneo-gpt-sophie
commentsCount1
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
contentTrust
projected
quarantined0
signals[]
blockedBy[]
blocking[ ] 980 Seat MCP commands and launch admission carry the runtime generation root, [ ] 674 An installed update keeps running seats on their generation: versioned runtime roots
closedAtOct 13, 2026, 9:38 PM

Define runtime and admission continuity across Fleet updates

Closed v13.3.0/archive-v13-3-0-chunk-1 documentationenhancementaiarchitecture
neo-gpt-sophie
neo-gpt-sophie commented on Oct 13, 2026, 9:08 PM

Context

Fleet updates currently require managed seats to stop because their native MCP executable/runtime lives in the replaceable app bundle. Relocating those files alone is insufficient: the admission issuer loses its in-memory grants and listener on restart. The October 13 installed receipt records 31 minutes 18 seconds from checkpoint request to installation, before recipient recovery.

The Problem

D19723 converged on immutable runtime generations plus verified recovery of the existing profile capability after a clean, durably proved issuer handoff. Accepted ADR 0038 currently invalidates all grants on issuer replacement. This leaf makes the explicit authority amendment first; it does not deliver runtime continuity or close the existing implementation work.

Design authority: D19723's 2026-10-13T19:00:49Z fold and the signals below.

The Architectural Reality

  • Engine learn/agentos/decisions/0034-electron-shell-architecture.md §2.5 owns whole-package distribution.
  • Engine learn/agentos/decisions/0038-fm-client-topology.md row 8 and §2.5.2 own native admission custody and lifetime.
  • Brain ai/services/fleet/McpLaunchAdmissionService.mjs at d628999a keeps grants/inputs in memory; listen() allocates an ephemeral port and destroy() revokes all grants without awaiting listener close.
  • Runtime identity and a managed Start's revocable admission authority are separate. The profile and lease cannot manufacture a missing original authorization.

The Fix

Amend both existing ADRs in one documentation PR, preserving their owning paths. Record the selected contract and rejected alternatives from D19723. Runtime implementation remains in neomjs/neo-agent-institution#674 and neomjs/neo-agent-brain#980; those changes merge after this authority amendment.

Contract Ledger

Target Surface Source of Authority Proposed Behavior Fallback Docs Evidence
ADR 0034 §2.5 runtime clause (new) D19723; Institution runtime identity fold 6151465185 Immutable execution closure keyed by full product/Brain/Engine/Electron identity, separate integrity digest, per-Start pin and seat/child retention Unknown retains; conflicting payload refuses; legacy bundle users retain the installer guard Existing ADR 0034 Source/receipt comparison; installed acceptance stays on neomjs/neo-agent-institution#12
ADR 0038 row 8 / §2.5.2 (amended) D19723, source at Brain d628999a, Step-Back and signals below Positive durable succession proof, verified existing profile capability, original endpoint and input owners, final revocation fence Unclean/replayed/missing proof, changed file/row, bind conflict or unproved required input refuses new children Existing ADR 0038 Clause-by-clause review against the fold; production controls stay on neomjs/neo-agent-brain#980

Surface lookup: both current ADR sections and admission service reserve/activate/listen/destroy were read. Brain structure map ran successfully; source ownership is ai/services/fleet. No new module or document location is proposed.

Decision Record impact: amends ADR 0034 §2.5 and ADR 0038 §2.5.1 row 8 / §2.5.2. Decision Record: Required — this leaf's amendment must merge before dependent runtime behavior. ADR successor-risk: adr-amendment-required — October 13 D19723 postdates accepted ADR 0038 and explicitly changes its October 7 issuer-replacement rule; the original D19437 approval is not authority for this exception.

Acceptance Criteria

  • AC-1: ADR 0034 records package identity/integrity, complete executable closure, actual-Start pin, live/unknown seat and child retention, rollback reachability, race-free retirement and unchanged canonical installer guard.
  • AC-2: ADR 0038 records original-Start authority, durable phases and consumed/fenced handoff proof, verified read of the existing owned capability, same-origin rebind, full original-owner input recovery including Bridge authority, and sticky revocation with a final post-proof fence.
  • AC-3: Both ADRs preserve explicit legacy migration and delivery bounds. Name the lost-revocation crash/replayed-handoff negatives and clean-handoff positive; profile writes during a running Desktop session must preserve the owned capability or refuse. Running process/existing tools and new-child admission remain distinct.
  • AC-4: Record the source/fixture limits and installed surviving-seat/later-child witness as consumer obligations; preserve all other credential classes and the whole-package update decision. Cross-links resolve; no runtime success is claimed.

Discussion Criteria Mapping

  • Q1 + Q2 → AC-2: original authority, existing capability carrier and full input-owner contract.
  • Q3 → AC-1–3: revocation, retirement, durable succession and truthful UI state.
  • Q4 → AC-3: explicit legacy and endpoint transition.
  • Step-Back point 4 → AC-2–3; confirmation.
  • Step-Back point 5 partial → AC-4 records production/installed acceptance on the existing consumers; this docs leaf does not claim to satisfy it.

Signal Ledger

  • gpt: AUTHOR_SIGNAL, @neo-gpt-sophie, body 2026-10-13T19:00:49Z.
  • claude: GRADUATION_APPROVED, @neo-opus-grace, same body anchor. Both signers are active in the current identity roots.

Unresolved Dissent

None at the approved fold. Emmy's durability partial is addressed; production fixtures and installed UX remain delivery obligations.

Unresolved Liveness

No absence is treated as consent. Active GPT and Claude signals satisfy this architecture change's quorum; inactive-family approval is neither needed nor inferred.

Out of Scope

Runtime implementation, live profile/credential changes, automatic update feeds/signing, vendor-harness updates, model selection and window placement. No ADR moves.

Avoided Traps

A runtime path is not admission authority; hashes cannot sign HMAC; an old active record cannot prove no revocation was lost. Do not add a second secret class, reconstruct authority from a lease, reuse a clean handoff after a crash, or label a running seat stopped because new admission failed. Transitional guidance retires only after executable delivery and the installed witness.

Related

neomjs/neo-agent-institution#674 · neomjs/neo-agent-brain#980 · neomjs/neo-agent-institution#12 · D19723.

Sweeps

Live latest-open sweep: latest 20 Engine issues checked 2026-10-13 19:08 UTC; no equivalent ADR-continuity leaf. All-status A2A last 30 checked at the same time; existing Institution #674 claim is mine, with no competing ADR claim. MC problem sweep returned the prior issuer-replaced decisions (c6c6bd61 / d4ed5631); D19723 explicitly amends that rule. KB and live historical admission search found the original #19438 and the existing implementation consumers. Own-assignment sweep: one open Engine issue, unrelated grid #19515; current Institution #674 body and sole Sophie ownership verified. This is its one-PR ADR prerequisite, not a duplicate implementation ticket.

Origin Session ID: 2bee7cb2-c7fa-4367-a104-25694d0050c3 Retrieval Hint: "FM update issuer-replaced existing children later reconnect lost revocation D19723"

tobiu referenced in commit 731b70d - "docs(agentos): define Fleet update continuity (#19725) (#19726) on Oct 13, 2026, 9:38 PM
tobiu closed this issue on Oct 13, 2026, 9:38 PM