AI agent governance · Patent pending

One workstation.
Every developer, a team.

writ turns the AI assistants you already use into a governed team of agents: a builder in every project, a shared test platform for every language and an independent reviewer. Your decisions are in front of every agent on every prompt, and enforced when one is ignored.

01 · DECIDE

Your decisions, every prompt

Settled decisions restated, in your words, with every request to every agent.

02 · COORDINATE

One desk for the team

Every agent, project and assistant through one governed front door.

03 · ENFORCE

Refused, redirected, evidenced

When a decision is ignored, the action is refused, the approved way is handed back, and both are recorded.

The problem

AI agents forget what you decided.

An instruction given at the start of a session fades as the work goes on. Rules files get loaded once and left behind. Then the agent relitigates a settled decision, weakens a failing test or calls work done that isn’t.

writ doesn’t rely on the agent remembering.

~69%

of an instruction’s effect was gone after 2,048 tokens of unrelated work.

In our testing, we placed an instruction in an AI’s context, let it work on something else, then measured how much still applied.

Retained (solid) vs. lost (hatched). Controlled test on a small open model.
What writ does

A governed team, not a pile of chat windows.

1

Decisions on every prompt

Your settled decisions, restated in your words to every agent, at the workspace and machine level.

2

A record agents can’t rewrite

Decisions, open work, facts and handoffs, kept durably. Nothing edited or deleted.

3

A person approves

New tools and changes to tests wait for a person’s yes, for that exact change.

4

Refused, with the way through

A rule your organisation sets is enforced when the agent acts, with your approved alternative handed back.

ONE WORKSTATION · ONE DEVELOPERBUILDERS · ONE AGENT PER PROJECT · 6–18 AT ONCEProject Aits own agentProject Bits own agentProject Cits own agentProject Dits own agent… Project Nits own agentwrit.decisions on every prompt · the record · one desk · enforcementTest platform · Luashared by every Lua projectTest platform · Goshared by every Go projectIndependent reviewerwrites findings, never edits codeSHARED TEST PLATFORMS · ONE PER LANGUAGEINDEPENDENT REVIEW
The team on one workstation

Each developer now runs an engineering team.

A builder in every project. A shared test platform for each language. An independent reviewer that never edits code. writ keeps them on your decisions, routes requests between them, and wakes the one that owes the work.

In our own daily use: 6–18 agents at once on one workstation, across a live ~30-project estate.

Meet the team
Who it’s for

From one developer to the whole organisation.

A single developer

Run a team, not a chat window.

Agents across every project that keep to your decisions, wake each other when work arrives and pick up where they left off.

A team of developers

The same decisions everywhere.

Shared conventions in front of every agent, a reviewer that isn’t the author, and tests that can’t be argued away.

The organisation · with Canon

One approved policy, proven.

Security, platform and compliance teams publish policy to every seat and see where it’s enforced, with evidence for audit.

Works with what you use

Governs the assistants you already license.

writ is not another coding agent. It sits in front of the ones your developers already use, in the editors they already use.

Claude CodeDevinGitHub CopilotVS CodeJetBrains IDEsSplunk
Proven in production

Built under real load.

6–18 agentsat once on one workstation, daily
~30 projectsa live software estate
Local firstnothing sent to Verilex
Patent pendingprovisional application on file

Figures are from Verilex’s own daily use, not a customer result.

See a team at work, and a refusal.

A live demo on your own workflow. Technical deep dive available under NDA.

Book a demoDownload the brochure