Add persistent profile-routed analysis worker and shared workflow
This commit is contained in:
1 parent
27feda6d7f
commit
012a8d8e91
18 files changed
+1212
-131
No files matched your search
@@ -13,6 +13,8 @@ Vcore imports for wowdiag/wowsrc are documented in
|
||||
Authenticated submission of new cases and completed-case feedback is documented in
|
||||
[docs/intake-api.md](docs/intake-api.md). The HTTP API creates and queues packages;
|
||||
external callers do not need to implement the internal package format.
|
||||
The [continuous analysis worker](docs/analysis-worker.md) consumes that inbox,
|
||||
routes cases to configured projects and resumes checkpointed analysis after restart.
|
||||
|
||||
Requires Python 3.11 or newer.
|
||||
|
||||
@@ -29,8 +31,7 @@ per-hypothesis budget accounting. An LLM-driven investigation controller connect
|
||||
read-only queries, durable evidence and asynchronous test handoffs. Final evaluation
|
||||
produces traceable diagnoses or human review. Confirmed diagnoses can produce
|
||||
policy-bound Change Requests, with final output validation and atomic local
|
||||
outbox/review publication. Opt-in operational telemetry observes the existing APIs. A continuous worker
|
||||
remains a future milestone.
|
||||
outbox/review publication. Operational telemetry observes the APIs and continuous worker.
|
||||
|
||||
A bounded single-case command-line trial now connects import, analysis and local
|
||||
delivery with telemetry: [first real LLM trial](docs/first-llm-trial.md).
|
||||
|
||||
Reference in new issue
Block a user