One sentence becomes a day.

You write down something you want. What follows is a chain, and every link in it is inspectable. This is that chain.

"Run a half marathon under 1:45" becomes four milestones.

The roadmap review card: four drafted milestones, each with a title and a completion criterion, with reorder, remove and already-done controls, and a Create goal with this roadmap button. — Drafted, then handed back to you. Nothing is saved until you press create.

A want is not actionable and a roadmap is. Each milestone carries a completion criterion, which is the part that matters later: "hold a 10 second tuck planche" can be finished, "work on strength" cannot. Too thin to plan against, and it asks a question or two first.

Every morning, one milestone per goal competes for your day.

The Direction card: five ranked items, each with the reason it was ranked, and Done, Pin and Dismiss controls. — Five items. The line under each is the reason it beat the others.

Only the current milestone of each goal is eligible, so one goal cannot flood the list. Agenda items and deadlines join them, and all of it is scored on priority, target date, how long since anything moved, and how much of the roadmap is done.

No model chooses. The scoring is arithmetic in code and the reason you see is that arithmetic written out. Only your own presses move it.

III

Then it puts them in the hours you actually have.

Today's plan: three timed blocks with specific detail lines, a note that two ranked items were left unscheduled, and a button to put the plan on the IKARUS calendar. — Real times, and detail specific enough to start. Two items did not fit, and it says so rather than padding the day.

Ranking answers what, this answers when. It can decide what fits, but it cannot reorder the list or add to it. Three blocks that fit beat eight that do not.

The detail comes from the milestone's completion criterion, which is why it reads "2K easy, 4K half marathon pace, 2K easy" and not "go for a run".

Fixed commitments: three declared blocks of time with their hours and days, each with Pause and Remove. — Declared once. The planner treats these hours as gone.

You declare these once. The planner is told the windows, then anything landing inside one is dropped in code afterwards, because a rule that lives only in a prompt is a preference.

Nothing reaches your calendar until you press the button, and it writes to a calendar named IKARUS and nowhere else.

What you keep repeating gets offered back.

A proposed automation card headed IKARUS noticed a pattern, with a title, a description, the access it would use, and Review and enable, Snooze and Dismiss controls. — One card, with what was detected. It has done nothing yet.

Three separate sessions inside two weeks makes a pattern. Twice is a coincidence and raises nothing, which is why an idle week produces no cards rather than weak ones.

Enable opens the steps as an unsaved draft, so you read what it would do before it exists. Once it runs, anything destructive still stops for you, every run.

One gate, and it is the same gate every time.

Every call in that chain, from chat, a workflow, a replayed recording or the planner itself, passes the same two checks: is this tool granted to this Executive by name, and what level is its class at. There is no second path.

Read, write, destructive and external are set separately. Refusals are logged as faithfully as successes, so you can see what IKARUS tried, not just what it managed.

Set the write class below, then attempt to attach a browser tab.

Illustration

Write class level

Choose a level, then attempt the call.

The Trust Center, where you set all of it

IThe walkthrough The same chain from the other side: what you press, step by step VIEW IIThe systems Every capability underneath, and the constraints each one runs with VIEW