Personal OS: from scattered work to a clear next decision.

Work answers a practical question: what should I move forward next? It groups current priorities, commitments and project work, then provides a route to the record behind each item. Review holds work that needs checking. Needs you collects decisions that require the owner, so background preparation does not become another personal to-do. The three views serve different moments in the same workflow.

Completion depends on the owning record. A closed decision should leave the active work and review surfaces, while its evidence remains in history. References to the same decision resolve to one item rather than separate copies. Missing evidence stays visible as a gap; a refresh time does not turn an old result into current progress.

Hermes is the main assistant and synthesis layer. It connects permitted workspace context into one grounded answer, brief or next decision. Bots opens ongoing specialist conversations rather than creating a new chat for every dashboard visit. The role card, conversation and Details panel refer to the same specialist, making it possible to ask a follow-up without losing the work being discussed.

Details separates the role's job from its recorded execution. It exposes current work, last result, blockers, recent runs and the next recorded event where available. A model selected for a conversation is distinct from the model recorded for an automated run. LinkedIn Growth appears under Personal Brand and opens that existing chat; it is not an extra independent agent.

An approval card carries the proposal the owner is being asked to judge. LinkedIn cards show the action kind, account, lane, target, context and complete text in the conversation. The response or refusal appears beside that card. The eligible desktop review records the exact local decision; the subsequent worker still needs its own authority and checks before any external action.

Suggested responses solve a different problem. Selecting a multiple-choice option places its code in the message box and focuses it, leaving the user able to edit before sending. Email has its own Review > Email surface with the complete sender, recipients, subject, body and attachments. Rejected email revisions remain rejected; an automatic retry cannot quietly turn the same rejected text back into a fresh approval.

The inbox workflow reads connected sources, identifies reply obligations and prepares complete drafts for Review > Email. Its operations view distinguishes drafts ready, replies due, held items and source coverage. These states help separate a missing reply from an unavailable mailbox or an incomplete scan. The drafting work prepares the decision rather than sending on the owner's behalf.

Calendar context informs the day shape: agenda, commitments and available time can influence the daily view and priority discussion. That calendar feed is read-only. A proposed booking remains a separate action. Mailbox coverage and historical backfill are not uniformly complete, and the proposed Jev private-email classifier remains gated rather than established as active.

Health covers meals, training, sleep, recovery and energy using available evidence. Its meal-planning home includes individual preferences, candidate recipes, served history and an explicit stock check. Feedback can apply to one week or remain ongoing, and a never rating from either household member takes priority. Repeating the same feedback event does not teach the system twice.

Shopping preparation uses whole packs and checked stock, with expiry or expected delivery dates. Stale pantry entries cannot silently remove a needed purchase. Recipe research retains its source and published nutrition; missing values remain unknown, and researched recipes stay candidates until ingredient and shopping checks pass. Meal planning can remain usable when wider phone-derived health inputs are stale. It provides non-diagnostic planning, with no automatic purchase or individual medical claim.

The brand pipeline connects topic research, source-backed writing, visual production and review. It supports detailed text posts, infographics and multi-page carousels rather than treating every idea as a short text update. Personal-account binding, media previews and companion copy keep the intended channel visible. Thomas's monochrome visual system carries through the finished material.

Personal Brand also prepares qualified LinkedIn growth work and exact action cards in its shared chat. The user can inspect the proposed target, account and complete wording before deciding. The specialist's dated task and event history gives context, while its Details panel states current access limits. A recorded local review is separate from scheduling or publishing, and the case does not claim an always-visible browser session.

Daily Job and Additional Money share the goal of progressing paid opportunities but operate different workflows. Daily Job checks role suitability and provider evidence, prepares relevant application material and records the confirmed submission result. Its standing instruction permits suitable ordinary initial applications within defined daily limits. Recruiter replies, interviews, assessments and offers remain separate decisions.

Additional Money keeps service opportunities and selected platform applications apart from the job lane. It retains its own reports, eligibility checks and confirmed outcomes. Specifically authorised free initial applications may proceed; new terms, payments, contracts, identity checks and personal screeners have separate boundaries. A local preparation receipt, application submission and settled income are different outcomes and remain labelled accordingly.

Finance supports budgeting, savings, runway and resilience planning from the current permitted evidence. Its recurring work can produce a money-move or planning pack. Source dates and missing inputs remain part of the result, so an old account view cannot become a fresh recommendation simply because the interface refreshed. Finance does not transact.

Life coordinates household plans, travel and personal obligations. The latest preparation increment separates work owed by the owner, other people's commitments, verification holds and terminal history. It ranks a bounded set of preparation packets and requires independent closure evidence. This first increment produces local plans and holds; complete source-bound drafts, executed administration and real-world closures are later work.

Recurring controllers read their permitted sources, prepare local plans or assets and submit typed results for independent Review. A useful result may be a changed artifact, a verified unchanged result or a proved blocker. These are distinct states. Review checks whether the reported outcome matches its evidence, while OS tracks reliability, source freshness and improvement proposals.

Bot conversations receive relevant changed results and sustained source incidents. Routine unchanged checks stay in reports, Details or expandable Earlier automated checks rather than filling the chat. Direct command receipts keep their own identity, so a repeated check is not presented as a second execution. Recorded local activity supports inspection; external outcomes require the appropriate provider confirmation.

The operating model is shared across the desktop application and responsive interface: current work, specialist conversations, evidence and decisions retain the same meaning. A wide screen can place Details beside a conversation; a narrow screen gives the conversation and its controls more focused space. Existing Android, foldable and Wear OS work extends the estate around device-specific tasks.

The current public tour renders the genuine shared interface with fictional records and visible Demo data. It demonstrates layout and workflow without disclosing personal finances, health facts, contacts or provider receipts. Current desktop evidence and earlier physical-device evidence are described separately. The phone lane is held during device repair, so this refresh does not claim fresh wearable measurements, phone push delivery or full device feature parity.