MemWiki reconciliation
Type: agentic-system-analyses/types/agentic-system-reconciliation-report.md
Reconciliation
All four reports use the frozen source and evidence layers in the boundary Source register. This reconciliation connects the supplied records without changing their values or judging their support. No correction answers, refusal or prior reconciliation were supplied. No source files were read for this reconciliation.
Duplicate identities and retained containers
Amendment: EPI-OBJ-hot is superseded by MEM-OBJ-hot. Both denote the same .memory/wiki/hot.md at the reviewed revision: Markdown project state and next-step guidance, consumed first by the external coding agent. Both retain the same ingestion-completion passage. The epistemic inventory and ledger's references to this object concern the memory record's retained context, not a second store. Supersession changes no finding about freshness, provenance or observed consumption. SRC-1, .memory/wiki/hot.md, AGENTS.md.
Amendment: EPI-OBJ-index is superseded by MEM-OBJ-index. Both denote .memory/wiki/index.md, the Markdown directory interpreted by the external agent for conditional page selection. The epistemic record supplies the actual six-link enumeration; the memory record distinguishes routing metadata from referenced knowledge. Their findings about the missing landscape/competitor links apply to the same directory. This is not an acceptance mechanism or a duplicate of the protocol files. SRC-1, .memory/wiki/index.md, .memory/wiki/log.md, AGENTS.md.
Amendment: EPI-OBJ-log is superseded by MEM-OBJ-log. Both denote .memory/wiki/log.md, retained prose reporting work and ingestion, subsequently available for history reading and fold. Both preserve its claimed landscape/competitor index update. The epistemic object inventory and fold ledger therefore address the memory record's already-derived history, not a raw execution trace. Neither record authenticates the reported production route. SRC-1, .memory/wiki/log.md, AGENTS.md.
Amendment: EPI-RTE-wiki-lint is superseded by MEM-RTE-wiki-lint. Both denote the same /memwiki-lint branch: user chat request, host-agent diagnosis of outdated information, missing hot context or empty pages, then proposed fixes. Both retain implementation status claimed and operation status uninspected. The epistemic record's evaluator domain and advisory chat-result authority concern this same route; they do not establish a separate check or an acceptance transition. Its ledger and health-claim comparison remain bounded by the proposal-versus-fix uncertainty in the memory record. SRC-1, AGENTS.md, README.md; the command passage is retained in the epistemic record and RT-RTE-agent-commands.
Amendment: EPI-RTE-log-fold is superseded by MEM-RTE-log-fold. Both denote /memwiki-fold: the foreground model selects older log entries and condenses them into retained summary prose while being instructed to preserve crucial history. Both retain implementation status claimed and operation status uninspected. The epistemic ledger's indeterminate semantic relation and later-context authority concern this same transformation. Supersession establishes neither fidelity nor downstream activation. SRC-1, AGENTS.md, .memory/wiki/log.md; the exact command passage is retained in the epistemic record and RT-RTE-agent-commands.
EPI-OBJ-domain-pages is a valid four-page container overlapping MEM-OBJ-domain-pages, which covers stack/patterns/bugs, and MEM-OBJ-decisions, which separately covers decisions and rationale. Identity with either individual memory record is ruled out because the path sets differ. The two memory records together cover its entire path set; no required page part is missing. The combined epistemic record already identifies rationale and the bug placeholder, and its findings do not become wrong merely because memory separates decisions. It therefore remains alongside those parts without split supersession. SRC-1, .memory/wiki/stack.md, .memory/wiki/patterns.md, .memory/wiki/bugs.md, .memory/wiki/decisions.md.
RT-RTE-agent-commands remains a valid maintenance container. MEM-RTE-repository-ingest, the lint records and the fold records are declared branches, not replacements for its dispatch identity. All three branches are represented. Ingestion's operation status claimed, based on the attributed log entry, does not upgrade the container's uninspected operation status to observed execution or establish execution of lint/fold. The differing scope and evidence do not constitute a disagreement. SRC-1, AGENTS.md, .memory/wiki/log.md.
No other identity is established. MEM-OBJ-raw is an input directory with unresolved deployed payloads, not the session route or a derived page. RT-OBJ-protocol-files contains installed obligations and hooks, not wiki contents. RT-BAP-host-protocol is their consumer/channel/force/horizon, not the files or the primary-truth claim. EPI-CLM-primary-truth, EPI-CLM-project-memory, EPI-CLM-health-fixes and RT-CLM-safe-update concern different claimed operations or warrant. EPI-ABS-acceptance-gate assesses a bounded absence rather than re-declaring a route. Workflow declares no records; its annotations supplement runtime routes. SRC-1, src/index.ts, AGENTS.md, CLAUDE.md, README.md.
Cross-report connections and integration dispositions
Runtime's deterministic installation/update routes connect to memory's mutable project pages through the external host session, not through an executable synthesis service. Workflow's session annotation traces the same file handoff: hot/log writes at task end, then hot-first and conditional domain reading in a later session. Epistemic separately classifies retention and operational reliance without acceptance. These accounts converge on different aspects of RT-RTE-agent-session, not on a demonstrated successful run. SRC-1, AGENTS.md, CLAUDE.md; runtime retains the session-end and primary-source passages.
Memory's dependency contradiction in MEM-OBJ-domain-pages and MEM-OBJ-decisions agrees with runtime's package-account limit and epistemic's domain-object assessment. This is a discrepancy between retained assertions and package metadata, not between analysts. It prevents treating maintained prose as validated truth or package installation as dependency-free; it does not establish a failed lint run. SRC-1, .memory/wiki/stack.md, .memory/wiki/decisions.md, package.json; memory and epistemic retain the relevant passages.
The missing landscape/competitor pages and links are likewise a shared limit of the reported ingestion history. MEM-OBJ-log, MEM-OBJ-index, their epistemic counterparts and workflow's delivery account all distinguish reported updates from surviving routing evidence. None reconstructs the cause or timing of divergence. SRC-1, .memory/wiki/log.md, .memory/wiki/index.md.
Unresolved conflict: MEM-OBJ-index and EPI-OBJ-index, compared with workflow's delivery account and its annotation on RT-RTE-agent-commands, disagree about the frozen index enumeration. Memory says it enumerates the six other starter pages; epistemic retains six links, to hot, log, stack, patterns, bugs and decisions. Workflow says the index lists seven standard wiki pages. The supplied index quotation is the evidence concerned; the seven-page wiki inventory includes the index itself, whereas the other reports describe its outgoing links. This prevents a consistent cross-report statement of how many pages the index lists. It does not invalidate their shared finding that the two reported new links are missing. Reconciliation does not correct workflow's count. SRC-1, .memory/wiki/index.md.
Lint's proposal-versus-fix transition remains a source-level uncertainty shared by MEM-RTE-wiki-lint, EPI-CLM-health-fixes, runtime's maintenance record and workflow's verification account. No report requires an admitted repair or automatic ingestion gate. Fold's semantic-preservation intent similarly coexists with requested textual replacement in both fold records; append-only language is not treated as byte preservation. Neither issue is a cross-report conflict. SRC-1, AGENTS.md, README.md.
Memory alone flags the hot page's completed-ingestion statement beside initial setup tasks. MEM-OBJ-hot leaves intentional outstanding work versus stale context unresolved; the epistemic hot object does not assert freshness, so there is no competing conclusion to settle. Missing raw examples, host implementation, original traces and comparisons limit all reports' lineage, compliance, activation and benefit conclusions. RT-CMP-host-agent keeps model mutability and deployed host controls unresolved. These limits do not conflict with the bounded explicit-acceptance absence in EPI-ABS-acceptance-gate, whose search concerns the shipped CLI/protocol rather than all possible host evaluation. SRC-1, .memory/wiki/hot.md, AGENTS.md, README.md, src/index.ts, src/index.js.