# HyperTwist Canonical Compact Closeout Format

Created on `2026-05-19`.

Status:

- active HyperTwist closeout doctrine

Authority note:

- treat `C:\VectorShell\docs\ops\VECTORSHELL_CANONICAL_COMPACT_CLOSEOUT_FORMAT_2026-05-19.md`
  as the controlling shape authority
- use this HyperTwist document to lock the same section order and compression
  discipline into HyperTwist-local evaluation, clean-room, and bounded
  implementation workflow surfaces
- packet docs remain authority; chat closeouts are presentation only

## Required section order

Use this order unless a section is genuinely not applicable:

1. `Main packet`
2. `Restrictive-lane handoff` when applicable
3. `Result`
4. `Why that call`
5. `Windows validation` or host-validation equivalent
6. `Authority surfaces updated`
7. `Pushed` when applicable
8. `State`
9. `Next live repo` or `Next live batch`
10. `Task-summary omission report`

If a section did not happen, say so explicitly instead of silently omitting it.

## Result taxonomy rule

`Result` must explicitly state the repo-level outcome category:

- `implemented now`
- `retained for later implementation`
- `retained as reference only`
- `retained only for pattern extraction`
- `excluded`

If the repo or retained lane remains retained, `Result` must also state the
realization class explicitly:

- `full bounded capability realization`
- `narrower bounded slice`

When a narrower bounded slice is chosen:

- say that directly
- name the exact kept capability families
- name the exact deferred, donor-only, reference-only, pattern-only,
  non-promoted, or excluded capability families

Do not leave that taxonomy implicit in general prose.

If a packet resolved, reused, or materially changed a contested slice
authority call, `Result` or `Why that call` must also surface:

- exact contested slice
- candidate repos considered or standing candidates reused
- `A` tier per candidate for that slice
- `R` route for the retained winner where relevant
- `F` class for the retained winner
- preserved secondary value from non-winners
- exact non-promoted families

Route that overlap language through:

- `C:\HyperTwist\docs\ops\HYPERTWIST_CROSS_LANE_AUTHORITY_HIERARCHY_AND_RECONCILIATION_2026-05-20.md`

## Compactness rule

Compactness is allowed. Information loss is not.

You may compress by:

- grouping same-type facts into paragraphs
- using short grouped bullets
- combining same-class evidence, file names, validation facts, or state facts
  on one line with commas or semicolons

You may not compress away:

- repo-level outcome category
- retained-versus-reference-versus-pattern-versus-excluded taxonomy
- full-bounded-versus-narrower-slice realization taxonomy
- restrictive posture
- clean-room boundary
- exact donor scope
- exact kept versus not-kept capability families
- validation blockers
- omission accounting
- next-sequence naming
- lane, validation, custody, push, state, cleanup, or next-pack facts

## HyperTwist local usage rule

HyperTwist packet and workflow docs that govern evaluation or bounded
implementation closeouts must point here rather than treating closeout shape as
optional.

In particular:

- evaluation doctrine must require the outcome taxonomy
- clean-room model-output rules must require the section order and omission
  accounting
- bounded implementation prompts must require explicit `Result` taxonomy even
  when the packet realizes only one bounded slice

## Relationship to broader doctrine

This closeout doctrine is the HyperTwist-local reference target for:

- `C:\HyperTwist\docs\HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md`
- `C:\HyperTwist\docs\HYPERTWIST_REPO_INTAKE_RETENTION_AND_PRODUCT_FIT_DOCTRINE_2026-05-14.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_CROSS_LANE_AUTHORITY_HIERARCHY_AND_RECONCILIATION_2026-05-20.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_PACKET_CLEANUP_AND_REBUILDABLE_ARTIFACT_HYGIENE_2026-05-20.md`
- `C:\Workspaces\HyperTwist\clean-room-specs\MODEL_OUTPUT_RULES.md`
- `C:\Workspaces\HyperTwist\clean-room-specs\README.md`
- repo-specific clean-room prompt-sequence and bounded-implementation prompt
  surfaces

## Retroactive note

Older HyperTwist packets and summaries that predate this doctrine may still be
useful but may not encode the exact `Result` taxonomy now required.

If a current routing or retention decision depends on that missing taxonomy:

- do targeted backfill
- say explicitly that the older packet was taxonomy-ambiguous
- do not invent certainty that the packet itself did not record

Retroactive authority and cleanup backfill are governed by:

- `C:\HyperTwist\docs\ops\HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md`

For any retroactive backfill pass, the closeout must also state:

- exact earlier packet or standing note reopened
- exact trigger reason
- whether repo-local extraction changed, cross-lane authority changed, cleanup
  interpretation changed, or only wording changed
- what remained valid and was preserved
- what changed and why
- whether more selective backfill remains
