[PORTAL] Add honest local Bannerlord readiness/status to the Nexus #724

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

Goal:
Represent Bannerlord honestly in the Nexus as it moves from downloaded → runnable → harness-usable.

Acceptance criteria:

  • Nexus exposes Bannerlord state clearly (downloaded, runtime ready, launched, harness-bridged, blocked, etc.)
  • no fake "online" state before the local runtime is real
  • screenshot proof from the Nexus UI plus CLI/log proof from the local setup
  • final card/portal should tell Alexander whether he can meaningfully drop in now

This issue closes the loop between local setup and visible portal truth.

Goal: Represent Bannerlord honestly in the Nexus as it moves from downloaded → runnable → harness-usable. Acceptance criteria: - Nexus exposes Bannerlord state clearly (downloaded, runtime ready, launched, harness-bridged, blocked, etc.) - no fake "online" state before the local runtime is real - screenshot proof from the Nexus UI plus CLI/log proof from the local setup - final card/portal should tell Alexander whether he can meaningfully drop in now This issue closes the loop between local setup and visible portal truth.
Timmy self-assigned this 2026-03-28 17:35:48 +00:00
Author
Owner

Triage refinement:

Nexus guardrail:

  • this issue must not turn into Bannerlord-specific shell bloat
  • keep the portal/status layer honest and minimal
  • respect the repo's hard 10-line net-addition discipline and anti-builder posture

What belongs here:

  • truthful state labels like downloaded / runtime ready / launched / harness-bridged / blocked
  • clear operator legibility about whether Bannerlord is meaningfully droppable-in right now

What does NOT belong here:

  • growing runtime-specific control code
  • invented world simulation
  • decorative claims of readiness before the local runtime and bridge are real
Triage refinement: Nexus guardrail: - this issue must not turn into Bannerlord-specific shell bloat - keep the portal/status layer honest and minimal - respect the repo's hard 10-line net-addition discipline and anti-builder posture What belongs here: - truthful state labels like downloaded / runtime ready / launched / harness-bridged / blocked - clear operator legibility about whether Bannerlord is meaningfully droppable-in right now What does NOT belong here: - growing runtime-specific control code - invented world simulation - decorative claims of readiness before the local runtime and bridge are 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
Analyzed: This issue is not stale. URL: http://143.198.27.163:3000/Timmy_Foundation/the-nexus/issues/724
Author
Owner

Automated triage pass (OpenAI Wolf Pack) — detailed review

Read-back summary: Goal: Represent Bannerlord honestly in the Nexus as it moves from downloaded → runnable → harness-usable. Acceptance criteria: - Nexus exposes Bannerlord state clearly (downloaded, runtime ready, launched, harness-bridged, blocked, etc.) - no fake "online" state before the local runtime is real - screenshot proof from the Nexus UI plus CLI/log proof from the local setup - final…
Issue classification: feature/enhancement
Signals: state=open | age≈6d | last activity≈0d | comments=3 | labels=none | assignees=['Timmy']
Discussion signal: Latest comment by @Timmy 0d ago: "Analyzed: This issue is not stale. URL: http://143.198.27.163:3000/Timmy_Foundation/the-nexus/issues/724"
Triage decision: Still actionable. Recommend posting updated scope + acceptance criteria and assigning an owner so this can move from discussion into execution.

If any context above is outdated, reply with the latest status and this triage can be refreshed quickly.

Automated triage pass (OpenAI Wolf Pack) — detailed review **Read-back summary:** Goal: Represent Bannerlord honestly in the Nexus as it moves from downloaded → runnable → harness-usable. Acceptance criteria: - Nexus exposes Bannerlord state clearly (downloaded, runtime ready, launched, harness-bridged, blocked, etc.) - no fake "online" state before the local runtime is real - screenshot proof from the Nexus UI plus CLI/log proof from the local setup - final… **Issue classification:** feature/enhancement **Signals:** state=open | age≈6d | last activity≈0d | comments=3 | labels=none | assignees=['Timmy'] **Discussion signal:** Latest comment by @Timmy 0d ago: "Analyzed: This issue is not stale. URL: http://143.198.27.163:3000/Timmy_Foundation/the-nexus/issues/724" **Triage decision:** Still actionable. Recommend posting updated scope + acceptance criteria and assigning an owner so this can move from discussion into execution. _If any context above is outdated, reply with the latest status and this triage can be refreshed quickly._
Timmy was unassigned by claude 2026-04-04 19:46:04 +00:00
ezra was assigned by claude 2026-04-04 19:46:04 +00:00
Member

Handoff to @ezra

Delegated to Ezra for architecture/scoping/visual-design ownership.
Timmy is stepping back from carrying implementation-level assignments to focus on sovereign judgment.

Refs #826

**Handoff to @ezra** Delegated to **Ezra** for architecture/scoping/visual-design ownership. Timmy is stepping back from carrying implementation-level assignments to focus on sovereign judgment. Refs #826
ezra was unassigned by allegro 2026-04-05 17:02:10 +00:00
allegro self-assigned this 2026-04-05 17:02:11 +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#724