A way to work with your agent
One conversation.
The whole outcome.
Give your project a producer who stays with you, coordinates the work, and checks what comes back.
You discuss the goal. Your producer handles the moving parts: deciding what needs doing, assigning workers, evaluating their returns, and bringing the result together.
Start with one requestFirst candidate · Evolving in public
Build, research,
and run checks.
Preserves requests,
decisions, and state.
Returns come back to the producer
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 Producer Pattern in this project: https://producer.metal-sole.comYour agent reads the installation guide, checks its supported capabilities, and sets up the pattern in this project. 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 producer stays responsible for the integrated result. A worker’s return is something to evaluate; the producer decides whether it meets the request or needs another pass.
“Add a settings page,
update the guide,
and check it on a phone.”
- 01Make each outcome visible
The page, the guide, and the phone check each have a clear owner and acceptance criteria.
- 02Assign the work, keep the context
Workers execute bounded assignments. The recorder preserves the original request, later steering, and current state.
- 03Judge the whole result
The producer checks evidence, requests fixes, 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.
Clear assignments.
No forced org chart.
A new project conversation defaults to its producer. An explicit assignment sets the role and scope; inherited history does not. Workers execute, the producer judges, and the recorder handles routine state.
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.
🎬 Producer Pattern · trackedOr lean, for that mode. Later producer replies begin with 🎬.
The marker identifies a checked setup and the conversation’s producer role. It does not certify behavior or tell you whether workers are currently running.
Ask your project agent
Verify the Producer Pattern installation in this project. Check the loaded startup wiring, required files, configured mode, 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 producer has checked its setup and role.
- 📋
- A periodic situation-report block, easy to scan or skip.
📋 SitRep
Periodic reports keep active, waiting, returned, and pending-evaluation work visible while the producer supervises. They report the current situation and next proof; a saved status alone does not prove activity. The heading is reserved for periodic report blocks. Ordinary progress sentences do not need it, and the checked producer 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. A tracker migration is a separate decision.
Read the update protocolAsk the agent in
your existing project.
Manual update request
Update the Producer Pattern in this project from https://producer.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.