@try-works/dsh-recursive-mode 0.6.0 → 0.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -90,8 +90,13 @@ export declare const DEFAULT_ENFORCEMENT: EnforcementConfig;
90
90
  * active phase must be locked before proceeding to next phase*: `'lock-order'` refuses
91
91
  * locking ahead, `'phase-order'` refuses WRITING ahead. Two labels rather than one,
92
92
  * because the guard log has to tell the owner which of the two the agent attempted.
93
+ *
94
+ * `'memory-read'` is the third WRITE-side rule and the owner's other requirement, verbatim: *the memory must
95
+ * be read before writing requirements.md*. It rides the same write-tool family as `'phase-order'` (see
96
+ * `memoryReadRule` in `policy-globs.ts`) and is listed here because this union is what the guard's decision
97
+ * record is typed by — a label the record's type does not know is a label the log cannot honestly carry.
93
98
  */
94
- export type GuardRule = 'lock-order' | 'phase-order' | 'tdd-evidence' | 'locked-write' | 'transition' | 'none';
99
+ export type GuardRule = 'lock-order' | 'phase-order' | 'memory-read' | 'tdd-evidence' | 'locked-write' | 'transition' | 'none';
95
100
  /** T15: the transition gate's verdict as attached to a decision (advisory only). */
96
101
  export interface GuardTransition {
97
102
  passed: boolean;