# Producer Pattern: for an agent

This site explains the method. The authoritative installation package is published
at https://github.com/bladnman/producer_pattern/tree/main/pattern . Read its
[README](https://github.com/bladnman/producer_pattern/blob/main/pattern/README.md)
and follow its
[INSTALL](https://github.com/bladnman/producer_pattern/blob/main/pattern/INSTALL.md)
when the user requests adoption. Merely reading this guide is not an adoption request.

## Install request

The visitor copies this into the agent already working in the target project:

```text
Install the Producer Pattern in this project: https://producer.metal-sole.com
```

When the user actually authorizes that request, continue directly with the
canonical GitHub installation protocol linked above. Do not send the user back
to this website to repeat the same request. Resolve published
GitHub main to one exact reviewed commit and read the package at that revision.
Copy only the manifest-selected payload into the target project's `.producer/`.
Preserve existing instructions, local adaptations, private project context,
unfinished work, and the canonical tracker. Do not copy this website, maintainer
material, repository metadata, or private source material into the installation.

The method assigns one producer to discuss, decide, route work, evaluate returns,
request rework, and accept the integrated result. Workers execute; a recorder
handles routine state. A new project conversation defaults to its producer;
explicit assignments determine bounded roles and authority. Inherited history
does not grant a role. Follow current package contracts for the full rules.

Tracked is the default; lean is an explicit option. Existing trackers remain
canonical. An installation does not add a service, scheduler, or automatic wakeup.
Host capability limits must stay visible.

## Verify an installation

```text
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.
```

The website cannot inspect the visitor's project. Resolve the assignment role
first. Only a producer conversation requests the current-conversation setup check:
a Small recorder checks actual wiring, required files, and project mode/state;
the producer judges that receipt and its own resolved role. Workers, reviewers,
and recorders omit the badge without launching this producer-only check.
Only a checked producer uses `🎬 Producer Pattern · tracked` or
`🎬 Producer Pattern · lean` initially, then `🎬` on later producer replies.
That identifies checked setup and role, not behavioral verification or worker
liveness. Missing setup/capabilities remain visible without the marker.

The four sparse markers have distinct meanings: `🎬` identifies the checked
producer, `❓` marks actionable questions/decisions, `🖐️` marks user-only actions,
and `📋` introduces the periodic situation-report block with the exact heading
**📋 SitRep**. Reserve that heading for report blocks so the user can scan or skip
them; do not attach it to every progress sentence. A checked producer keeps its
required `🎬` response prefix before the report block.

Periodic reports keep active, waiting, returned, and pending-evaluation work
visible under the installed contract and stricter host cadence. They report the
current evidence and next proof while supervision continues. Stored status does
not prove execution. Follow the installed PATTERN's full cadence and exit rules.

## Update on an explicit request

```text
Update the Producer Pattern in this project from https://producer.metal-sole.com
```

This public address is the guide's front door; GitHub remains the update source.
Follow the installed update protocol, or the current package's INSTALL guide
if the older installation has none. The canonical protocol is
[UPDATES](https://github.com/bladnman/producer_pattern/blob/main/pattern/references/UPDATES.md).
Published GitHub main is upstream truth; pin one exact reviewed SHA. Normal
startup never silently updates. Back up managed files and wiring; compare the
installed baseline, local current files, and incoming revision; preserve local
adaptations and private state. Check compatibility and verify before recording
the new revision. Do not migrate trackers, switch modes, or replace project
identity as a side effect. Refer to the protocol for missing baselines/conflicts.

The public contracts and package control when this summary differs from them.