Guide·09 of 10
The coach
What it can offer, what it records, and how to say no.
The first minute
01Link
Take an offer
lodelodeAfter a navigation, a chip may appear with one offer, its evidence, and what it would save each week. Tap lode twice to take it. Exactly one line is written to your config.
Mailcoach lode m → Maillode lodeyou searched for it 31 times across 6 weeks · about 40 seconds a week · tap lode twice to bind it · lode ⌫ not this oneMail, reached through the launcher again
When you are ready
02Link
Say not this one
lode⌫lode and delete declines. Later retries at a better moment then parks. Never sleeps for a season. Both reopen only if the evidence materially outgrows the answer.
Hold lode, then delete
03Few know thisLink
What it can offer
A letter for an app you keep finding through the launcher. A shorter address for a chain that keeps stumbling. The letter your hand already presses by mistake, bound to what it wanted. A layout for two apps that travel together. Meetings, once you have joined a few by hand.
04Few know thisLink
The closed road
lodespaceAccept a letter and the launcher, asked for that app, answers with the letter and opens it only on a second return. The toll lifts when your hand has the letter, or after nine weeks at most.
Hold lode, then space
05Link
Read what it knows, or delete it
lodestar observations prints the record plainly, because a store you cannot read is one you cannot consent to. lodestar observations clear deletes both records, or one with --logbook or --health.
06Link
Join a meeting from the door
lodelodeWith meetings on, a chip appears a few minutes before a meeting with the join behind a double tap, in the profile the calendar chose. Off by default, and the calendar permission is asked only when you turn it on.
MailWeekly sync · Workmeeting Weekly sync · in 4:52lode lodeopens in Work · matched calendar · lode ⌫ not this oneFive minutes before a meeting
The fine print
What nobody finds by pressing keys
- The record is how you got places, never what you did there: pauses inside an address, whether the map was consulted, abandoned chains, the wrong key pressed, transitions between apps. No titles, no addresses, no text.
- The coach paces itself by what your hands demonstrate. After an accept it stays silent until that address has actually compiled, and each accept in a row shortens the wait.
- A gesture you have not fired in ninety days becomes a finding, with the one config line that would retire it. Nothing turns off on its own.
- Health, on its own switch, keeps the rhythm of your hands: when each key goes down and how long it is held, by hand, finger and kind of key, and how the pointer moves. It never stores which key, but the pattern can partly show what you typed, so it stays on your Mac. It also notes when it could not see, so a quiet stretch is never mistaken for rest.
- The logbook and health each have a switch and a size limit in Settings, under Observations, and off means nothing is written.
Why
Why it works this way
Seeing a shortcut changes nothing. In the study behind this design, people who could keep using the old path used the new one 29 percent of the time, and half of them never used it at all. When the old path was closed, 73 percent switched. So the chip's job is consent, and the intervention is structural: the old road gets a toll, priced in one deliberate confirm.
Settings
The settings behind this page
Read from the schema Lodestar itself emits. The settings window shows the same rows, and each wears the path it writes.
coach.enabledboolean · default trueLet Lodestar offer one improvement at a time, in quiet moments, priced in seconds.
$ lodestar config set coach.enabled trueobservations.logbookboolean · default trueKeep the logbook: how you move between apps, windows and gestures, on this machine only. Sites by name, never their pages, titles or what you type. The coach reads it.
$ lodestar config set observations.logbook trueobservations.logbook-mbinteger · default 256Disk the logbook may claim. Once it is full the oldest months leave first; their monthly summaries stay.
$ lodestar config set observations.logbook-mb 256observations.healthboolean · default trueKeep the health record: when each key goes down and how long it is held, by hand, finger and kind of key, and how the pointer moves. No key is stored, but the pattern can partly show what you typed, so it stays on this machine and is included in backups. Independent of the logbook.
$ lodestar config set observations.health trueobservations.health-mbinteger · default 1024The size Lodestar tells you the health record is nearing. Health is never deleted on its own.
$ lodestar config set observations.health-mb 1024meetings.enabledboolean · default falseOffer the calendar's next meeting as a chip.
$ lodestar config set meetings.enabled falsemeetings.lead-minutesinteger · default 5Minutes before the start the chip appears.
$ lodestar config set meetings.lead-minutes 5meetings.calendarsobjectCalendar or account name → profile. Outranks web.routes for meetings.
$ lodestar config set meetings.calendars {}