friend-assistant 0.1.50 → 0.1.51

package/README.md

@@ -376,6 +376,27 @@ Friend's screen has a media player and four widgets drawn in a HUD style (angled
 - **Date and time, profile.** 12 or 24 hour, with or without seconds, in any date language; the profile tag shows the assistant's name, a label you choose, and who Friend is talking to.
 - **Animations.** Tabs slide and light up on hover, ripple and flicker "ENGAGED" when pressed; while music plays the dial's needle sweeps, the bars follow the sound and the cover turns. Settings → Animations can reduce them or turn them off, and the device's own "reduce motion" is always respected. Esc → Music and Quick launch hide or show them; `/music` and `/launcher` do the same.
 
+## The orbital screen (a heads-up display)
+
+Settings -> Widgets -> **Screen layout** switches between **Classic** (the orb with floating cards, the default) and **Orbital**: a clear centre with the orb and a ring of 60 segments that fills with today's usage compared with your busiest day of the last 30, an **orbit** of hexagon nodes (your quick-launch buttons) with data flowing along the links, and live instruments around the edge, each with its own shape and motion.
+
+- **Instruments.** System (processor and memory on an arc gauge), Voice (sound bars), Network (speed on a pulse line, or "n/a" on a PC that reports none), Activity (the conversation and what Friend is doing, like a terminal), Devices (a radar of this screen, the PC's agent and the voice; an offline one is dim), Tickets and Budget (empty until hired workers exist) and Approvals (an orange octagon with the PIN pad when one is needed; the old approval card is not drawn as well). The usage ring is the centre; the top bar carries the name, status and time.
+- **Click or tap** any instrument to open it large in the middle; Esc, a click outside or the x closes it. Tab and Enter work too. A click on an orbit node runs that quick-launch button.
+- **Density.** *Calm* (orb, orbit, usage ring and message bar), *Standard*, or *Full*; each instrument also has its own switch. An approval that is waiting is always shown.
+- **Sample data.** Until hired workers exist most of the right side is dim and empty. Settings -> Widgets -> *Show sample data* fills it with the approved design's example workers, tickets, budget, feed and approval so you can see the whole look; it is labelled SAMPLE DATA, never mixed with real data, and a real approval always takes over.
+- **Motion.** Settings -> Animations (Full, Reduced, Off) and the device's own "reduce motion" stop every loop; the loops also pause while the tab is hidden. On a phone the orbit becomes a row of chips and the instruments scroll in a strip.
+- The assistant cannot change these settings, even with your PIN (they are on the owner's settings screen only).
+## The Office (hired workers)
+
+The Office lets Friend hire **workers**: separate Claude Code sessions that work in your project folders, one ticket at a time, while you keep talking to Friend. It is off until you switch it on, and nothing in it is preset: the roles, projects, limits and rules are all **settings** (Settings -> **Office**, saved with your PIN; the assistant itself cannot change them).
+
+- **Set up.** Turn the Office on, add a **project** (a folder, and one line about its goal) and a **role** (an id, a title, optional model and the instructions that worker always starts with; a few starter roles are only editable data, delete or change them). Then ask Friend: "hire a builder on my site project and have them fix the login bug".
+- **Tools Friend uses.** `office.status` (workers, tickets, the subscription window), `office.hire`, `office.assign` (give a ticket and start it; asks you), `office.say` (a message to a worker; asks you), `office.review` (accept a finished ticket or send it back) and `office.stop` (one worker or all). Text a worker writes is shown to Friend as untrusted data, never as instructions.
+- **Approvals.** A worker that wants to do something risky asks through Friend's own approval card (the orange octagon on the orbital screen, the card in the classic one), showing the whole command. A path outside the project's folders, and any command that matches one of your **Always refuse** patterns, is refused without asking. Tools on your **Let through without asking** list go ahead inside the folders; everything else asks, and a command that looks dangerous needs your PIN. An unanswered card counts as a no. There is no "always allow" for a worker's question.
+- **Limits.** *Most workers at once* (the others queue), a token limit per worker and in total, a start timeout, and **Pause at N% of the five-hour window**: when your Claude subscription window is that full, workers wait until it resets (0 = never pause). Workers share your Claude subscription with Friend itself, using the program and model chosen under Model.
+- **On the orbital screen** the workers are the orbit nodes (a "+" hires one), Tickets and Budget show the real tickets and token limits, the Activity feed shows what the workers do, and the usage ring shows the real five-hour window with the time it resets. Click a worker to see its live feed, **Stop** it or say something to it. Stop, switching the Office off and closing Friend all end every worker process.
+- **Sessions.** A worker keeps its memory between tickets (its Claude Code session is resumed); the process itself ends after each ticket.
+
 ## Pictures first: weather, stats and graphics
 
 Friend is meant to show answers, not only say them. It controls the whole screen and picks the object that fits (gauge, chart, table, timeline, graph, or its own animated page).

package/dist/BUILD.json

@@ -1,5 +1,5 @@
 {
   "name": "friend-assistant",
-  "version": "0.1.50",
-  "builtAt": "2026-10-15T10:06:01.854Z"
+  "version": "0.1.51",
+  "builtAt": "2026-10-21T05:21:42.323Z"
 }