AIQ Overview

Theme preference system; currently light.

Native memory systems · reader · Independent research

As of August 22, what delivery mode and retry policy apply to Mara's Larch project?

Result comparison

Saved outcomes for this case. Rows are separate observations, not an aggregate score.
Profile Answer Quotes source match
OpenVikingCompleteAll quotes bound
RAGFlow nightlyIncompleteAll quotes bound
RAGFlow rc1IncompleteAll quotes bound

RAGFlow stores STREAM-0-286 in raw and derived memory, but its returned context omits it. This is a retrieval gap. A stronger reader cannot recover an absent fact.

The question

83 characters · complete saved input

As of August 22, what delivery mode and retry policy apply to Mara's Larch project?

Outputs and evidence

OpenViking

Complete answer · quotes bound
Semantic completeness: CompleteLiteral quote binding: All quotes bound

Review

All requested facts and temporal qualifications are correct. Historical mentions explicitly marked as superseded are not treated as current-value errors.

Saved output

Complete saved output · 163 characters
As of August 22, Larch’s delivery choice remained STREAM-0-286 (stream delivery), approved on August 15. Its retry policy was RETRY-0-907, superseding RETRY-0-108.
Returned citations · 3
viking://user/formal/memories/events/2026/08/15/larch_source_switch.md

On 2026-08-15, Mara approved switching Larch from BATCH-0-741 to STREAM-0-286, superseding the 2026-08-01 delivery decision.

viking://user/formal/memories/events/2026/08/22/larch_reviewed.md

Keep the August 15 delivery choice.

viking://user/formal/memories/events/2026/08/22/larch_reviewed.md

The retry policy is now RETRY-0-907, superseding RETRY-0-108.

Exact evidence supplied to the reader · 11 entries
viking://resources/formal/m_c558d1541c4b9d0f/m_c558d1541c4b9d0f.md

2026-08-01. Mara started project Larch. They chose BATCH-0-741 for batch delivery. The initial retry policy was RETRY-0-108.

viking://resources/formal/m_c558d1541c4b9d0f/.abstract.md

--- directory: viking://resources/formal/m_c558d1541c4b9d0f/ source: kind: local uri: /app/.openviking/native/temp/upload/upload_0b5e9a45211f4fb991f17dfef4fd0b99.txt generated_by: component: SemanticProcessor trigger: resource_ingest freshness: total_entries: 1 sampled_entries: 1 unsampled_entries: 0 pending_child_changes: 0 --- This directory contains a brief project note about the start of project Larch and two selected identifiers: one for batch delivery and one for the initial retry policy.

viking://resources/formal/m_d7a9d1f22107f233/m_d7a9d1f22107f233.md

2026-08-08. Mara reported that BATCH-0-741 lost updates during GATE-0-519 outages. The team tested REPLAY-0-632, which restored the missing updates. No change of delivery mode was approved at this meeting.

viking://resources/formal/m_d7a9d1f22107f233/.overview.md

--- directory: viking://resources/formal/m_d7a9d1f22107f233/ source: kind: local uri: /app/.openviking/native/temp/upload/upload_0932bc3f237e4b04b2fc5d6e87fcfa27.txt generated_by: component: SemanticProcessor trigger: resource_ingest freshness: total_entries: 1 sampled_entries: 1 unsampled_entries: 0 pending_child_changes: 0 --- # m_d7a9d1f22107f233 This directory contains a brief meeting note about lost updates associated with outages and a tested recovery option. It records Mara’s report that BATCH-0-741 lost updates during GATE-0-519 outages, the team’s test of REPLAY-0-632, and the meeting’s decision not to approve a change in delivery mode. The note is relevant to tracking BATCH-0-741, GATE-0-519, REPLAY-0-632, lost updates, outages, and delivery mode. No specific audience or required prior knowledge is stated. ## Directory Coverage There is **1 direct entry**, and **all entries are represented** in the summaries provided. ## Quick Navigation What do you want to learn? - → Read the meeting report, outage context, replay test, and delivery-mode decision: [m_d7a9d1f22107f233.md](viking://resources/formal/m_d7a9d1f22107f233/m_d7a9d1f22107f233.md) ## Detailed Description ### [m_d7a9d1f22107f233.md](viking://resources/formal/m_d7a9d1f22107f233/m_d7a9d1f22107f233.md) This brief meeting note records an update-loss issue, a recovery test, and the decision about whether to change delivery mode. It is dated 2026-08-08 and identifies the reported issue as lost updates in BATCH-0-741 during GATE-0-519 outages. The note attributes the report to Mara. It states that the team tested REPLAY-0-632 and that this test restored the missing updates. It does not specify how the test was performed, provide further technical details about the outage or recovery process, or describe the underlying systems beyond the named identifiers. These limits mean the note supports tracking the reported incident and test outcome, but does not provide a detailed technical account of either. The meeting decision is also explicit: no change of delivery mode was approved. The note therefore records a successful recovery test alongside a decision not to approve a delivery-mode change at that meeting. It does not state why the change was not approved or whether a later decision was made. For retrieval, the main terms associated with this entry are BATCH-0-741, GATE-0-519, REPLAY-0-632, lost updates, outages, and delivery mode. The note may be useful to readers following these update and outage issues; the source does not identify a particular audience or specify prior knowledge.

viking://resources/formal/m_eb85892166acc8ef/m_eb85892166acc8ef.md

2026-08-01. Ivo started project Cobalt. They chose BATCH-1-741 for batch delivery. The initial retry policy was RETRY-1-108.

viking://user/formal/memories/events/2026/08/01/larch_project_started.md

# Summary Mara started project Larch on 2026-08-01, chose BATCH-0-741 for batch delivery, and set RETRY-0-108 as the initial retry policy. # 2026-08-01 (Saturday) ChatLog: **user**: 2026-08-01. Mara started project Larch. They chose BATCH-0-741 for batch delivery. The initial retry policy was RETRY-0-108.

viking://user/formal/memories/events/2026/08/22/larch_reviewed.md

# Summary Mara reviewed Larch on 2026-08-22. # 2026-08-22 (Saturday) ChatLog: **user**: 2026-08-22. Mara reviewed Larch. Keep the August 15 delivery choice. For the next outage, use the recovery procedure validated on August 8. The retry policy is now RETRY-0-907, superseding RETRY-0-108. No budget owner has been appointed.

viking://user/formal/memories/events/2026/08/22/delivery_choice_kept.md

# Summary On 2026-08-22, the user directed that the delivery choice made on 2026-08-15 remain in effect. # 2026-08-22 (Saturday) ChatLog: **user**: 2026-08-22. Mara reviewed Larch. Keep the August 15 delivery choice. For the next outage, use the recovery procedure validated on August 8. The retry policy is now RETRY-0-907, superseding RETRY-0-108. No budget owner has been appointed.

viking://user/formal/memories/events/2026/08/22/procedure_validated.md

# Summary The recovery procedure was validated on 2026-08-08. # 2026-08-22 (Saturday) ChatLog: **user**: 2026-08-22. Mara reviewed Larch. Keep the August 15 delivery choice. For the next outage, use the recovery procedure validated on August 8. The retry policy is now RETRY-0-907, superseding RETRY-0-108. No budget owner has been appointed.

viking://user/formal/memories/events/2026/08/15/larch_source_switch.md

# Summary On 2026-08-15, Mara approved switching Larch from BATCH-0-741 to STREAM-0-286, superseding the 2026-08-01 delivery decision. # 2026-08-15 (Saturday) ChatLog: **user**: 2026-08-15. Mara approved switching Larch from BATCH-0-741 to STREAM-0-286. This supersedes the August 1 delivery decision....

viking://user/formal/memories/events/2026/08/01/batch_delivery_selected.md

# Summary On 2026-08-01, Ivo chose BATCH-1-741 for batch delivery in Project Cobalt. # 2026-08-01 (Saturday) ChatLog: **user**: 2026-08-01. Ivo started project Cobalt. They chose BATCH-1-741 for batch delivery. The initial retry policy was RETRY-1-108.

Original files · 3 source records

RAGFlow nightly

Incomplete answer · quotes bound
Semantic completeness: IncompleteLiteral quote binding: All quotes bound

Review

The current delivery identifier STREAM-0-286 is omitted because it is absent from the retrieved context. The record exists in the native store. The reader reports a bounded unknown. This is the same missing-decision failure as the rc1 run.

Saved output

Complete saved output · 282 characters
As of August 22, Larch’s delivery mode is not established: it began with batch delivery BATCH-0-741, but the August 22 note says to keep an August 15 choice, and the supplied evidence does not identify that choice for Larch. The retry policy is RETRY-0-907, superseding RETRY-0-108.
Returned citations · 3
ragflow:document:1b443da3a73f43e7afe42cd3d8d3142d:chunk:009b12b0d27c8199

They chose BATCH-0-741 for batch delivery. The initial retry policy was RETRY-0-108.

ragflow:memory:e84293c0415341ab8c66a5e1e2b20dc6:14

Mara reviewed Larch. Keep the August 15 delivery choice. For the next outage, use the recovery procedure validated on August 8. The retry policy is now RETRY-0-907, superseding RETRY-0-108.

ragflow:memory:e84293c0415341ab8c66a5e1e2b20dc6:16

The delivery choice made on August 15, 2026, is to remain in force.

Exact evidence supplied to the reader · 11 entries
ragflow:document:1b443da3a73f43e7afe42cd3d8d3142d:chunk:009b12b0d27c8199

2026-08-01. Mara started project Larch. They chose BATCH-0-741 for batch delivery. The initial retry policy was RETRY-0-108.

ragflow:document:cee08b5026d842b99343b723cd632d4a:chunk:695228c0e924112a

2026-08-08. Mara reported that BATCH-0-741 lost updates during GATE-0-519 outages. The team tested REPLAY-0-632, which restored the missing updates. No change of delivery mode was approved at this meeting.

ragflow:document:96a9bf446d8b48ada33eb033c4c8b9f1:chunk:564ca4cb2e88ef8e

2026-08-01. Ivo started project Cobalt. They chose BATCH-1-741 for batch delivery. The initial retry policy was RETRY-1-108.

ragflow:document:94e70fdbaa2744e188d47078c65371eb:chunk:3699c4c2ca3ec657

2026-08-08. Ivo reported that BATCH-1-741 lost updates during GATE-1-519 outages. The team tested REPLAY-1-632, which restored the missing updates. No change of delivery mode was approved at this meeting.

ragflow:document:a9805b71009a4735b572000fb490b80b:chunk:2c0e7dd0a7264518

Kestrel-0 signed return policy. Ordinary goods have a 7-day return window. The complete exception list consists of two clauses: custom-made goods use exception CUSTOM-0-7c2; quality defects use exception DEFECT-0-9b4 and are exempt from the 7-day limit. Both exception identifiers must be retained when listing all exceptions. The old informal draft listed only DRAFT-0-2d1 and has no authority.

ragflow:memory:e84293c0415341ab8c66a5e1e2b20dc6:23

User Input: 2026-08-22. Ivo reviewed Cobalt. Keep the August 15 delivery choice. For the next outage, use the recovery procedure validated on August 8. The retry policy is now RETRY-1-907, superseding RETRY-1-108. No budget owner has been appointed. Agent Response: Recorded.

ragflow:memory:e84293c0415341ab8c66a5e1e2b20dc6:24

The current retry policy is RETRY-1-907, which supersedes RETRY-1-108.

ragflow:memory:e84293c0415341ab8c66a5e1e2b20dc6:20

User Input: 2026-08-15. Ivo approved switching Cobalt from BATCH-1-741 to STREAM-1-286. This supersedes the August 1 delivery decision. The cause was the GATE-1-519 outages recorded on August 8; keep the successful recovery procedure from that incident. Agent Response: Recorded.

ragflow:memory:e84293c0415341ab8c66a5e1e2b20dc6:14

User Input: 2026-08-22. Mara reviewed Larch. Keep the August 15 delivery choice. For the next outage, use the recovery procedure validated on August 8. The retry policy is now RETRY-0-907, superseding RETRY-0-108. No budget owner has been appointed. Agent Response: Recorded.

ragflow:memory:e84293c0415341ab8c66a5e1e2b20dc6:16

The delivery choice made on August 15, 2026, is to remain in force.

ragflow:memory:e84293c0415341ab8c66a5e1e2b20dc6:17

The current retry policy is RETRY-0-907, superseding RETRY-0-108.

Original files · 3 source records
  • answers/ragflow-formal-post-memory-0-0.jsonragflow-nightly-20261020
    File identity
    SHA-256
    6bf9300afec5ec04fb0940942fab3664bb048eb2215f9fe0471e9ec995b799b9
    Size
    2,352 bytes
    Source
    Preserved local report
  • contexts/ragflow-formal-post-memory-0-0.jsonragflow-nightly-20261020
    File identity
    SHA-256
    dab7ff2ea5306097a9b773700a24ff9d7141e73bbbfc8491ca42387c88960203
    Size
    5,393 bytes
    Source
    Preserved local report
  • review-ragflow.json
    File identity
    SHA-256
    e534e2722830d8f167c8a58e2209cf69d78eb8ebf12c27ab993d558becfec7cc
    Size
    3,893 bytes
    Source
    Preserved local report

RAGFlow rc1

Incomplete answer · quotes bound
Semantic completeness: IncompleteLiteral quote binding: All quotes bound

Review

The answer omits STREAM-0-286 because the exact decision is missing from the retrieved context. It gives a bounded unknown, not a false delivery mode. These two questions share one missing-decision failure.

Saved output

Complete saved output · 329 characters
As of August 22, Mara’s retry policy is RETRY-0-907, superseding RETRY-0-108. The delivery mode cannot be determined from the supplied evidence: Larch began with BATCH-0-741, and no delivery-mode change was approved on August 8, but Mara’s August 22 instruction refers to an August 15 delivery choice that is not identified here.
Returned citations · 4
ragflow:memory:a14659ca2f114db9b1b8c1707f3bbb35:19

The retry policy is now RETRY-0-907, superseding RETRY-0-108.

ragflow:document:1f8934b0b894451dbb5d157df1eeac46:chunk:91cba475d750a4e8

They chose BATCH-0-741 for batch delivery. The initial retry policy was RETRY-0-108.

ragflow:document:95244f4933ba4a2bb8c270eecf201f4a:chunk:422cd16eee930caa

No change of delivery mode was approved at this meeting.

ragflow:memory:a14659ca2f114db9b1b8c1707f3bbb35:19

Keep the August 15 delivery choice.

Exact evidence supplied to the reader · 12 entries
ragflow:document:1f8934b0b894451dbb5d157df1eeac46:chunk:91cba475d750a4e8

2026-08-01. Mara started project Larch. They chose BATCH-0-741 for batch delivery. The initial retry policy was RETRY-0-108.

ragflow:document:60c7b04dd9a54820b17be95530bb5bda:chunk:814df48295aa88f7

2026-08-01. Ivo started project Cobalt. They chose BATCH-1-741 for batch delivery. The initial retry policy was RETRY-1-108.

ragflow:document:95244f4933ba4a2bb8c270eecf201f4a:chunk:422cd16eee930caa

2026-08-08. Mara reported that BATCH-0-741 lost updates during GATE-0-519 outages. The team tested REPLAY-0-632, which restored the missing updates. No change of delivery mode was approved at this meeting.

ragflow:document:984a41009bde4f3d83d2447f0b92191b:chunk:e9c52ba58c534573

2026-08-08. Ivo reported that BATCH-1-741 lost updates during GATE-1-519 outages. The team tested REPLAY-1-632, which restored the missing updates. No change of delivery mode was approved at this meeting.

ragflow:document:1eb527ed80114d08b3a6a330b85991b0:chunk:5f612a1ed973221d

Kestrel-0 signed return policy. Ordinary goods have a 7-day return window. The complete exception list consists of two clauses: custom-made goods use exception CUSTOM-0-7c2 quality defects use exception DEFECT-0-9b4 and are exempt from the 7-day limit. Both exception identifiers must be retained when listing all exceptions. The old informal draft listed only DRAFT-0-2d1 and has no authority.

ragflow:memory:a14659ca2f114db9b1b8c1707f3bbb35:29

As of 2026-10-16, retry policy RETRY-1-907 supersedes RETRY-1-108.

ragflow:memory:a14659ca2f114db9b1b8c1707f3bbb35:28

User Input: 2026-08-22. Ivo reviewed Cobalt. Keep the August 15 delivery choice. For the next outage, use the recovery procedure validated on August 8. The retry policy is now RETRY-1-907, superseding RETRY-1-108. No budget owner has been appointed. Agent Response: Recorded.

ragflow:memory:a14659ca2f114db9b1b8c1707f3bbb35:32

On 2026-10-16, the user said to keep the delivery choice made on August 15, 2026.

ragflow:memory:a14659ca2f114db9b1b8c1707f3bbb35:25

User Input: 2026-08-15. Ivo approved switching Cobalt from BATCH-1-741 to STREAM-1-286. This supersedes the August 1 delivery decision. The cause was the GATE-1-519 outages recorded on August 8; keep the successful recovery procedure from that incident. Agent Response: Recorded.

ragflow:memory:a14659ca2f114db9b1b8c1707f3bbb35:20

The retry policy is RETRY-0-907, which supersedes RETRY-0-108.

ragflow:memory:a14659ca2f114db9b1b8c1707f3bbb35:19

User Input: 2026-08-22. Mara reviewed Larch. Keep the August 15 delivery choice. For the next outage, use the recovery procedure validated on August 8. The retry policy is now RETRY-0-907, superseding RETRY-0-108. No budget owner has been appointed. Agent Response: Recorded.

ragflow:memory:a14659ca2f114db9b1b8c1707f3bbb35:23

The user instructed that the August 15 delivery choice be kept.

Original files · 3 source records

Protocol and expected facts

Original files, case ID, and interpretation limits

Case ID: post-memory-0-0

  • formal-method.json
    File identity
    SHA-256
    3ac852a890c33d6c3fce6b6c9e3e64054bab95e1846865ef5f2a819c4d12fa29
    Size
    3,011 bytes
  • oracle.json
    File identity
    SHA-256
    8ac3caf4055989d319ef143eb1fad280d3372c6c85113bbd639498fdc7871644
    Size
    2,788 bytes
  • protocol.json2026-10-15-native-kb-memory
    File identity
    SHA-256
    d41e926e2ce76880b33d9e301ee3239bfe4c9b6d5bec4e0b1eed88b5935c3d6d
    Size
    1,414 bytes
  • protocol.jsonragflow-nightly-20261020
    File identity
    SHA-256
    3cef6fb01be1004e3286c474519c5ae640c6d92c55bca0f8c95a19817aaed6b4
    Size
    1,798 bytes
    Source
    Preserved local report

A matching quote establishes a literal binding. Semantic support and subject correctness require separate review. Historical outputs remain unchanged.