This preprint presents ARPM, a prototype external-memory system for factual and temporal continuity in long dialogue. Its strongest contribution is not a new psychological personality but an inspectable architecture: stable knowledge and dialogue experience are separated, retrieved through different paths, fused with vector ranking and a BM25-style variant through RRF, decayed over round distance and physical time, unfolded chronologically, and checked through an analysis-before-response protocol. This moves continuity into auditable state, retrieval, prompts, and logs rather than leaving it entirely in weights or context.
In two structured 50-round tests, an automatic rule marks 27/50 answers correct at signal-to-noise 1:5 and 22/50 at 1:200+, while manual review raises them to 50/50 and 40/50. The audit exactly reproduces the arithmetic from released CSVs: 23 and 18 changes, all 0-to-1 and none reversed. The final label is not conventional recall; it jointly judges prompt evidence, support, and answer correctness. Without a second annotator, condition blinding, agreement, or reverse audit, the gap establishes disagreement with the automatic rule, not an unbiased advantage over another system.
The ablation workbook also reconstructs the headlines. History disabled is six questions with four normal labels and two errors, yielding 66.7%. Without hybrid retrieval there are 20 rows: 16 correct, three barely correct, and one wrong; 80% counts only strict correct. H and A2 are 20/20 and anomaly-free. Groups differ in size, date, prompt, preset, and label vocabulary, with no repeats, randomization, seeds, intervals, or inference. These are descriptive log ablations, not precise causal effects.
The cross-model test hands one evolving conversation across models after context clearing against a claimed 5.1-million-Chinese-character novel-noise substrate. The paper states 183 rounds and two excluded timeouts, but the public aggregate and three logs span indexes 1-172. Phase II is a 154-record memory dump, not an eleven-round scoring table that reconciles 183. The denominator is not reproducible. Model, round, topic, accumulated contamination, and difficulty also change together; Qwen2.5 decline, Qwen3/LongCat recovery, and MiniMAX drift are trajectory observations, not causal model comparisons.
“Persona consistency” combines tone, occupation, address form, task and sensory continuity, factual memory, time, and tag compliance. Its A-E scale has no psychometric validation, factor structure, reliability, or human ground truth, and the protocol acknowledges mixed human/model-assisted scoring. The faithful construct is externally supported continuity of facts, references, and style in one trace, not personality, identity, or subjective experience.
The repository is useful and inspectable, but execution reveals defects. Temporal weight exceeds 1 for future timestamps and silently remains 1 for timezone-aware past timestamps; direct tests produced 1.15356 at +24h and 1.0 at timezone-aware -24h. Knowledge uses unnormalized inner product while history uses normalized cosine although both share a documented 0-1 threshold. “BM25+” is a custom shifted-IDF variant. Missing package initializers allowed another storage package to block imports. Paper-era tests pass 9/10 configuration, 9/11 role-validator, and 3/5 isolated retriever tests; failures persist on current main, with no CI or paper tag. Main has drifted to v4.1.
A public experiment note also contains a plaintext API credential, not reproduced here; it should be revoked and purged. Flask lacks authentication, binds to 0.0.0.0, defaults to debug outside Docker, and exposes destructive endpoints; the UI stores the provider key in localStorage. This is a local prototype, not a network-ready service.
Overall, ARPM supports feasible, inspectable factual-temporal continuity. CSVs support manual counts and the workbook supports descriptive labels. The artifact does not establish 183 rounds, causal cross-model comparisons, superiority over other memory/long-context systems, or psychological personality. “Not applicable” availability declarations conflict with the repository, and current main is not the exact submission snapshot.