Sage-wiki reconciliation

Type: agentic-system-analyses/types/agentic-system-reconciliation-report.md

Reconciliation

Shared boundary and evidence

All four reports use the revision and run identity fixed by boundary. Their implementation findings refer to SRC-1 in the Source register; none supplies observed execution or causal experiments. The runtime's wired implementation conclusions and the epistemic ledger's implemented architectural classifications concern capacity, not activation. Operation remains uninspected. No source files were read for this reconciliation; the supplied members provide the evidence passages.

Duplicate supersessions and distinct parts

Amendment: EPI-OBJ-source-text is superseded by MEM-OBJ-raw-sources. Both refer to retained raw source/capture markdown, distinguish caller import from model-decomposed capture items, and identify later compilation as a consumer. Identity evidence is their matching filesystem object, producers and consumers, supported by SRC-1 internal/prompts/templates/capture_knowledge.txt, pkg/engine/methods.go and internal/mcp/tools_write.go through the cited records and capture routes. The epistemic object-inventory finding concerns this same retained input, not a separate extraction product. Its unknown source warrant and extraction fidelity remain unchanged; the memory record's warning that a “raw” directory can contain derived candidates remains applicable.

Amendment: EPI-RTE-graph-answer is superseded by MEM-RTE-graph-query. Both identify the local wiki_graph_query branch: hybrid seeds, bounded serialized subgraph, structured completion, citation-integer filtering and returned answer/edge metadata without inspected answer filing. Their evidence is SRC-1 internal/mcp/tools_graph.go and internal/query/graphqa.go; the records retain the serializer and citation-filter passages. The affected epistemic ledger entries distinguish content transformation from citation checking within this same route. They do not establish separate routes or semantic acceptance. Both records retain wired implementation and uninspected operation; neither citation validation nor this supersession warrants the answer prose.

Amendment: EPI-RTE-global-answer is superseded by MEM-RTE-global-query. Both identify the global wiki_graph_query branch, using retained community summaries in map calls, filtering empty/IRRELEVANT partials, reducing the survivors and returning an unfiled answer with community citations. Identity evidence is SRC-1 internal/mcp/tools_graph.go and internal/query/globalqa.go, including the filter/reduce passages supplied by these records. The epistemic content-transformation finding and the memory selector/budget findings concern this one route. Community citations remain lineage information, not checked per-claim support; implementation is wired and operation uninspected in both declarations.

The following overlaps do not establish duplicate identities or require a split of a wrong container:

• MEM-OBJ-articles includes prose and code-built metadata, whereas EPI-OBJ-article-text isolates the prose/definition/self-rated-confidence surface from symbolic selectors. The article container can remain alongside that content part. Both differ from the generation route RT-RTE-compile-sources.
• MEM-OBJ-pending-outputs includes answer files, question/answer text and trust/dependency state. EPI-OBJ-output-text isolates question/answer prose. Neither is the admission route RT-RTE-admit-output, and the valid mixed container need not be superseded.
• MEM-OBJ-communities covers membership/cache metadata and summary artifacts; EPI-OBJ-community-text isolates summary prose. EPI-RTE-community-summary instead identifies production/retention. These are a valid container, content part and route, not three identities for one object.
• EPI-OBJ-relation-text groups evidence spans and entity descriptions, overlapping the prose surfaces of both MEM-OBJ-relations and MEM-OBJ-entities. EPI-OBJ-relation-state isolates structured graph/provenance state. None is coextensive with either mixed memory object. The supplied records distinguish prose consumption, identity/traversal and temporal selection; a wholesale supersession would discard those distinctions.
• MEM-OBJ-manifest retains source/concept lineage, not queue leases/pass progress in RT-OBJ-compile-items. MEM-OBJ-vectors retains selector representations, not the provider component RT-CMP-embedder. MEM-OBJ-entries and MEM-OBJ-summaries have no runtime object counterparts.
• MEM-OBJ-learnings is the retained learning-entry result of the broader caller-write route RT-RTE-write-article, not a second declaration of that route. MEM-OBJ-entity-aliases and MEM-RTE-resolve-aliases are decision state and its maintenance route, not generic compilation under new names.

The epistemic source-count, article-cleanup, quality-score, quality-rewrite, span-check, edge-supersession and community-summary routes explicitly retain RT-RTE-compile-sources as their container. The workflow annotation adds progression and delivery findings to that same runtime record without declaring another identity. These parts and the valid container remain distinct; none calls for superseding the compile route. The three answer routes are also distinct: document/article synthesis and filing in RT-RTE-query-answer, local edge answering and global community answering select different evidence and have different persistence contracts.

EPI-RTE-answer-agreement is an on-filing comparison part of output admission. EPI-RTE-grounding-check and EPI-RTE-verify-promote identify standalone Verify evaluation and disposition. They reuse state/promotion machinery but are not duplicate declarations of the runtime container or of one another. EPI-RTE-output-withdrawal spans source withdrawal and additional resolve/clean controls; it is not coextensive with that container. The style check, style fix and benchmark judge have no runtime record counterparts. The three epistemic public claims concern graph grounding, quarantine and contradiction handling; none duplicates RT-CLM-review-order, which concerns explicit promotion ordering.

Integration dispositions and independent convergence

Additional answer routes. Memory's first integration issue and the epistemic coverage account independently extend the runtime's detailed inventory with local/global graph answering. The supersessions above connect the duplicate specialist declarations. They do not turn the runtime's selected account into a claim that document Q&A is the sole shipped answer route.

Learning-consumer uncertainty. RT-RTE-write-article leaves learning-store consumers untraced. MEM-OBJ-learnings records bounded production-caller searches and the unfilled article-template slot; the epistemic coverage likewise declines to infer an active feedback loop from that slot. Storage/recall capability and unknown external use remain, while native lesson-to-article delivery is not established. The runtime does not assert the wired consumer the memory finding would contradict. No supersession or conflict is required.

Answer provenance. Memory's query annotation adds fallback-neighbor source-path omissions to the runtime's pre-budget chunk-ID limitation in RT-RTE-query-answer. These qualify different provenance surfaces: returned chunk IDs need not equal delivered content, and returned source paths need not enumerate it. MEM-OBJ-pending-outputs and EPI-RTE-grounding-check consequently describe dependency checks against recorded/current sources, not a complete original-context snapshot. No supplied finding requires complete provenance.

Community freshness and selection. MEM-OBJ-communities and EPI-RTE-community-summary converge on member-hash/model cache reuse and leave complete edge-change invalidation unestablished. Memory's implemented highest-single-summary fallback in MEM-RTE-global-query corrects an older source comment, not a contrary specialist finding. The epistemic account does not assert the comment's narrower fallback.

Scribe delivery. RT-RTE-scribe-session establishes filtered transcript-to-ontology updates but leaves exact later delivery unresolved. Memory adds explicit ontology-tool traversal while MEM-OBJ-entities distinguishes pathless definitions from article hits. This supplies a particular consumer without establishing general article-Q&A delivery; the epistemic ledger's bounded later-ontology-consumer finding remains compatible.

Publication, acceptance and recovery. The workflow account, compile record and epistemic quality records converge on publication before conditional scoring, one possible fresh rewrite, and possible publication despite a low final score. Workflow adds that completion flags can advance despite individual article errors. Runtime interruption/resumption findings do not promise repair of every failed article. Output trust is a different path: RT-CLM-review-order is locally scoped, and RT-RTE-admit-output already retains the automatic earlier-confirmation exception. The epistemic acceptance finding in EPI-RTE-verify-promote is conditional proxy acceptance for future answer reuse, not universal quarantine, truth certification or a global atomic publication guarantee.

Disagreements and remaining limits

No unresolved cross-report disagreement is identified in the supplied versions. No correction answers or declined objections were supplied for this attempt. The memory integration issues above add consumers, qualifications or distinct parts rather than contradicting findings on which another report depends. Public-claim/implementation mismatches retained in the epistemic comparison are source-system claim comparisons, not disagreements between analysts.

Uninspected batch semantics, backend parity, deep restoration, full lint consumption, additional evaluator drivers, provider internals and deployed host behavior remain limits where the declaring reports place them. They prevent system-complete equivalence, recovery, warrant and benefit conclusions; they neither erase the bounded implemented routes nor establish absent behavior. No unresolved split requiring an undeclared part is asserted by this reconciliation, and no report's status or substantive finding is replaced here.