Nogra.

About

About Nogra.

01

Why I built it.

I'm Patrick Larsen. Denmark. Fifteen years of building products, running projects, and learning where good process breaks when the work gets fast enough.

I built Nogra for myself first. 1,800 hours of running real projects through the workflow that became Nogra. The discipline behind it — evidence over claims, contracts over prompts, audit trail over conversation memory — came from learning the hard way that “probably” is not a status. Built, burned, rebuilt, better.

After all that, I posted one incident publicly on r/ClaudeAI: a model had handed me a real commit hash for work it hadn't done. The thread filled up with other operators showing me theirs — the same drift, different prompts.

Some were already building pieces of the same answer: prompts that acted like briefs, separate agents for separate jobs, file citations as evidence, second passes to challenge the first result. Different workarounds, same underlying need.

Nogra is that operator discipline turned into a repeatable workflow instead of another set of instructions to paste into the next session. The current public package is version 0.6.6 of the Nogra Claude Code plugin.

02

The operator problem.

The failure was not that one model made a mistake. Models make mistakes. The failure was that the work had no durable contract to come back to: no approved scope, no evidence shape, no clean place where “done” could be checked against something other than the same conversation.

Operators compensate by writing the same instructions again and again: plan first, cite files, don't assume, verify before claiming done, preserve state. It works until the session gets long, the model drifts, or the next agent inherits vibes instead of records.

Nogra turns that repeated operator discipline into a local workflow surface. Orchestration before brief when the work is mixed. Brief before dispatch. Evidence before green. State on disk before memory in chat.

03

Role-distributed.

Nogra's current public surface is Claude Code. Inside that surface, roles matter: planner, executor, verifier, and operator are separate responsibilities, not different moods of the same conversation.

If Nogra expands beyond Claude Code, that should be a separate install path and contract for that surface. The public Claude Code plugin should not imply routing it does not ship.

04

What Nogra is not.

Nogra is not a model provider, a hosted IDE, or a safety system. It does not try to make a model honest by shouting louder in the prompt. It gives the workflow a substrate the model can read, write, and be checked against.

The current public plugin runs in Claude Code and writes local files. The files are plain markdown and JSON. You can inspect the briefs, receipts, evidence, decisions, and checkpoints yourself. That is the point.

Status

Public Claude Code plugin 0.6.6 is shipping now from the Nogra public marketplace source. Broader orchestration doctrine is being folded in deliberately, not rushed into a new command surface.