PORTFOLIO INDEX
Builder · Register · Publishing · Mission operations · Product lab · Private command · Collaboration · Activity

I am Daniel Conroy, an independent systems architect and product builder based in Edinburgh, Scotland.

I turn persistent friction into working systems: community platforms, game intelligence, emergency-command tools, browser utilities, media software, private market intelligence and the infrastructure that keeps them alive. My work spans product direction, interface design, architecture, implementation, evidence, validation, delivery and live operation.

The subject changes. The operating standard does not.

I do not treat “it started once” as an operational definition.

The current estate contains thirteen first-party systems: ten public products and three private operational platforms. Two collaboration orbits, forks, upstream contributions, private recovery mirrors and archived source history are deliberately kept outside that ownership count.

The machine-readable ownership register is maintained in data/portfolio.json. The same source drives the generated portfolio totals below, preventing the written page and automated metrics from drifting apart.

I founded and originally created Team Killing Bastards and now lead its identity, technical direction and long-term stewardship alongside MartyBlyth. The current production estate unifies the parent community, specialist game intelligence and supported product distribution inside one governed monorepo.

The production monorepo remains private because it contains deployment topology and operational controls. The finished public surfaces remain open. The retired standalone Crimson Desert and MissionChief repositories are preserved as source history with their migration provenance intact.

One suite now covers the decision layer, the moving fleet and the incident map.

The Toolkit turns MissionChief's scattered signals into one responsive command environment: incident priority, resource pressure, fleet state, patient transport, map intelligence, coverage, financial reconciliation, diagnostics and safe recovery.

It does not replace MissionChief's authority. It makes the operational picture legible and reaches the correct native controls. Incomplete evidence fails closed.

Install or update from TKB Scripts · Open the field guide · Explore eight interfaces · Inspect release control

TKB Scripts is the sole supported public installation and update route. GitHub is the canonical source, release archive and engineering record.

A complete original UK emergency-services vehicle pack with static and animated map assets, independent emergency-light rhythms, helicopter rotor motion, specialist silhouettes and automated visibility testing.

Preview the complete fleet · Use vehicle pack 5897 in MissionChief

Every mapped UK mission receives a compact incident marker and a permanent TKB Response Level 1–5. MissionChief's native red, amber and green states remain independent, so priority and live progress never become the same signal.

Browse every mission slot · Use mission pack 539 in MissionChief

The product lab starts with recurring annoyances that should not require a subscription, a developer-operated server or an invasion of privacy to solve. Six products now cover presence, sound, language, time, evidence and media—each with an explicit trust boundary.

A polished Windows utility for choosing a recognised game identity, shaping optional activity text and publishing cosmetic game presence through Discord's local Rich Presence connection. The Rust backend resolves selections against the active detectable-game catalogue rather than accepting arbitrary application IDs.

It is experimental and unofficial: presence is cosmetic only, cannot prove ownership or genuine gameplay, and does not complete Quests, earn Orbs or access Discord account data.

Download the Windows release · Inspect privacy and capability boundaries

Level is an automatic loudness leveller rather than a blunt volume booster. It lifts sustained quiet material gradually, reduces loud changes quickly, shapes dialogue when requested and catches peaks across four tuned listening modes.

Audio processing is transient and local. There is no server, recording, account, advertising, analytics or tracking; website preferences stay in extension storage.

Open the project · Read the architecture · Inspect the privacy policy

A privacy-conscious Manifest V3 extension for Brave and Chromium. It translates readable text inside the original page, preserves the site's real session and interactive state, masks common private values before approved external translation, and keeps automatic behaviour explicitly site-scoped.

Install from the Chrome Web Store · Inspect the public source

ChatTime reveals the original creation date and time of messages on chatgpt.com. It supports local time or UTC, 12-hour or 24-hour clocks, optional dates and seconds, placement above or below messages, and independent user/reply visibility.

The extension uses message time already loaded in the page. It has no server, analytics, advertising, account, remote code or network requests; its only extension permission stores display preferences.

Open the project · Read the privacy policy

An evidence-led reference that separates official documentation, reproduced behaviour, historical records, community claims and unknowns. Human-readable guidance sits beside privacy-safe evidence records, verification timelines, bounded research tasks and a validated static API.

Explore the encyclopedia · Search the research · Inspect the evidence register · Use the static API

An Emby Server plugin that builds best-rated playlists for each TV season without changing season order, episode metadata, ratings or watched state. It can rank one show, selected shows or the full visible library, then refresh after scans or on a schedule.

Open the repository · Read the Emby community release thread

These systems are private by design. Credentials, deployment topology, member data, market records and unreleased game state do not belong on a public profile.

Public descriptions explain purpose and boundaries. They do not expose secrets, member information, recovery material or enough topology to weaken the live estate.

Good collaboration should make authorship clearer—not absorb somebody else's work into my portfolio count.

MartyBlyth is the developer, creator, principal userscript author, technical owner and release authority. Command Nexus remains Marty's project.

I am the project helper for repository infrastructure, documentation, validation and general operations. With Marty's permission, I also contributed scoped iOS Safari compatibility work. The Resource Administration and Mission Finder engines remain Marty's work.

I provide organisation, portfolio and delivery support around Blyth Control Centre and other Marty-owned work. Marty remains their creator, product owner and primary technical authority.

My public LSSM fork is a contribution workspace—not a first-party product. Both changes remain under upstream maintainer authority, with their live review state left to the pull-request pages.

ConroyMedia is where architectural claims meet operating reality.

It connects Docker services, Caddy routing, DDNS, media automation, service monitoring, Windows telemetry, GitHub Apps and isolated runners, Home Assistant integrations, deployment controls, backups and tested recovery paths.

flowchart LR
    Idea[Product intent] --> Proof[Evidence and validation]
    Proof --> Release[Immutable release]
    Release --> Operate[Live operation]
    Services[Services and infrastructure] --> Observe[Monitoring and telemetry]
    Operate --> Observe
    Observe --> Control[Bounded control]
    Control --> Recover[Backup · restore · rollback]

A dependable system can explain its state, identify its authority and show the route home when something fails.

_{Repository-owned cards regenerate from GitHub's API. Private work and some organisation activity remain intentionally outside public statistics.}

Usually: PC gaming, Linux and handheld tinkering, self-hosted infrastructure, interface concepts, game worlds or cinematic music experiments.

Development is supervised by Eli and Nala, who contribute no code but retain decisive control over keyboard availability.