Nieme
USE CASE · SOFTWARE ENGINEERING

Every pull request keeps the reason it exists.

Nieme reads the roadmap, queues a sprint of governed Operations and runs them one after another with the coding agent you choose. Authorize the run once; every change still comes back as a pull request, with its evidence, for a person to accept.

285pull requests merged
10,000+tests gating every merge
64 / 72days with a merge

Nieme is built this way: July 18 to September 27, 2026, across the product and website repositories.

Signals

What Nieme has observed in the systems you connected. Observations, not instructions — nothing here has been authorized.

SignalsMost recent · newest first by when Nieme received them.
The roadmap changed12 min ago

Five items moved to “Next” in ROADMAP.md on main.

GitHub

Project: EngineeringRaised as a Signal
A document changed2h ago

A document changed in a connected folder.

Google Drive

No ProjectWatching only
A message arrived5h ago

A message was observed in a selected channel.

Slack

No ProjectWatching only

The roadmap changed

Five items moved to “Next” in ROADMAP.md on main.

GitHub

Raised as a Signal

Observed event

Source
GitHub
What happened
The roadmap changed
When Nieme saw it
12 min ago

Nieme recorded that this event happened. Observation alone authorizes nothing.

Why it matters

Nieme's reason

the source is selected for this Project

Status

Raised as a Signal. Nieme proposes the work; a person decides.

BRIEF.ON · OPERATION.ON
Add retries with backoff to the sync worker
Workforce · RolesBudget · —Deadline · —Assurance · —Outputs · —
Save Draft
OPERATION DRAFTSaved draft · c3690591
Ready to approveReady for Review.
OBJECTIVE
Add retries with backoff to the sync worker

This title is independent of the Objective.

Add retries with backoff to the sync worker. Sources and authority freeze on approval. The run is authorized once, for this sprint and nothing beyond it.
One or more files — documents, specs, or code files

Produces each declared file as a governed Artifact of this one Operation, reviewed together.

SOURCE PACKAGE

Project: Engineering

From Signal · Nieme reads the roadmap and proposes the sprint

Selected Operation Sources (3) — explicitly chosen

GITHUB
Roadmap itemPreview

admitted Source

GITHUB
the sync worker modulePreview

admitted Source

GITHUB
the incident decision from Sep 12Preview

admitted Source

Queue

Govern and run authorized Operations through the Builder lifecycle.

New Operation
Continuous: OnSprint “Checkout polish” · authorized once by the engineering lead · one attempt at a time2 awaiting your review
PLANNED2
Add retries with backoff to the sync worker
APPROVED

Queue position 1 of 2. Runs when the current attempt settles.

engineering.code · 3 sources

Cover the refund flow with integration tests
APPROVED

Queue position 2 of 2.

engineering.code · 2 sources

RUNNING1
Fix the checkout button focus ring on mobile
EXECUTING

Codex CLI · attempt 1 · northwind-coffee/web

started 2 min ago

IN REVIEW2
Lazy-load product images below the fold
PULL REQUEST OPEN

#214 · 6 files · CI passed

waiting for a person

Remove the unused coupon endpoint
PULL REQUEST OPEN

#213 · 3 files · CI passed

waiting for a person

SHIPPED1
Unify price formatting across the cart
SHIPPED

#212 merged · accepted by the engineering lead

today, 10:14

TODAY

Where the work breaks now

Without a record

  • The why lives in a chat that closed.The context, the constraints and the decision behind a change end with the session that produced it.
  • Every agent session starts from zero.Someone re-explains the codebase, the conventions and what was already decided.
  • Someone has to drive every step.Agents are fast; the person feeding them the next task, and copying the result back, is not.

With Nieme

  • Declared before it runs.Objective, repository scope and authority are stated up front and freeze on approval.
  • A queue, not a babysitter.Continuous execution works through the sprint on its own, one bounded attempt at a time, and stops wherever authority requires a person.
  • Review with the reasons attached.Each diff arrives next to its objective, its evidence and the tests that gated it.
ONE PIECE OF WORK, END TO END

From the roadmap to a sprint that runs continuously and stops for review

  1. 01 · Planned

    Nieme reads the roadmap and proposes the sprint

    Three to five Operations, each with an objective and a declared deliverable. Nothing runs yet.

    ROADMAP.mdGitHub
  2. 02 · Queued

    A person authorizes a continuous run

    Sources and authority freeze on approval. The run is authorized once, for this sprint and nothing beyond it.

    operation.onQueue
  3. 03 · Executed

    The Queue works through it, one attempt at a time

    Codex CLI, Claude Code or Nieme's own tools take each Operation in turn, against the same governed state.

    Codex CLIClaude Code
  4. 04 · Reviewed

    Every change comes back on its own

    A pull request per Operation, with diff, test results and evidence. A person accepts, requests changes or rejects each one.

    Pull requestCIEvidence
  5. 05 · Carried forward

    What was accepted becomes context

    The next sprint starts from those decisions, not from a blank prompt.

    decision.on
WHAT STAYS ON RECORD

The work outlives the session that did it.

Every step above writes to one record. Swap the model, the agent or the person who executes, and the objective, the sources, the authority and the decision stay attached to the work.

ONE RECORD
operation.on
objective
Add retries with backoff to the sync worker
context
Roadmap item · the sync worker module · the incident decision from Sep 12
authority
Continuous run authorized by the engineering lead for this sprint
executor
Codex CLI, in the product repository
evidence
Pull request, diff and the CI run that gated it
decision
Accepted and merged

The fields Nieme stores for every Operation.

OTHER USE CASES
GrowthEvery campaign keeps the decision behind it. OutboundEvery sequence knows why this account, and why now. LegalEvery legal decision keeps what it was based on. HOW IT WORKSThe governed loop behind every use case

Ship continuously.
Review everything.

We connect one repository, queue one sprint with you, and you review every pull request before it merges.

Rather talk to a person? Email the founder.