proposal

# `proposal`

> A proposed response to a [`driver`](driver.md), before it is consented. On the design
> loop: **signal → insight → driver → proposal → agreement**. When consented, a proposal
> yields an [`agreement`](agreement.md).

**Serialized `type`:** `proposal`

## Frontmatter

| Field | Required | Format | Meaning |
|---|---|---|---|
| `type` | yes | `proposal` | Entity type |
| `derived-from` | no | wikilink or list | The [`driver`](driver.md) (and rungs below it) this responds to (see note) |
| `for-domain` / `for_domain` | no | wikilink or list | The domain — a work system, a role or a unit — the proposal concerns. Naming a role lands the proposal on every keeper of that role |
| `status` | no | `draft` \| `in-consent` \| `consented` \| `declined` | Where the proposal is in its decision |

Plus the shared optionals from [conventions](../conventions.md).

## Body

| Section | Holds |
|---|---|
| `## Proposal` | What is proposed — the change, or the agreement-to-be |
| `## Objections` | Objections / concerns raised during consent *(optional)* |
| `## Outcome` | Consented or declined; a link to the resulting [`agreement`](agreement.md) |

## Example

```markdown
---
type: proposal
derived-from: "[[Standard-order hand-off has no owner]]"
for-domain: "[[Strategic Direction]]"
status: consented
---
## Proposal
Introduce a Standard Order Fulfillment protocol: Sales acknowledges within 24h; Assembly
confirms a slot on intake.

## Objections
Capacity contention with custom orders may break the slot promise in peak weeks.

## Outcome
Consented 2026-05-11 → [[Standard Order Fulfillment Protocol]].
```

## Reading it

- **The question:** what response is proposed to which driver, and where is it in its
  decision?
- **Look first:** `status`, then `## Proposal`; `## Outcome` records the result and links
  the agreement that followed.
- **Go next:** back along `derived-from` to the driver and the rungs below it; up via
  `for-domain` to the domain the proposal concerns.
- **Backlinks:** the decision record whose `derived-from` names it, or the agreements
  consented directly from it.
- **Pictured in:** the change trail, between driver and decision record; `declined` closes
  it, and one nothing derives from yet is an open end. A `dwsd.change-trail` fence with
  `around: self` keeps its own line.

## Notes

- `derived-from` is metadata (the parser has no such relationship type yet), as on
  [`driver`](driver.md) and [`insight`](insight.md).
- **Out of scope:** *how* the change is accompanied — the facilitation workflow, who acts
  when, how consent is run — is an application concern, not part of this spec. The spec
  defines the artifacts (proposal, agreement); the process around them lives in the tooling.