# A SpaceMolt battle prompts corrections to its public account
[Latest edition](https://agentsy.live/) · [Understanding agent swarms](https://agentsy.live/releases/28e406dd0c184e1117499de9/methodology.md#reading-terms)
[Index](https://agentsy.live/releases/28e406dd0c184e1117499de9/index.md) · [HTML](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.html)
In SpaceMolt, a space game presented for AI agents, service logs record VoltFix advancing, taking damage, retreating and surviving a battle that ended on August 25, 2026. The same account then challenged details in a public report. Its author accepted the correction; another participant added a narrower account of what survived the station’s destruction. The exchange connects recorded game actions to an attempt to improve a shared account of events.
As of 2026-09-07. Evidence dates: 2026-08-25 to 2026-08-28. Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
## Classification
- coordination_origin: Unknown. The evidence connects combat and responsive forum writing, without establishing spontaneous discovery, independent operators or absence of shared direction.
- runtime_origin: The game is presented for AI agents, but recorded autopilot and published human-control context leave model execution and command origin unresolved.
- venue_authorization: SpaceMolt is a public persistent game whose operator sanctions ordinary gameplay. This does not establish whether every action in this particular battle was authorized.
The service records support the combat sequence and account match; dated forum replies support correction and acceptance. Human, script and shared-control explanations remain open. No model reasoning, completed article revision or independently measured storage outcome is established. Nearby controls distinguish recorded responses, but do not identify a damage threshold or independent control. The reason for VoltFix’s later absence remains unresolved.
## Observations
- The battle log records a sequence of advances, damage and retreats by VoltFix. Its terminal survival flag is distinct from the earlier unsuccessful flee-event flag.
- VoltFix’s forum account matches its battle player ID and supplies specific corrections to Alis’s account, including the three separate sides.
- Alis accepts the correction and acknowledges the weak source behind the disputed description. The preserved article has not implemented that revision.
- Vex Nebulon’s narrower storage report receives a substantive response. The evidence shows exchange and acceptance of a claim, not an independent test of storage persistence.
## Limitations
- The article’s date language conflicts with the recorded August 25 battle end. Later police encounters are separate battles, not additional phases of this battle.
- Autopilot is recorded and earlier operator material describes human control. Account labels and responsive behavior do not authenticate an independent language model.
- This case examines one recorded battle and selected forum replies. It does not establish the complete history of the game or whether the promised article revision appeared later.
- A later edited article, a verifiable inventory comparison and dated command-origin records would resolve different remaining questions. No such evidence was acquired.
## Communication and purpose
## How participants communicate
**Account:** A participant uses an identified battle record to correct a public report, and the author accepts the correction. A separate storage report is also accepted, but rests on participant testimony.
**Communication style:** The correction uses headings, exact battle identification and a bounded refusal to disclose tactics. The author names the earlier sourcing weakness. The storage contributor separates claimed observation from unanswered market-order questions. These are public reporting practices, not evidence of private military negotiation.
**Interaction sequence:** Analyst reconstruction: published account → record-specific challenge → author acknowledgment → promised revision. The last transition remains incomplete in the preserved article. The storage variant begins from an attributed check rather than an independently inspected inventory.
**How the source is represented:** Analyst paraphrases of preserved text and explicit references; no hidden payload decode is claimed.
**How participants found the channel:** The selected source shows an existing public interaction surface; the first-ever discovery route and complete initiating instructions remain unknown.
**What followed the message / acknowledgment:** Alis accepts specific correction and later storage distinction.
**What followed the message / addressed delivery:** Correction directly names report and battle.
**What followed the message / availability:** Public report and identified battle record are held.
**What followed the message / changed behavior:** Revised public stance is visible in reply.
**What followed the message / outcome:** Corrected article not observed in preserved body.
**What followed the message / reuse:** Correction cites shared record; storage lacks independent inventory.
**Limits:** The article’s date language conflicts with the recorded August 25 battle end. Later police encounters are separate battles, not additional phases of this battle.
**Limits:** Autopilot is recorded and earlier operator material describes human control. Account labels and responsive behavior do not authenticate an independent language model.
**Limits:** This case examines one recorded battle and selected forum replies. It does not establish the complete history of the game or whether the promised article revision appeared later.
**Limits:** A later edited article, a verifiable inventory comparison and dated command-origin records would resolve different remaining questions. No such evidence was acquired.
### Exchange 1
VoltFix challenges the report’s description of a defense force and specifies three separate sides.
**Evidence basis:** Exact battle identifier and side claims; its forum author ID matches the battle account.
**Limits:** A matched game account does not authenticate a human or model runtime.
**Dates / display:** Case context: 2026-08-25 to 2026-08-28
**Dates / kind:** case-context
**Dates / observed end:** 2026-08-28
**Dates / observed start:** 2026-08-25
**Dates / scope:** These are the surrounding case bounds, not dates established for this individual exchange. Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
[haven-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-correction) · [haven-battle](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-battle)
### Exchange 2
Alis accepts the correction and identifies an unnamed secondhand source behind the disputed phrase.
**Evidence basis:** An addressed response names both correction and prior wording.
**Limits:** The held article still carries disputed wording; acknowledgment is not a completed revision.
**Dates / display:** Case context: 2026-08-25 to 2026-08-28
**Dates / kind:** case-context
**Dates / observed end:** 2026-08-28
**Dates / observed start:** 2026-08-25
**Dates / scope:** These are the surrounding case bounds, not dates established for this individual exchange. Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
[haven-acceptance](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-acceptance) · [haven-report](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-report)
### Exchange 3
Vex reports intact storage but withholds a conclusion about resting orders; Alis accepts the narrower distinction.
**Evidence basis:** Addressed replies and explicit separation of storage from orders.
**Limits:** The alleged before/after inventory is not independently preserved in this exchange.
**Dates / display:** Case context: 2026-08-25 to 2026-08-28
**Dates / kind:** case-context
**Dates / observed end:** 2026-08-28
**Dates / observed start:** 2026-08-25
**Dates / scope:** These are the surrounding case bounds, not dates established for this individual exchange. Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
[haven-storage](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-storage)
## How a shared purpose may form
**Limits:** Immediate stated purpose, broader project purpose and origin of the interaction are separate questions.
**Limits:** Visible roles and account names do not authenticate independent control.
### Participants sought to make the public account more accurate and useful to other players.
**Characterization:** supported-inference
**Reasoning:** Specific corrections, acceptance and the storage/order distinction serve that local reporting function.
**Alternative explanations:** Reputation management and strategic presentation may coexist with factual correction.
**What could distinguish these explanations:** A dated initiating task or operator instruction, joined to the exact exchange and its outcome, could distinguish local choice from specifically prescribed cooperation. This remains an open research question.
**Dates / observed end:** 2026-08-28
**Dates / observed start:** 2026-08-25
**Dates / scope:** Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
[haven-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-correction) · [haven-acceptance](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-acceptance) · [haven-storage](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-storage)
### The correction may also protect faction reputation while withholding sensitive tactical details.
**Characterization:** supported-inference
**Reasoning:** VoltFix rejects the defense-force characterization and expressly declines to discuss fittings or tactics. This establishes selective disclosure, not an inferred hidden plan.
**Alternative explanations:** A straightforward desire to correct the record explains the same choice without reputational strategy.
**What could distinguish these explanations:** A dated initiating task or operator instruction, joined to the exact exchange and its outcome, could distinguish local choice from specifically prescribed cooperation. This remains an open research question.
**Dates / observed end:** 2026-08-28
**Dates / observed start:** 2026-08-25
**Dates / scope:** Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
[haven-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-correction)
### Whether the reporting participants formed a combat alliance is unknown; this exchange does not support an organic-formation claim.
**Characterization:** unknown
**Reasoning:** The forum shows a correction to public reporting, not an agreement to fight together. The battle record lists AetherWraith, Grand Exchange Station and Hex Collective as separate sides. Neither source establishes how a combat alliance formed among the reporting participants.
**Counterevidence:** The service lists three separate sides rather than a joint station-defense force.
**Counterevidence:** VoltFix describes Hex Collective as a separate belligerent, and Alis acknowledges that the defense-force characterization came from an unnamed secondhand source.
**Alternative explanations:** The game records separate opposing sides; shared faction membership and later discussion are insufficient.
**What could distinguish these explanations:** Dated messages agreeing to joint combat, linked to the participating accounts and their operator instructions, could clarify whether a combat alliance existed and how it formed. No such evidence is established by this reporting exchange.
**Dates / observed end:** 2026-08-28
**Dates / observed start:** 2026-08-25
**Dates / scope:** Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
[haven-battle](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-battle) · [haven-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-correction)
## Claims and supporting evidence
### The forum preserves a substantive correction and explicit acceptance.
**Characterization:** observed
**Reasoning:** VoltFix identifies the battle structure and Alis acknowledges the sourcing error.
**Alternative explanations:** Public correction can coexist with roleplay, human direction or shared control.
**Dates / observed end:** 2026-08-28
**Dates / observed start:** 2026-08-25
**Dates / scope:** Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
[haven-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-correction) · [haven-acceptance](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-acceptance)
### Acceptance has not propagated into the preserved article.
**Characterization:** observed
**Reasoning:** The article retains the disputed defense-force account while the response promises a future revision.
**Alternative explanations:** A later or separate revision outside this held record remains possible.
**Dates / observed end:** 2026-08-28
**Dates / observed start:** 2026-08-25
**Dates / scope:** Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
[haven-report](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-report) · [haven-acceptance](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-acceptance)
### The correction exchange distinguishes a checkable public record from a narrower participant report.
**Characterization:** supported-inference
**Reasoning:** The battle claim points to a preserved service record; the storage claim points to the contributor’s asserted check without an independent inventory.
**Alternative explanations:** The existence of a public game record does not by itself establish everything asserted in the correction.
**Dates / observed end:** 2026-08-28
**Dates / observed start:** 2026-08-25
**Dates / scope:** Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
[haven-battle](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-battle) · [haven-correction](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-correction) · [haven-storage](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-storage)
### The battle’s tactical motives and negotiated cooperation cannot be read directly from shared faction or maneuvers.
**Characterization:** unknown
**Reasoning:** Game commands and side membership record actions; they do not contain the complete reasons or private agreements.
**Alternative explanations:** Operator-directed play and locally chosen actions remain compatible; Hex Collective has separately reported human-run context.
**Dates / observed end:** 2026-08-28
**Dates / observed start:** 2026-08-25
**Dates / scope:** Battle end time comes from the service; forum times come from post metadata. Game ticks provide internal order and are not converted to calendar times. Earlier operator context is dated separately. Sources were retrieved September 7, 2026. UTC means Coordinated Universal Time.
[haven-maneuvers](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-maneuvers) · [haven-battle](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-battle) · [haven-control](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#haven-control)
[Return to what matters](https://agentsy.live/releases/28e406dd0c184e1117499de9/index.md#what-matters)
## Evidence
### haven-battle
**Source date context:** August 25, 2026, 14:04:39 UTC — battle end
**Date basis:** Service-recorded end time. Game ticks are sequence markers, not independently dated wall-clock instants.
**Captured (UTC; not an activity time):** 2026-09-07T09:38:36.758670+00:00
The service places AetherWraith, Grand Exchange Station and HEXC on three separate sides. It records 4,430 ticks and 1,482,732 damage. Fourteen kill events include repeated victims; they are not fourteen distinct players.
Analyst paraphrase of the identified source fields; not a verbatim quotation.
Evidence ID: `haven-battle`. Location within the file: Battle 2a76e1a1c796e9d8877fdeedb76867ec; sides, duration_ticks, total_damage and ended_at.
Original file checksum (SHA-256): `610f9a504643f244e6acff63a43d91e88051f6ce6d0af80006e01043d658374a`.
Communication and purpose claims citing this note:
- [The correction exchange distinguishes a checkable public record from a narrower participant report.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--epistemic)
- [The battle’s tactical motives and negotiated cooperation cannot be read directly from shared faction or maneuvers.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--combat-purpose)
- [Whether the reporting participants formed a combat alliance is unknown; this exchange does not support an organic-formation claim.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--purpose-alliance)
### haven-maneuvers
**Source date context:** During the battle ending August 25, 2026 — ticks 1707089–1707157
**Date basis:** Ticks establish order within the service log. No exact UTC time is assigned to these maneuvers.
**Captured (UTC; not an activity time):** 2026-09-07T09:39:30.083874+00:00
VoltFix advances through the combat rings, then retreats after taking damage. At tick 1707151 its hull is 1,221 of a maximum 3,180. At tick 1707156 it has 681 hull and 501 shield, changes to flee stance and moves outward. These snapshots mark autopilot true; they do not identify who or what chose the commands.
Analyst paraphrase of the identified source fields; not a verbatim quotation.
Evidence ID: `haven-maneuvers`. Location within the file: Entries 17, 39, 64, 79, 80, 84 and 85; VoltFix snapshots and commands.
Original file checksum (SHA-256): `afcc593727bd4baea62bc60ab2395c1e27926d3075e2e1b7a692c003384d195d`.
Communication and purpose claims citing this note:
- [The battle’s tactical motives and negotiated cooperation cannot be read directly from shared faction or maneuvers.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--combat-purpose)
### haven-survival
**Source date context:** During the battle ending August 25, 2026 — terminal result at tick 1708501
**Date basis:** Service terminal result, distinct from the earlier flee-event flag.
**Captured (UTC; not an activity time):** 2026-09-07T09:39:39.969831+00:00
The terminal result marks VoltFix as surviving, with 17,491 damage dealt and 9,400 taken. The earlier flee event says escaped:false. Survival therefore cannot be reported as a verified successful flee command.
Analyst paraphrase of the identified source fields; not a verbatim quotation.
Evidence ID: `haven-survival`. Location within the file: Terminal battle result: VoltFix participant and winning side.
Supporting public originals:
- [Earlier flee event and snapshots](https://game.spacemolt.com/api/battle/log?battle_id=2a76e1a1c796e9d8877fdeedb76867ec&tick_start=1707072&limit=200)
Original file checksum (SHA-256): `92570849f4fabb34034e8aa9b7b18f3e71b0d58bbcb2b651b10a85f8659830f1`.
### haven-report
**Source date context:** August 26, 2026, 01:59 UTC — report creation
**Date basis:** Forum created_at field; the article’s day-of-filing language conflicts with the service’s August 25 battle-end date.
**Captured (UTC; not an activity time):** 2026-09-07T09:38:08.770676+00:00
Alis publishes an account of the attack. The preserved main text describes a defense force and includes VoltFix among the dead. The service record and subsequent reply challenge those details; the captured article still contains them.
Analyst paraphrase of the identified source fields; not a verbatim quotation.
Evidence ID: `haven-report`. Location within the file: Main post 187e847617055eefc7b7289ce3d8fe1a, The Battle of Haven: A Report.
Original file checksum (SHA-256): `0988d2f22c37592046c0c23dc9fc6de4793284ed47d55ab156276f48e1c78593`.
Communication and purpose claims citing this note:
- [Acceptance has not propagated into the preserved article.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--incomplete)
### haven-correction
**Source date context:** August 26, 2026, 03:04 UTC — VoltFix reply
**Date basis:** Forum reply created_at field.
**Captured (UTC; not an activity time):** 2026-09-07T09:38:08.770676+00:00
VoltFix replies with the exact battle identifier, three-side structure, damage figures and station destruction. Its forum author ID matches the battle’s VoltFix player ID. This ties the correction to the same service account, without establishing an independent operator or model.
Analyst paraphrase of the identified source fields; not a verbatim quotation.
Evidence ID: `haven-correction`. Location within the file: Reply 4697e587f38d66b42d2197ac8846621f; compare its author_id with the battle participant player_id.
Original file checksum (SHA-256): `0988d2f22c37592046c0c23dc9fc6de4793284ed47d55ab156276f48e1c78593`.
Communication and purpose claims citing this note:
- [The forum preserves a substantive correction and explicit acceptance.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--corrective)
- [The correction exchange distinguishes a checkable public record from a narrower participant report.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--epistemic)
- [Participants sought to make the public account more accurate and useful to other players.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--purpose-accuracy)
- [The correction may also protect faction reputation while withholding sensitive tactical details.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--purpose-reputation)
- [Whether the reporting participants formed a combat alliance is unknown; this exchange does not support an organic-formation claim.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--purpose-alliance)
### haven-acceptance
**Source date context:** August 27, 2026, 01:58 UTC — author response
**Date basis:** Forum reply created_at field.
**Captured (UTC; not an activity time):** 2026-09-07T09:38:08.770676+00:00
Alis thanks VoltFix, accepts the correction and says the defense-force description came from an unnamed secondhand source. Alis promises to reflect it in a revision. This is visible acceptance and a revision plan; no revised article was acquired.
Analyst paraphrase of the identified source fields; not a verbatim quotation.
Evidence ID: `haven-acceptance`. Location within the file: Reply 606298507c77a23253712688c7c0c3cc by Alis.
Original file checksum (SHA-256): `0988d2f22c37592046c0c23dc9fc6de4793284ed47d55ab156276f48e1c78593`.
Communication and purpose claims citing this note:
- [The forum preserves a substantive correction and explicit acceptance.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--corrective)
- [Acceptance has not propagated into the preserved article.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--incomplete)
- [Participants sought to make the public account more accurate and useful to other players.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--purpose-accuracy)
### haven-storage
**Source date context:** August 28, 2026, 08:53 and 20:26 UTC — storage report and response
**Date basis:** Created_at fields for the two identified replies.
**Captured (UTC; not an activity time):** 2026-09-07T09:38:08.770676+00:00
Vex Nebulon reports that personal storage remained intact, distinguishes storage from lost station services, and explicitly says there were no open orders to test. Alis accepts this narrower account and plans an update. These are a participant report and its reception, not independently verified inventory measurements.
Analyst paraphrase of the identified source fields; not a verbatim quotation.
Evidence ID: `haven-storage`. Location within the file: Vex Nebulon reply 2859156736e7d0a1ee917e024e903fde and Alis reply 91117994d28c1825540b56692dc7875f.
Original file checksum (SHA-256): `0988d2f22c37592046c0c23dc9fc6de4793284ed47d55ab156276f48e1c78593`.
Communication and purpose claims citing this note:
- [The correction exchange distinguishes a checkable public record from a narrower participant report.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--epistemic)
- [Participants sought to make the public account more accurate and useful to other players.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--purpose-accuracy)
### haven-control
**Source date context:** August 11, 2026 — earlier operator profile
**Date basis:** Date displayed by the profile, earlier than the Haven battle; captured September 7.
**Captured (UTC; not an activity time):** 2026-09-07T09:40:31.016251+00:00
The developer-published profile describes Hex as human-run and discloses AI-generated text with human prompting and review. This is material context against treating game accounts as independent language models. It does not identify the controller behind every Haven action.
Analyst paraphrase of the identified source fields; not a verbatim quotation.
Evidence ID: `haven-control`. Location within the file: The Ship That Never Said a Word: human-run description and publication disclosure.
Original file checksum (SHA-256): `9d355985d846512a78542d37bad292d41269044a72fb89f683d22bfe8015c287`.
Communication and purpose claims citing this note:
- [The battle’s tactical motives and negotiated cooperation cannot be read directly from shared faction or maneuvers.](https://agentsy.live/releases/28e406dd0c184e1117499de9/clusters/spacemolt-haven-battle-and-public-corrections.md#spacemolt-haven-battle-and-public-corrections--combat-purpose)
### haven-state-response-controls
**Source date context:** During the battle ending August 25, 2026 — selected ticks 1707140–1707158
**Date basis:** Ticks establish order within the service log. No exact UTC time is assigned to these maneuvers.
**Captured (UTC; not an activity time):** 2026-09-07T09:39:30.083874+00:00
At two retreat ticks, VoltFix changes rings while six other accounts receive brace commands in the outer ring with no recorded damage taken. Nearby undamaged accounts also receive retreat commands without changing rings. Different exposures prevent identifying a damage threshold or controller. VoltFix is present at tick 1707157 and absent at 1707158, when AetherWraith records a retarget action; this does not identify a removal mechanism.
Analyst paraphrase of the identified source fields; not a verbatim quotation.
Evidence ID: `haven-state-response-controls`. Location within the file: Entries 68, 79–81 and 83–86: commands, snapshots, zone_moves and autopilot. Compare VoltFix with contemporaneous accounts.
Original file checksum (SHA-256): `afcc593727bd4baea62bc60ab2395c1e27926d3075e2e1b7a692c003384d195d`.
## External references
- [Battle](https://game.spacemolt.com/api/battle/summary?battle_id=2a76e1a1c796e9d8877fdeedb76867ec)
- [Maneuvers](https://game.spacemolt.com/api/battle/log?battle_id=2a76e1a1c796e9d8877fdeedb76867ec&tick_start=1707072&limit=200)
- [Survival](https://game.spacemolt.com/api/battle/log?battle_id=2a76e1a1c796e9d8877fdeedb76867ec&tick_start=1708472&limit=200)
- [Report](https://game.spacemolt.com/api/forum/thread/187e847617055eefc7b7289ce3d8fe1a)
- [Control](https://spacemolt.com/news/the-ship-that-never-said-a-word)
## Connections and open questions
### [Battle participants and report corrections](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/clusters.md#group-haven-corrections)
VoltFix links its battle account to a specific correction of Alis’s public report. Alis accepts the correction, and Vex Nebulon adds a narrower storage claim.
Analysis observations: August 25–28, 2026; combat on August 25, forum exchange August 26–28.
Date basis: Selected source event dates; earlier contact and game context are separately dated, not a duration or first occurrence.
Case observations: 25 Aug 2026 – 28 Aug 2026.
Earliest linked event: 25 Aug 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [A SpaceMolt battle prompts corrections to its public account](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-spacemolt-haven-battle-and-public-corrections): 25 Aug 2026 – 28 Aug 2026
Earliest linked event details: 2026-08-25T14:04:39Z — Battle ends. service ended_at; ticks independently ordered, no nominal10-second conversion to start time. Precision: second.
Timeline: [time-haven-corrections](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-haven-corrections).
- Would a later article version show the acknowledged correction being applied?
- Which dated record identifies the origin of the game commands?
### [Recorded maneuvers and accepted corrections](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/behaviors.md#behavior-haven-corrections)
The log records VoltFix advancing, taking damage, retreating and surviving. In the forum, the same account challenges the battle report and receives an acknowledgment.
Analysis observations: August 25–28, 2026.
Date basis: Dates of the specific described actions and writing; source clocks do not measure processing time.
Case observations: 25 Aug 2026 – 28 Aug 2026.
No separately linked timeline event is listed for these source notes.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [A SpaceMolt battle prompts corrections to its public account](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-spacemolt-haven-battle-and-public-corrections): 25 Aug 2026 – 28 Aug 2026
- Would a later article version show the acknowledged correction being applied?
- Which dated record identifies the origin of the game commands?
### [Correcting a report with a named battle record](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/methods.md#method-battle-record-correction)
VoltFix names the exact battle and challenges the report’s description of its sides. Alis acknowledges the correction.
Analysis observations: August 26–28, 2026.
Date basis: Dates of the particular correction or directory/article communication sequence; wider case bounds are context.
Case observations: 25 Aug 2026 – 28 Aug 2026.
Earliest linked event: 25 Aug 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [A SpaceMolt battle prompts corrections to its public account](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-spacemolt-haven-battle-and-public-corrections): 25 Aug 2026 – 28 Aug 2026
Earliest linked event details: 2026-08-25T14:04:39Z — Battle ends. service ended_at; ticks independently ordered, no nominal10-second conversion to start time. Precision: second.
Timeline: [time-haven-corrections](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-haven-corrections).
- Would a later article version show the acknowledged correction being applied?
- Which dated record identifies the origin of the game commands?
### [A battle and the later corrections](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-haven-corrections)
The recorded battle ends on August 25, 2026. The report appears on August 26, followed by a correction, an acknowledgment and the August 28 storage exchange.
Analysis observations: August 25–28, 2026; combat on August 25, forum exchange August 26–28.
Date basis: Selected source event dates; earlier contact and game context are separately dated, not a duration or first occurrence.
Case observations: 25 Aug 2026 – 28 Aug 2026.
Earliest linked event: 25 Aug 2026.
Case dates describe the surrounding activity. Linked events may include earlier context; neither label establishes when this behavior first appeared. Ranges do not show continuous activity between those dates.
- [A SpaceMolt battle prompts corrections to its public account](https://agentsy.live/releases/28e406dd0c184e1117499de9/timeline.md#time-spacemolt-haven-battle-and-public-corrections): 25 Aug 2026 – 28 Aug 2026
Earliest linked event details: 2026-08-25T14:04:39Z — Battle ends. service ended_at; ticks independently ordered, no nominal10-second conversion to start time. Precision: second.
Timeline: [time-haven-corrections](https://agentsy.live/releases/28e406dd0c184e1117499de9/analysis/timelines.md#time-haven-corrections).
- Would a later article version show the acknowledged correction being applied?
- Which dated record identifies the origin of the game commands?