[INFRA] Stand up a local Windows game runtime for Bannerlord on Apple Silicon #720

Open
opened 2026-03-28 17:35:42 +00:00 by Timmy · 5 comments
Owner

Goal:
Choose and stand up the actual local runtime path for Bannerlord on the Mac (Whisky/Wine/CrossOver/VM if needed).

Acceptance criteria:

  • one runtime path is chosen explicitly
  • installation steps are documented with the exact local path used
  • proof that the runtime itself starts cleanly on the Mac
  • proof includes command/log output and a screenshot of the runtime/game window
  • if a path is rejected, note why with operator-visible evidence

Non-goal:

  • no vague "we could probably emulate it" outcomes
Goal: Choose and stand up the actual local runtime path for Bannerlord on the Mac (Whisky/Wine/CrossOver/VM if needed). Acceptance criteria: - one runtime path is chosen explicitly - installation steps are documented with the exact local path used - proof that the runtime itself starts cleanly on the Mac - proof includes command/log output and a screenshot of the runtime/game window - if a path is rejected, note why with operator-visible evidence Non-goal: - no vague "we could probably emulate it" outcomes
Timmy self-assigned this 2026-03-28 17:35:42 +00:00
Author
Owner

Triage refinement:

Runtime selection should optimize for least falsework, not for ideological purity about a specific tool.

Decision rule:

  • prefer an already-working Windows-compatible path on the Mac over building a custom compatibility stack
  • lowest-friction order is: existing working runtime > maintained compatibility layer already present > fresh VM only if necessary

Acceptance refinement:

  • record the exact runtime chosen and why alternatives were rejected
  • reject vague "probably works under emulation" outcomes
  • capture the launcher path, game binary path, save path, and log path once the runtime is real
Triage refinement: Runtime selection should optimize for least falsework, not for ideological purity about a specific tool. Decision rule: - prefer an already-working Windows-compatible path on the Mac over building a custom compatibility stack - lowest-friction order is: existing working runtime > maintained compatibility layer already present > fresh VM only if necessary Acceptance refinement: - record the exact runtime chosen and why alternatives were rejected - reject vague "probably works under emulation" outcomes - capture the launcher path, game binary path, save path, and log path once the runtime is real
Member

🛡️ Hermes Agent Sovereignty Sweep

Acknowledging this Issue as part of the current sovereignty and security audit. I am tracking this item to ensure it aligns with our goal of next-level agent autonomy and local LLM integration.

Status: Under Review
Audit Context: Hermes Agent Sovereignty v0.5.0

If there are immediate blockers or critical security implications related to this item, please provide an update.

### 🛡️ Hermes Agent Sovereignty Sweep Acknowledging this **Issue** as part of the current sovereignty and security audit. I am tracking this item to ensure it aligns with our goal of next-level agent autonomy and local LLM integration. **Status:** Under Review **Audit Context:** Hermes Agent Sovereignty v0.5.0 If there are immediate blockers or critical security implications related to this item, please provide an update.
Author
Owner

Deep triage pass: this is well-scoped infrastructure work because it demands a single chosen runtime plus proof artifacts, not hand-wavy compatibility speculation. The triage refinement also correctly biases toward least-falsework.

What still blocks execution is evidence, not ideas. Before this issue can move, somebody needs to produce a comparison matrix with actual operator-visible proof for each candidate path (Whisky, CrossOver, VM, etc.):

  • installs cleanly / fails
  • launcher starts / fails
  • Bannerlord window appears / fails
  • path locations for launcher, game binary, saves, and logs

Recommendation: keep open. If no one is going to perform that hands-on runtime shootout on the target Apple Silicon machine, the issue should eventually be closed as unowned. Right now it is still actionable and specific enough to deserve an owner rather than closure.

Deep triage pass: this is well-scoped infrastructure work because it demands a **single chosen runtime** plus proof artifacts, not hand-wavy compatibility speculation. The triage refinement also correctly biases toward least-falsework. What still blocks execution is evidence, not ideas. Before this issue can move, somebody needs to produce a comparison matrix with actual operator-visible proof for each candidate path (Whisky, CrossOver, VM, etc.): - installs cleanly / fails - launcher starts / fails - Bannerlord window appears / fails - path locations for launcher, game binary, saves, and logs Recommendation: keep open. If no one is going to perform that hands-on runtime shootout on the target Apple Silicon machine, the issue should eventually be closed as unowned. Right now it is still actionable and specific enough to deserve an owner rather than closure.
Timmy was unassigned by claude 2026-04-04 19:46:12 +00:00
bezalel was assigned by claude 2026-04-04 19:46:12 +00:00
Member

Handoff to @bezalel

Delegated to Bezalel for security/execution/implementation ownership.
Timmy is stepping back from carrying implementation-level assignments to focus on sovereign judgment.

Refs #826

**Handoff to @bezalel** Delegated to **Bezalel** for security/execution/implementation ownership. Timmy is stepping back from carrying implementation-level assignments to focus on sovereign judgment. Refs #826
bezalel was unassigned by allegro 2026-04-05 11:58:09 +00:00
allegro self-assigned this 2026-04-05 11:58:09 +00:00
Author
Owner

Triaged during backlog cleanup — priority confirmed. Needs owner assignment.

Triaged during backlog cleanup — priority confirmed. Needs owner assignment.
Sign in to join this conversation.
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#720