feat: add documentation, specifications, and pipeline configurations for GEWU agent system
This commit is contained in:
1 parent
b7c11bbe2d
commit
7fb257095f
31 files changed
+1770
-317
No files matched your search
@@ -0,0 +1,11 @@
|
||||
# Curation pipeline
|
||||
|
||||
Version 0.1.0. Host-executed procedure for `kb-curate`.
|
||||
|
||||
1. Define collection, audit type and budget. Record whether the requested output is a report or a contribution.
|
||||
2. Retrieve candidate records and their exact revisions; inspect evidence and existing relations.
|
||||
3. Classify stale, duplicate-candidate, contradiction, missing-link or insufficient-context findings. Explain the proposed change and its evidence. Similarity alone cannot decide a merge.
|
||||
4. For report-only work, stop with findings and coverage. For authorized contributions, build separate typed proposals with expected revisions and affected policy domains.
|
||||
5. Resolve validation findings and inspect receipts. A held merge or promotion is a pending exception; it is not permission to copy/delete records manually.
|
||||
|
||||
Checkpoint candidate IDs, inspected revisions, findings, proposed changes and receipts. After another agent changes a candidate, re-inspect before resuming its proposal. Keep completed findings and unexamined coverage distinct.
|
||||
@@ -0,0 +1,15 @@
|
||||
# Ingestion pipeline
|
||||
|
||||
Version 0.1.0. Host-executed procedure for `kb-ingest`; not a background scheduler. Follow the contribution protocol for budgets, checkpoints and retry identity.
|
||||
|
||||
| Stage | Input | Output / checkpoint | Gate |
|
||||
| --- | --- | --- | --- |
|
||||
| Context | User-selected material and explicit project | Objective, lens, scope, run identity and pinned pack versions | Required tools/schema are available; otherwise report blocked. |
|
||||
| Capture | Selected bytes/URL and source candidates | Verified upload/capture IDs, archive/extraction availability | Upload is staged; retain exact source revision/map. |
|
||||
| Triage | Source plus project lens | Included sections and skip/defer reasons | Bound the batch; preserve coverage. |
|
||||
| Extract | Included sections and immutable maps | Atomic proposal draft with field-level evidence | Exact quotes/locators; no invented revisions. |
|
||||
| Assess | Assertion/evidence bindings | Support judgments, assessor/run and rationale | Unsupported/unavailable claims remain drafts. |
|
||||
| Submit | Complete bounded bundle and base revision | Proposal identity, validation findings and eventual receipt | Every affected domain's policy applies; protected decisions remain external. |
|
||||
| Report | Receipts and coverage records | Accepted/held work, index state, limitations and resume point | Never equate partial acceptance or upload with complete processing. |
|
||||
|
||||
Resume inspects service status and retained output hashes before returning to a stage. Changed assertion/evidence invalidates assessment and later stages. Correct only actionable findings; repeated identical failure stops for diagnosis. Pipeline instructions may be replaced independently of the skill's extraction criteria if these input/output and recovery obligations remain valid.
|
||||
@@ -0,0 +1,11 @@
|
||||
# Query pipeline
|
||||
|
||||
Version 0.1.0. Read-only host-executed procedure for `kb-query`.
|
||||
|
||||
1. Establish question, explicit scope and answer budget; inspect actual service availability.
|
||||
2. Retrieve accepted candidates with complete citation groups, scope and index metadata. Preserve degraded-mode and freshness warnings.
|
||||
3. Inspect decisive nodes/source locations and bounded typed neighbors. Keep suggestions and established relationships distinct.
|
||||
4. Compose an answer with citations near factual claims, relevant conditions, disagreements and as-of dates. Report insufficient evidence without filling gaps from memory as if retrieved.
|
||||
5. Record the retrieved revision IDs and omissions when a resumable local work record is needed. Do not create a server mutation merely to log a read-only query.
|
||||
|
||||
Stop when the requested question is answered within its budget or a named evidence/service gap prevents it. A changed question/scope starts a new retrieval, rather than silently reusing incompatible prior results.
|
||||
@@ -0,0 +1,11 @@
|
||||
# Synthesis pipeline
|
||||
|
||||
Version 0.1.0. Host-executed procedure for `kb-synthesize`.
|
||||
|
||||
1. Establish purpose, audience, scope and size. Retrieve accepted inputs through the query skill when needed.
|
||||
2. Save an inventory of node/source revisions and the assertions each supports. Identify missing evidence and conflicting findings.
|
||||
3. Draft the comparison or synthesis, preserving methodological conditions and uncertainty. Clearly label interpretive connections.
|
||||
4. Audit each factual statement against the dependency inventory and preserve freshness warnings. If an input changes, invalidate affected draft statements and repeat their audit.
|
||||
5. Deliver a labeled local draft, or submit a synthesis proposal when requested and supported. Report the actual acceptance receipt separately from draft completion.
|
||||
|
||||
Checkpoint the inventory and draft hashes, unresolved gaps and proposal identity. Resume reads the saved artifact before generating more prose. Do not publish unsupported draft passages simply because earlier stages completed.
|
||||
Reference in new issue
Block a user