E08 — Wider purpose, including humans and goal formation

Authored design — 2026-09-15. Section 4. This cascade elaborates the existing checklist item. It is not a dispatch, implementation receipt or completion verdict. Work outside WM-01–14 still requires Joe’s explicit greenlight; having a cascade is necessary but not permission.

Section 3/4 index · Exact TODO · Cascade JSON

Situation and design problem

Selecting a supplied ticket is not goal formation, and producing artifacts is not evidence of human benefit. The four apex requirements need their own exact authority and participant-facing evidence.

Governing checklist snapshot

E08 — Wider purpose, including humans and goal formation. OPEN: evidence for all four apex requirements, including participant feedback and accountable formation of goals. The choice of an already supplied task is insufficient for goal formation.

This is the checklist’s dated evidence account, not a new deployment census. Existing source/test evidence keeps its bounded credit. The acceptance obligation above governs this design.

Pattern applications

E08-1 — Bind the four ruled requirements

Pattern: wm-purpose-and-account/recipient-benefit-shapes-the-model

Use September 9 Item 26 and apex-thesis-v1: A records carry warrant; B one queryable self-account; C feedback reaches every participant; D accountable next-action choice including goal formation. Produce four separate requirement/evidence subjects. Joe rejected reducing these institutional requirements to unexplained weights.

E08-2 — A: preserve warrant with the record

Pattern: wm-qualifying-run/certificate-and-world-must-meet

Retain each assertion with derivation, original evidence, authority and limits through storage and retrieval. Demonstrate that a recipient can inspect the warrant, not only a trimmed conclusion. Bind to E02 rather than commission a parallel evidence store.

E08-3 — B: make one queryable self-account

Pattern: wm-qualifying-run/complete-acquisition-universe

Declare the stack-state/provenance query and its required universe. Join the existing evidence vocabularies without hiding incompatible meanings or missing records. Show reconstitution and honest holes in the answer; an empty projection is not proof that nothing is missing.

E08-4 — C: deliver feedback to every participant

Pattern: wm-purpose-and-account/recipient-benefit-shapes-the-model

Name the actual human, agent and stakeholder recipients for the work, their delivery paths and evidence of receipt/use. Retain disagreements and inaccessible participants. A message emitted into a log does not show that the participant received or could act on it.

E08-5 — D: form and choose goals accountably

Pattern: workshop/accountable-next-action-choice

Separate problem discovery, goal proposal, authorized adoption and action choice. Retain concerns, alternatives, uncertainty and who may revise priorities. Selecting a supplied ticket is not goal formation; simulated demand cannot become participant preference by relabeling.

E08-6 — Check the composed institutional arrangement

Pattern: wm-purpose-and-account/recipient-benefit-shapes-the-model

Test all four claims together on actual work: can participants retrieve the warranted account, receive feedback and question or revise the proposed goal through their authority? Retain independent findings and the consequences. No one successful query or accepted goal proposal proves all four.

Composition and interfaces

Each node’s stated artifact is the input or constraint for the related node below. These are design dependencies, not a claim that a runtime scheduler automatically fires patterns. Existing WM producers are reused through the linked contracts; no second implementation is implied.

Retain the actual subject, source/model revision, task/occurrence, cutoff, producer and consumer for each interface. A missing field is a named gap; a default that changes the meaning is not an adapter. Reuse existing records where they satisfy these obligations. If a new component is indispensable, identify its exact TODO/cascade clause before seeking a separately bounded implementation instruction.

Worked situation

The system chooses an existing ticket efficiently, while a participant needs a different unresolved problem addressed. That proves a choice among inputs, not accountable goal formation or benefit. The participant’s concern must have a traceable route to a proposed, authorized goal.

This is a distinguishing design example, not a claimed production experiment.

Implementation sequence and closure evidence

1. Bind the first application to the actual source, task and authority. Resolve the decisions below before their dependent change; do not reproduce a known gap merely to claim activity.
2. Implement only the specifically dispatched producer/consumer change from the middle applications. Retain the meaningful pre-change failure and relevant post-change controls; do not start a general infrastructure project.
3. Acquire the final application’s evidence and independent review. Compare it against every clause of the exact TODO, identifying any still-open dependency. Source, tests, serving state, ordinary use and whole-run validation receive different credit.

Distinguishing controls: Reject invented apex criteria, simulated demand called preference, supplied-task selection called goal formation, unsupported human-benefit claims and feedback logged without consequence.

Closure rule: every part of the quoted obligation must be supported by the indicated artifacts and actual connections. A useful rejection proves the rejecting boundary only. One accepted subclause does not tick the whole item. A bellback must supply the exact reviewed subject, executed checks, independent verdict and remaining clauses.

Dependencies and authority boundaries

E01 · WM-13 · R19 · E10

The four requirement names and their status are ruled, not open. Their computational/institutional realization and task-specific evidence criteria still require design review; no weights or autonomous goal-setting authority are invented.

Dependency links describe required interfaces; they do not authorize work on those items. No implementation outside the existing TODO list is approved. Publication does not select a numerical law, settle an unresolved operator ruling or authorize a run.

Pattern and source scope

All seeded patterns are applied above. The JSON pins their source bytes and the governing checklist/rulings. Historical formulas, thresholds and examples in a pattern remain scoped examples unless the governing contract adopts them. This draft adds no pattern-library entries and claims no independent semantic ratification.

Existing pattern source snapshots

Reference text; historical examples and prescriptions retain the scope stated above.

@flexiarg workshop/accountable-next-action-choice
@title Accountable Next-Action Choice
@keywords choice, priority, accountability, uncertainty, goals, G, received-preference
@audience task managers, strategic loops, selectors
@tone normative
@style pattern
@grade principle
@provenance apex-thesis cluster D ("Accountable next-action choice, including goal formation: deciding what to do next, accountably, under uncertainty — with the goals themselves formable, not given") — members: G over policies; C; find/organise (WM core); policy-conditioned EIG; policy-grain compliance; shared-budget arbitration; pre-goal preference C_ser. Minted for apex coverage (Joe, 2026-09-12).
@review Joe approved the pattern-language framing; this member pending detailed read.
@class process
@domain process
@family-note workshop/ family, seventh member; cluster D of the apex — completes A-D coverage of the small pattern language. Out of the math pool by construction.
@status workshop declaration 2026-09-12; NOT assayed.

! conclusion:
  The choice of the next action is accountable when it can say, with
  evidence: what was chosen, from what candidates, under what
  preference, at what uncertainty — and the preference was RECEIVED
  from where preference legitimately lives, never computed by the
  chooser.

  + context:
    Selection machinery exists (ranked-actions, intrinsic-value
    posteriors, preregistered G); goal formation is the harder half
    (pre-goal preferences, C_ser); and the failure mode is a chooser
    that quietly becomes the source of the preferences it optimizes.

  + IF:
    Any agent, loop, or manager selects what work happens next.

  + HOWEVER:
    Under real uncertainty the account includes the uncertainty:
    wide intervals, unranked ties, and "no action cleared its
    threshold" are all legal typed outcomes — accountable does not
    mean confident. Simulated demand (Part III agents) is input to
    preference, never preference itself.

  + THEN:
    The selector emits its account with the choice: candidates,
    ranked-actions with reasons, the received preference's
    provenance (operator pin or rehydrated posterior), the
    uncertainty typed, and the shared-budget arithmetic. Choosing
    without emitting the account is the violation.

  + BECAUSE:
    "Accountable next-action choice" is the apex thesis's D stated
    as a constraint; the constitutional line (priority received,
  never computed) is what keeps the crew a tool of its operator
    rather than an agent with opinions about what matters.

  + NEXT-STEPS:
    next[The task-manager spec's constitutional line is this pattern's first enforcement; keep it verbatim when built.]
    next[Ranked-actions' missing reconciliation exits (lint ticket) are this pattern's open gap.]