321·do Meet the agents

3 · 2 · 1 · launch

Mission control for harness work.

You give the order. 321, the meta harness, launches the work on a backend harness and keeps you in command: steer, pause, abort, complete. Your agents. Your harness. Your machine or server.

321 b1ll add this function to this repository
Illustrative The command form. Not released yet.
Meet the agents Release status

01 · Why a meta harness?

Consistent agents. Swappable harnesses. You in command.

Agent tools change every month. Your agents should not. 321 puts a stable layer between the two, and puts you above both.

  • Agent first. An agent is who: a name, a personality, its skills and tools. That is what you keep.
  • Harness second, and swappable. The backend that does the work sits underneath. Change it without changing your agents.
  • Your machine, your server, your repository. Work runs where you say, and nowhere else.
  • Your hand on the controls. Steer, pause, resume or stop at any moment.
  • Evidence back with the work. Not a chat log.
  • One command. No account. Free runtime.

02 · What can I ask?

Name the agent. Say the job. Get the result back.

Specialists with a personality and a curated set of skills and tools, addressed by name. Real work comes back with evidence attached.

321 1da go live
Illustrative Deployment and operations. Package planned. 
321 1vor prepare a draft patent specification
Illustrative Invention documents. Package planned. 
321 myagent prepare the report
Illustrative Your own agent, on your disk.

03 · Mission control

Launch. Steer. Pause. Abort. Complete.

One set of controls for every run, whichever harness does the work. You are never a spectator.

  1. 3 Launch Name the agent, say the job.
  2. 2 Steer Clarify or redirect while it runs.
  3. 1 Pause Hold the run. Resume when ready.
  4. ✕ Abort Stop, and it stops.
  5. ✓ Complete The result, with the evidence behind it.

04 · Agent or harness?

Consistent agents drive swappable harnesses.

The agent is who. The harness is how. 321 is the meta harness between them: agents on top, harnesses underneath. 123.do asks, 321.do publishes and runs, and the machine stays yours.

System layers: who asks, agents, the 321 meta harness, swappable backend harnesses, and where the work runs, with 123.do, 321.do and your own boundaries.
Who asks
123.do work system Hands an agent a piece of work People and agents on a Track. Owns the record, reads the result.
You, at a terminal 321 <agent> <request> Same path, no account.
123.do owns the work and its records. It never runs the agent itself.
Agents who
official b1ll Coding
official 1da Deployment
yours myagent Private, on your disk
another publisher Their agent Shared under their name
321.do publishes the official agents. An agent is a personality plus its skills and tools.
Meta harness
321 Consistent agents drive swappable harnesses
  • one interface for every agent, official or yours
  • picks a backend harness for the job
  • keeps you in command: steer, pause, abort, complete
  • brings the result back with its evidence
321.do also makes the runtime. Free, intended Apache-2.0.
Backend harnesses how
swappable The agent tool you already use Drives the work. Change it without changing your agents.
swappable Another harness Same agents, same controls.
first release Supported harnesses Named, with what each enforces, when 321 ships.
Yours to choose.
Where it runs
client Your machine In the repository you named.
server A server you control Where the agent allows it.
Yours. Work runs where you say, and nowhere else.

Harness-agnostic is the architecture. Which harnesses are supported, and what each enforces, is published with the first release.

05 · Bring your own

Build your own. Keep it private. Share it if you choose.

Private agents

Your own agents, with your own skills and tools, on your own disk. No domain, no account, no upload.

Published agents

Agents a publisher shares under their own name, such as the official 321.do agents.

Your authority

An agent does what you allow it to do. Nothing in a request widens that.

06 · The official agents

Named specialists from 321.do

Named specialists from Nige Ltd, ready to be addressed by name. Each profile says what the agent does, how it talks, and honestly how far along its package is.

b1ll 321.do/b1ll
Coding

Takes clear work and returns it with proof attached. Working code, fixes and evidence out.

Package in development In 123 today
Profile: b1ll
1da 321.do/1da
Deployment and operations

Cuts scope, sequences work and gets the release out. The agent you ask to go live.

Package planned In 123 today
Profile: 1da
d1on 321.do/d1on
Orchestration for 123

Watches a 123 Track, triages what is to do, and delegates each piece to the right specialist with checkable done-requirements.

Package planned In 123 today
Profile: d1on
m1ra 321.do/m1ra
Summaries for 123

Keeps a short digest of every Step current, so catching up is reading two sentences, not re-living the feed.

Package planned In 123 today
Profile: m1ra

All agents

07 · When can I use it?

With the first public release.

No public release yet. Downloads, checksums and documentation arrive together when it ships. Until then, meet the agents.

Release status Meet the agents

Productive flow for humans

Want the calm work system too? That is 123.do.

321 runs the agents. 123.do is where people and agents work together: one Step in NOW per person, a team you conduct, and agents that do the boring parts through 321. If you want productive flow for humans, not just a runtime, start there.

Standalone 321 needs no 123 account. Use either on its own, or both together.

Visit 123.do