# Director Pattern: for an agent This site explains the method. The authoritative installation package is published at https://github.com/bladnman/director_pattern/tree/main/pattern . Read its [README](https://github.com/bladnman/director_pattern/blob/main/pattern/README.md) and follow its [INSTALL](https://github.com/bladnman/director_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 Director Pattern in this project: https://director.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 `.director/`. 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 gives the project a Director who discusses, decides, keeps unfinished commitments, and accepts each outcome. The Director entrusts each complete outcome to one Request Manager, who owns its planning, specialist tasks, evaluation, rework, and follow-up; a specialty is a task within the outcome, not a reason for another manager. Specialists execute, and one shared recorder handles routine state. The Director may dispatch substantial independent analysis that returns a proposal; no intake layer is mandatory. Assignment roles are only `worker` and `director`; Request Manager and Recorder are maintained responsibilities, not new role values. A new project conversation defaults to its Director; explicit assignments determine bounded roles and authority. Inherited history does not grant a role. Follow current package contracts for the full rules. Adoption also maps what staffing needs, in the project's PROJECT context: a canonical role index (reuse existing maintained roles and guardrails), the host's model and effort mapping, the recorder route and state location, and the identity roster location. A missing mapping stays a visible gap; do not invent generic specialists to fill it. Tracked is the default; lean is an explicit option. Existing trackers remain canonical. An installation does not add a service, scheduler, runtime, or automatic wakeup, and promises no live agents. Host capability limits must stay visible. ## Verify an installation ```text 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. ``` The website cannot inspect the visitor's project. Resolve the assignment role first. Only the project Director requests the current-conversation setup check: a Small recorder checks actual wiring, required files, project mode/state, and whether PROJECT names the role index, model mapping, recorder route, and identity roster location; the Director judges that receipt and its own resolved role. Request Managers receive the checked facts in their assignment, and workers, reviewers, and recorders omit the badge without launching this Director-only check. Only a checked project Director uses `๐ŸŽฌ Director Pattern ยท tracked` or `๐ŸŽฌ Director Pattern ยท lean` initially, then `๐ŸŽฌ` on later Director replies. Managers and other actors use an assigned identity such as `๐Ÿ™ Contract โ€”`, never the badge. The badge identifies checked setup and role, not behavioral verification or live managers or workers. Missing setup/capabilities remain visible without the marker. The four sparse markers have distinct meanings: `๐ŸŽฌ` identifies the checked project Director, `โ“` 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 Director keeps its required `๐ŸŽฌ` response prefix before the report block. Use a periodic overview after several minutes of otherwise quiet managed work or when several developments or workstreams benefit from one combined report. Ordinary replies, worker returns, and status changes do not automatically need a full SitRep. Communicate meaningful changes promptly; meaningful ordinary progress updates already satisfy the cadence without a redundant report. Allow no more than five minutes of silence during supervision, respecting stricter host timing with concise updates. Overviews keep active, waiting, returned, and pending-evaluation work visible with 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 Director Pattern in this project from https://director.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/director_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, including the project's role index and definitions, model mapping, and identity roster. 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.