feat: adopt local SQLite engineering memory and quality gates

This commit is contained in:
2026-11-22 14:39:00 +00:00
parent f5d5db73c2
commit 218c060b94
228 changed files with 28728 additions and 1161 deletions
+6 -4
View File
@@ -1,7 +1,7 @@
# EPIC contract
An EPIC is a Work with `epic: true` and a versioned definition under
`epic/<Work ID>.md`. Ordinary schema-1 Works default to `epic: false`; reads never
An EPIC is a Work with `epic: true` and a versioned typed SQLite policy.
The legacy file backend uses `epic/<Work ID>.md`. Ordinary schema-1 Works default to `epic: false`; reads never
rewrite them. Definition revisions retain SHA-256-linked snapshots under
`epic/.history/<Work ID>/`. Links point to project-scoped Work IDs, not source repos.
@@ -50,9 +50,11 @@ editing links/scopes and reviewing authorization again.
`epic check` is read-only. `epic reconcile` deterministically repairs missed
propagation from canonical child state, including after interruption between child
and parent writes. Repeated notifications do not duplicate completion or receipts.
No server, message broker, database or agent invocation is used. Invalid histories,
SQLite is embedded; no server, message broker or agent invocation is used. Invalid histories,
missing links and unsafe paths are diagnosed; arbitrary corrupted files still need
deliberate repair. Publication remains atomic per file, not a global transaction.
deliberate repair. SQLite commits related propagation transactionally; only legacy
files retain per-file publication. Required gates also constrain parent delivery.
New aggregate receipts are structured database facts; old receipt files stay readable.
## CLI