cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs(ai): record strategy queue evidence

Browse Source
This commit is contained in:
cesnimda
2026-08-09 13:24:26 +02:00
parent a62122640c
commit 89b9cdd92d
10 changed files with 125 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture/durable-operations.md
+4 -2
View File
@@ -1,6 +1,6 @@
# Durable operation state
Updated: 2026-08-02
Updated: 2026-08-09
`UserOperations` is the shared persistence foundation for long-running CV, Strategy Snapshot and later AI work. It is not a workflow engine and carries no raw CV, email, prompt, job description or private note. Producers store only bounded task/policy fields plus an opaque subject reference.
@@ -24,4 +24,6 @@ Terminal notifications are described in `notifications.md`. Authenticated owner
`AiOperationWorker` claims only registered task types by priority, enters the explicit owner scope, rechecks entitlement/privacy/cancellation, runs one inference by default, heartbeats the lease, enforces a timeout, classifies bounded retry/permanent failure and commits the existing terminal notification. Its execution scope carries the rechecked privacy/task decision to the shared sidecar client. Successful and failed provider attempts persist bounded provider/model/route provenance in existing operation fields.
`Workers:AiOperationsEnabled` defaults false and no production feature handler is registered yet. AI-002 supplies sequential local-first routing and a process-local single-model circuit; AI-003/004 add the Strategy/CV handlers and 202 producer endpoints. The current one-worker default is the local-model concurrency limit until PROD-003 benchmarks justify anything else.
`strategy.snapshot` is the first production feature handler. Its producer returns `202`, stores only a bounded job/attachment subject, reuses active work and exposes a context-specific resume lookup. The worker rehydrates owner-filtered data, makes one bounded structured request and publishes one unique `AiWorkspaceNote` only after full response validation. Its GET route is cache-only, so a page read never starts model work.
`Workers:AiOperationsEnabled` still defaults false pending selected-model/browser/MariaDB/restart/production gates. AI-002 supplies sequential local-first routing and a process-local single-model circuit; `strategy.snapshot` is deliberately absent from the external allowlist. AI-004 adds the CV handler. The current one-worker default is the local-model concurrency limit until PROD-003 benchmarks justify anything else.