Reading Naetive without reading code

Last reviewed: 28 Oct 2026

You run the project. Agents write the code. Naetive is where you find out what is going on without opening a chat or a repository. This page is the daily routine, for someone who never reads a diff.

The morning: Status

Open Status. One word says how the project's understanding is doing:

Thriving or Steady: fine. Read on.
Starting: too new to judge. Ask an agent to map the project if it has not.
Drifting: the code moved and the understanding did not follow. Ask any agent: "re-check the understanding against the recent changes."
At risk: entries are disputed and waiting on you. Open Understanding and settle them; it takes a minute.

Then the four cells. Agents saying None connected when you expected one means something is disconnected: open Connect. Work tells you what is in motion and how many jobs are stale. Code is the last push Naetive saw.

Then: Work, one band at a time

Needs you first. It is short by design: a blocker an agent named, a decision it is waiting on, a disputed entry. Everything else moves on without you; this band is the whole list of where it does not. Each item says what it needs in a sentence.

In motion next. Each card is a job an agent is on or touched today. Open the card, not a chat. Read three things:

the spec, top section: what this is and why, in plain words;
the todos: how many are ticked;
the last update: what changed and what is next, in one or two sentences.

That is enough to know where the job is. The files and commits are attached under the update if someone technical wants them.

Stale occasionally. A job untouched for a week is either done and not closed, or forgotten. Say to an agent: "pick up the export job where it left off" or "archive it".

Reading an entry on Understanding

An entry is one thing the project knows. Its title and summary are written for you, in words you could repeat to a colleague. Under it:

seen in the code or data means an agent saw it. an interpretation means it is the agent's reading, not yet confirmed.
Checked against the code lists the files it rests on, and you can open them. Not checked yet. means nothing backs it yet; treat it as a note, not a fact.
Your turn means it is disputed and waiting on you in Needs you.
Detail for agents, folded, is the technical part. Skip it.

If an entry looks wrong to you, click Query this → on it and say why in one line; the next agent checks it against the code and it comes back to you only if the agent cannot settle it. Or say so to any agent: "I don't think that is right, dispute it".

Settling a dispute

Needs you gives three buttons. Let an agent settle it: an agent re-reads the code and decides, then records the answer. Keep: you know it is right, and it stands as it is. Drop: you know it is wrong; it leaves the understanding and your code is untouched. When in doubt, let an agent settle it; that is what it is for.

Asking for a picture

Any connected agent can tell you the state of things in prose: "Give me a two-paragraph update on the project for the team" or "What are the open risks?". It reads the same understanding and the same jobs you see, so its answer matches the pages.

What you do not have to do

You do not write entries, tick todos, or post updates; agents do. You do not read the code. You read Status, then Needs you, then In motion, and you answer the few questions that reach you. That is the job.