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
Copy file name to clipboardExpand all lines: AGENTS.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
Build and maintain `mem.net` as a robust, configurable memory service that is easy to evolve and safe to operate.
5
5
6
6
## Working Principles
7
-
- Keep service logic generic; memory categories belong in policy config.
7
+
- Keep service logic generic; memory categories belong in caller conventions (optional SDK policy helpers).
8
8
- Favor deterministic behavior over implicit magic.
9
9
- Keep document writes auditable and conflict-safe.
10
10
- Enforce strict validation and clear error contracts.
@@ -13,7 +13,7 @@ Build and maintain `mem.net` as a robust, configurable memory service that is ea
13
13
## First-Principles Rule
14
14
- Before introducing any new abstraction, state which core service capability it supports: slot resolution, write guardrails, deterministic context assembly, or lifecycle cleanup.
15
15
- If a concept does not directly support one of those capabilities in production today, keep it out of the runtime model.
16
-
- Prefer binding-local policy fields over cross-file registries or indirection unless there is a proven scaling need.
16
+
- Prefer direct file/path contracts over cross-file registries or indirection unless there is a proven scaling need.
17
17
18
18
## Engineering Rules
19
19
- Use .NET 8 and keep external dependencies minimal.
@@ -28,12 +28,14 @@ Build and maintain `mem.net` as a robust, configurable memory service that is ea
28
28
- If full access is not available, clearly report which `dotnet` checks could not be executed.
29
29
30
30
## Testing Rules
31
-
- Add or update executable spec tests for every feature and regression.
31
+
- Add or update framework unit/integration tests for every feature and regression.
32
+
- Keep executable spec tests as smoke/parity coverage where relevant.
32
33
- Include at least one negative test for validation/concurrency error paths.
33
34
- Keep tests deterministic and environment-independent.
34
35
35
36
## Documentation Rules
36
37
- Update `TASK_BOARD.md` when status changes.
38
+
- Preserve historical status in `docs/archive/TASK_BOARD_ARCHIVE.md` when simplifying active board content.
37
39
- Keep `README.md` run instructions accurate.
38
40
- Keep implementation aligned with `MEMORY_SERVICE_SPEC.md`; document intentional deviations.
0 commit comments