Change log

What has landed in NEU, newest first, and what it changes for you.

Now

A task taken from your session keeps a link to that session.

A task held from a session carries the session's own link, so the task thread shows where the work is happening and a colleague can open it. Built; an independent checker verifies it, then the owner's word before it merges. This line changes the moment that happens.

record: task-010

9 October 2026

sec-011 to sec-013

The hub's database keys moved to the new scheme. The old keys are switched off.

The server reads a new kind of secret key first and says which kind it loaded; the legacy keys that had leaked into a shell file and a dead service were disabled. Both health pages confirmed the new key before the old ones went. For you: the one key that could read everything no longer exists.

task-011

The plan is readable from your session with its order and ids.

Mission control holds the order of the plan, and the connector returns each line with its id and position, so a session can take the next line without a person pointing at it. For you: your session knows what comes next.

6 October 2026

sec-005, runtime-013, gate-002

The walls between accounts, checked and fixed.

One account could read another account's task comments, messages, inbox or timeline through four routes. Closed. The guardian now acts on a spliced but real false completion and never passes an invented approval. An agent that proposes shows the proposal's code and never calls it recorded. For you: what is yours stays yours, and a proposal is never dressed as a fact.

5 October 2026

brain-170

Procedures are filed by section. An answer cites the exact heading.

A written procedure used to go in as one block. Now every heading becomes its own entry, embedded with its place in the document, and the whole-document blob leaves the search results. The agency's 14 procedures were re-filed as 217 sections. For you: an answer points at the paragraph, not the file.

mcp-026, mcp-027, brain-168

Search the brain by meaning from your session, with the brain's own vocabulary.

The connector gained search by meaning and the brain's self-describing schema: one sentence for every type and link name, the ids in use per pocket, filters by status, and retired entries marked as retired with their successor. For you: ask in plain words and get the entries, never a withdrawn one as current.

4 October 2026

brain-160 to brain-165

Links closed: reading follows them, lists never offer a withdrawn entry, a pocket can follow a folder.

Six changes in one day. Reading follows the links a few steps. A list never offers a retired entry as current. A report shows what is unlinked per pocket. A scoped token can link and set status inside its pocket. Search is grant-scoped. A registered pocket follows a folder of files, runs a dry run on change, and files the report; the write still waits for the owner. For you: the brain stays consistent without a person combing it.

mcp-024, mcp-025, task-009, task-010, ship-001

Propose links and retirements from your session; a task remembers the session that held it.

Already-filed entries can be linked or retired by proposal from your session, with the filing method carried in the connector's standing instructions. A task taken from your session shows who has it and links to the session, and your session reads the task's thread. A feature switch now answers per hub. For you: nothing is edited in silence, and work from your session is on the record.

3 October 2026

mcp-020, mcp-021

Typed knowledge proposed from your session: a client, a decision, a person, with its type checked.

The connector reads the brain's schema and vocabulary and proposes typed entries; a held approval still saves after the page was left open. For you: the brain never receives a shapeless note.

1 October 2026

mcp-017 to mcp-019

One brain connection per pocket; clients created from your session in a batch; a task carries how it is verified.

Your session can write to more than one pocket, each through its own connection. Registry clients are proposed as one batch. A task is created with its verification and its definition of done, shown in the task drawer. For you: a task says how you will know it is done before anyone starts.

28 September 2026

mcp-016

A batch of told events: one page, one click. The task board updates as work moves.

Everything said in a meeting is proposed as one batch and approved on one page. Tasks gained an "in review" state and a board that refreshes nearly in real time. For you: the meeting goes in once, and you see who is reviewing what.

26 September 2026

mcp-015

The task loop from your session: take, work, submit, review. One holder per task.

A task held from your session is closed to the hub's agents and the reverse; the loop is tagged by role and backstopped by a person. Verified by the owner driving it live. For you: no two hands on one task.

25 September 2026

mcp-014

Archive instead of delete. The plan's descriptions editable from your session.

Areas, programs, projects and milestones are archived, never hard-deleted, from your session or the app; their descriptions, objectives and vision are editable in both. For you: nothing disappears, and the plan reads as you meant it.

24 September 2026

mcp-010, connector-ui-001/002

The connector, shipped: one sign-in, permissions first, the first widget.

Your session signs in to the hub through a redesigned consent page with a readable permission list; a settings panel shows and changes what it may do; one identity per person and client; task access granted from settings without reconnecting; the first card rendered inside the conversation. For you: your session is a user of the hub, with grants you can read.

21 September 2026

orch-002 to orch-004

One runtime. The old agents' separate runtimes retired into it.

Three earlier agent runtimes were replaced by one; retiring an agent now really removes it and a new account gets its own workspace, both checked by an independent checker. For you: one place where agents run, one place to look.

20 September 2026

sec-003, sec-004, brain-152, brain-157

Approve means write. Email you can tune. Files stay in one account. The entity catalog ships.

An approved proposal is written at once, no second step. Email preferences per type, a daily digest, password reset. Two more account walls closed: a delivered file and an image belong to one account. In the brain, a catalog of 147 entity types across twelve domains, and a queue for proposed new clients. For you: fewer steps, tighter walls, a shared vocabulary for what things are.

18 September 2026

mcp-007, brain-144

Propose from your session, approve in the hub, and the write lands. End to end.

The first write path from your session: a proposal, an approval page in the hub, a write with a write-capable token minted explicitly for approved writes. The owner drove it live. For you: your session can add to the brain, and only through your yes.

17 September 2026

mcp-004 to mcp-006, auth-001 to auth-003, budget-002, runtime-012, runtime-013, ops-007

The hub's own sign-in for your session, account isolation, and a model budget the public page cannot blow.

NEU runs its own OAuth 2.1 server for the connector sign-in; five read-only tools over the brain's read contract; owner-scoped grant and revoke of an Area. Six shared tables gained an owner and a backstop that fails closed. The public docs chat is limited per visitor and per day, every call priced and recorded; long conversations read their history from the prompt cache; the guardian judges with the agent's identity and corrects only with evidence; health endpoints tell the truth. For you: the doors have locks, and the bill has a ceiling.

16 September 2026

budget-001, runtime-011

Every hub has a monthly model budget. Warned once, refused at the cap.

Each hub's model spend is capped per month; the inbox warns once, and at the cap the hub refuses with a plain message instead of a surprise bill. Agent turns cache their tool definitions and system prompt. For you: a known worst case on cost.

15 September 2026

client-119, client-120

A read-only brain dashboard inside the app, through a token that can only read.

A dashboard of the brain in mission control, served only through the dashboard token; an agent's handle cannot move between owners and a wake runs only for its owner. For you: a view of the brain that cannot write.

14 September 2026

brain-119, brain-130, client-117, client-118, conn-107

Scoped, revocable tokens for every reader; an approved client is established before its records arrive.

A consumer of the brain gets a token scoped to its pocket, minted on the box without crossing a screen, and revocable; an approved client exists in the registry before any of its records land; a corpus with no declared owner confirms nothing. For you: who may read what is a token you can take back.

11 September 2026

brain-106, brain-119, brain-124, infra-101, agent-001, github-005

The read contract, version one. The agency's brain goes live.

A client's history is readable through one canonical contract; writes land in the token's pocket; the agency's brain instance is live and its procedures are in; an agent is seeded from a manifest in the repo it serves; a repository grant carries verbs, and a read grant never writes. For you: the first hub with a company's knowledge in it, read through one door.

5 September 2026

brain-120, brain-121

Typed entries are minted only through the typed door. The third door is closed.

Every path that could create an entry without its type and provenance was closed, including the agent's own memory tool. Upload provenance points at an original or declares it does not. For you: there is one way in, and it asks where the entry came from.

2 September 2026

brain-118, brain-125, conn-107

Nothing lands confirmed without saying on what basis.

A value graded derived or reported is never stored as confirmed, whatever the writer asked; owner-stated facts carry a confidence and an expiry; an unchanged re-ingest writes nothing, and a forced one is explicit. A held re-ingest ran: 460 claims, 73 real supersessions. For you: the brain cannot be talked into certainty.

1 September 2026

conn-107, brain-107, infra-100

The corpus extractor, and the derivation contract approved.

A folder of documents becomes brain entries through one extractor; the first corpus went in. The contract for turning a meeting or a document into proposals, each tied to the text that supports it, was approved. The dev brain moved to self-hosted Postgres. For you: the method by which knowledge enters was written down before the code that automates it.

12 August 2026

brain-101, brain-103, conn-105, conn-106

The registry and the pipeline: entities, identities, sources, links, deny by default.

The brain's backbone: typed entities with identities, sources and links; a people roster proposed and confirmed with an audit; scope denied unless granted. Connectors for Google Drive and Gmail, Asana and a meeting bot were staged, not switched on. For you: the skeleton everything since has hung on.

What is being built now and what follows. V1 is the first version; Next comes after it; Later is planned with no date.

Search by exact words beside search by meaning.

An entry is found by the words it contains as well as by what it means, so a name, a code or a figure lands on its entry. For you: twenty of twenty real questions find their entry.

record: the V1 exit test

Filing on one word.

You say "file it" at the end of a call or a day. Your session prints what it understood, you say one word, and it lands in the brain with its source and date; the confirmation comes later, in one batch. For you: the day is filed before you forget it.

record: plan line 16.6

Procedures as skills every connected session receives.

A written procedure becomes a skill: steps a session follows and cites. Any session connected to the hub receives the hub's skills on arrival. When a section of the document changes, the skill says so and a named person officialises the new version. For you: no prompt engineering, ever.

record: plan lines 16.1 to 16.4

A team in one hub, on one screen.

Every worker has their own NEU; the company's hub is let to them on one screen, pocket by pocket, with a verb each; their own sessions reach what they were granted. For you: a new hire sees the right half of the company on day one.

record: client-116 S1 to S7, mcp-009

One app for every hub you may enter.

A rail of hubs on the left, like workspaces. Inside a hub: inbox, chat, brain, agents, runs, settings, all for that hub, and nothing of a hub you may not enter. For you: one place to look, whatever you belong to.

record: plan lines 17.1 to 17.10

Agents act within the grant of the person speaking.

In a hub chat the agent does only what the speaker may do; only named people may instruct an agent that acts or spends. For you: a shared agent cannot be talked past its owner's rules.

record: plan line 2.11

Connectors to meetings, task boards and drives.

The hub follows a meeting recorder, a task board and a document drive the way it follows a folder today: a finished meeting, a closed task or a changed file becomes proposals with their source, waiting for a yes. For you: nothing goes stale, nothing updates behind your back.

record: conn-105, conn-106

The API for building on a hub.

Knowledge, agents, tasks and runs reachable by programs, under the same grants as people. For you: a dashboard or an app on top of your hub without rebuilding the memory and the agents.

record: plan line 2.10

Every page of the docs re-read against what is built.

Each page carries the rows it rests on; when a row changes state, the page is due for a re-read. A truth pass over every existing page before the first version closes. For you: the docs never describe something that is not there.

record: plan line 11.8

The first two built by us: a coach's dashboard and a money picture, each an asset of its hub. For you: proof that the API carries a real screen.

record: decisions 88 and 117

After the first version passes its own exit test in the agency, the next hubs open to a few companies, each set up in one sitting. For you: an invitation with a date on it.

record: decision 147

Later

Other assistants beside Claude.

The hub's door is an open standard; the first version is Claude. Other assistants follow when their side of the standard is ready. For you: the hub outlives any one vendor.

record: version 2