MeshAgentDesignerBuilt on MeshboneIn development

The designer for every starter pack

Shape the starter pack to the way your organisation works.Watch the work, draw the change, or configure it by hand. The guardrails stay where they are.

Every Industry Agent starts as a standard pack: a catalogue of services, each with its agents, its decision gates and its evidence records, identical for every customer. MeshAgentDesigner turns that pack into yours. It can watch how your people do the work today and propose the changes, read the process you drew in Lucidchart or another drawing tool, or take the changes you configure by hand. Every change is versioned, held for a named owner where it carries weight, and reported in the three columns every build is measured in.

For any organisation adopting an Industry Agent Starter Pack, and the operations, process and architecture teams who own how the work is done.

Talk to us about the designer The three ways in How it modifies a pack

In development

What exists today, and what does not

The drawing-to-agents step exists as an internal prototype: a BPMN canvas inside Nanolitte that compiles every drawn task into an agent and every arrow into a link, with each person-step becoming a hold for approval. It has not been released to a customer. Watching the work, the Lucidchart connection, the comparison against a starter pack, the three-column report and the versioned variant are specified and not built. Nothing runs for a customer. When the first part is released we will say which, and until then the status on this page stays as it is.

Three ways in

Watch the work. Draw the change. Configure by hand.

Three ways to the same result: a proposed version of the pack, shown against the standard one, held for the person who owns the service. Use one or all three.

Way 1

Watch the work

The designer observes, with notice and consent, and proposes the change.

With written notice to the people involved and their recorded consent, the designer watches the applications a team already uses while they do the work: the steps taken, the systems opened, the hand-offs, the waits and the exceptions. It does not read keystrokes, screen contents or message text, and the record it keeps is of the process, not the person. From what it sees it drafts a change to the pack as a drawing you can read beside the standard one: a step your people take that the pack does not, a step the pack has that nobody takes, a hand-off that happens in a different order.

Who decides

Each proposed change is held for the owner of the service to approve. Where the organisation has set a delegation for changes that carry no legal, financial, safety or regulatory weight, the change is applied under that delegation and the record is kept. Outside it, a person decides, every time.

Way 2

Draw the change

Draw the process in the tool you already use. The designer reads it as a process.

Each box becomes a step, each step a task for an agent or a decision for a person, each arrow a hand-off, each diamond a rule. The designer lays your drawing over the starter pack and shows the difference. Lucidchart first: the designer reads a Lucidchart document through Lucid's REST API with the read-only access you grant it, and sends the pack's own drawing back into Lucidchart as a document you can edit, so the round trip stays in the tool you know. Microsoft Visio, draw.io and any tool that writes BPMN 2.0 are read as files.

Who decides

A drawing that removes a decision gate, a delegation check or an evidence record is refused with the reason, whoever drew it. Everything else becomes a proposed version of the pack, held for the owner to approve.

Way 3

Configure by hand

Open the pack and change it, one setting at a time.

The thresholds, the wording of a letter, the order of steps, who approves what and up to what limit, which data an agent may read, which model drafts. Every setting is a field with a plain-language description of what it does and which of the three columns it lands in: standard, configured or coded. Where a change needs code, the designer says so before anyone commits, and the fixed-scope build carries it.

Who decides

Settings with legal, financial, safety or regulatory effect are held for the named owner who holds the delegation, like every other decision that carries weight. Agents prepare. People decide.

How it modifies the base packs

From the starter pack to your pack, and back to the template

Every Industry Agent Starter Pack is identical for every customer. The designer is how it becomes one organisation's own, without touching the rails or the guardrails.

1
The starter pack
MeshGov, MeshFin, or a package once its catalogue is published: a service catalogue with a page per service, each naming its agents, the gates where a person decides, the records it keeps and the standards it is mapped to. The same for every customer, and its assurance reused.
2
The designer
Watch the work, draw the change, or configure by hand. The designer produces a proposed version of the pack and shows the difference against the standard one: which steps changed, which gates each change touches, and which column it lands in: standard, configured or coded.
3
Your pack
A versioned variant of the starter pack, running on the same rails with the same guardrails. It goes live on Meshbone when the owner approves. Every version is kept on the evidence chain, with who proposed it, who approved it and why, and any version can be restored.
4
Back to the template
Anything a second organisation could use goes back into the starter pack as an option, so the pack improves with every customer. Anything particular to you stays yours. That is how the custom share is kept small by design, and measured on every build.

The ruleThe designer changes the pack. It never changes the rails, and it never draws a guardrail out.

The drawing tools

Design in the tool you already use

The designer keeps every pack as a BPMN 2.0 process, the Object Management Group's standard for business process diagrams, so any tool that reads or writes it can be the place you design. Lucidchart is first because it is the tool most of our buyers draw in.

Lucidchart
Read through Lucid's REST API with read-only access you grant; the pack's drawing sent back into Lucidchart through Lucid's Standard Import, as a document you can edit.
Microsoft Visio
Read as a Visio file (.vsdx).
draw.io
Read as a draw.io file (.drawio).
Any BPMN 2.0 tool
Read and written as BPMN 2.0 XML (.bpmn), the form the designer keeps every pack in.
The designer's own canvas
A BPMN canvas inside the designer, for organisations that do not draw elsewhere.

Lucidchart and Lucid are trademarks of Lucid Software Inc.; Visio is a trademark of Microsoft Corporation; draw.io is a product of JGraph Ltd; BPMN is a trademark of the Object Management Group. Arrochar Labs is not a partner of any of them and none has reviewed anything here. The Lucidchart connection uses Lucid's published REST API under the access a customer grants to its own documents.

What it cannot change

The layers the designer refuses to draw out

Whoever proposes the change and however it arrives, these stay. A refusal is recorded with its reason, like every other event.

The decision gates
No change removes a hold where a person decides. A step with legal, financial, safety or regulatory effect keeps its gate.
The delegations
Who may approve what, and up to what limit, changes only by the people who hold the delegation to change it, never by a drawing.
The evidence chain
Every version of the pack, every proposal, approval and refusal, is written to the same tamper-evident chain as the work itself.
The agentVIKING™ controls
No change takes an agent outside its charter, its data or its tools. The rogue-agent controls run on every version of every pack.
The rails
AIG Sentinel and Meshbone are the same for every customer. The designer changes the pack. It never changes the rails.

The baseline

The standards we expect to work to

BPMN 2.0 (also published as ISO/IEC 19510) for the process itself. Lucid's published REST API and Standard Import for the Lucidchart round trip, and the Visio and draw.io file formats as their owners publish them. For watching the work, the workplace surveillance and privacy law of the place where the people work, with written notice before observation starts in the period that law requires, the policy on record, consent recorded on the evidence chain, and the people observed able to see what was recorded about their work. None of this is final until the designer is released, and the page will say so when it is.

How it fits together

A complete suite of AI governance agents. An architecture that makes them accountable.

Each part of ASG™ does one job, in order, and hands the next part something it can check. That is the difference between building AI agents and running them so an auditor, a regulator or a minister can see what happened.

Before the first build, Orbit Roadmaps finds where AI creates value and profiles the risk.

After it, Execdive turns what the chain recorded into plain-language insight for executives.

Policy, enforcement, templates, data, controls, evidence. Then services.

This describes the architecture, not what every deployment runs today: 5 of the 27 agentVIKING™ controls are still in development.

Industry Agent Starter Packs

The starter packs it shapes

MeshGov

Demonstration running

All Industry Agent Starter Packs

Bring us the drawing

If you have a Lucidchart diagram of how your operations run today, or a team willing to be watched for a fortnight, you have what the first design needs. Talk to us.

Talk to us about the designer

Shape the starter pack to the way your organisation works.Watch the work, draw the change, or configure it by hand. The guardrails stay where they are.

What exists today, and what does not

Watch the work. Draw the change. Configure by hand.

Watch the work

Draw the change

Configure by hand

From the starter pack to your pack, and back to the template

The starter pack

The designer

Your pack

Back to the template

Design in the tool you already use

The layers the designer refuses to draw out

The standards we expect to work to

A complete suite of AI governance agents. An architecture that makes them accountable.

The starter packs it shapes

Bring us the drawing