Skip to content

vision: mandatory Apply|Discard gate (no ungated split close) #16

Description

@Zychs

Vision

Split stays open until sandbox returns commit (Apply) or omit (Discard) — workflow continuity without resource leak (README.md Gating and Persistence; dyslexistree-design sandbox-until-Apply).

Reality

No gate UI, no gate state machine, no code path. Corpus gate is binary Apply|Discard only.

Requirements

  • Binary mandatory gate; no third silent path (close / navigate-away without choice).
  • Discard leaves primary snapshot and git status untouched.
  • Apply semantics for Phase C: view-merge only (disk writes are Phase D).

Exit

VERSIONING §7.2 clean-omit verification passes end to end on the spike.

Depends on

Sandbox substrate issue (Phase C trunk).

Refs

docs/VERSIONING.md §3 Gate tier · README.md Gating · frontier array build/run/debug mapping

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestphase-cGHM2 Phase C — sandbox substrate (trunk)vision-varianceGap between README/GHM2 vision and current code

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions