Workflow 1.0 · Operating system

Build a reliable baseline. Keep the game alive.

My workflow turns game ideas into approved design, architecture, module specifications and validated software without closing the door on creativity. Persistent workspaces preserve useful reasoning; authoritative documents preserve truth.

Explore the initial baselineFollow a design change
Thirty-second overview

Two systems operate together.

Interactive explorer

Select a stage to inspect its contract.

The explorer separates workspace, agent, document, gate and repository responsibilities. Colour is supportive; labels and shapes carry the meaning.

Initial Baseline
Continuous Development
Initial Baseline · workspace

Idea

What is this?
Persistent ChatGPT chat
Who performs it?
Creator and normal ChatGPT
What does it receive?
Open questions, observations and creative possibilities
What does it produce?
Creator-approved Idea-Brief.md
When is it complete?
The brief is approved for design work; the workspace remains open
When do I return?
Any new mechanic, content, presentation thought, experiment or refinement
Authority model

Discussion, truth, role and reality are distinct.

Chats preserve useful working context. Documents and repository state determine what is currently authoritative.

Context space

Chat

Persistent reasoning and discussion. Useful, but non-authoritative.

Approved truth

Document

Preserves approved intent for its specified responsibility.

Active role

Agent

Defines who is reasoning now and the boundary they must respect.

Current reality

Repository

Authoritative for the software and assets that currently exist.

Choose your route

Enter at the point your project needs.

Start a new project
  1. Idea Workspace
  2. Game Design
  3. Bible
  4. Architecture
  5. Module Workspace
  6. Codex
  7. Validation
Follow the baseline
Change an existing project
  1. Idea Workspace
  2. Creator approval
  3. Update owning truth
  4. Capability Impact Check
  5. Affected workspace
  6. Codex
  7. Validation
Follow a change
Return to a project
  1. Identify the owning module.
  2. Open its retained Work chat.
  3. Read authoritative documents.
  4. Identify the affected Slice.
  5. Open the retained Codex module chat.
  6. Inspect repository reality.
  7. Continue from the next valid action.
Use the return protocol
Full reference

Go deeper without losing your place.

Process

Baseline, readiness and re-entry

Follow workspace stages, per-module gates, Codex delivery and controlled change.

Open Process
Structures

Truth and implementation homes

Locate authoritative documents and place Unity assets by ownership and role.

Open Structures
AI Strategy

Agents and persistent workspaces

Understand specialist boundaries, reasoning, retrieval and stop conditions.

Open AI Strategy
Prompt Library

Activations and operations

Browse reusable Workflow 1.0 prompt records by workspace, agent and operation.

Open Prompt Library
View full Workflow 1.0 map

Initial Baseline

Idea Workspace → Game Design Workspace → Game Design Bible → Architecture Workspace → Module Workspace → Slice Specifications → Codex Module Workspace → Validation

Continuous Development

Brainstorm → Creator Approval → Update Owning Truth → Capability Impact Check → Re-enter at Owning Level → Propagate Downward → Implement → Validate → return to Idea Workspace when creativity continues

Re-entry rule: travel upward only as far as necessary, then propagate approved change through every affected downstream level.