A way to work with your agent
One conversation.
The whole outcome.
Give your project a Director who stays with you, hands each outcome to an accountable manager, and checks what comes back.
You discuss the goal. Your Director keeps the conversation and the list of unfinished commitments, entrusts each complete outcome to one Request Manager, and accepts the result. The manager plans the work, assigns specialists, and evaluates what they return.
Start with one requestFirst candidate · Evolving in public
One per outcome. Directs specialists to build, research, and check.
Shared. Preserves requests, decisions, and state.
Specialists return to their manager;
the manager returns to the Director
for judgment, rework, and acceptance.
Start here
Give this to your agent.
Paste it into the conversation with the agent already working in your project.
Install request · Copy, then paste into your project agent
Install the Director Pattern in this project: https://director.metal-sole.comYour agent reads the installation guide, checks its supported capabilities, and sets up the pattern in this project. It maps what staffing needs, such as your role index, the host’s model and effort options, a recorder route, and an identity roster, and leaves any gap visible. Existing instructions, project context, and your canonical tracker are preserved. The guide points to the canonical GitHub package. For an agent: read the setup guide
How the work moves
Many pieces.
One accountable conversation.
The Director stays accountable to you. Each complete outcome has one Request Manager, who evaluates what specialists return and submits an integrated result. That submission is something to review, not automatic acceptance: the Director decides whether it meets the request or needs another pass.
“Add a settings page,
update the guide,
and check it on a phone.”
- 01One outcome, one owner
The page, the guide, and the phone check are parts of one finishable result, so one manager owns all of it and its completion obligations from the start. Separate managers are for outcomes you can accept independently.
- 02Assign the work, keep the context
The manager picks the project’s matching roles and gives specialists bounded assignments. The recorder preserves the original request, later steering, and current state.
- 03Judge the whole result
The manager checks returns and orders rework; the Director reviews the integrated result and accounts for anything still waiting. Passing a build and checking a real phone are separate claims.
Tracked by default.
Lean when you choose.
New installations retain requests and unfinished work by default. Lean is an explicit option with a smaller retention promise. An existing tracker stays canonical. Files keep continuity; they install no runtime and cannot keep an agent running.
Clear assignments.
No forced org chart.
A new project conversation defaults to its Director. An explicit assignment sets the role and scope; inherited history does not. A small outcome can go straight to a worker. Staffing uses your project’s role index and model options, so matching specialist rules apply instead of generic helpers.
After setup
Know what’s
actually installed.
This website cannot inspect your project. Ask the agent in that project to check the installation, its startup wiring, mode, and pinned source revision.
🎬 Director Pattern · trackedOr lean, for that mode. Later Director replies begin with 🎬. Managers and other actors use an assigned name, such as 🐙 Contract —, never the badge.
The marker identifies a checked setup and the conversation’s project Director role. It does not certify behavior or tell you whether managers or workers are currently running.
Ask your project agent
Verify the Director Pattern installation in this project. Check the loaded startup wiring, required files, configured mode, role index, Recorder route, and pinned source revision. Report any gaps and distinguish setup from current worker activity.A few signals to watch for
- ❓
- A question or decision needs your answer.
- 🖐️
- An action needs you, such as authentication or a physical check.
- 🎬
- The conversation’s Director has checked its setup and role.
- 📋
- A periodic situation-report block, easy to scan or skip.
📋 SitRep
Use a periodic overview after a quiet stretch of ongoing work or when several developments need a combined view. Ordinary replies and brief progress do not need a full SitRep; meaningful updates already satisfy the cadence. Communicate meaningful changes promptly, keep silence under five minutes, and respect stricter host timing with concise updates. Reports keep held work and next proof visible while supervision continues; saved status alone does not prove activity. The checked Director keeps its 🎬 response prefix.
Keep it current, deliberately
Update when
you ask.
Installations do not silently update at startup. Published GitHub main is the upstream source of truth; your agent resolves a reviewed revision to an exact commit.
The update protocol backs up managed files, compares changes, preserves local adaptations and private state, and records the new revision after verification. Your role index, model mapping, and identity roster belong to your project and are not replaced. A tracker migration is a separate decision.
Read the update protocolAsk the agent in
your existing project.
Manual update request
Update the Director Pattern in this project from https://director.metal-sole.comThe website’s guide points your agent to GitHub. Use the installed update protocol; older installations can start from the current package’s installation guide.
The method is the source
Small enough to read.
Explicit enough to inspect.
This is a first candidate, with public contracts and a living rationale. Source files, local installation, behavioral verification, and publication are separate steps.