Use before code or PR handoff for UI-impacting DPF work. Triggers on UX/UI/design/feature fit, route/tab, first viewport, guided work, dashboard/cockpit, metric/KPI/status/card/button/link/disclosure, coworker launcher, empty state, navigation, portal UX, and customer/workspace/business/platform surfaces, including config/settings/admin screens, forms, or fields (setting, preference, toggle, wizard, credential picker, per-model option, numeric/text input). Config forms are UI surfaces.
Use for agriculture-ranching operating plans and decision briefs spanning fields, pasture, crops, hay, livestock, working animals, equipment, inputs, vendors, weather, markets, and obligations. Keeps location, evidence date, authority, and human approval explicit.
Use when a unit of work is functionally complete and needs to leave the working tree. Decide the integration shape first, confirm the branch is green, obtain independent semantic review of the stable committed tree before pregate or publication, sweep for loose/overlapping work, then hand off to dpf-pr-with-dco.
Use when ready to open a DPF pull request. Encodes the full DPF PR contract, including a fresh independent semantic-review receipt for the stable local commit before pregate/first publication, DCO, overlap sweep, exact-tree local CI, and a regular non-draft ready PR.
Use when adding a NEW business archetype to the DPF platform — a new industry or vertical the storefront-templates taxonomy does not yet cover, or when an archetype idea is floated and needs the paved road. Covers all four provisioning dimensions (template substrate, WSID profession corpus, AI coworker decision, skills/tools) and the completeness gate that blocks a shallow archetype from shipping.
Use when reviewing or updating a DPF specification, design doc, or implementation plan for architectural alignment — in Build Studio planning/review or during external Claude/Codex development. Applies the chief-architect lens: canonical contracts, data-model stewardship, kernel principles, and standards research, producing advisory findings with concrete spec edits. Advisory by contract; it sharpens a spec, it does not gate a build.
Use when clearing Dependabot or security-advisory alerts on the DPF repo — a batch of npm vulnerability alerts, a 'bump the vulnerable dependency' ask, or a security-tab sweep. Covers the DPF pattern for transitive vulnerabilities, lockfile regeneration, verification, and shipping a DCO PR.
Use when driving the live DPF portal through the browser (Claude-in-Chrome) — messaging a coworker, clicking through a build's gates, filling an admin form — OR observing what the build/inference engine is doing: which model ran a phase, why a tool call failed, where a build is stuck. Covers the DOM mechanics that fail by default on live pages, and where build truth actually lives across the database, activity events, container logs and runtime-health surfaces.