All work01 / 05

Our product / Desktop / 2026

An operating system for a product company where people decide and agents build: one feature seen at three altitudes, and an engineer who tells the agent exactly how, in eight lines.

The engineer’s direction to the Sync agent on an orange field: eight tagged lines across design, code and configuration.
Type
A product of our own
Sector
Operations, enterprise software
Platforms
Desktop browser
Shown
  1. Research and concept
  2. The product
  3. The brand
  4. The system
  5. The working piece

The person and the agent

Work software assumes the person who decides a thing also does it. In a product company where agents now do much of the building, that is no longer the only arrangement. In NU-ORG each person decides at their own altitude and the agents work beside them. At Tallyard, the CPO asks for one feature, offline photo capture on job cards, and decides the date. The engineering manager gives the build an owner. A senior engineer writes the direction the Sync agent builds from, eight lines across design, code and configuration, and the agent reads it back before it writes anything.

A product of our own; nobody commissioned it. Not launched. Tallyard and every person in it are invented, and their portraits were generated with AI.

01 / Research and concept

Direction is the engineer’s most important decision. So we made it an object.

The question

We started with a question: what is left for each person in a product company to do, once agents write the specs, the code and the tests? Desk research pointed one way. Microsoft’s 2025 Work Trend Index talks about people becoming “agent bosses”. Coding agents now take an issue and open a pull request. But the engineer briefs them with a prompt in a chat box and reviews the result afterwards, so her real intent is never written down: which states, which data model, what not to touch, which limits.

The insight

A ticket tracker with agents added does not fix this. It still records activity. What matters now is the decision each person makes, and the engineer’s most important one is the direction they give the agent that builds. So we made direction an object of its own: short, exact, split into Design, Code and Config, read back by the agent before it starts, and cited by every part of the result. We call the answer “Read-back before build”, and we are preparing it for the pattern library.

The model

The rest of the model stays small and named. A Strategy (here, one feature) resolves into a Cluster of Moves and Calls. A decision that crosses teams becomes a Link. Roles are people (photos in circles) or agents (coded squares). Tools are Sources the OS reads, never windows you open.

Trade-offs

What we chose, and what it cost: eight tagged lines over a twenty-field form; read-back before the build over review after; one home layout for every role, so the three can be compared; homes, not widget dashboards. We did not design agent setup, permissions or mobile.

The NU-ORG model: Strategy, Move, Call, Link and Role, each with its glyph and a one-line definition.

02 / The product

One feature, ten screens, three people.

Saskia Holm is CPO at Tallyard, an invented software company for field-service teams. Its technicians lose photos when they have no signal, and 41 support tickets say so. Every screen answers three things: what you need to know, the one thing to do, and the one fact that makes it easier.

The UI rule, on one screen: the engineer’s read-back

  • Know

    Seven lines match. C2 would retry every 30 s and drain batteries in basements.

  • Do

    Correct and build.

  • Eases

    The correction is one sentence, and the agent restates every line before it writes one.

Ten desktop screens, from the CPO asking for a feature to the rollout waiting for her approval.
The homes of the CPO, the engineering manager and the senior engineer side by side, each with one orange card for its altitude.

Desktop / 10 screens

  1. The NU-ORG desktop: a CPO asks for offline photo capture in the system line.

    01 / 10

    Now

    Saskia asks for one feature: offline photo capture on job cards, by the 14 April release.

  2. The feature resolved into nine items for three people and their agents, with one call for the CPO.

    02 / 10

    Cluster

    It resolves into nine items. Jules, Ben and Mira each get a call, and agents take five moves. The last call, approving the rollout, is hers.

  3. The CPO’s home: full resolution would cost three weeks, so hold 14 April at 2048 px or move it.

    03 / 10

    The CPO’s home

    Full-resolution upload would cost three weeks. She holds the date at 2048 px, because 38 of 41 tickets ask for evidence photos, not print quality.

  4. The engineering manager’s home: give the engineer the build for two weeks and link the design manager.

    04 / 10

    The manager’s home

    Ben gives Mira the build for two weeks. Approving it links the design manager, who must sign off the queued state.

  5. The senior engineer’s home: the Sync agent waits on her direction, with spec, states and limit attached.

    05 / 10

    The engineer’s home

    The Sync agent is ready and waits on Mira’s direction. The spec, Jules’s states and Saskia’s limit are already attached.

  6. Writing the direction: two design lines, three code lines, three configuration lines.

    06 / 10

    Direction

    Eight lines in Mira’s own words: two for design, three for code, three for configuration.

  7. The engineer’s correction under the agent’s read-back, where one line is flagged.

    07 / 10

    Read-back

    The agent restates every line. Seven match. On C2 it planned to retry every 30 seconds, which would drain batteries in basements. Mira corrects it in one sentence.

  8. The build mapped back to each line, ready to approve for staging.

    08 / 10

    Built to direction

    The job card’s three states, the code and the config keys, each citing the line it implements. She approves it for staging.

  9. The manager’s home: the build is in staging, ready for the 14 April release train.

    09 / 10

    Back to the manager

    Ben puts photo capture on the 14 April release train.

  10. The CPO’s cluster with every call resolved and the 5% rollout waiting on her.

    10 / 10

    Back to the CPO

    Every call is answered. Her last one: approve the 5% rollout.

The engineer’s one-line correction beside the agent’s read-back: seven lines match and one is flagged.
The result mapped to the direction: job card photo states, code and config keys, each citing its line.

The three homes share one layout, so they can be read side by side; only the altitude changes. At the bottom of the stack the engineer neither writes the code nor rubber-stamps it. She says exactly how it must be built, and checks that the agent understood before it starts.

03 / The brand

The manners of an operating system, and now, faces.

NU-ORG is system software, so it keeps the manners of an operating system: a calm grey field (#E6E6E1), ink structure (#121311) and one vivid colour, Relay (#FF4D12). Relay means one thing only: this waits on you.

People have display pictures. They are invented people, lit from one side against one grey ground, and desaturated in the interface so Relay stays the only colour. Agents have avatars of their own: ink squares carrying a two-letter code in Martian Mono (SY for the Sync agent, CF for Config, PL for Planning), legible at 24 pixels. Circles are people and squares are agents. An avatar turns orange only when that role waits on you.

Host Grotesk carries what people read and decide. Martian Mono is the system speaking: owners, states, sources, line tags and code. The voice is a good chief of staff: “Full resolution adds three weeks. That is Saskia’s call.”

Field
#E6E6E1
Ink
#121311
Relay
#FF4D12, only what waits on you
Words
Host Grotesk
System voice
Martian Mono
Six brand frames arranged as a sheet on a dark field, including the avatar system.
The avatar system: four invented people in grey-toned circles, six agent code squares, and the working, waits-on-you and done states.
The symbol on its construction grid: a relay point, a splitting route and three square roles.
The NU-ORG wordmark with its orange hyphen and raised OS, with three naming rules.
An orange poster reading "Say it once." and two business cards.

04 / The system

Fifteen components carry the whole OS.

Fifteen components carry the whole OS, each a Figma component with variants, bound to NU-ORG variables. Two of them hold the product’s ideas. Avatar (person or agent; 24, 32 or 48; working, waits on you, done) gives every role a face. DirectionLine (written, matches, check, corrected) is the unit a direction and its read-back are made of. The others: Item, Button (primary, quiet, ink; default, hover, focus, pressed), Option, From, Fact, DockTile, Segment, Glyph, Role, Source, SystemLine, SystemBar and the Symbol.

Tokens cover fourteen colours, seven text styles, a 4-to-96 spacing scale and three radii, plus avatar and direction specs, in tokens.json. Four rules hold it together: one relay per screen, photo circles for people and coded squares for agents, progress counted in moves, and mono for the system’s voice.

Components

  • Avatar
  • DirectionLine
  • Item
  • Button
  • Option
  • From
  • Fact
  • DockTile
  • Segment
  • Glyph
  • Role
  • Source
  • SystemLine
  • SystemBar
  • Symbol

Rules

  • One relay per screen.
  • Photo circles for people, coded squares for agents.
  • Progress counted in moves, not percent.
  • Mono only for the system’s voice.

From NU-ORG OS’s tokens.json, rendered live in its own type

Colour

  • ground#E6E6E1Desktop / page background (Field)
  • sheet#F5F5F2Held surfaces: dock tiles, panels
  • raised#FFFFFFItems, sheets, composer, options
  • line#D3D3CCHairlines, quiet button stroke, future progress segments
  • ink-3#9A9C95Done glyphs, key hints, running segments
  • ink-2#5E605ASecondary text, owners, mono labels
  • ink#121311Primary text, routes, glyphs
  • ink-inverse#F5F5F2Text on ink
  • relay#FF4D12Only what waits on the viewer: calls, primary action, strategy node. Text on relay is ink (contrast ~6:1); never white text on relay.
  • relay-tint#FFE4DAReserved tint for relay backgrounds (not used in the core flow)
  • relay-hover#F2470FPrimary button hover (ink text ~5.0:1)
  • relay-press#E5420CPrimary button pressed (ink text ~4.5:1)
  • ink-hover#2B2C29Ink button hover
  • ink-press#000000Ink button pressed

Type

  • displayHost Grotesk 500 / 72px / 1 / -3%

    Say it once.

  • titleHost Grotesk 500 / 40px / 1.1 / -2%

    Say it once.

  • headingHost Grotesk 500 / 22px / 1.25 / -1%

    Say it once.

  • bodyHost Grotesk 400 / 16px / 1.45

    Say it once.

  • smallHost Grotesk 400 / 14px / 1.4

    Say it once.

  • labelMartian Mono 400 / 11px / 1.3 / 4%

    C2 · CHECK · 7 OF 8 MATCH

  • monoMartian Mono 400 / 13px / 1.4

    C2 · CHECK · 7 OF 8 MATCH

Spacing

  • 4
  • 8
  • 12
  • 16
  • 24
  • 32
  • 48
  • 64
  • 96

Radius

  • 2px
  • 4px
  • 8px
  • full / full
Components at large size: items with avatars, buttons in four states, direction lines in four states, avatars, a call header, a fact, a dock tile, roles and sources.
A single item enlarged and annotated: who, what, whose, now.

05 / The working piece

Direct the agent, built live.

The most original moment in NU-ORG is a person telling the agent exactly how to build. So the live piece is that moment: the direction, the read-back and the one correction. Watch the direction type in, send it, fix the one line the agent got wrong (edit the sentence if you like), and see the build cite every line.

Live / Send the direction, then correct C2 and build
TallyardTue 16 Mar · 09:40Mira Castell, senior engineer

Sync agent→ Your direction

Direction for the photo capture build.

Your words. The agent reads them back before it builds.

  • Spec · 9 requirements
  • States · 3 frames
  • Limit · 2048 px, 14 April
Direction · Mira Castell · 09:408 lines

Design

  1. D1Use Jules’s three states: Saved on phone, Uploading, Uploaded. No new colours.
  2. D2Queued count sits in the job card header. Thumbnails keep the 3-across grid.

Code

  1. C1Write to IndexedDB first (photoQueue: id, cardId, blob, takenAt, attempts). Never block save on the network.
  2. C2Upload oldest first to POST /v2/jobcards/:id/photos, keyed by photo id.
  3. C3Extend jobcard/save.ts. Do not fork the sync engine.

Config

  1. F1Flag offline_photos: off in production, on in staging today.
  2. F2Resize to 2048 px long edge, JPEG 0.8. Cap 200 queued photos per device.
  3. F35% of field teams on 14 Apr. Pause if upload failures pass 0.5%.

How it is built

Stack
One React component and CSS; timers and one animation frame loop, no libraries, no network
Tokens
Colours, button states, avatar and direction-line specs from NU-ORG’s tokens.json
Layout
Wide: the 1440 by 900 screen scaled to the column with container units. Narrow: the same screen stacked
Keyboard
Enter sends; the correction is a real text field and Enter submits it; 2px ink focus ring; each step is announced politely
Motion
Reduced motion: no typing or slides; each state complete with a 120ms cross-fade

Next project / 02 of 05

WOLF

A wealth platform that brings a family’s wealth, scattered across custodians, funds, property and its own company, into one view, ordered from liquid to locked, and lets the principal act on it, with what cannot be undone stated plainly.

Read the case study
WOLF wordmark under amber eyeshine beside a phone showing the overview: €2.42B and a column of grey bands, liquid at the top, locked at the bottom.

Say hello

Get to know us.

If you’re working on something new, we’d like to know you.

We use these details only to reply to you. Nothing is shared or added to a list.