---
type: group-context
task-group: <task-group>
created: <YYYY-MM-DD>
generator: okstra-brief-gen
---

# Task-Group Context: <task-group>

> Shared by every task in this task-group. okstra copies it into each run's
> `instruction-set/task-group-context.md` and carries it in the analysis
> packet's `## Task-Group Context` section, ahead of the brief extract.
> Write only what no single ticket can recover — a summary of the tickets
> decides nothing. Preparation refuses this file while any `<...>`
> placeholder line remains; delete the file instead if the group needs none.

## Why This Group Exists

<The situation that created this group: what keeps happening, to whom, and why it takes a group of tickets rather than one. Not a summary of the tickets.>

## Definition of Better

<The measure the whole group is judged by, as a quantity and its direction. Name the denominator explicitly: a per-page ratio and a fleet-wide count are different measures, and a run that has only one of them will reason from it.>

## Group-Wide Constraints

<Rules every task in the group must respect, one bullet each, so no brief has to repeat them. Write `_(none)_` when there are none.>

## Ticket Relations

<Which tickets are causes, which are observation means, which depend on which. Write `_(none)_` when the briefs' Related Task Graph already says it all.>

<!-- okstra:task-memory:begin -->
<!-- okstra redraws this region after every report-finalize, at `okstra set-work-status`, and before each run copies this file. Edit the sections above it, not this one. -->
## Task Memory

_(no runs recorded yet)_
<!-- okstra:task-memory:end -->