🔒 ONYX BLADES SECURE CHANNEL · SYSTEMS REGISTER
GALACTIC
————
ED ⇄ LOCAL
AUTH: —[ SIGN OUT ]
SYSTEMS REGISTER · v3.0
CAPABILITY MANIFEST · WHAT THE BOARD DOES · LAMP = STATUS
Turn ►
AMBER COCKPIT
▶ Registry pull · Southern Draw Actual → all hands · v3.0 · compiled 3312-08-15
Every hull carries a systems register; this is the board’s — and whether you already fly with the Blades or you’re sizing us up from outside, it’s the honest manifest of what we’ve built and where we’re headed. One purpose behind all of it: put the whole squadron’s effort on a single pane of glass — what we’re building, what it’s starving for, where to buy it, and whose name goes on the plaque. Read the lamps: steady green is flight-proven kit, steady amber is fitted and awaiting shakedown, and the breathing violet is still on the drawing board — it glows because we intend it, it fades because it isn’t real yet.
What the Onyx Blades toolset does — for members and anyone weighing up joining. The Blades run a live site for Elite Dangerous that tracks colonisation builds end-to-end (live progress, supplier sourcing, automatic build registration, architect attribution, and per-commander stats), with more game loops on the way. Status lamps: green = verified working, amber = built, awaiting live test, pulsing violet = planned / not built yet.
01
The Flight Deck
What every pilot flies · flight-proven
Closed-Net Access
The board rides a sealed channel — Onyx Blades eyes only. Every page, every download, gated at the perimeter.Cloudflare Access gates every /blades page and the plugin download. Squad emails only, one-time PIN login.
Live Colonisation Board
The wired build on one screen: completion, outstanding tonnage, and how many bellies-full it takes your current ship to finish the job.Live build progress from RavenColonial: % complete, remaining tonnage per commodity, and trip-count math keyed to your live loadout.
Loadout-Aware Trip Counter
The board counts trips in YOUR hull, not a stranger's — swap into a bigger belly and the run-count drops the moment you dock.Trip math uses your live ship's cargo capacity (reported by the plugin), not a fixed Type-9. Recomputes automatically when you swap ships.
Live Ship & Cargo Report
The wing sees what you're flying and how much you can carry, without you saying a word.The Blades Registrar plugin reports your current ship, hold size and used space to the board (MY DASHBOARD current-ship readout + SQUAD HAULERS panel). Newest report wins.
Supplier Targeting
Tap any commodity and the nav computer ranks nearby markets that actually have it — Large pads first, carriers flagged as the moving targets they are. ⧉ beams the system to your cockpit clipboard — and with the galaxy-map assist armed, it goes further: the map opens and the course is laid in for you, live, without you leaving the seat.Per-commodity supplier rankings via the Ardent network: in-stock and Large-pad gated, distance/price scored, fleet carriers and stale data flagged. One tap sends the system name to your own PC clipboard through the plugin. Turn on the galaxy-map assist (per-pilot, off by default) and the same tap instead opens the galaxy map, pastes the system and holds select to plot the route.
Manifest Sort Cycle
The manifest sorts to the job in hand — heaviest need first to triage the haul, A–Z to match the pad, or grouped by market class the way the commodities board reads. One tap cycles it; the deck remembers.A ↕ SORT button on the shipping manifest cycles highest-need → A–Z → market-category grouping and remembers the choice. Category grouping awaiting an in-game cross-check.
Commodity Name Resolver
Every cargo reads true — no more run-together gibberish where the game's shorthand meets the board. The name you see is the name Inara knows.Manifest commodity names resolve through a normalised index of the full commodity table (plus Elite's internal-symbol quirks), so run-together names display correctly and their ↗ Inara links land on the right commodity.
Inara Supplier Cross-Check
A second set of eyes on the trade lanes — one tap opens Inara's ledger for the same cargo, near the same build, when you want to double-check the fleet's own numbers.Each commodity supplier drawer carries an ↗ Inara deep-link to that commodity's sellers near the build system (also shown when Ardent finds nothing or is unreachable). Link-out only — Inara exposes no live market API. Verified live in the drawer against an active build.
Transmit-from-Inara
Chase a supplier on Inara, copy the system, and one glowing button beams it to your cockpit PC — landing on the clipboard, or laid straight into the galaxy map as a plotted course if you fly with the assist armed. Then it's gone, its work done.After an Inara supplier look-up, a ⧉ TRANSMIT SYSTEM → PC button reads the copied system from your clipboard and sends it to your PC via the plugin — to the clipboard, or, with the galaxy-map assist enabled, opening the map and plotting the route outright. It clears itself once sent — and also on ⟳ REFRESH, or after two page loads. There is no timer: left alone on a page you never reload, it stays. Verified.
SQUAD NET Ticker
The wire that never sleeps — build status, most-needed cargo, commander syncs, carrier movements. Rides every console; goes loud when a window is closing.Scrolling status line. On Colonisation and My Stats it carries the squadron feed — build %, most-needed commodity, per-commander hauls, linked carriers — with alert tiers that escalate as a build deadline nears. On the public Home page it carries the four admin-written slots only; squadron data never reaches it.
Cockpit Fittings
Four hull liveries on a rotary dial, a galactic⇄local chronometer, and this very SIGNAL toggle. The ship remembers how you like it.Theme dial (amber / cyan / onyx / jade-green), ED⇄local clock, lore/plain text toggle — all persistent across pages and visits.
02
The Build Registry
Builds, carriers & lifecycle · flight-proven
Squadron Build List
One shared manifest of cohort builds. Pick a build and every console in the fleet shows the same picture.Shared KV-backed build list behind the picker on every page.
Auto-Registration on Landing
Set down at a construction ship with the Registrar relay running and the build walks itself onto the board. No forms, no comms.The Blades Registrar EDMC plugin detects construction-ship dockings and posts the build to the registry automatically. Verified end-to-end.
Build Lifecycle
Builds move from the active line to the honors list when the last tonne lands. Proven the night Moy Engineering Silo went operational.Active vs completed grouping driven by RavenColonial's completion flag — verified live with the Moy build.
Completion Stamping
Finished builds are filed once and remembered — the board stops pestering the fleet net about ships that already flew.First sight of a completed build stamps completion (and architect) into the registry so archived builds skip live lookups.
Standing-Down State + Honors Board
When no build is active the board stands down with dignity — and posts the roll of completed constructions instead of pretending a finished site still needs cargo.With zero active builds the dashboard shows an idle state plus recent completions (name, system, architect, date, tonnage).
Self-Updating Board
The board watches the wire and redraws itself when something actually changes — no more hammering refresh to see a build land or complete. Come back to the tab and it catches up on the spot.Change-detected polling (~60s while visible, instant catch-up on tab return) re-renders on real changes only, using RavenColonial eTags and registry diffs.
Career Service Record
Your dossier now reads across every build the cohort has touched: career tonnage, builds contributed, and your line in each build's log.MY DASHBOARD aggregates tracked hauls across all registry builds with a per-build breakdown and selected-build highlight. Only uplink-tracked deliveries count — the page says so when totals fall short.
Fleet Carrier Watch
Linked carriers show on the board with their sell manifests — mobile stockpiles in the cohort's pocket.Carriers linked to the build in RavenColonial are listed with their sell counts.
Carrier Identity & Affiliation
Every carrier linked to a build named and badged — ours flying squadron colours, outsiders flagged as unaffiliated.Linked carriers show name + call sign, matched by market ID against the squad carrier registry: squad-owned carriers show their owner, the rest are tagged unaffiliated. Verified against live data — every carrier linked to a squadron build resolved to its owner. The unaffiliated branch is sound but has not yet fired: no outside carrier has linked to one of our builds. Note that registry freshness is coarse by nature —
CarrierStats only fires when an owner opens carrier management in-game, so a record reading weeks old is expected, not a fault.Squad Carrier Link
Park a carrier beside a build and call it in from the cockpit — the fleet watches the mobile depot appear, tops it off while it sits, then jumps the whole haul to the construction site. Call it back off the same way you called it in.A pilot links their own fleet carrier to the build they're viewing, straight from the commander deck; the Registrar reads carrier ownership from CarrierStats (live + on the launch backfill) and the board relays the link to RavenColonial, which renders it as a mobile depot. The control is a toggle — click it again on the same site to unlink. Shakedown flown 2026-08-14 with a real carrier: link appeared in RavenColonial, unlink removed it, both confirmed against live project data. ⚠ RavenColonial does not enforce one build per carrier — a carrier can sit on several sites at once, and linking it to a new one does not clear the old. Since a carrier holds one hold of cargo, unlink the site you have left, or its tonnage is offered to both.
Station-Type Override
When the papers say only 'construction site', the quartermaster writes in the real class by hand — Large Industrial, Gia pattern — and every deck reads it true.Admins set a build's real facility type from the console; the board shows it in place of the generic 'Colonisation Construction Site' label. Verified live (Gorbenenko Manufacturing). Hand-set for now — auto-inference is on the drawing board.
03
Attribution & Claims
Architect intelligence · fitted, awaiting shakedown
Claims Ledger
The moment a Blade pays for a system claim, the ledger hears it. From that second, the fleet knows whose name goes on the plaque.The plugin reports ColonisationSystemClaim events (which only fire on the architect's own machine) to a squad claims ledger — first-party architect proof.
Journal Backfill
First light on the new relay, it reads your old flight recorder and files every claim you ever made. History, recovered.On first launch the plugin scans local journal history and reports all past claims — pre-plugin systems get attributed retroactively.
Auto-Create with Attribution
Land at an unregistered site and — after a courtesy grace period — the board cuts the build's papers itself, architect name already on them: ledger first, Raven records second, squad colours as the fallback.Safeguarded auto-create of missing RavenColonial builds, with architect resolved claims-ledger → Raven sibling builds → squad fallback (flagged unverified). In routine use: every build on the squadron list bar the very first was started this way.
Architect Display
Known architects show on the board, pulled from the fleet's shared records.Architect names read from RavenColonial project records and stored with each registry build.
Claim Hot List
The clock is always running on a fresh claim — the net calls out the ones burning down before the primary port is laid.Claims still inside their ~4-week primary-port window ride the Colonisation ticker first — CLAIM EXPIRING for one with no build yet, PRIMARY PORT DUE once a build has started. Red under three days, amber under seven. Colonisation only; the My Stats and Home tickers do not carry it. Cached so it stays cheap as the board fills. Awaiting live shakedown.
Architect Deck
Every architect's own ready-room — see your claims, their countdowns, and set the record straight without troubling the quartermaster.Self-service deck: bind your CMDR once, then see every system you have claimed with its window countdown, fix a mistyped name, mark a primary you have deployed, or release one you have let go — all scoped to your own claims. Reached from the commander deck. Awaiting live shakedown.
04
The Registrar Relay
Self-updating plugin + test-pilot program · newly fitted
Self-Updating Registrar
The relay patches itself in the dark — pulls the new build, checks the seal, swaps it clean, and flies it the moment EDMC comes back up. No reinstall, no zip-hunting.The Blades Registrar plugin auto-updates in place: host-pinned download, SHA-256 verified, atomic swap, applied on the next EDMC restart. Verified end-to-end.
Version Heartbeat
Every relay calls its build number home on a quiet loop, so the board always knows who's current and who's a build behind.The plugin reports its running version to the board on a heartbeat; drives the restart blare and the roster's per-pilot version readout.
Beta Channel & Test Pilots
A shakedown crew flies the next build first — but the ticket is an invitation, not an order. A cleared pilot chooses when to take the new kit up, and can drop back to the line build whenever they like. Pull the ticket and the relay walks them back regardless.Test-pilot status reveals the ⚑ TEST TRACK switch; it does NOT move anyone by itself. Every pilot defaults to the stable build, including test pilots. Arming the switch moves that pilot to the beta channel (any version carrying a letter); disarming it returns them to stable, and they can switch as often as they want. Revoking test-pilot status does auto-downgrade them. Verified live.
RESTART-EDMC Blare
A relay a build behind and the SQUAD NET wire sounds off — tag, border and the words RESTART EDMC pulsing amber-to-fleet — and it won't quit until the new build reports in. No relay at all? COMPLETE SETUP instead.Ticker takeover on every member page blares RESTART EDMC (or COMPLETE SETUP for pre-2.0 / no plugin) until the heartbeat reports the target version, then clears itself. Only the tag, border and keyword flash, so the message stays readable. Verified live.
Roles Console
The quartermaster's crew sheet — grant a pilot their shakedown ticket from a dropdown of the whole roster, take it back with a click.Admin ROLES card assigns test-pilot (and other) roles per commander from a member dropdown; multi-role supported; changes take on the pilot's next heartbeat, and a revoke pushes them back to stable.
One-Click Release Cut · quartermaster's bench· admin only
Not a pilot's control — the armourer's. Ship the build and the console reads its own papers, version and notes lifted straight from the deployed relay, and one button cuts it to the whole fleet or just the shakedown crew.⚙ Admin-only — no pilot sees this. The REGISTRAR RELEASE card on the admin console auto-fills version + suggested notes from the deployed zip's load.py; one click cuts stable (all pilots) or beta (test pilots), SHA-256 hashed. A letter in the version = beta.
Shakedown Checklist
Cleared for shakedown? A ⚑ TEST PILOT chip lights your deck and opens the flight card — what to fly, what to watch, and a switch to sign each item back to the fleet.Test pilots see a ⚑ TEST PILOT chip (gated on real role) linking a shakedown checklist; a Submit reports which items tested good, durably and keyed to you — so re-opening the same checklist restores your own ticks, and items another pilot has confirmed carry a badge. Working; it comes into its own with more than one test pilot, since the point of it is signing findings back to the fleet rather than keeping them to yourself. Carry-over BETWEEN checklists is not built yet.
05
The Command Deck
Admin & leadership · flight-proven
Admin Console + Backup
A command deck behind a locked hatch — the fleet's quartermaster reads the ledger, corrects a mis-filed plaque, waves a new Blade through the airlock, and takes the whole record home in a strongbox. Flown and proven.Admin-gated console at /blades/admin/ (⚙ ADMIN chip on MY DASHBOARD) over the KV registry: raw build & claims editor, orphan/stale/junk detection, live source-pulse, admin roster, and full backup — one-click export → repo, with merge/replace restore. Backups are ON-DEMAND: nothing takes one for you. Lockout-proof (owner is permanent). Live-verified end-to-end.
Admiral's Desk & Home Welcome
The Admiral speaks to every recruit at the front door, and rewrites that greeting from a desk of their own — no keys to the whole ship required.Leadership-tier Admiral's Desk at /blades/admiral/ edits the public home welcome message + signature, surfaced live to signed-out visitors via a public mirror. Admiral role is Desk-only; full admin stays separate.
Squad Access
The airlock roster — an admin waves a new Blade through the perimeter with a single email, or seals it behind them, without ever touching the station's core systems.Admins grant or revoke squadmate site logins straight onto the Cloudflare Access policy from the console — recruits sign in at once by email OTP. Owner & admins are protected from removal. Live-verified.
Squad Broadcast
Four channels on the fleet wire the quartermaster works by hand — galactic headlines, the standing community goal, and two open frequencies for squad word. Old news burns off on a timer so the band never goes stale.Admin-editable ticker slots (GalNet summary, Community Goals, two free-form) with per-slot auto-expiry, scrolling in SQUAD NET across every page. Paste AI summaries; set an expiry and stale news clears itself.
Uplink Field Manual
The five-stage provisioning guide you are standing in, plus the squad-only Registrar download.Setup guide with staged instructions and the gated plugin zip download.
06
The Adjutant
Your unit's standing orders — what the relay does for you in flight · live for every pilot in Registrar 3.0
Honk on Arrival
Drop into a new system and the relay fires the discovery scanner for you — the honk sounds before your hand leaves the stick.Live in Registrar 3.0: on a hyperspace arrival the plugin auto-fires your Discovery Scanner, reading your own fire key from your bindings. Toggle it live from MY DASHBOARD → ◈ ASSIGNMENTS → SERVICE RECORD. Windows; needs a keyboard-bound fire control.
Auto-Plot to Galaxy Map
Tap a supplier on the deck and the cockpit answers — the galaxy map swings open and the system drops into the search, no reaching for the keyboard.Live in Registrar 3.0: on a NAV / Inara send the plugin opens the galaxy map and pastes the system for you. Builds on the nav-to-clipboard bridge. Toggle from ◈ ASSIGNMENTS → SERVICE RECORD; needs a keyboard Open-Galaxy-Map bind.
Fuel Safety Check
The relay watches your tank against the road ahead and calls out before the black leaves you drifting.Live in Registrar 3.0: warns in EDMC when you plot a jump and your fuel is already getting thin — under roughly two jumps' worth at your recent burn rate, or the tank below 20%. It reads your live fuel level and per-jump burn; it does NOT measure the specific jump you plotted, so it cannot tell you that one particular hop would strand you. Toggle from ◈ ASSIGNMENTS → SERVICE RECORD.
Pirate / Cargo-Scan Alarm
A stranger's scanner reaches for your hold — and the deck sounds off before they finish reading your manifest.Live. A hostile hail raises a CRITICAL alert: klaxon on your PC, an RWR-style threat tone and a screen flash on the board, logged to the alerts strip. Real encounters showed a cargo scan is a confirmation rather than a warning — police and pirates both scan, and only the hail comes early — so the scan itself is logged quietly and the hail is what sounds off. Needs no keybinds; it only listens. Toggle from ◈ ASSIGNMENTS → SERVICE RECORD.
Give the Stick Back
An unfocused cockpit is a deaf one — the stick goes quiet the moment you reach for a screen.Windows only. Elite receives nothing from your stick while it is not the foreground window, so this hands focus back: a global hotkey (ctrl+alt+e by default) and an automatic attempt when the pirate alarm fires. It escalates through four methods and reports which one actually won, because Windows does not always grant the foreground to a background process. Toggle from ◈ ASSIGNMENTS → SERVICE RECORD.
Back to the Game When I Act
Send a system to the cockpit and the cockpit answers — you are flying again before you look up.Windows only. After a NAV/Transmit send or an assist toggle, focus returns to Elite — and never while you are simply reading or scrolling the board. An action older than 20 seconds is ignored, so a restart cannot yank you out of the game for a click you made ten minutes ago. Side effect worth having: auto-plot to the galaxy map now fires on those sends, because Elite is focused when it runs. Toggle from ◈ ASSIGNMENTS → SERVICE RECORD.
↵ GAME Control
One switch on the panel that means: I am done here, put me back.A fixed control in the top-right of the board on Colonisation and My Stats, so it is in reach wherever you have scrolled. Explicit, so it works even with the automatic version switched off. It reports SENT rather than done — the board cannot see the Windows foreground and does not pretend to. It disables itself when your plugin is not reporting, and hides itself on a device that turns out not to be your game PC.
07
The Drawing Board
Proposed systems · lamps breathing until they're real
Build-Type Recognition
Every station class eats a different diet. Teach the board to read a depot's manifest like a fingerprint and it can name the structure before the architect says a word.Proposed: infer RavenColonial buildType from the depot's ResourcesRequired commodity profile at auto-create, instead of leaving it blank.
Attribution Badges
A quiet flag on any build whose architect is provisional — and a one-tap way to set the record straight.Proposed: unverified-architect badges in the picker/board plus an in-UI correction flow (data already flows through the API).
Haul Timeline
The build's heartbeat, drawn: hour-by-hour delivery pulses from first tonne to gone-operational.Proposed: delivery sparklines from RavenColonial's hourly stats buckets, per build and per commander.
Squad Urgent Broadcast
The amber-to-fleet takeover, held in reserve for the day the whole squadron needs to look up at once — a word from the Admiral across every deck, all at once.Reserved: the urgent whole-bar ticker takeover (already driving the restart blare) opened up as an admin-posted, squad-wide alert channel.
08
Beyond Colonisation
Other game loops on the squadron’s horizon — proof the Blades fly wide
Mining Operations
Core, laser, and subsurface hotspots plotted for the fleet — who’s cracking what, and where the void-opals run hot.Planned: shared mining hotspot intel and per-commander yield tracking, fed by the plugin’s mining events.
Combat & Bounty Wing
Massacre stacks, bounty pools, and AX sorties against the Thargoids — the fleet’s kill-board, live.Planned: shared bounty/combat and AX-operation boards from journal combat events.
Trade & Logistics
Squad trade lanes and carrier runs — the credits that keep the colonies fed.Planned: shared trade-route boards and carrier logistics tracking.
BGS Influence
The quiet war — Blades influence across contested systems, moved one mission at a time.Planned: background-simulation influence tracking per system from the plugin’s BGS events.
Exploration & First Footfalls
The deep black — expedition routes, first-discovered tags, and cartographics brought home.Planned: exploration and first-footfall / cartographics tracking.