← All case studies
Fig. 01 · Portfolio project · rebuilt in 2026

AI Production System

A shipped game's production rebuilt in Jira and Confluence, with an AI pipeline that turns meeting minutes into tracked, linked work.

Role
Designer and builder, solo portfolio project
When
Rebuilt in 2026 from the 2023 project records
Built in
Jira, Confluence and an AI meeting-to-issue pipeline
Source project
Fading Lights, shipped on Google Play in 2023

Built with AI assistance under my design, decisions and approval.

The story · five parts

01Constraint

A shipped game whose real decisions lived in Discord threads, voice calls and a shared folder, with nothing traceable.

02Intervention

In 2026 I rebuilt its production system in Jira and Confluence and built an AI pipeline that turns meeting minutes into linked Jira issues, labeling every page as evidenced, recollection or retrospective scenario.

03Measured

Whether every issue traces to the meeting or QA report that created it.

04Result

One connected path from idea to release, including a research kill with its reason.

05What it proves

I make decisions traceable.

Evidence

Fig. 01.1 · Silent loop, 10 s, four stops at 2.5 s each

The system in 10 seconds

Four views of the same space, in the order work moves through it.

  1. 1/4The path. Nine stops from idea to release, each with its evidence label.
  2. 2/4AI pipeline. Meeting minutes become Jira issues, each linked back to the meeting.
  3. 3/4QA. One bug card per issue, ending with the retest condition.
  4. 4/4Kanban board. Role-restricted workflow, WIP limit, Fix Versions.

The nine-stop path, idea to release

Evidencedoriginal records Recollectionmy account Retrospective scenariodemonstration

Idea and identity

1GDD 01 · Synopsis

What shipped and what was marketed, kept apart.

EvidencedRecollection
2Brand Identity Guidelines

Palette, type and tone that style every page and label.

EvidencedRetrospective scenario

Research

3RB-01 · AI Maze Stitching

Falsifiable hypothesis; kill criteria set before work.

Retrospective scenario
4HQ-43 · OQ-2

Killed at Gate 1: no staff or funding. Hypothesis recorded as untested.

Retrospective scenarioRecollection

Production

5Meeting · 2023-02-11 · Maze Scale

The AI pipeline turns each decision into a tracked card linked to these minutes.

AI pipelineEvidencedRecollection
6HQ-24 · Crossplatform basic controls

One card from that meeting, through review and merge into build 0.1.

EvidencedRetrospective scenario

QA and release

7QA Report · v1.0.1

QA states findings; fixes go into the next build.

EvidencedRecollection
8HQ-40 · On-screen joystick

Steps end with "Notice that"; expected result is the retest condition.

RecollectionRetrospective scenario
9Board and releases

Kanban with short milestones; each build a Fix Version with its QA report.

Retrospective scenario
Fig. 01.2 · The nine stops as they appear on the Home page of the rebuilt space, grouped by phase. The labels are the ones on each page.
Title card reading Meeting minutes to Jira issues, traced, beside a table of action items linked to Jira issues. Watch on YouTube · 1 min
Fig. 01.3 · One-minute tour of the nine stops · silent, captioned · YouTube

See it live

The space is private. I invite reviewers as users and walk them through the path, or they explore on their own.