diff --git a/docs/HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md b/docs/HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md index 06aa296..7f69c12 100644 --- a/docs/HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md +++ b/docs/HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md @@ -333,7 +333,12 @@ When `Model A` evaluates or refreshes a retained repo, the output should try to ## Retroactive interpretation rule for existing packets -This doctrine applies retroactively to the already closed HyperTwist packets. +This doctrine may inform already closed HyperTwist packets, but it does not +authorize fake whole-corpus rewrites or blind full resets. + +Use the governing retroactive backfill doctrine: + +- `docs/ops/HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md` When reading any existing `0R` packet: @@ -344,12 +349,17 @@ When reading any existing `0R` packet: If an older packet appears too narrow relative to the retained value: -- update the packet -- update the clean-room or boundary-sensitive handoff +- reopen the exact earlier affected packet or handoff selectively +- name the exact packet or handoff reopened +- preserve what remained valid explicitly +- change only what later evidence materially changed - preserve the guardrails Do not push the ambiguity downstream into `Model B`. +Repo-local extraction may remain valid even when cross-lane authority later +needs selective backfill. + ## Document responsibility split Use the HyperTwist docs this way: @@ -386,6 +396,10 @@ Use the HyperTwist docs this way: - slice decomposition before authority ranking - selective retroactive backfill when a later same-family repo materially changes an earlier contested-slice authority call +- `docs/ops/HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md`: + - governing selective retroactive authority and cleanup backfill rule + - no fake whole-corpus rewrite rule + - exact reopened-packet reporting rule - `docs/ops/HYPERTWIST_PACKET_CLEANUP_AND_REBUILDABLE_ARTIFACT_HYGIENE_2026-05-20.md`: - post-packet cleanup order - rebuildable-artifact rule diff --git a/docs/HYPERTWIST_MODEL_A_MODEL_B_COORDINATOR_DOCTRINE_2026-05-14.md b/docs/HYPERTWIST_MODEL_A_MODEL_B_COORDINATOR_DOCTRINE_2026-05-14.md index b43ce75..ae4f4fd 100644 --- a/docs/HYPERTWIST_MODEL_A_MODEL_B_COORDINATOR_DOCTRINE_2026-05-14.md +++ b/docs/HYPERTWIST_MODEL_A_MODEL_B_COORDINATOR_DOCTRINE_2026-05-14.md @@ -13,6 +13,7 @@ It is the HyperTwist-local coordinator counterpart to: - [HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md:1) - [HYPERTWIST_CROSS_LANE_AUTHORITY_HIERARCHY_AND_RECONCILIATION_2026-05-20.md](C:/HyperTwist/docs/ops/HYPERTWIST_CROSS_LANE_AUTHORITY_HIERARCHY_AND_RECONCILIATION_2026-05-20.md:1) - [HYPERTWIST_PACKET_CLEANUP_AND_REBUILDABLE_ARTIFACT_HYGIENE_2026-05-20.md](C:/HyperTwist/docs/ops/HYPERTWIST_PACKET_CLEANUP_AND_REBUILDABLE_ARTIFACT_HYGIENE_2026-05-20.md:1) +- [HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md](C:/HyperTwist/docs/ops/HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md:1) - [MODEL_B_SOURCE_ACCESS_BOUNDARY.md](C:/HyperTwist/docs/MODEL_B_SOURCE_ACCESS_BOUNDARY.md:1) ## Purpose @@ -163,6 +164,19 @@ note to state: - preserved secondary value - non-promoted families +Retroactive authority backfill is governed by: + +- `C:\HyperTwist\docs\ops\HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md` + +Required rule: + +- repo-local extraction may remain valid even when cross-lane authority needs + backfill +- reopen the earlier affected packet or standing note selectively +- do not silently contradict older packets +- do not bulk-rewrite history for appearance +- preserve valid earlier value explicitly + ## Cleanup coordination rule Packet cleanup and worktree hygiene are governed by: diff --git a/docs/ops/HYPERTWIST_CANONICAL_COMPACT_CLOSEOUT_FORMAT_2026-05-19.md b/docs/ops/HYPERTWIST_CANONICAL_COMPACT_CLOSEOUT_FORMAT_2026-05-19.md index 831b570..19f867b 100644 --- a/docs/ops/HYPERTWIST_CANONICAL_COMPACT_CLOSEOUT_FORMAT_2026-05-19.md +++ b/docs/ops/HYPERTWIST_CANONICAL_COMPACT_CLOSEOUT_FORMAT_2026-05-19.md @@ -118,6 +118,7 @@ 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` @@ -134,3 +135,17 @@ 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 diff --git a/docs/ops/HYPERTWIST_CROSS_LANE_AUTHORITY_HIERARCHY_AND_RECONCILIATION_2026-05-20.md b/docs/ops/HYPERTWIST_CROSS_LANE_AUTHORITY_HIERARCHY_AND_RECONCILIATION_2026-05-20.md index 9cf3171..15ba4e2 100644 --- a/docs/ops/HYPERTWIST_CROSS_LANE_AUTHORITY_HIERARCHY_AND_RECONCILIATION_2026-05-20.md +++ b/docs/ops/HYPERTWIST_CROSS_LANE_AUTHORITY_HIERARCHY_AND_RECONCILIATION_2026-05-20.md @@ -9,6 +9,10 @@ If a looser prompt, packet, or standing note conflicts with this document on authority ranking, execution routing, realization width, or selective retroactive backfill, this document wins. +Retroactive backfill behavior itself is governed by: + +- `C:\HyperTwist\docs\ops\HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md` + ## Purpose This document defines the mature decision model for cross-lane discrepancies @@ -296,6 +300,7 @@ This document extends, but does not replace: - `C:\HyperTwist\docs\HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md` - `C:\HyperTwist\docs\HYPERTWIST_MODEL_A_MODEL_B_COORDINATOR_DOCTRINE_2026-05-14.md` +- `C:\HyperTwist\docs\ops\HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md` - `C:\HyperTwist\docs\ops\HYPERTWIST_CANONICAL_COMPACT_CLOSEOUT_FORMAT_2026-05-19.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` @@ -307,22 +312,22 @@ This document extends, but does not replace: ## Retroactive backfill rule -Older packets do not all need full re-evaluation. +Use the governing retroactive backfill doctrine: -Backfill in this order: +- `C:\HyperTwist\docs\ops\HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md` -1. packets or summary surfaces where contested ownership was stated only - loosely -2. packets where the current winner, adjunct, reference, or pattern split is - ambiguous -3. packets where a restrictive repo may actually be the higher capability - authority but was previously described too defensively -4. earlier same-family packets whose contested-slice authority call is - materially changed by a later same-family repo or later reconciliation pass +Authority backfill here is selective, comparative, and slice-local. -Do not rewrite older packets just to paraphrase them. +Required rule: + +- do not do fake whole-corpus rewrites +- do not do blind full resets +- do not invent certainty for older ambiguous packets +- reopen only the earlier affected packet or standing note when later + same-family evidence materially changes a contested slice +- preserve valid repo-local extraction explicitly when only cross-lane + authority changed +- name the exact earlier packet or standing note reopened Backfill only where the hierarchy model materially changes interpretation, -implementation routing, or checkpoint gating. - -Do not invent certainty for older ambiguous packets. +implementation routing, checkpoint gating, or preserved secondary value. diff --git a/docs/ops/HYPERTWIST_PACKET_CLEANUP_AND_REBUILDABLE_ARTIFACT_HYGIENE_2026-05-20.md b/docs/ops/HYPERTWIST_PACKET_CLEANUP_AND_REBUILDABLE_ARTIFACT_HYGIENE_2026-05-20.md index 4966111..26a0434 100644 --- a/docs/ops/HYPERTWIST_PACKET_CLEANUP_AND_REBUILDABLE_ARTIFACT_HYGIENE_2026-05-20.md +++ b/docs/ops/HYPERTWIST_PACKET_CLEANUP_AND_REBUILDABLE_ARTIFACT_HYGIENE_2026-05-20.md @@ -21,6 +21,10 @@ If those documents conflict with this one, this document wins. Do not weaken any stricter repo-specific or packet-specific rule that is explicitly documented elsewhere. +Retroactive cleanup-backfill behavior itself is governed by: + +- `C:\HyperTwist\docs\ops\HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md` + ## Purpose - make post-packet cleanup an operating doctrine instead of chat memory @@ -264,12 +268,22 @@ still operationally relied on. Do not invent certainty from memory. +Required retroactive cleanup rule: + +- do not do fake whole-corpus rewrites +- do not do blind full resets +- the correct target is the relied-on ambiguity, not blanket relabeling +- cleanup backfill is comparative and operational, not cosmetic +- name the exact earlier packet, standing note, or workflow doc reopened +- state whether cleanup interpretation changed or only wording changed + ## Relationship to active doctrine This document is the HyperTwist-local cleanup authority referenced by: - `C:\HyperTwist\docs\ops\HYPERTWIST_WORKTREE_PLACEMENT_AND_VALIDATION_ARTIFACT_POLICY_2026-05-19.md` - `C:\HyperTwist\docs\ops\HYPERTWIST_CANONICAL_COMPACT_CLOSEOUT_FORMAT_2026-05-19.md` +- `C:\HyperTwist\docs\ops\HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md` - `C:\HyperTwist\docs\HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md` - `C:\Workspaces\HyperTwist\clean-room-specs\MODEL_OUTPUT_RULES.md` - `C:\Workspaces\HyperTwist\clean-room-specs\README.md` diff --git a/docs/ops/HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md b/docs/ops/HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md new file mode 100644 index 0000000..db944fc --- /dev/null +++ b/docs/ops/HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md @@ -0,0 +1,178 @@ +# HyperTwist Retroactive Authority And Cleanup Backfill - 2026-05-20 + +## Status + +This document is now the governing HyperTwist doctrine for retroactive +authority backfill and retroactive cleanup backfill. + +If a packet, standing note, workflow doc, or prompt implies blanket +relabeling, fake whole-corpus rewrite, blind full reset, or invented certainty +for an older ambiguous packet, this document wins. + +## Purpose + +This doctrine exists to make retroactive repair selective, comparative, and +operational. + +Its job is to stop two opposite errors: + +1. treating an older packet as frozen even when later evidence materially + changes current routing +2. treating every later clarification as permission for a cosmetic + whole-corpus rewrite + +Retroactive backfill is for the exact contested slice or relied-on ambiguity +that still matters now. + +It is not for blanket relabeling. + +## Governing rule + +Do not do fake whole-corpus rewrites. + +Do not do blind full resets. + +Do not invent certainty for older ambiguous packets. + +Do selective backfill only where later evidence materially changes: + +- interpretation +- operational routing +- authority ranking +- cleanup interpretation +- active state reporting + +Repo-local extraction may remain valid even when cross-lane authority needs +backfill. + +Repo-local extraction may remain valid even when cleanup interpretation needs +backfill. + +Backfill is comparative and operational, not cosmetic. + +The correct target is the contested slice or relied-on ambiguity, not blanket +relabeling. + +## Backfill classes + +### A. Authority backfill + +Authority backfill is triggered when: + +- a later same-family repo materially changes a contested capability slice +- an older packet's winner versus adjunct versus reference versus pattern split + is ambiguous +- a restrictive or otherwise harder-route repo appears to be the stronger + authority and was previously softened incorrectly + +Authority backfill requirements: + +- reopen the earlier affected packet or standing note selectively +- name the exact earlier packet or standing note reopened +- state the exact contested slice +- preserve valid repo-local extraction unless later evidence materially changes + it +- state whether the change is: + - repo-local extraction changed + - cross-lane authority changed + - only wording changed + +Authority backfill is not permission to: + +- reset an entire family cluster by default +- relabel every older packet for appearance +- flatten preserved secondary value from non-winners into exclusion + +### B. Cleanup backfill + +Cleanup backfill is triggered when an older packet or workflow doc is still +operationally relied on but is ambiguous about: + +- temporary root used +- whether cleanup happened +- whether retained residue was intentional +- whether remaining dirt is packet-created or pre-existing + +Cleanup backfill requirements: + +- mark the ambiguity explicitly instead of inventing certainty +- backfill only where the ambiguity still matters operationally +- name the exact earlier packet, standing note, or workflow doc reopened +- state whether the change is: + - cleanup interpretation changed + - only wording changed + - or whether packet truth itself changed + +Cleanup backfill is not permission to: + +- bulk-rewrite older closeouts for appearance +- claim a repo was clean when only packet dirt was removed +- erase plausible pre-existing residue by narrative rewrite + +## Prioritization order + +When retroactive backfill is actually needed, prioritize in this order: + +1. contested slices that affect current implementation routing +2. older packets whose authority or adjunct or reference or pattern split is + ambiguous +3. cleanup-ambiguous packets still relied on in workflow or state reporting +4. family clusters with dense overlap and high donor value +5. lower-risk historical packets only if still active in planning or doctrine + +## Required outputs for every retroactive backfill pass + +Every retroactive backfill pass must output: + +- exact earlier packet or packets reopened +- exact standing note or notes reopened when applicable +- exact reason the backfill was triggered +- whether: + - repo-local extraction changed + - cross-lane authority changed + - cleanup interpretation changed + - only wording changed +- what remained valid and was preserved +- what changed and why +- whether more selective backfill remains + +If no retroactive backfill was actually triggered, say that explicitly. + +## Practical interpretation rule + +If later evidence changes a contested slice: + +- reopen only the earlier affected slice-local packet or standing note +- preserve valid earlier value explicitly +- patch current routing from the corrected result + +If later evidence does not change the contested slice, do not reopen the +earlier packet just to harmonize wording. + +If cleanup posture is ambiguous but no current routing, reporting, or residue +decision depends on it, record that the ambiguity exists and defer the +backfill. + +## Relationship to active doctrine + +This document governs retroactive backfill behavior across: + +- `C:\HyperTwist\docs\ops\HYPERTWIST_CROSS_LANE_AUTHORITY_HIERARCHY_AND_RECONCILIATION_2026-05-20.md` +- `C:\HyperTwist\docs\ops\HYPERTWIST_PACKET_CLEANUP_AND_REBUILDABLE_ARTIFACT_HYGIENE_2026-05-20.md` +- `C:\HyperTwist\docs\ops\HYPERTWIST_CANONICAL_COMPACT_CLOSEOUT_FORMAT_2026-05-19.md` +- `C:\HyperTwist\docs\ops\HYPERTWIST_WORKTREE_PLACEMENT_AND_VALIDATION_ARTIFACT_POLICY_2026-05-19.md` +- `C:\HyperTwist\docs\HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md` +- `C:\HyperTwist\docs\HYPERTWIST_MODEL_A_MODEL_B_COORDINATOR_DOCTRINE_2026-05-14.md` +- `C:\Workspaces\HyperTwist\clean-room-specs\MODEL_OUTPUT_RULES.md` +- `C:\Workspaces\HyperTwist\clean-room-specs\README.md` +- `C:\Workspaces\HyperTwist\clean-room-specs\bounded-implementation-workflow.md` +- `C:\Workspaces\HyperTwist\clean-room-specs\GENERIC_OPERATOR_SEQUENCE_AND_PROMPTING.md` +- `C:\Workspaces\HyperTwist\clean-room-specs\0600-phase5r-clean-room-operator-sequence-and-handoff.md` +- `C:\Workspaces\HyperTwist\clean-room-specs\0500-phase5r-restrictive-lanes.model-b-consolidation-prompt.md` + +Use this document when deciding whether an older HyperTwist packet needs: + +- no change +- selective authority backfill +- selective cleanup backfill +- or only a narrow wording correction diff --git a/docs/ops/HYPERTWIST_WORKTREE_PLACEMENT_AND_VALIDATION_ARTIFACT_POLICY_2026-05-19.md b/docs/ops/HYPERTWIST_WORKTREE_PLACEMENT_AND_VALIDATION_ARTIFACT_POLICY_2026-05-19.md index da3f26f..2c67998 100644 --- a/docs/ops/HYPERTWIST_WORKTREE_PLACEMENT_AND_VALIDATION_ARTIFACT_POLICY_2026-05-19.md +++ b/docs/ops/HYPERTWIST_WORKTREE_PLACEMENT_AND_VALIDATION_ARTIFACT_POLICY_2026-05-19.md @@ -16,6 +16,9 @@ Relationship note: `C:\HyperTwist\docs\ops\HYPERTWIST_PACKET_CLEANUP_AND_REBUILDABLE_ARTIFACT_HYGIENE_2026-05-20.md` - if this document conflicts with the broader cleanup doctrine, the broader cleanup doctrine wins +- selective retroactive cleanup backfill for older relied-on packet or workflow + ambiguity is governed by + `C:\HyperTwist\docs\ops\HYPERTWIST_RETROACTIVE_AUTHORITY_AND_CLEANUP_BACKFILL_2026-05-20.md` - use the broader doctrine for deep source packet evaluation and other packet types that generate rebuildable artifacts outside bounded implementation @@ -50,6 +53,9 @@ Cleanup rule: `git worktree remove `; if the folder is deleted manually, follow with `git worktree prune` so stale worktree metadata does not remain under the main repo. +- If an older relied-on packet or workflow doc is cleanup-ambiguous, do + selective cleanup backfill only where that ambiguity still matters + operationally; do not bulk-rewrite older closeouts for appearance. Operational note: