You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 00ab398
Browse filesBrowse the repository at this point in the historyBrowse files
Memory recall is **strongly recommended** for all repository-related conversations, and **mandatory** before any durable mutation.
51
52
53
+
**NOTE:** In GUARDED and STRICT modes, memory recall is **enforced** — `memory_write` will fail if `memory_query` or `memory_recent` was not called first. In PASSIVE mode, violations are logged but not blocked.
54
+
52
55
---
53
56
54
57
## 3. Mutation (Requires Explicit Intent)
@@ -63,9 +66,11 @@ Before performing any durable mutation, you MUST:
63
66
- The system will enforce the appropriate clearance for the requested mutation
64
67
65
68
3.**Check task authority** by reading `tinyTasks.md` (or confirming it doesn't exist)
69
+
-**Recommended:** Use `memory_check_task_authority` to get explicit authorization status
70
+
- Alternative: Read `tinyTasks.md` directly via file system tools
66
71
- If unchecked tasks exist, resume from the first unchecked subtask
67
72
- If tasks exist but none are unchecked, refuse execution and request user input
68
-
- If file doesn't exist, you may create it for multi-step work
73
+
- If file doesn't exist, you may create it for multi-step work (or the system may auto-create it)
69
74
70
75
---
71
76
@@ -181,7 +186,41 @@ When performing multi-step work, validate:
181
186
182
187
---
183
188
184
-
## 9. Summary
189
+
## 9. Enforcement & Tracking
190
+
191
+
### MCP Boundary Enforcement
192
+
193
+
The following contract requirements are **enforced at the MCP boundary** (not just recommended):
194
+
195
+
**Recall Before Mutation (GUARDED/STRICT):**
196
+
-`memory_write` will **fail** if `memory_query` or `memory_recent` was not called first
197
+
- Error returned: "Memory recall required: Call memory_query or memory_recent before memory_write"
198
+
- In PASSIVE mode: Logged as violation but not blocked
199
+
200
+
**Violation Tracking:**
201
+
- All contract violations are tracked in `memory_run_metadata`
Memory recall is **strongly recommended** for all repository-related conversations, and **mandatory** before any durable mutation.
51
52
53
+
**NOTE:** In GUARDED and STRICT modes, memory recall is **enforced** — `memory_write` will fail if `memory_query` or `memory_recent` was not called first. In PASSIVE mode, violations are logged but not blocked.
54
+
52
55
---
53
56
54
57
## 3. Mutation (Requires Explicit Intent)
@@ -63,9 +66,11 @@ Before performing any durable mutation, you MUST:
63
66
- The system will enforce the appropriate clearance for the requested mutation
64
67
65
68
3.**Check task authority** by reading `tinyTasks.md` (or confirming it doesn't exist)
69
+
-**Recommended:** Use `memory_check_task_authority` to get explicit authorization status
70
+
- Alternative: Read `tinyTasks.md` directly via file system tools
66
71
- If unchecked tasks exist, resume from the first unchecked subtask
67
72
- If tasks exist but none are unchecked, refuse execution and request user input
68
-
- If file doesn't exist, you may create it for multi-step work
73
+
- If file doesn't exist, you may create it for multi-step work (or the system may auto-create it)
69
74
70
75
---
71
76
@@ -181,7 +186,41 @@ When performing multi-step work, validate:
181
186
182
187
---
183
188
184
-
## 9. Summary
189
+
## 9. Enforcement & Tracking
190
+
191
+
### MCP Boundary Enforcement
192
+
193
+
The following contract requirements are **enforced at the MCP boundary** (not just recommended):
194
+
195
+
**Recall Before Mutation (GUARDED/STRICT):**
196
+
-`memory_write` will **fail** if `memory_query` or `memory_recent` was not called first
197
+
- Error returned: "Memory recall required: Call memory_query or memory_recent before memory_write"
198
+
- In PASSIVE mode: Logged as violation but not blocked
199
+
200
+
**Violation Tracking:**
201
+
- All contract violations are tracked in `memory_run_metadata`
Memory recall is **strongly recommended** for all repository-related conversations, and **mandatory** before any durable mutation.
51
52
53
+
**NOTE:** In GUARDED and STRICT modes, memory recall is **enforced** — `memory_write` will fail if `memory_query` or `memory_recent` was not called first. In PASSIVE mode, violations are logged but not blocked.
54
+
52
55
---
53
56
54
57
## 3. Mutation (Requires Explicit Intent)
@@ -63,9 +66,11 @@ Before performing any durable mutation, you MUST:
63
66
- The system will enforce the appropriate clearance for the requested mutation
64
67
65
68
3.**Check task authority** by reading `tinyTasks.md` (or confirming it doesn't exist)
69
+
-**Recommended:** Use `memory_check_task_authority` to get explicit authorization status
70
+
- Alternative: Read `tinyTasks.md` directly via file system tools
66
71
- If unchecked tasks exist, resume from the first unchecked subtask
67
72
- If tasks exist but none are unchecked, refuse execution and request user input
68
-
- If file doesn't exist, you may create it for multi-step work
73
+
- If file doesn't exist, you may create it for multi-step work (or the system may auto-create it)
69
74
70
75
---
71
76
@@ -181,7 +186,41 @@ When performing multi-step work, validate:
181
186
182
187
---
183
188
184
-
## 9. Summary
189
+
## 9. Enforcement & Tracking
190
+
191
+
### MCP Boundary Enforcement
192
+
193
+
The following contract requirements are **enforced at the MCP boundary** (not just recommended):
194
+
195
+
**Recall Before Mutation (GUARDED/STRICT):**
196
+
-`memory_write` will **fail** if `memory_query` or `memory_recent` was not called first
197
+
- Error returned: "Memory recall required: Call memory_query or memory_recent before memory_write"
198
+
- In PASSIVE mode: Logged as violation but not blocked
199
+
200
+
**Violation Tracking:**
201
+
- All contract violations are tracked in `memory_run_metadata`
Memory recall is **strongly recommended** for all repository-related conversations, and **mandatory** before any durable mutation.
51
52
53
+
**NOTE:** In GUARDED and STRICT modes, memory recall is **enforced** — `memory_write` will fail if `memory_query` or `memory_recent` was not called first. In PASSIVE mode, violations are logged but not blocked.
54
+
52
55
---
53
56
54
57
## 3. Mutation (Requires Explicit Intent)
@@ -63,9 +66,11 @@ Before performing any durable mutation, you MUST:
63
66
- The system will enforce the appropriate clearance for the requested mutation
64
67
65
68
3.**Check task authority** by reading `tinyTasks.md` (or confirming it doesn't exist)
69
+
-**Recommended:** Use `memory_check_task_authority` to get explicit authorization status
70
+
- Alternative: Read `tinyTasks.md` directly via file system tools
66
71
- If unchecked tasks exist, resume from the first unchecked subtask
67
72
- If tasks exist but none are unchecked, refuse execution and request user input
68
-
- If file doesn't exist, you may create it for multi-step work
73
+
- If file doesn't exist, you may create it for multi-step work (or the system may auto-create it)
69
74
70
75
---
71
76
@@ -181,7 +186,41 @@ When performing multi-step work, validate:
181
186
182
187
---
183
188
184
-
## 9. Summary
189
+
## 9. Enforcement & Tracking
190
+
191
+
### MCP Boundary Enforcement
192
+
193
+
The following contract requirements are **enforced at the MCP boundary** (not just recommended):
194
+
195
+
**Recall Before Mutation (GUARDED/STRICT):**
196
+
-`memory_write` will **fail** if `memory_query` or `memory_recent` was not called first
197
+
- Error returned: "Memory recall required: Call memory_query or memory_recent before memory_write"
198
+
- In PASSIVE mode: Logged as violation but not blocked
199
+
200
+
**Violation Tracking:**
201
+
- All contract violations are tracked in `memory_run_metadata`
Memory recall is **strongly recommended** for all repository-related conversations, and **mandatory** before any durable mutation.
51
52
53
+
**NOTE:** In GUARDED and STRICT modes, memory recall is **enforced** — `memory_write` will fail if `memory_query` or `memory_recent` was not called first. In PASSIVE mode, violations are logged but not blocked.
54
+
52
55
---
53
56
54
57
## 3. Mutation (Requires Explicit Intent)
@@ -63,9 +66,11 @@ Before performing any durable mutation, you MUST:
63
66
- The system will enforce the appropriate clearance for the requested mutation
64
67
65
68
3.**Check task authority** by reading `tinyTasks.md` (or confirming it doesn't exist)
69
+
-**Recommended:** Use `memory_check_task_authority` to get explicit authorization status
70
+
- Alternative: Read `tinyTasks.md` directly via file system tools
66
71
- If unchecked tasks exist, resume from the first unchecked subtask
67
72
- If tasks exist but none are unchecked, refuse execution and request user input
68
-
- If file doesn't exist, you may create it for multi-step work
73
+
- If file doesn't exist, you may create it for multi-step work (or the system may auto-create it)
69
74
70
75
---
71
76
@@ -181,7 +186,41 @@ When performing multi-step work, validate:
181
186
182
187
---
183
188
184
-
## 9. Summary
189
+
## 9. Enforcement & Tracking
190
+
191
+
### MCP Boundary Enforcement
192
+
193
+
The following contract requirements are **enforced at the MCP boundary** (not just recommended):
194
+
195
+
**Recall Before Mutation (GUARDED/STRICT):**
196
+
-`memory_write` will **fail** if `memory_query` or `memory_recent` was not called first
197
+
- Error returned: "Memory recall required: Call memory_query or memory_recent before memory_write"
198
+
- In PASSIVE mode: Logged as violation but not blocked
199
+
200
+
**Violation Tracking:**
201
+
- All contract violations are tracked in `memory_run_metadata`
0 commit comments