# HyperTwist Overnight Mode closeout, continuation, and boundary shape - 2026-06-19

## Purpose

This note defines the mandatory closeout shape for `Overnight Mode`.

Naming clarification:

- `Continuity Mode` and `Disciplined Agentic Mode` are accepted synonyms for
  this same behavior
- `Overnight Mode` remains the canonical closeout and doctrine label used in
  repo authorities

It exists so that:

- stacked `continue` prompts remain deterministic
- the assistant does not veer off-task overnight
- the user can wake up to truthful continuity instead of unrelated drift

## Required shape

Every substantial closeout should explicitly include the following sections in
plain language.

### 1. Active lane

State the exact active lane or donor family.

Examples:

- bounded provider lane
- validation closeout lane
- reassessment lane

### 2. What just closed

State exactly what was completed in the turn.

Examples:

- `P2` status and inspection landed
- bounded validation passed through build
- post-`P3` reassessment authored

### 3. Current lane state

State whether the lane is:

- still open
- materially widened but still open
- materially closed
- blocked

### 4. Exact next adjacent slice

State the single exact next slice in the same lane.

Not:

- a broad category
- a vague family
- a different donor

But:

- one exact adjacent slice
- in present-tense authority-backed wording

### 5. Safe batch on `continue`

State the exact sequence that should be drained automatically if `continue`
arrives and no new blocker appears.

This should be a compact ordered batch such as:

1. `P3`
2. post-`P3` reassessment
3. bounded validation
4. lane closeout note

### 6. Stop conditions

State the exact reasons the assistant would stop rather than continue.

Examples:

- unresolved quiz boundary
- missing authorization
- source not real
- validation failure changes the plan
- fresh-family authority not yet selected

### 7. Fresh-family boundary note

If the current lane is closing near a family transition, state explicitly
whether the next family is already authorized.

If not, say:

- do not auto-open the next donor family
- a fresh live-authority selection pass is required first

### 8. Goal guidance

State one of the following plainly:

- the next safe batch is large enough that a goal should be created now
- the current goal should continue without interruption
- no new goal should be created because a real boundary has been reached

### 9. Truth boundary

State what is not being claimed.

Examples:

- no automation execution claim
- no owner promotion claim
- no new family opening claim

## Required interpretation of later `continue` prompts

When a later `continue` prompt arrives, future instances must read the closeout
in this exact order:

1. active lane
2. current lane state
3. exact next adjacent slice
4. safe batch
5. stop conditions
6. fresh-family boundary note

The assistant must not jump directly from "continue" to broad roadmap memory.

## Disobedience clause

If the closeout records a real unresolved stop condition, future stacked
`continue` prompts must be disobeyed until the stop condition is actually
resolved.

That includes:

- missing quiz answers
- missing authorization
- unresolved validation blocker
- missing fresh-family authority

## Anti-drift examples

### Good closeout

- active lane named
- next adjacent slice named
- safe batch named
- blocker named
- no fresh-family jump implied

### Bad closeout

- "continue implementation"
- "next we can do more"
- "there are many possibilities"
- "we could also open another donor family"

Those vague shapes are forbidden for `Overnight Mode`.

## Truth boundary

This shape is mandatory for substantial closeouts because deterministic
continuation is impossible without deterministic closure wording.
## Update - 2026-06-22 - required recommendation-adoption field at prepared decision boundaries

When a substantial closeout stops at a prepared quiz or decision packet, the
closeout must now explicitly state one of the following:

- plain `continue` **may** adopt the displayed canonical recommended string, in which case the exact string must be restated verbatim
- plain `continue` **may not** adopt it, in which case the blocking reason must be stated explicitly

Required shape example:

- recommendation-adoption status: `continue` may adopt `A D / O:B C E / HO:F`

or

- recommendation-adoption status: explicit user choice still required because sovereign ownership or legal routing remains materially unresolved

Expanded closeout-shape repertoire:

- recommendation-adoption status: plain `continue` may adopt the displayed
  recommendation because the boundary is same-family, low-ambiguity, and no
  real stop condition remains active
- recommendation-adoption status: plain `continue` may not adopt the displayed
  recommendation because the boundary still requires explicit user choice
- recommendation-adoption status: plain `continue` does not itself settle the
  suggestion because a live blocker, quiz boundary, legal boundary, or
  fresh-family boundary still controls

The governing interpretation is now explicit:

- plain `continue` may confirm or adopt a displayed suggestion
- plain `continue` may also fail to confirm or adopt it
- the closeout must state which case is true
- future instances must not infer adoption from `continue` alone when the
  closeout does not authorize that adoption

Compact-string note:

- `HO:<codes>` is the canonical hard-omit prefix in new closeouts and prepared
  decision packets
- older historical closeouts may still use `X:<codes>` for hard omit; read that older form as
  legacy shorthand for `HO:<codes>`
- `O:<codes>` remains the omit-from-current-lane / reroute-later bucket

Expanded closeout-shape repertoire:

- recommendation-adoption status: plain `continue` may adopt the displayed
  recommendation because the boundary is same-family, low-ambiguity, and no
  real stop condition remains active
- recommendation-adoption status: plain `continue` may not adopt the displayed
  recommendation because the boundary still requires explicit user choice
- recommendation-adoption status: plain `continue` does not itself settle the
  suggestion because a live blocker, quiz boundary, legal boundary, or
  fresh-family boundary still controls

The governing interpretation is now explicit:

- plain `continue` may confirm or adopt a displayed suggestion
- plain `continue` may also fail to confirm or adopt it
- the closeout must state which case is true
- future instances must not infer adoption from `continue` alone when the
  closeout does not authorize that adoption

This field is mandatory because deterministic continuation now includes a narrow
safe path for recommendation adoption, and future instances must not leave that
truth implicit.

## Update - 2026-07-19 - safe adjacent queue and default branch fields

Closeouts must no longer present routine safe adjacent options as if every
option requires fresh operator selection.

When multiple options are listed, the closeout must include these fields:

- recommended/default branch
- safe adjacent queue on `continue`
- branches that are safe to execute automatically
- branches that require a real halt

Required interpretation:

- if the listed options are all safe, adjacent, and logically orderable, plain
  `continue` means execute them in the best professional sequence rather than
  halt for a menu choice
- if one option is safest and another is also important, execute the safest one
  first and then the next one if it remains adjacent
- if a later option crosses a true donor-family, quiz, legal, destructive,
  external publishing, or failed-validation boundary, stop only at that later
  real boundary

Expanded closeout-shape repertoire:

- recommended/default branch: execute `release evidence archive policy ->
  bounded packaging preflight` because both are first-party, adjacent, and
  non-destructive
- recommended/default branch: execute `P1 -> P2 -> reassessment -> closeout`
  because the same-family lane is already source-real and authority-backed
- recommended/default branch: stop before donor-family implementation because
  no next family has been selected from live authority
- safe adjacent queue on `continue`: `documentation propagation -> status
  pointers -> commit/push under the active repository landing policy`
- halt-required branch: public deployment, signing, provider mutation,
  destructive mirror movement, or unresolved quiz answer

The closeout must be written so that a sleeping operator can stack `continue`
without the assistant veering into an unrelated project, while also not forcing
the operator to approve every small obvious step.
