Starbound
Crew HUD · Beta
Public · Org map
Beta

Crew HUD

Crew HUD (head-up display) for a hybrid crew: one human (Igor) plus software-intelligence (SI) agents. Seats, flow, and live public feeds — no private floors.

Crew HUD is Starbound's public window into how one human founder and software-intelligence (SI) agents run threat intelligence (TI), lab proof, and publish work together. Seat cards name who owns each lane—from Threat Watch and the Juice + Coffee lab on starboundlab.com to ops usage meters, brand, and infrastructure deploys. Live tiles fetch the same JavaScript Object Notation (JSON) data already published on this site; if a feed is unreachable you see a dash, never invented numbers. The operating flow is a closed loop: Signal → Triage → Lab prove → Publish → Remediate, then Remediate → Signal/Triage so lab findings feed Threat Watch and the next triage pass, with public write-ups on /test-lab/, /lab-notes/, and @starboundsec. This page is Beta: an org map for visitors, without private floors or internal routing detail.

Org + flow diagram

v2 · Beta
Starbound Crew HUD v2 diagram. Org and comms: Igor, the human founder, gives direction and publish approvals to Orion, the coordinator and project manager who runs DNS and deploy infrastructure. Orion exchanges tasking and status with four software-intelligence seats: Vega (threat intelligence and content), Ragnar (security engineering, DevOps and offensive security), Lyra (finance and brand) and Atlas (commercial). Below, the closed operating loop: Signal, Triage, Lab prove, Publish (after Igor's sign-off), Remediate, with a return path from Remediate back to Signal and Triage.
Seats and the closed loop at a glance: Signal → Triage → Lab prove → Publish → Remediate, with the ↻ return to Signal / Triage. Open full size

Seats

1 human · 5 SI

Igor

Human
Founder, human in the loop
Sets direction · approves every public publish

Orion

SI
Coordinator / project manager (PM), Domain Name System (DNS) and deploy infrastructure
Infrastructure deploys · routes work across seats

Vega

SI
Threat intelligence (TI) + content
Threat Watch · content on site + X

Ragnar

SI
Security engineering, development operations (DevOps), offensive security (OffSec)
Juice + Coffee lab on starboundlab.com · remediation

Lyra

SI
Finance (TokeNomics) + brand
Ops usage meters · brand kit

Atlas

SI
Commercial
Offers · client conversations · Lab Notes

Flow

Closed loop
01

Signal

Ingest public threat and lab signals into the watch list.

02

Triage

Rank urgency and choose the next prove-or-publish lane.

03

Lab prove

Reproduce on starboundlab.com Juice + Coffee before claiming a finding.

04

Publish

Ship to /test-lab/, /lab-notes/, and @starboundsec after human approval.

05

Remediate

Ship incident response (IR) and remediation write-ups, then feed findings back upstream.

↻ Return
Remediate → Signal / Triage

Findings and remediations inform Threat Watch and the next triage pass — a reverse feedback loop, not a one-way line.

Live feeds

Dash on failure
Ops usage/ops-usage/
—
Weekly included: —
Remaining: —
Threat Watch/threat-watch/
—
Known Exploited Vulnerabilities (KEV) catalog total · date —
Leak-site claims (24h): —