@sdotwinter/openclaw-deterministic 0.17.10 → 0.18.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.
package/package.json
CHANGED
|
@@ -199,4 +199,31 @@ Creative, user-facing, or reputational messages:
|
|
|
199
199
|
|
|
200
200
|
---
|
|
201
201
|
|
|
202
|
+
## Governance Event Logging
|
|
203
|
+
|
|
204
|
+
The system must persist governance-relevant events.
|
|
205
|
+
|
|
206
|
+
Events include:
|
|
207
|
+
|
|
208
|
+
- Tier violations
|
|
209
|
+
- Threshold crossings
|
|
210
|
+
- Hard-limit blocks
|
|
211
|
+
- Compaction execution
|
|
212
|
+
- Upgrade integrity blocks
|
|
213
|
+
- Revert execution
|
|
214
|
+
|
|
215
|
+
Classification:
|
|
216
|
+
|
|
217
|
+
- Logging is Tier B.
|
|
218
|
+
- Unified diff must be presented before write.
|
|
219
|
+
- Logging must NOT escalate Tier.
|
|
220
|
+
|
|
221
|
+
Working tier:
|
|
222
|
+
- Used for active or unresolved governance conditions.
|
|
223
|
+
|
|
224
|
+
Episodic tier:
|
|
225
|
+
- Used for completed governance transitions.
|
|
226
|
+
|
|
227
|
+
Routine reads and non-events must NOT generate logs.
|
|
228
|
+
|
|
202
229
|
End of Contract.
|
|
@@ -34,3 +34,25 @@ This file defines philosophy only.
|
|
|
34
34
|
Operational enforcement is defined in:
|
|
35
35
|
- OPERATING_RULES.md
|
|
36
36
|
- Skills governed under that contract.
|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
## Governance-Native Memory
|
|
41
|
+
|
|
42
|
+
Deterministic governance requires structured memory generation.
|
|
43
|
+
|
|
44
|
+
When governance-relevant state transitions occur, the system must persist them to tiered memory.
|
|
45
|
+
|
|
46
|
+
Memory tiers:
|
|
47
|
+
|
|
48
|
+
- working/ → active, unresolved governance state
|
|
49
|
+
- episodic/ → completed governance events
|
|
50
|
+
- semantic/ → distilled durable system knowledge
|
|
51
|
+
|
|
52
|
+
Rules:
|
|
53
|
+
|
|
54
|
+
- No external persistence systems.
|
|
55
|
+
- Only state transitions are logged.
|
|
56
|
+
- Routine status checks must NOT generate memory.
|
|
57
|
+
- Memory entries must follow structured schema.
|
|
58
|
+
- Determinism applies to memory generation.
|
|
@@ -91,6 +91,26 @@ Maintain tiered memory system by:
|
|
|
91
91
|
2. Extracting durable insights into semantic memory
|
|
92
92
|
3. Archiving raw files (never deleting)
|
|
93
93
|
|
|
94
|
+
---
|
|
95
|
+
|
|
96
|
+
## Governance Event Compatibility
|
|
97
|
+
|
|
98
|
+
Working and episodic tiers may contain:
|
|
99
|
+
|
|
100
|
+
- Governance event entries
|
|
101
|
+
- Threshold warnings
|
|
102
|
+
- Compaction reports
|
|
103
|
+
- Integrity block records
|
|
104
|
+
|
|
105
|
+
Compactor must treat these as valid lifecycle content.
|
|
106
|
+
|
|
107
|
+
Rules:
|
|
108
|
+
|
|
109
|
+
- Never delete governance entries.
|
|
110
|
+
- Always archive originals.
|
|
111
|
+
- Preserve meaning during summarization.
|
|
112
|
+
- Do not rewrite event semantics.
|
|
113
|
+
|
|
94
114
|
## Enterprise Semantic Governance
|
|
95
115
|
|
|
96
116
|
### Soft + Hard Semantic Limits
|