vasily/GEWU_agent
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: strengthen synthesis grounding and comparisons

Browse Source
This commit is contained in:
vasily committed 2026-10-14 19:42:24 +08:00
1 parent 6c9653866c
commit 3f959c42bb
4 files changed
+23 -20
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

pipelines/synthesize.md
+5 -4
View File
@@ -1,11 +1,12 @@
# Synthesis pipeline
Version 0.1.0. Host-executed procedure for `kb-synthesize`.
Version 0.2.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.
3. For comparison work, select only matrix columns supported by the inputs, cite each populated cell to its accepted record and source revision, and mark unavailable values as unknown. Summarize agreement, disagreement and evidence gaps when useful.
4. Draft the synthesis, preserving methodological conditions and uncertainty. Label interpretive connections and cite their dependencies.
5. Audit material factual statements against the dependency inventory as supported, partially supported, unsupported or conflicting. Check that cited records support the statement as written, retain required locations and freshness warnings, and qualify, remove or surface unsupported and conflicting statements as open questions. If an input changes, invalidate affected draft statements and repeat their audit.
6. 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.