Skip to content

Friction and boundaries

  • Managed admission refused a 60 GiB RAM limit with a 12 GiB reserve. Resolved in the durable recipe: 52 GiB RAM, zero container swap, same 12 GiB reserve. Effective limits verified; zero OOM events.
  • Mini controller failed before dispatch. Existing SSH access ran the same supported client-sync CLI with credentials supplied privately in process memory; repeat reported no changes. Controller repair is deferred outside this model-only change.
  • Local Pi full-catalog sync refused the pre-existing 16K compaction reserve against the router 64K output ceiling. No compaction policy was changed; existing local image support produced matching Pi output without correlated request/route provenance. Full local catalog convergence remains an explicit gap.
  • Packaged CLI omits recipe memory limits. Boot unit explicitly uses the containment-capable workspace CLI; move back to the packaged launcher after that feature ships.

  • Evidence-show did not recognize the native multimodal schema in this checkout. Native JSON was inspected directly; no schema conversion or invented normalized result.

  • Additional 259,922-token retrieval completed coherently but refused the synthetic launch code as sensitive. Retained as a failed functional attempt; no OOM or engine error. No matched baseline comparison establishes whether vision caused this behavior. Longer-context semantic acceptance remains unqualified.

User-requested retry: the same 259,922-token fixture passed after the user reported an overlapping prompt. Both attempts are retained; concurrency causation is not established.