Witburrow | Bugs, Patches & Release History
Updated: Oct 22
October 22, 2026: Witburrow soft rename
Manager OS (MOS) is now Witburrow; the manager default is Wit. Naming update WIT-NAME-2026.10.22.1 is available through the existing update manifest for local review and explicit approval. Custom names are preserved, and ambiguous preferences are not overwritten.
This is naming metadata and an opt-in procedure, not a new stable package or a completed migration of existing installations. MOS-2026.10.12.1 and all three stable downloads, checksums, technical identifiers and old URLs remain unchanged. Older release-ID-only checkers may require a manual review. Community intake remains closed. Historical entries below retain their original names and dates.
Quick setup: download the latest TXT starter pack, give it to the AI you use, and ask it to read the setup instructions and guide you through first-run setup. Choose White Bread, No Crust for the standard profile, or Guided Setup to hear the choices explained. Witburrow does not add tools or permissions to your AI account.
MOS development log: bugs, patches & release history
Updated October 14, 2026. This is an editorial history of 34 sanitized changes, not a claim of 33 production-tested software fixes. The current downloadable MOS starter, handbook and full public framework remain the October 12 release.
Read the labels carefully: a documented rule is not an enforced security control, a saved workflow is not proof that a scheduled run succeeded, and a small controlled test is not proof of fresh-session or concurrent-agent reliability.
Prehistory and scope
Conceptual precursors in 2025 explored memory limits and moving context between AI chats. An identifiable Command Center document existed by August 20, 2026. The formal MOS changelog begins September 6, 2026. This chronology is not exhaustive, and older precursors are not counted as MOS releases.
Chronological bug fixes and updates (34 entries)
Origins and early organization
1. Aug 20-24 — ORIGIN | HISTORICAL RECORD
Early Command Center established a single current task view, separate file/memory/calendar responsibilities, and a low-friction 'one next action' mode. An early file-path mismatch motivated better source locating.
2. Sep 06 — FRAMEWORK | RULE ADOPTED
Introduced canonical Home, state labels, confidence labels, evidence-first review, clear next steps and the rule that completed/deferred decisions stay closed.
3. Sep 07 — PATCH | FIX DOCUMENTED
Found duplicate/stale tasks and 'maybe someday' ideas presented as active commitments; grouped work under single owners and separated candidates from commitments.
4. Sep 08 — PATCH | FIX DOCUMENTED
Separated current project state from historical detail; protected source identities and added fresh-read/rebase discipline when another writer had updated a file.
September: reliability and governance
5. Sep 09-13 — BUG CLASS | REPEATED DRIFT OBSERVED
Current summary headers and task descriptions lagged newer evidence. The source-of-truth principle now requires an owner/last-verified pointer and checks before stating something is missing or settled.
6. Sep 11 — PATCH | CONFIGURATION FIX
A recurring owner lacked useful execution visibility. Replaced it with an owner that reports DONE, EMPTY, BLOCKED and failure outcomes rather than equating invocation with progress.
7. Sep 14-16 — UPDATE | RULE ADOPTED
Continuous-improvement review moved into an existing weekly owner; long-running jobs were split into bounded packets with durable checkpoints, one targeted retry and no replay of completed work.
8. Sep 16 — INCIDENT | RECOVERY VERIFIED
A lengthy run appeared stuck, yet saved outputs were recoverable and intact. The recovery rule now checks saved records before deciding to rerun.
9. Sep 18 — UPDATE | RULE ADOPTED
Added a three-front focus limit, narrow authority rules, stop-checks, reversible change receipts and a recovery tabletop.
10. Sep 18 — PATCH | FIX VERIFIED
Commissioning surfaced stale context/recovery pointers. The current front door and recovery manifest were repaired without rewriting unrelated history.
11. Sep 18 — SECURITY | SPECIFICATION TESTED
Adversarial review identified seven rule ambiguities involving authority, urgency, replay, evidence trust and lifecycle state. Explicit gates and regression expectations were added.
12. Sep 18 — PERFORMANCE | CONFIGURATION VERIFIED
Replaced long embedded automation prompts with compact workflow pointers, keeping actual execution authority and cadence distinct from file definitions.
13. Sep 19-20 — SECURITY | RULE ADOPTED
Inbound updates now pass through a human approval/airlock policy. Untrusted content cannot become instructions simply because it appears in a retrieved file or advisory result.
14. Sep 20 — UPDATE | NARROW EXECUTION VERIFIED
Loop Contract introduced stable owner IDs, checkpoints, retry budgets, replay protection and exact STOP/reopen behavior; an invalid advisory packet was correctly rejected during a bounded test.
15. Sep 20 — UPDATE | SPECIFICATION PRESENT
A policy-kernel/userland distinction, safe-mode and recovery concepts, capability isolation and guarded write transaction rules were added.
16. Sep 20 — ONBOARDING | CONFIGURATION PRESENT
Added Guided Setup, White Bread No Crust, Advanced Custom and Recover Existing modes. Defaults cannot override local decisions or grant permissions.
17. Sep 20-23 — UPDATE | RULE PRESENT
Added progress heartbeats and context capsules that retrieve the smallest relevant set of records for fresh/mobile/voice sessions; access limits remain explicit.
18. Sep 24 — PERFORMANCE | MEASURED SIZE; RUNTIME GAIN UNTESTED
Measured the canonical reference set and introduced HOT/WARM/COLD loading to avoid hauling full archives into routine context. Catalogues describe possible modules, not automatic deployments.
19. Sep 27 — PERFORMANCE | RULE PRESENT
Resource Governor prefers reuse and adequate low-cost tools before escalating to scarce or paid tools, without sacrificing accuracy or privacy.
20. Sep 27-Oct 03 — PATCH | CONFIGURATION FIX
Scheduled owners were deduplicated and current workflow-state records synchronized. Compatible reviews were folded into existing owners instead of starting a watcher for every problem.
October: consolidation and releases
21. Oct 03 — STRUCTURE | CONFIGURATION VERIFIED
Created a domain ownership registry and compact front doors. Evidence remains with its owner; handoffs carry the minimum safe, current result or source pointer.
22. Oct 03 — UPDATE | RULE PRESENT
Combo-Breaker preflight prioritizes ABSORB, COMBINE, ON-DEMAND and ONE-OFF before creating new recurring owners.
23. Oct 09-10 — LIMIT | HOST LIMIT DOCUMENTED
Buddy checks improve visibility but do not provide independent host-failure detection or guaranteed automatic restart. A proposed sub-hour duplicate watchdog was not implemented.
24. Oct 10 — PATCH | FIX VERIFIED
Corrected stale recovery pointers, status labels and overbroad commissioning claims. A bounded efficiency-comparison method and handoff-agreement tests were added.
25. Oct 10 — PUBLIC RELEASE | PUBLICATION VERIFIED
Released an earlier sanitized starter/handbook package. Observed cached older download aliases required use of verified versioned files.
26. Oct 11 — TEST | NARROW TEST PASS
Ordered stale-write simulation rejected a second out-of-date candidate after the first write. One orchestrator coordinated both candidates; simultaneous independent writer safety remains unproved.
27. Oct 11 — ONBOARDING | PUBLICATION VERIFIED
Added a copy-paste fictional demo, four-case test kit and improved page navigation. A contrast issue was corrected before publication; mobile and full accessibility checks were not complete.
28. Oct 12 — PERFORMANCE | MEASURED TEXT ONLY
Shortened seven recurring prompts by 15.9% in characters while preserving recorded identities/cadences. Actual run-time/time/token savings were not measured.
29. Oct 12 — PUBLIC RELEASE | PUBLICATION VERIFIED
Published a small starter, handbook and separate full sanitized reference with Nerd-rules and Combo-Breaker explained. Public edition remains documentation, not an installed autonomous agent.
October 14 private improvements (public documentation only)
30. Oct 14 — PATCH CANDIDATE | PRIVATE RULE VERIFIED; PUBLIC PENDING
Private draft rules now distinguish when an event became true from when the system recorded it. Public examples can clarify delayed evidence without forcing bulk history rewrites.
31. Oct 14 — PATCH CANDIDATE | PRIVATE RULE VERIFIED; PUBLIC PENDING
Minimal, provenance-carrying original excerpts were added for rare handoffs where an exact statement matters. Source pointers remain the default; excerpts inherit no command authority.
32. Oct 14 — REGRESSION CANDIDATE | SCENARIO TESTED; LIVE MODEL UNTESTED
New tests address obsolete facts resurfacing after a newer upload, forged instructions inside quoted history, and document-conversion whitespace inflation.
33. Oct 14 — PIPELINE CANDIDATE | WRITE PATH NARROWLY TESTED; FUTURE RUN UNTESTED
Improvement recommendations now specify source comparison, materiality, approval, backup, minimal staged patch, file-integrity check and live readback before declaring a release.
34. Oct 14 — GOLDEN MILE | CREDITED PUBLIC COMPANION; BEHAVIORAL VALIDATION PENDING
Extended the existing MOS rules and targeted evaluations after a Gen 8 comparison and a 12-source research review. Nine lightweight standard safeguards were identified and integrated privately, while three deeper diagnostic options remain off by default. Clever Girl's existing weekly review now classifies candidates without adding a scheduler. Exact private-file saves were verified, but fresh-session gains are NOT TESTED.
Credit: u/Testchimp80's Gen 8 work provided targeted handoff/provenance inspiration; twelve source projects/papers are individually credited in the companion. No source code imported or external benchmark reproduced.
Known limitations and open tests
Current unknowns: independent fresh-session retrieval; simultaneous independent writers without atomic locking; genuinely independent scheduler/crash recovery; saved-memory prompt-injection resistance in real contexts; and measured maintenance, token, time or human-correction savings.
A real content-conversion bug inflated whitespace in a controlled file update and was repaired, but that does not prove every future document round trip is safe. Earlier CDN caching also left some old aliases stale. File-integrity and live-link checks remain necessary.
The documented October 14 provenance, time-label and improvement-pipeline refinements were saved internally and narrowly checked. They are described here for transparency. They are not included in the October 12 download package, not an autonomous deployment, and not evidence of general model reliability.
Public package versus website updates
Current public package: MOS-2026.10.12.1 / v2026.10.12-R1 (October 12, 2026). Website history refreshed October 14, 2026. These are separate version dates. Manager OS remains free, and installing it requires the user's own setup, available tools and explicit permissions.
Preserved original release-history snapshot
Manager OS release history — September 21, 2026 This is a preserved historical release snapshot. It is not the current download page. Current packages and release labels are listed at https://www.ijaspers.com/post/manager-os. Archived release: MOS-2026.09.21.1 (MOS v3) Public repository: https://github.com/iJaspers/manager-os Update policy: discovery and verification may be automatic; behavior-changing installation always requires local human approval. Community contribution intake remains CLOSED until the private security-reporting lane is verified live. Historical manifest — preserved as published: {"protocol":"MOS_UPDATE_EXCHANGE","schema_version":1,"release_id":"MOS-2026.09.21.1","generation":"v3","channel":"stable","published_at":"2026-09-21","update_policy":"human_approval_required","automatic_install":false,"github_repo":"https://github.com/iJaspers/manager-os","contribution_intake":"closed_pending_security_lane_verification","security_lane":"closed_pending_private_reporting_verification","source":"ijaspers.com"}
Comments