LMOS VOID Beta 0.35.0: Guided Autopilot, Virtual C-Suite, and Owner-Gated Jerry Execution
LMOS adds a private AI Board where executive advisors can organize questions and proposals, Layne approves every execution, and Jerry becomes the single development/QA lane with collision, privacy and no-contact guardrails.
What changed
Added the private Guided Autopilot board inside Jerry.
Added six recognizable executive identities with role-specific lenses and private owner questions.
Added proposal composer, owner approval checklist, Jerry execution lane, completion history and private Board Inbox.
Added private C-suite meeting creation and owner-calendar scheduling.
Added an overnight approved-work policy that remains owner-gated and one-job-at-a-time.
Changed manual Jerry job creation and rotating QA so they create pending proposals instead of executable work.
Added collision prevention for overlapping work in the same app/scope.
Added a hard worker check for the owner-approval marker before execution.
Removed legacy Jerry memberships from real owner projects and made every synthetic executive profile non-discoverable.
The operating rule
Board thinks. Layne approves. Jerry executes. Advisors never write code or contact customers. Jerry never gets blanket access to private member/customer data. If a task needs information outside the approved system evidence or owner-provided context, it stops and asks.
Overnight reality
LMOS can hold a nightly approved-work policy and queue, but code-writing still needs a real ChatGPT automation bridge. The product does not pretend an internal queue is autonomous reasoning. When the bridge is connected, it should process only already-approved jobs and preserve the same one-job-at-a-time guardrail.
Use the beta on real work.
The most useful feedback is not “I like it.” Tell us where you hesitated, what took too many clicks, what did not save the way you expected, and what would make this useful enough to return to next week.