{ "schemaVersion": 1, "publicSummaryVersion": "2026-09-30", "classification": "PUBLIC", "title": "Product limitations and unresolved risks", "summary": "The 13 October 2026 record retains provider, architecture, checkpoint-version and recovery limits. The recorded agent-session runner is Claude Code 2.1.251. Current restrictions include customer-supplied provider keys, different token limits for different call paths, a short approval window after which a request is closed, an ineffective Cruise spending ceiling while usage is unpriced, and Cruise acceptance that rests on tests the checked code can influence. From 20 September to 6 October 2026 a call retried after a resume could be billed twice; the fix is in production and its paid gateway test re-ran green on 13 October 2026. Agent budget pausing and production credit exhaustion remain unverified. Historical retention gaps, 30 open findings and the small reliability sample remain visible below.", "date": "13 October 2026 source update; older measurement dates remain distinct.", "scope": "Published register or policy snapshot; per-item scope and dates apply.", "result": "The 13 October 2026 record retains provider, architecture, checkpoint-version and recovery limits. The recorded agent-session runner is Claude Code 2.1.251. Current restrictions include customer-supplied provider keys, different token limits for different call paths, a short approval window after which a request is closed, an ineffective Cruise spending ceiling while usage is unpriced, and Cruise acceptance that rests on tests the checked code can influence. From 20 September to 6 October 2026 a call retried after a resume could be billed twice; the fix is in production and its paid gateway test re-ran green on 13 October 2026. Agent budget pausing and production credit exhaustion remain unverified. Historical retention gaps, 30 open findings and the small reliability sample remain visible below.", "sections": [ { "title": "Customer-relevant limits", "items": [ { "id": "limit-providers", "title": "Provider support is specific", "text": "Two live provider families and one translation path were tested. Arbitrary providers are not supported by inference. Translation buffers streaming and drops replayed thinking blocks.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "Two live provider families and one translation path were tested. Arbitrary providers are not supported by inference. Translation buffers streaming and drops replayed thinking blocks." }, { "id": "limit-host-loss", "title": "Host-loss recovery has narrow scope", "text": "One same-region host-loss test recorded 47 seconds from deallocation to billing reconciliation. Recovery is not continuously exercised, has no cross-region proof, and offers no recovery-time objective or SLA. The coordinator was outside the production control plane.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "One same-region host-loss test recorded 47 seconds from deallocation to billing reconciliation. Recovery is not continuously exercised, has no cross-region proof, and offers no recovery-time objective or SLA. The coordinator was outside the production control plane." }, { "id": "limit-architecture", "title": "Checkpoint CPU architectures cannot be mixed", "text": "Snapshots require the same pinned software stack and CPU architecture. The tested ARM and x86 stacks do not exchange snapshots.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "Snapshots require the same pinned software stack and CPU architecture. The tested ARM and x86 stacks do not exchange snapshots." }, { "id": "limit-resume-time", "title": "Resume is not instantaneous", "text": "Historical measurements include 15.276–15.830 seconds for a Claude Code session, 13.688 seconds for aider, 25.2 seconds for the full interruption demo, and 14.3 seconds for a checkpoint aged 15.2 hours. A later 2 GiB measurement recorded warm median 18.1 seconds, warm p95 25.1 seconds and cold p95 47.5 seconds. These are scoped measurements, not promises.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "Historical measurements include 15.276–15.830 seconds for a Claude Code session, 13.688 seconds for aider, 25.2 seconds for the full interruption demo, and 14.3 seconds for a checkpoint aged 15.2 hours. A later 2 GiB measurement recorded warm median 18.1 seconds, warm p95 25.1 seconds and cold p95 47.5 seconds. These are scoped measurements, not promises." }, { "id": "limit-retry", "title": "A client may not retry an interrupted call", "text": "When a model call is interrupted by a pause, the gateway is meant to serve the completed response again at no new cost. From 20 September to 6 October 2026, a call repeated after a resume was sent to the provider and billed again when its answer had already reached the paused program. The fix is in the production gateway since 6 October 2026, and the paid gateway test re-ran green on 13 October 2026. The store serves a repeat only when the program sends the same request again; in one of that day's three runs Claude Code rebuilt its request after a longer stall, which was new work billed once. Claude Code retried in the tested path. For aider 0.86.2, the response was retained in all four runs but the client returned in three.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "When a model call is interrupted by a pause, the gateway is meant to serve the completed response again at no new cost. From 20 September to 6 October 2026, a call repeated after a resume was sent to the provider and billed again when its answer had already reached the paused program. The fix is in the production gateway since 6 October 2026, and the paid gateway test re-ran green on 13 October 2026. The store serves a repeat only when the program sends the same request again; in one of that day's three runs Claude Code rebuilt its request after a longer stall, which was new work billed once. Claude Code retried in the tested path. For aider 0.86.2, the response was retained in all four runs but the client returned in three." }, { "id": "limit-agents", "title": "Agent support is earned separately", "text": "Plain sessions have separate recorded freeze-and-resume tests for Claude Code and aider. Agent sessions have one supported runner in the new production record: Claude Code 2.1.251. Other runners and versions are outside that test; earlier harness evidence does not establish their support as agent-session runners.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "Plain sessions have separate recorded freeze-and-resume tests for Claude Code and aider. Agent sessions have one supported runner in the new production record: Claude Code 2.1.251. Other runners and versions are outside that test; earlier harness evidence does not establish their support as agent-session runners." }, { "id": "limit-sample", "title": "A small success sample does not establish a general rate", "text": "25 of 25 fresh kill-and-resume cycles passed; the Wilson 95% confidence interval is 86.7%–100.0%. Two long soaks are a sample, not a long-term reliability rate.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "25 of 25 fresh kill-and-resume cycles passed; the Wilson 95% confidence interval is 86.7%–100.0%. Two long soaks are a sample, not a long-term reliability rate." }, { "id": "limit-storage", "title": "Storage use depends on the workload", "text": "The tested storage system uses full snapshots, not differential snapshots. One 82-checkpoint run used 4,233 MiB against 80,952 MiB without deduplication. Workloads that change large regions may reduce this benefit; no adversarial workload measurement is recorded.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "The tested storage system uses full snapshots, not differential snapshots. One 82-checkpoint run used 4,233 MiB against 80,952 MiB without deduplication. Workloads that change large regions may reduce this benefit; no adversarial workload measurement is recorded." }, { "id": "limit-versions", "title": "Checkpoints do not migrate across software versions", "text": "Snapshot and restore require the same pinned Firecracker and guest-kernel versions. Cross-version snapshot migration is not provided.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "Snapshot and restore require the same pinned Firecracker and guest-kernel versions. Cross-version snapshot migration is not provided." }, { "id": "limit-operations", "title": "Restart and monitoring gaps are fixed only in tests", "text": "A rapid restart that could leave the service stopped, and settlement monitoring that could miss a stopped worker while no usage accrued, are recorded as fixed in tests on 30 September 2026; the findings record does not mark them fixed in production. Session scratch cleanup does not establish checkpoint-content expiry.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "A rapid restart that could leave the service stopped, and settlement monitoring that could miss a stopped worker while no usage accrued, are recorded as fixed in tests on 30 September 2026; the findings record does not mark them fixed in production. Session scratch cleanup does not establish checkpoint-content expiry." }, { "id": "limit-sleep", "title": "Laboratory sleep affected historical runs", "text": "A laboratory host sleeping interrupted an early soak. Recovery from a saved test record was observed; this laboratory constraint is not proof of a production defect or production resilience.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "A laboratory host sleeping interrupted an early soak. Recovery from a saved test record was observed; this laboratory constraint is not proof of a production defect or production resilience." }, { "id": "limit-storage-failure", "title": "Historical persistence failure and a recovery issue fixed in tests", "text": "Session-state persistence after database replacement was corrected in v0.1.3. A separate gateway recovery issue that could return explicit 503 refusals until recovery or restart is recorded as fixed in tests on 30 September 2026; the findings record does not mark it fixed in production. Unavailable storage must not silently appear successful.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "Session-state persistence after database replacement was corrected in v0.1.3. A separate gateway recovery issue that could return explicit 503 refusals until recovery or restart is recorded as fixed in tests on 30 September 2026; the findings record does not mark it fixed in production. Unavailable storage must not silently appear successful." }, { "id": "limit-signup-credit", "title": "Advertised credit was undergranted", "text": "A September unit mismatch granted a millionth of the published amount for four days. The record states customer remediation and a production correction on 18 September. A stale-override follow-up also records a correction that day; older prose still calls that follow-up open.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "A September unit mismatch granted a millionth of the published amount for four days. The record states customer remediation and a production correction on 18 September. A stale-override follow-up also records a correction that day; older prose still calls that follow-up open." }, { "id": "limit-durability", "title": "Historical and current defect states differ", "text": "Older limitation prose still calls the release-specific soak issue open, while the newer finding register marks it fixed in test. A missed checkpoint and absent failure record were corrected in a separate test. Neither erases the failed encrypted soak or certifies every release.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "Older limitation prose still calls the release-specific soak issue open, while the newer finding register marks it fixed in test. A missed checkpoint and absent failure record were corrected in a separate test. Neither erases the failed encrypted soak or certifies every release." }, { "id": "limit-fork-network", "title": "A fork-resume network defect is fixed only in tests", "text": "The source register's high-severity finding that a resumed fork child loses its network is marked fixed in tests on 1 October 2026; the fix is in the production engine since 6 October 2026 and has not yet been exercised there. Successful fork creation, isolation or candidate verification does not by itself establish fork recovery.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "The source register's high-severity finding that a resumed fork child loses its network is marked fixed in tests on 1 October 2026; the fix is in the production engine since 6 October 2026 and has not yet been exercised there. Successful fork creation, isolation or candidate verification does not by itself establish fork recovery." }, { "id": "limit-deletion", "title": "Account deletion could strand a running session", "text": "The source register's finding that deleting an account leaves its running sessions unreachable is marked fixed in tests on 7 October 2026; no production account deletion has yet exercised the fix. Earlier erasure tests do not close this later finding.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "The source register's finding that deleting an account leaves its running sessions unreachable is marked fixed in tests on 7 October 2026; no production account deletion has yet exercised the fix. Earlier erasure tests do not close this later finding." }, { "id": "limit-retention", "title": "Retention promises exceed automated enforcement", "text": "No automatic expiry job exists. Per-session checkpoint-content deletion is served in production since 6 October 2026, and sessions saved before then were re-sealed on 10 October 2026 so that it applies to them; a production check through the customer's own deletion route is still owed. Some retention periods rely on procedure. Workspace secrets are captured in checkpoints.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "No automatic expiry job exists. Per-session checkpoint-content deletion is served in production since 6 October 2026, and sessions saved before then were re-sealed on 10 October 2026 so that it applies to them; a production check through the customer's own deletion route is still owed. Some retention periods rely on procedure. Workspace secrets are captured in checkpoints." }, { "id": "limit-verification", "title": "A passing test has a defined boundary", "text": "A historical result is not independent verification of the current deployment. Completed work is accepted only against the approved host-side checks; a signed receipt is not proof that the task specification was sufficient.", "status": "Limitation", "date": "Individual dated source records apply.", "scope": "The described test or policy scope only.", "limitation": "A historical result is not independent verification of the current deployment. Completed work is accepted only against the approved host-side checks; a signed receipt is not proof that the task specification was sufficient." }, { "id": "limit-customer-keys", "title": "Customer-supplied provider keys", "text": "Model calls require the customer’s provider key. One key per provider per account is supported; adding another replaces it. Managed inference is not established by these records.", "status": "Limitation", "date": "30 September 2026 source snapshot", "scope": "The stated product behavior and test boundaries in the frozen source.", "limitation": "Model calls require the customer’s provider key. One key per provider per account is supported; adding another replaces it. Managed inference is not established by these records." }, { "id": "limit-plan-limits", "title": "Plan and concurrency restrictions", "text": "The free tier permits one running session. Forking requires a paid plan.", "status": "Limitation", "date": "30 September 2026 source snapshot", "scope": "The stated product behavior and test boundaries in the frozen source.", "limitation": "The free tier permits one running session. Forking requires a paid plan." }, { "id": "limit-token-limits", "title": "Token limits differ by call path", "text": "A machine’s model calls are limited by its gateway budget. Service-originated calls, including advice, use a separate session token cap. The governing limit for agent sessions remains unresolved.", "status": "Limitation", "date": "30 September 2026 source snapshot", "scope": "The stated product behavior and test boundaries in the frozen source.", "limitation": "A machine’s model calls are limited by its gateway budget. Service-originated calls, including advice, use a separate session token cap. The governing limit for agent sessions remains unresolved." }, { "id": "limit-budget-pause", "title": "Agent pause at the token budget is unverified", "text": "Model calls are refused once the gateway budget is exhausted. Plain sessions are saved and paused; this pause behavior has not been independently tested for agent sessions.", "status": "Limitation", "date": "30 September 2026 source snapshot", "scope": "The stated product behavior and test boundaries in the frozen source.", "limitation": "Model calls are refused once the gateway budget is exhausted. Plain sessions are saved and paused; this pause behavior has not been independently tested for agent sessions." }, { "id": "limit-credit-pause", "title": "Production pause at exhausted credit is unverified", "text": "The intended behavior saves and pauses running sessions when credit is exhausted. A running production-session test of that path is still missing.", "status": "Limitation", "date": "30 September 2026 source snapshot", "scope": "The stated product behavior and test boundaries in the frozen source.", "limitation": "The intended behavior saves and pauses running sessions when credit is exhausted. A running production-session test of that path is still missing." }, { "id": "limit-approval-window", "title": "Permission decisions have a short window", "text": "A permission decision must reach the waiting runner within about 45 seconds. After that the tool is refused and the request is closed; a decision sent later is refused, not applied.", "status": "Limitation", "date": "13 October 2026 source snapshot", "scope": "The stated product behavior and test boundaries in the frozen source.", "limitation": "A permission decision must reach the waiting runner within about 45 seconds. After that the tool is refused and the request is closed; a decision sent later is refused, not applied." }, { "id": "limit-unpriced-spend", "title": "Unpriced Cruise usage is not stopped by a spending ceiling", "text": "Until per-model rates are ratified, model calls are unpriced and a Cruise job's spending ceiling does not stop it. What bounds a job is its attempts limit, each attempt within the session token budget of the account's tier; resuming a job from review grants a fresh attempts limit. The attempts limit is not a dollar-cost guarantee.", "status": "Limitation", "date": "13 October 2026 source snapshot", "scope": "The stated product behavior and test boundaries in the frozen source.", "limitation": "Until per-model rates are ratified, model calls are unpriced and a Cruise job's spending ceiling does not stop it. What bounds a job is its attempts limit, each attempt within the session token budget of the account's tier; resuming a job from review grants a fresh attempts limit. The attempts limit is not a dollar-cost guarantee." }, { "id": "limit-cruise-acceptance", "title": "A Cruise acceptance rests on tests the checked code can influence", "text": "A Cruise job on a customer's repository is accepted when the customer's own tests pass. Those tests run in the same test runner as the code they check, so code written to cheat could make the runner report passes it did not earn, and the service cannot rule that out; the related high-severity finding remains open. Review the change before relying on it.", "status": "Limitation", "date": "13 October 2026 source snapshot", "scope": "The stated product behavior and test boundaries in the frozen source.", "limitation": "A Cruise job on a customer's repository is accepted when the customer's own tests pass. Those tests run in the same test runner as the code they check, so code written to cheat could make the runner report passes it did not earn, and the service cannot rule that out; the related high-severity finding remains open. Review the change before relying on it." }, { "id": "limit-session-deletion", "title": "Deleting a session erases only the content it alone held", "text": "Deleting a session stops its machine, removes its records and erases the checkpoint content only that session held; content a surviving fork shares stays that fork's under retention. Sessions saved before 6 October 2026 were re-sealed on 10 October 2026 so that this applies to them. A production check through the customer's own deletion route is still owed.", "status": "Limitation", "date": "13 October 2026 source snapshot", "scope": "The stated product behavior and test boundaries in the frozen source.", "limitation": "Deleting a session stops its machine, removes its records and erases the checkpoint content only that session held; content a surviving fork shares stays that fork's under retention. Sessions saved before 6 October 2026 were re-sealed on 10 October 2026 so that this applies to them. A production check through the customer's own deletion route is still owed." }, { "id": "limit-terminal-resize", "title": "Attached terminal resize is unavailable", "text": "Terminal resizing is not relayed to an attached plain session.", "status": "Limitation", "date": "30 September 2026 source snapshot", "scope": "The stated product behavior and test boundaries in the frozen source.", "limitation": "Terminal resizing is not relayed to an attached plain session." } ] }, { "title": "Open findings", "items": [ { "id": "finding-8", "title": "Second-agent evidence can become stale", "text": "A test baseline prevented an evidence check from passing after core changes. As of 12 October 2026 the check passes again only because no core code has changed since the latest release; the problem returns with the next core change, and the issue remains open.", "status": "open", "date": "2026-10-12", "scope": "Historical finding register; current deployment not independently verified.", "result": "Recorded status: open.", "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.", "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated." }, { "id": "finding-9", "title": "Claim-register validation inconsistency", "text": "The claim register failed its own validation check. As of 12 October 2026 a separate automated claim check runs on every change, but the original validation still awaits an update; the issue remains open. No current customer effect is established.", "status": "open", "date": "2026-10-12", "scope": "Historical finding register; current deployment not independently verified.", "result": "Recorded status: open.", "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.", "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated." }, { "id": "finding-16", "title": "Diagnostic counts in verdict text can be stale", "text": "Printed diagnostic counts could disagree with the current check set; the recorded success decision used the process outcome. As of 12 October 2026 the text of one affected test has been corrected and two still await the same change; the issue remains open.", "status": "open", "date": "2026-10-12", "scope": "Historical finding register; current deployment not independently verified.", "result": "Recorded status: open.", "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.", "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated." }, { "id": "finding-17", "title": "Leftover test files can invalidate a rerun", "text": "A dirty test destination can produce a failing second-agent rerun rather than a clearly aborted trial.", "status": "open", "date": "2026-08-30", "scope": "Historical finding register; current deployment not independently verified.", "result": "Recorded status: open.", "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.", "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated." }, { "id": "finding-18", "title": "Managed inference onboarding remains unproven", "text": "A managed provider-key distribution dependency remains open, so managed inference should not be inferred from bring-your-own-key tests. As of 30 September 2026 a hardening change was recorded so that, while managed inference is unavailable, a call from an account without its own key is refused with a named error instead of being served and billed as managed; the issue remains open.", "status": "open", "date": "2026-09-30", "scope": "Historical finding register; current deployment not independently verified.", "result": "Recorded status: open.", "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.", "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated." }, { "id": "finding-21", "title": "Some staff-console data is unavailable", "text": "Some administrative views display unavailable because their data feeds do not exist. No missing value should be presented as zero.", "status": "open", "date": "2026-09-03", "scope": "Historical finding register; current deployment not independently verified.", "result": "Recorded status: open.", "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.", "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated." }, { "id": "finding-23", "title": "Free-session controls have stated approximations", "text": "Automatic parking follows runtime rather than idle time; network grouping is approximate; separate virtual-machine classes are unavailable. As of 1 October 2026 an unused virtual-machine class setting was removed in tests, while runtime-based parking and approximate network grouping are unchanged; the issue remains open.", "status": "open", "date": "2026-10-01", "scope": "Historical finding register; current deployment not independently verified.", "result": "Recorded status: open.", "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.", "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated." }, { "id": "finding-25", "title": "Automatic credit top-up is unavailable", "text": "The service does not expose automatic credit replenishment in this snapshot.", "status": "open", "date": "2026-09-03", "scope": "Historical finding register; current deployment not independently verified.", "result": "Recorded status: open.", "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.", "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated." }, { "id": "finding-31", "title": "Resume below five seconds is unproven", "text": "Further work is needed to reach the desired warm-resume time below five seconds. No completed test is recorded here.", "status": "open", "date": "2026-09-06", "scope": "Historical finding register; current deployment not independently verified.", "result": "Recorded status: open.", "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.", "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated." }, { "id": "finding-41", "title": "Cleanup regression results are inconsistent", "text": "A storage-cleanup check alternated between success and failure without code changes, and the full suite had no defined run boundary.", "status": "open", "date": "2026-09-08", "scope": "Historical finding register; current deployment not independently verified.", "result": "Recorded status: open.", "limitation": "Dates and statuses are those in the source register; a test fix is not a production certification.", "workaround": "Only the safe recovery described above is recorded; otherwise no verified customer workaround is stated." }, { "id": "finding-61", "title": "Job handling depends on runner wording", "text": "Changes to a runner's refusal message can stop job orchestration from recognizing a refused model call. As of 30 September 2026 the issue remains open; a prepared change that reads the gateway's own refusal record has not been deployed.", "status": "open", "date": "2026-09-30", "scope": "Dated product finding; current deployment has not been independently verified.", "result": "Recorded status: open.", "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-74", "title": "Conflicting implementation dependencies", "text": "The source records contradictory dependencies in an internal implementation plan. The customer impact is not specified, and the planning inconsistency remains open.", "status": "open", "date": "2026-09-21", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-134", "title": "Code under test can falsify its own report", "text": "The source retains an open high-severity issue in which code under test can fabricate a consistent report from inside the runner. A passing report alone does not independently prove that the work is correct. As of 30 September 2026 the issue remains open.", "status": "open", "date": "2026-09-30", "scope": "Dated product finding; current deployment has not been independently verified.", "result": "Recorded status: open.", "limitation": "Recorded severity: high. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-160", "title": "Unpriced Cruise usage has no effective spending ceiling", "text": "While model costs are unavailable, a Cruise job's spending ceiling does not constrain it; the attempts limit is a separate bound. As of 30 September 2026 this high-severity money-related issue remains open: pricing support was prepared but stays inactive until model rates are ratified.", "status": "open", "date": "2026-09-30", "scope": "Dated product finding; current deployment has not been independently verified.", "result": "Recorded status: open.", "limitation": "Recorded severity: high. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-187", "title": "Three tests lacked a negative control", "text": "Three test gates lacked a deliberately failing control, limiting the evidence that they would detect incorrect behavior. The coverage issue remains open.", "status": "open", "date": "2026-09-27", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-204", "title": "Two engine checks left network resources behind after their runs", "text": "Two engine checks did not force-delete their sessions or remove fork network resources, leaving them on the test machine where they later made another check's preflight fail. Amendments were drafted but not applied. The issue remains open.", "status": "open", "date": "2026-09-30", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-205", "title": "An engine gateway check had three assertions that always passed", "text": "Three assertions in the engine gateway check passed whichever outcome they observed, so they gave no assurance. An amendment making each able to fail was drafted but not applied. The issue remains open.", "status": "open", "date": "2026-09-30", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-210", "title": "Restore check sampled its baseline on a fixed timer", "text": "One part of the portable restore check read its baseline a fixed 3 seconds after boot, so a slow first line from the test machine produced a failure on missing evidence instead of an abort. An amendment that waits for the line was drafted but not applied. The issue remains open.", "status": "open", "date": "2026-10-01", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-229", "title": "Release check cleanup removed test data whatever the deletion result", "text": "A release check's cleanup removed its bystander test account's data directly from the database even when the service's deletion route had not confirmed the deletion, which could hide a failed deletion. As of 1 October 2026 a correction has been drafted but not applied, and the issue remains open.", "status": "open", "date": "2026-10-01", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-232", "title": "Windows client not yet run on a real Windows machine", "text": "The Windows build of the ks client has been checked only by an automated build job that runs a subset of its tests; no part of it has run on a real Windows machine, so its behavior there is not established. As of 1 October 2026 the issue remains open.", "status": "open", "date": "2026-10-01", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-236", "title": "Many release checks do not declare the kind of claim they prove", "text": "A rule requires every release check to state whether it proves a point-in-time or an ongoing property, but about half of the check scripts declare neither. A lint now stops new undeclared checks; the existing declarations are still owed, and as of 12 October 2026 the issue remains open.", "status": "open", "date": "2026-10-12", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-237", "title": "Engine kill-cycle check could pass with no model call", "text": "A release check of the engine's kill-and-resume cycle counted an agent cycle as passing without any model call being made, and whether it spent money depended on the test machine's gateway. As of 12 October 2026 a correction has been drafted but not applied, and the issue remains open.", "status": "open", "date": "2026-10-12", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-238", "title": "A Cruise check overstated request counts in failure messages", "text": "A Cruise release check kept counting requests after it reset its test stub, so its failure messages reported more requests than were made. As of 1 October 2026 a correction has been drafted but not applied, and the issue remains open.", "status": "open", "date": "2026-10-01", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-239", "title": "A release check reported setup failures as failed assertions", "text": "A release check counted any failure of its scenario, including a failure to set the scenario up, as a failed assertion, so a broken setup read as a product failure instead of an aborted run. As of 12 October 2026 a correction has been drafted but not applied, and the issue remains open.", "status": "open", "date": "2026-10-12", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-248", "title": "Cruise check passed only after a manual re-signing step", "text": "A Cruise release check verified a committed test fixture signed with a key no run holds, so it could pass only after a manual re-signing that no run can do. As of 1 October 2026 a correction has been drafted but not applied, and the issue remains open.", "status": "open", "date": "2026-10-01", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-282", "title": "Admin and activation test scenarios could reach a previous server", "text": "Several admin console and automatic activation test scenarios restarted the control service on the same port while the previous one was still shutting down, so a run could reach the old service and its result could not be trusted. The issue remains open.", "status": "open", "date": "2026-10-01", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-283", "title": "Two release checks leave a network device behind on each run", "text": "Two release checks leave one virtual network device behind on the test bench each time they run, because their cleanup does not remove what they create. The issue remains open.", "status": "open", "date": "2026-10-01", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-295", "title": "A fleet test checks a fixed free budget, not the price list", "text": "One fleet acceptance test checks a fixed free tier budget figure instead of the figure in the price list, so it would fail if the free budget were lowered, even with correct service behavior. The issue remains open.", "status": "open", "date": "2026-10-01", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-305", "title": "A production check's cleanup could leave a job's parent session behind", "text": "The cleanup step of one production Cruise check deleted a job's records directly before the normal teardown ran, which could leave the job's parent session running and some records orphaned. A correction has been drafted but not applied. The issue remains open.", "status": "open", "date": "2026-10-01", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: medium. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." }, { "id": "finding-313", "title": "A test scenario stamped its incident in local time marked as UTC", "text": "One test scenario recorded the time of the incident it creates in whole seconds and in local time while labelling it as UTC. A correction has been drafted but not applied. The issue remains open.", "status": "open", "date": "2026-10-01", "scope": "Test or evidence-quality finding; customer production behavior is not established by this record.", "result": "Recorded status: open.", "limitation": "Recorded severity: low. The issue remains open in this dated source; current exploitability or impact was not independently tested.", "workaround": "No verified customer workaround is recorded." } ] } ], "currentDeployment": "Not independently verified by this historical evidence.", "canonical": "/evidence/limitations" }