BlightFall Operations & Product Infrastructure.

Building continuity around the game.

My role combines operations leadership, product thinking, systems design, implementation direction, documentation, stakeholder coordination, and acceptance testing.

BlightFall is an ongoing private Roblox project in development. As the team’s operational needs grew, I led a staged move away from subscription-dependent Notion infrastructure toward a maintainable system the project could own, validate, and recover.

Generative AI and AI coding assistants supported implementation while I led the requirements, architecture, review gates, testing, and operational adoption.

Preserve first, retire carefully.

I evaluated the existing workspace, classified what needed to be retained, and organized the migration into approval-gated work packages. Each package included testing, rollback, continuity, and retirement criteria so the team could move deliberately without losing useful project history.

The review preserved and assessed a 168-entry Notion export. The team is retiring the older infrastructure in stages, using parity and recoverability checks to guide each transition.

Connecting the tools without confusing their roles.

I designed the source-of-truth architecture across the game repository, Ops Hub, Dev Tracker, cloud documents, AI workspaces, development tools, and planned Discord integrations. The model gives each system a clear purpose while keeping decisions, ownership, dependencies, evidence references, and follow-through traceable.

The internal Ops Hub now validates 72 structured records covering decisions, actions, workstreams, risks, meetings, people, resources, ownership, relationships, and next steps.

Making operational updates reviewable and recoverable.

I directed the introduction of preview/apply transactions, validation, revision checks, audit history, device attribution, privacy checks, and recovery procedures. Changes can be reviewed before they are applied, conflicting revisions are caught, and the resulting history remains understandable later.

The system separates safe repository records from restricted evidence, credentials, financial material, agreements, and identity information stored outside Git. Automated privacy, transaction, relationship, and regression checks reinforce those safeguards.

Turning project records into useful views.

I directed and tested audience-aware reporting for internal, leadership, team-facing, Discord-ready, and external-safe use. Outputs include formatted previews, Markdown and PDF exports, concise Discord summaries, and weekly digests, with external reporting designed to fail closed when material is not safe to share.

I also designed a structured AI planning-to-implementation handoff that turns strategy conversations into traceable, reviewable development requests while keeping repository access private and review-gated.

Proving the system before depending on it.

I coordinated acceptance testing and stakeholder review across information routing, meeting workflows, report parity, privacy safeguards, continuity rehearsals, and recovery backups. Recovery materials were packaged, checksum-verified, downloaded back for integrity verification, and stored under restricted access.

I also direct continuing development of a least-privilege, review-gated Discord bridge for operational intake, developer accountability, reminders, and Dev Tracker updates.

Preparing for a project that can grow responsibly.

Alongside the internal operations work, I established the official blightfall.ca domain, business-email foundation, account-recovery planning, and a multi-platform social presence.

Together, these systems replace ad-hoc operational knowledge with a maintainable foundation for project continuity, institutional memory, accountability, and future company readiness.