What delivery mode was still approved for Ivo's Cobalt project immediately after the August 8 meeting?

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

--- directory: viking://resources/formal/m_eb85892166acc8ef/ source: kind: local uri: /app/.openviking/native/temp/upload/upload_01cf5be1d3384594a19c8291d8c765d5.txt generated_by: component: SemanticProcessor trigger: resource_ingest freshness: total_entries: 1 sampled_entries: 1 unsampled_entries: 0 pending_child_changes: 0 --- # m_eb85892166acc8ef This directory contains a brief informational record about the start of project Cobalt and two configuration choices associated with it. The note states that Ivo started the project on 2026-08-01, with BATCH-1-741 selected for batch delivery and RETRY-1-108 identified as the initial retry policy. It does not explain what the identifiers mean or describe the project, delivery process, or retry behavior in further detail. The material is suitable for readers looking for the recorded date, project name, or configuration identifiers; no intended audience or prerequisite knowledge is specified. ## Directory Coverage There is 1 direct entry, and all entries are represented in the summaries provided. ## Quick Navigation What do you want to learn? - **Find the dated record of the project start** → [m_eb85892166acc8ef.md](viking://resources/formal/m_eb85892166acc8ef/m_eb85892166acc8ef.md) - **Look up the stated batch delivery choice** → [m_eb85892166acc8ef.md](viking://resources/formal/m_eb85892166acc8ef/m_eb85892166acc8ef.md), which records BATCH-1-741. - **Look up the initial retry policy identifier** → [m_eb85892166acc8ef.md](viking://resources/formal/m_eb85892166acc8ef/m_eb85892166acc8ef.md), which records RETRY-1-108. - **Check what context is provided about the project or configuration behavior** → [m_eb85892166acc8ef.md](viking://resources/formal/m_eb85892166acc8ef/m_eb85892166acc8ef.md); the note does not provide further explanations of these topics. ## Detailed Description ### [m_eb85892166acc8ef.md](viking://resources/formal/m_eb85892166acc8ef/m_eb85892166acc8ef.md) This file is a short, dated statement about the start of project Cobalt and two associated configuration choices. It records that Ivo started the project on 2026-08-01. In connection with the project, it states that BATCH-1-741 was chosen for batch delivery and that RETRY-1-108 was the initial retry policy. The note does not define either identifier, explain why these choices were selected, or describe how batch delivery or retry behavior works. It also provides no further details about the project beyond the stated start and configuration information. Accordingly, the file serves as a concise record rather than a tutorial, reference guide, or API document. Readers can use it to retrieve the recorded date, the name Cobalt, and the two identifiers associated with batch delivery and the initial retry policy. The summary does not specify an intended audience or prerequisite knowledge. It also does not establish broader context for the project or explain the implications of the configuration choices, so those details should not be inferred from this note.

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.

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

--- directory: viking://resources/formal/m_f7ff6441bdd98e53/ source: kind: local uri: /app/.openviking/native/temp/upload/upload_07358da9e4124ed690805a9b15a09280.txt generated_by: component: SemanticProcessor trigger: resource_ingest freshness: total_entries: 1 sampled_entries: 1 unsampled_entries: 0 pending_child_changes: 0 --- # m_f7ff6441bdd98e53 This directory contains an operational update dated 2026-08-08 about lost updates associated with outages and a tested recovery approach. The note reports that BATCH-1-741 lost updates during GATE-1-519 outages and that testing REPLAY-1-632 restored the missing updates. It also records an important decision outcome: no change of delivery mode was approved at the meeting. The directory is useful for readers tracking the reported update loss, the replay-based recovery, and the delivery-mode decision. The identifiers are recorded without further technical explanation. ## Directory Coverage There is **1 direct entry**, and **all entries are represented** in the overview. ## Quick Navigation What do you want to learn? - What update loss was reported and what recovery was tested? → [m_f7ff6441bdd98e53.md](viking://resources/formal/m_f7ff6441bdd98e53/m_f7ff6441bdd98e53.md) - What was decided about changing the delivery mode? → [m_f7ff6441bdd98e53.md](viking://resources/formal/m_f7ff6441bdd98e53/m_f7ff6441bdd98e53.md) ## Detailed Description ### [m_f7ff6441bdd98e53.md](viking://resources/formal/m_f7ff6441bdd98e53/m_f7ff6441bdd98e53.md) This brief operational meeting or incident note records an update dated 2026-08-08. It reports that Ivo identified lost updates in BATCH-1-741 during GATE-1-519 outages. The note then describes a tested recovery approach: REPLAY-1-632 restored the missing updates. It does not provide further technical details about the identifiers, the outage conditions, or how replay was performed. The note also distinguishes the recovery result from a delivery-mode decision. Although replay restored the missing updates, the meeting did not approve a change of delivery mode. Thus, the recorded outcome is that the tested replay approach recovered the missing updates, while the delivery mode remained without an approved change in this meeting note. The document does not state whether a change was considered elsewhere or whether any later decision followed. This file is suited to readers who need a concise record of the reported loss and recovery, or who are checking the stated meeting outcome. Its searchable terms include BATCH-1-741, GATE-1-519, REPLAY-1-632, outages, lost updates, replay, and delivery mode. These terms reflect the subjects named in the note; the note itself does not expand on them with additional system descriptions, implementation guidance, or explanations.

# Summary On 2026-08-01, Ivo started 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.

# 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.

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

# Summary On 2026-08-22, Ivo reviewed Cobalt. # 2026-08-22 (Saturday) ChatLog: **user**: 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.

--- directory: viking://user/formal/memories/events/2026/08/01/ generated_by: component: MemoryUpdater trigger: memory_update freshness: total_entries: 4 sampled_entries: 4 unsampled_entries: 0 pending_child_changes: 0 --- # Events Overview - [On 2026-08-01, Ivo chose BATCH-1-741 for batch delivery in Project Cobalt.](./batch_delivery_selected.md) - [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.](./larch_project_started.md) - [On 2026-08-01, Ivo started Project Cobalt.](./project_cobalt_started.md) - [On 2026-08-01, Ivo set RETRY-1-108 as the initial retry policy for Project Cobalt.](./retry_policy_set.md)

# Summary On 2026-08-22, the user reaffirmed that the delivery choice made on 2026-08-15 should remain in effect; the specific choice was not stated. # 2026-08-22 (Saturday) ChatLog: **user**: 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.

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

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.

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.

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

Kestrel-0 approved regional routing table. Columns are region, response window, queue. North | 4 hours | NORTH-0-6a8 South | 12 hours | SOUTH-0-3e5 Rows are independent; do not mix a region with another row.

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.

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.

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.

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

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

User Input: 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. Agent Response: Recorded.

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

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.

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.

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

Kestrel-0 approved regional routing table. Columns are region, response window, queue. North | 4 hours | NORTH-0-6a8 South | 12 hours | SOUTH-0-3e5 Rows are independent do not mix a region with another row.

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

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.

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.

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

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.

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