How you would actually use it.

Not a feature list. This is the path most people take in their first week, in order, with the real screens at each step. Everything here is running in the app today.

Set a goal, get a roadmap back.

Start with something you actually want, written the way you would say it out loud. A name and a life area are the only required parts.

The new goal composer on the Goals page: a title field, a life area selector, an optional target date, an optional reason, and an Add goal button. — Target date and reason are optional, but both change the roadmap you get back.

What happens when you press Add goal

"Run a half marathon under 1:45" is specific enough to plan against, so it drafts straight away. "Get better at chess" is not, so it asks one to three short questions first. It does not interrogate you either way.

The roadmap review card: four drafted milestones, each with a title and a completion criterion, controls to reorder or remove them, an already done checkbox on each, a field to add another, and a Create goal with this roadmap button. — Nothing has been saved at this point. This card is a draft you are editing.

The review step is the important one

Each milestone arrives with a completion criterion, so it is something you can actually call finished. Rewrite, reorder, remove, add your own. This is the moment to make it match how you really plan to get there.

Tick already done on anything finished before today. It counts toward progress but writes no dated achievement, because it did not happen while IKARUS was watching. Create goal with this roadmap is the only control on that card that saves anything.

A saved goal: the roadmap rail showing two completed milestones struck through with dates, the current milestone marked CURRENT, and one still to come. — Two done, one current, one ahead. Progress reads 2 of 4 because two are finished, not because something estimated it at fifty percent.

Then you work it one milestone at a time

One milestone is always marked current, and that is your single next thing. This is also what makes the rest of the app work: a goal with a roadmap is what Direction ranks, what the brief notices going quiet, and what a Nexus can be pointed at.

Each morning, read Direction first.

It sits at the top of Today and it is deliberately short. Five items, ranked, chosen from everything you have going on.

The Direction card with five numbered items. Each has a title, the reason it was ranked, and Done, Pin and Dismiss controls. A Reset control sits in the header. — The grey line under each item is the reason it is there. That line is built from your data, not written by a model.

Why each thing is on the list

The reasons are plain facts, and nothing is ranked by a model deciding what it thinks you should care about. Items come from the current milestone of each active goal and from the agenda of any Nexus, which is why the list mixes a client deadline with a long run rather than quietly sorting work above everything else.

The three controls, and when to use each

Done completes the thing itself, not just the row. Pin holds something at the top when you have decided it matters more than the ranking thinks. Dismiss hides it until tomorrow. Those presses are the only thing that moves the ranking: nothing is learned quietly in the background.

III

An automation starts as a proposal.

You never build one from scratch unless you want to. IKARUS notices the routine first and offers it back.

A proposed automation card headed IKARUS noticed a pattern, with a title, a plain description, the access it would use, and Review and enable, Snooze and Dismiss controls. — One card per pattern, on the Automations page and in the brief. It has done nothing yet.

What has to be true before you see a card

The same sequence has to appear in three separate sessions inside two weeks, or four separate days for a daily routine. Below that nothing is raised, so an idle week produces no cards rather than weak ones. The card names what was detected and the access it would use.

What review and approve actually means

Review and enable does not enable anything. It opens the proposed automation in the editor as an unsaved draft, with every step listed the way it would run. You read them, change them, delete the ones you do not want. Only pressing create in that editor saves it.

Dismiss is permanent for that pattern. Snooze brings it back in seven days.

Once it is running, anything consequential still asks. A step that deletes, sends, or reaches outside your machine waits for you at the moment it runs, every run, and that confirmation covers only that run.

The Morning Brief, and how to read it.

It opens once when you first land on Today. One page, assembled on your machine, then out of your way.

The Morning Brief: an opening sentence naming a scheduling collision, then boxes for Calendar with three events, Priorities with two flagged messages, and Goals and routines. — The demo persona is fictional. On your machine these are your own events, your own flagged mail and your own goals.

The first line is the point

The opening sentence is not a summary of the boxes below it. It is the one thing the day turns on, usually a collision: a meeting sitting right before the block you meant to think in, a deadline landing on an afternoon that is already full. Read that line, decide the one thing it asks you to decide, and the rest of the morning gets easier.

The boxes underneath are the evidence for it. Goals and routines is the one to watch: it is where a goal you have not touched in two weeks shows up, before you have quietly abandoned it.

It is written once a day

It is written once, the first time you open Today, so re-opening costs nothing. If a source is not connected it says so, instead of quietly leaving a box out.

A Nexus is for one thing you are running.

Most of what you do needs a goal, not a workspace. A Nexus is for the handful of things big enough to have their own state.

The interior of a Nexus called Studio: a dark scoped chat on the left, and a sidebar with the mission, the current goal, four agenda items, recent chats, linked goals and the executive scope. — Inside a Nexus the interface changes colour, which is the point. You can tell at a glance that you are in a scoped space rather than the whole app.

What it holds

A mission and a current goal you write. An agenda whose items feed into Direction alongside your goals. A vault scope, so notes linked here stay here. And a chat that already has all of it in context, so you are not re-explaining the project every time.

When it is worth opening one

Open a Nexus when a thing has its own running state: a business, a dissertation, a house move, a rebrand. Something with a mission you could write down, work that arrives in pieces over months, and a body of notes that belongs to it and nothing else.

Do not open one for a goal. "Read a book a fortnight" in a workspace of its own is just an empty room to maintain. If you are not sure, leave it as a goal. It can move into a Nexus later.

IHow it works The permission model underneath all of this, and what earning autonomy means VIEW IIThe systems Browser Attach, the Vault, the Trust Center, Workflows, the Recorder, Adaptive Intelligence VIEW