Process Template

Two stencils. Copy part A to FUNCTION_SLUG-process/index.mdx, and part B once per job.

Part A — The inventory index

Frontmatter:

---
type: business-process # or industry-process
pillar: process
page_job: "Index every job and task required to run FUNCTION_NAME end to end."
title: FUNCTION_NAME Process
sidebar_label: Process
description: "The complete inventory of jobs and tasks needed to run FUNCTION_NAME, each with a stable ID, owner split, and coverage status."
tags:
  - FUNCTION_NAME
  - Process
  - Jobs
  - Workchart
template: domain-map-template
loop_phase: action
level: working
claim_state: REALITY
retrieval_trigger: "When choosing or locating one FUNCTION_NAME job to be done."
---

Body:

Which FUNCTION_NAME job owns the outcome you are trying to change?

[One or two sentences: what this function is accountable for, where its work
starts, where it ends, and which functions sit upstream and downstream.]

## The Inventory

[One `###` per stage, in the order work moves. Under each stage, one line per job:
linked title, stable ID, one-sentence job statement, and status. Status is `core`
or `supplemental`, plus `GAP` when no page exists yet.]

### Stage name

1. **[Job title](./FUNCTION_SLUG-verb-object)** — `FUNCTION_SLUG.verb-object` — core —
   [what this job produces]
2. **Job title** — `FUNCTION_SLUG.verb-object` — core — GAP — [what this job would produce]

## Coverage

[State it plainly: N jobs declared, M with pages, K declared gaps. A gap is located
work, not an apology. Name the costliest one.]

## Allocation

[The human/agent split across the inventory, keyed by job ID. Link the function's
work chart if it has one. Keep the numbers dated.]

## Context

- **depends-on** FUNCTION_NAME Principles — the rules these jobs run under
- **proved-by** FUNCTION_NAME Performance — the gauges these jobs move
- **pairs-with** FUNCTION_NAME Platform — the tools these tasks run on
- **pairs-with** FUNCTION_NAME Players — who holds each job
- **depends-on** Process Inventory — the method that built this list

[Link each of the five as a real route. The relationship label must come from the
closed seven-label vocabulary; an invented label is a dropped edge.]

## Questions

Next question: [the one question the coverage gap raises]

- [a question about an unowned or double-owned job]

Part B — One job page

Frontmatter:

---
type: business-process # or industry-process
pillar: process
page_job: "Run the FUNCTION_NAME job JOB_TITLE from trigger to evidence."
capability_id: FUNCTION_SLUG.verb-object
title: JOB_TITLE
sidebar_label: JOB_TITLE
description: "[Verb the object to produce the outcome] — tasks, decisions, controls, and evidence."
tags:
  - FUNCTION_NAME
  - Process
  - Jobs
template: domain-map-template
loop_phase: action
level: working
claim_state: REALITY
retrieval_trigger: "When JOB_TITLE must be performed, delegated, or improved."
---

Body — the eight-part job contract. Every part earns its place; none is optional:

[One sentence: verb, object, outcome. What is different in the world when this job is done.]

## Boundary

- **Job ID** — `FUNCTION_SLUG.verb-object`
- **Trigger** — [what starts it]
- **Cadence** — [per case, weekly, quarterly, on exception]
- **First action / last action** — [where the job begins and ends]
- **Upstream / downstream** — [the job IDs either side]

## Inputs And Outputs

- **Inputs** — [what must exist, and who supplies it]
- **Outputs** — [what this job hands on, and who receives it]

## Tasks

[The allocation matrix for this job. One row per task. Verb-led statements.
No tool names in the statement column — the tool has its own column.]

| ID  | Task | Core | Player | Human or agent | Skill | Tool | Evidence of done |
| --- | ---- | ---- | ------ | -------------- | ----- | ---- | ---------------- |
| T01 | [Verbs the object] | core | [role] | human decides | [skill] | [tool] | [artifact or signal] |
| T02 | [Verbs the object] | supplemental | [role] | agent drafts, human approves | [skill] | [tool] | [artifact or signal] |

## Decisions

[Each consequential branch: the rule, the information required, who decides, and
what escalates. Name what a human must retain.]

## Controls And Failure Modes

- **[Failure]** — [the control, placed at the earliest useful point]

## Gauge

[Link the performance pillar. Do not restate thresholds here — reference them.]

## Maturity

[Claim state, what evidence supports it, and the next step that would raise it.]

## Context

- **depends-on** [the upstream job]
- **pairs-with** [the downstream job]
- **proved-by** [the performance page carrying this job's gauge]
- **applies-to** [any cross-function method this job uses]

## Questions

Next question: [the question this job's weakest task raises]

Filled example

One row, so the shape is unambiguous:

ID	Task	Core	Player	Human or agent	Skill	Tool	Evidence of done
T01	Qualifies inbound leads against the ideal customer profile	core	Sales lead	agent scores, human confirms	ICP judgment	CRM	Scored lead with reason
T02	Records the disqualification reason for every rejected lead	core	Sales lead	agent records	Data discipline	CRM	Reason field populated
T03	Reviews qualification thresholds against closed-won evidence	supplemental	Sales owner	human decides	Evidence reading	CRM	Dated threshold decision

Qualifies inbound leads against the ideal customer profile is a task: present-tense verb, named object, observable. Lead qualification is a label. CRM lead scoring is a tool, and it belongs in the tool column so the statement survives a stack change.

Checks Before Publishing

• The index lists every job, including the ones with no page, and each has a stable ID.
• Jobs do not overlap, and together they cover planning, doing, measuring, improving, governing, recurring cadence, and exception work.
• Every task statement leads with a present-tense verb, names its object, and names no tool.
• Every job page carries all eight parts of the contract.
• No page in the folder is a principle, a metric, a tool profile, a role, a company example, or a cross-function method. At most one allocation view is present, and it is keyed to job IDs.
• type, pillar, and page_job are set on the index and on every job page; job pages also carry capability_id.
• The folder is named FUNCTION_SLUG-process, singular.

Context

• depends-on Process Inventory — the method this template renders.
• depends-on Information Architecture Standard — the pillar contract.
• pairs-with Players Template — the sibling pillar stencil.
• applies-to Tools and Skills Matrix — where the task rows land.
• proved-by Sales Process — a filled reference inventory.

Questions

Next question: which pillar stencil is missing next — principles, performance, or platform?

• Which function's process folder would fail the publishing checks today?