arka.norn · AI software delivery

Have AI agents produce software without losing control.

Norn turns your intent into a living plan, then that plan into local, bounded, traceable delivery.

You can continue with your usual agent or let Norn orchestrate execution. Either way, the repository, the decisions and the evidence stay under your control.

Install Norn See how it works
Chat is not enough

Your agents code fast.
The real problem starts after.

Sessions session 1session 2
Session 1 · Claudeclosed
context 0%
Je vais auditer les accès prestataires.
DécisionOn gèle le périmètre des accès prestataires.
ok, tu peux lancer le refactor
Refactor du module d'auth en cours…
12 fichiers modifiés, 3 tests rouges
corrige les tests avant de continuer
Correction du test d'intégration
Ajout du cache de session
renomme aussi les variables d'env
Renommage des variables d'env
Migration du schéma appliquée
et les imports ?
Nettoyage des imports terminé
Broker d'effets : première passe
attention au scope d'écriture
Scope d'écriture restreint à auth/**
Tests de scope : 14 passés
tu peux documenter le broker ?
Documentation du broker rédigée
Ajout des règles allow/deny
les worktrees sont isolés ?
Un worktree par tâche, vérifié
Intégration : aucun conflit
ajoute un test de non-régression
Test de non-régression ajouté
CI verte sur les trois lots
et le rollout ?
Rollout préparé en deux vagues
Première vague appliquée
on s'arrête là pour aujourd'hui
Fenêtre de contexte saturée.
Session 2 · Codexempty context
reprends le chantier des accès
Je découvre le dépôt. Aucun contexte antérieur.
Le SSO semble couvrir tous les comptes.
on avait décidé quoi pour les externes ?
Je n'ai pas cette décision.
a closed session is not a memory not found

When several agents step in, it becomes hard to know:

  • ?who decided what
  • ?what was actually validated
  • ?why the code changed
  • ?what can be applied without risk

Norn takes the project out of chat. The plan becomes the source of resumption and governance.

From need to delivery

Frame.
Plan.
Deliver.

You start from the expected outcome. Norn builds a living plan, stabilises it, then turns it into delivery — by you or by a team of bounded agents.

1Frame 2Plan 3Produce 4Deliver
Delivery planframing
Expected outcomecontractor access under control Decisionscope frozen Evidenceauth/scope.rs:142 Constraintno API break Openexternals outside SSO?
repository read and confronted with the need
Delivery planplanifié · dc41f0

Externals outside the SSO scopesettled

signed decomposition into bounded lots
Production mode manual assisted

Norn prepares the context and prompts. You execute with your agent. The lead agent orchestrates execution agents: one lot per agent, each bounded to its scope and worktree.

Lead agentit splits, delegates, reviews L1agent 1evidence L2agent 2evidence L3agent 3evidence L4agent 4evidence
Deliverywhichever the mode
Code applied4 lots · auth/** Evidence attachedtests, diffs, logs Plan up to datedc41f0 → e7a2b1 Resumption possibleby any engine
Continuity

Resume the project at the right place, even with another agent.

Claude
plan e7a2b1
  • L1write scope
  • L2access migration
  • L3account review
session interrupted
the conversation is not transferred
Resumption package
  • Problemcontractor access not covered
  • Decisionsscope frozen · phased rollout
  • Evidenceauth/scope.rs:142 · 42 tickets
  • Constraintsno API break
  • Openorphan account status
  • Resume atL2 · access migration
the plan state · not the history
Codex
plan e7a2b1
  • L1write scope
  • L2access migrationresumes here
  • L3account review
same plan · another engine
Agents propose. Norn bounds.

Nothing important is applied because a model decided so.

Agent output

“The agent is done.”

+184 −37 · 6 files
Norn verification
  • the plan used
  • each task's scope
  • the execution profile
  • dependencies
  • the evidence produced
  • the repository state
  • the risk before applying
Human authority

Apply to the repository?

ApplySend back
irreversible actions stay under human authority
Several agents, one trajectory

Norn does not ask agents to behave.
It limits what they can do.

An agent does not freely obtain shell, Git, network or commit access because its reasoning calls for it.

Planned plandc41f0 · 3 lots
L1Backend writesauth/scope.rs worktree/L1
L2Broker writescore/broker.rs worktree/L2
L3Tests writestests/scope/** worktree/L3
Effects gathered 3 lots · one single passage no direct repository access
Norn broker every effect passes here · Norn creates the commits · integration respects the DAG
shellgitréseaucommit
c1auth/scope.rs c2core/broker.rs c3tests/scope
You choose the level of autonomy

Start light. Automate when the framework is ready.

Norn prepares everything. Nothing leaves without your action.

Norn sends within the budget and rules you have set.

The delivery does not change. Only the trigger does.
Ready to send budget your turn to send
L1write scope review
L2contractor access migration
L3account deletion
L4compliance report
out of scope · your veto

Autonomy is never a condition for using the product.

No plan disconnected from the code

Norn confronts intent with what actually exists.

When a repository is already implemented, Norn starts by observing it before confronting that reality with the request.

  • →Important technical claims stay linked to file:line evidence and to the observed repository state.
  • →If the repository changes between stabilisation and planning, Norn refuses to plan as if nothing had happened.
Plan claim

SSO covers contractor access.

auth/scope.rs 140fn resolve_scope(id: &UserId) 142if user.is_external() { return Scope::None } 143sso_scope(user).unwrap_or_default()
Confronted with the repository the claim does not hold · externals out of scope auth/scope.rs:142
Every step leaves a trace

You can explain how the delivery was produced.

Norn keeps fingerprint-signed documents and append-only governance. Decisions, fixes, risks and debts are not rewritten afterwards.

GOV-014Decisionaccess scope frozena41c…
GOV-021Riskorphan accounts untreated7b0e…rewrite refused
GOV-038Debtscope resolved at runtimec2f9…
GOV-052Resolutionresolves GOV-021 · new evente18a…linked, not rewritten

You keep an auditable trajectory from the need to the application.

Your repository is not a SaaS by-product

Control stays local.

Norn is designed as a local, auditable control plane.

Your machine
norndurable state
no remote source of truth no telemetry credentials referenced, not stored Web exposed on loopback only no repository handed to a SaaS
bounded context1,2 ko External model what leaves is bounded and chosen
The same product, to match how you work

Web, terminal or automation.

Web

Cockpit to frame, follow, authorise and audit without living in commands.

TUI

Terminal cockpit for expert users.

CLI

Complete surface for automation and advanced workflows.

All three use the same capabilities and the same use cases.

Built for those who actually have agents produce code

When the problem is no longer generating code, but mastering its delivery.

Norn is for people already using Claude Code, Codex or other agents to work on real repositories.

Tech lead Product engineer Technical PM
  • →delegate more without losing the evidence
  • →frame before launching
  • →parallelise without letting agents step on each other
  • →resume with another agent
  • →keep human authority over what actually enters the repository
Not one more agent

Norn does not try to replace your favourite model.
It sits around their work.

a new IDE a development SaaS a chat an autonomous agent with free repository access an orchestrator maximising autonomy for its own sake

It is the layer that turns agentic work into governed delivery.

arka.norn

Give your agents more work.
Not more freedom than needed.

Install Norn, open your repository and start from the outcome you want.

The plan keeps the trajectory. The agents do the work. You keep the authority.
Install Norn Read the documentation