The creative loop

The Core Mental Model

KazaKit has three product layers.

3.1 Studio Layer

The Studio layer gives the user a cross-project view. It answers:

• What projects are active?
• What needs attention today?
• What issues are open?
• What has changed recently?
• What deadlines and events are coming?
• What goals, output, focus time, and achievements are accumulating?
• What knowledge belongs to the entire studio rather than one project?

Primary Studio destinations:

• Studio Overview
• Today
• All Issues
• Activity
• Global Calendar
• Studio Docs
• Badges / Trophy Room

3.2 Project Layer

The Project layer is where a single creative effort gets its own working environment. It answers:

• What is this project?
• What phase is it in?
• What should happen next?
• Where are its notes, documents, visual references, tasks, files, and history?

Primary Project destinations:

• Overview
• Library
• Workshop
• Moodboards
• Assets
• Chronicle
• Badges
• Project Settings

3.3 Global App Shell

The shell connects Studio and Project work. It includes:

• the project-switching rail;
• the dynamic Studio or Project sidebar;
• command search;
• keyboard shortcuts;
• notifications and toasts;
• the focus timer;
• focus audio;
• first-run language selection;
• onboarding;
• app-wide settings.

Simple Diagram

KazaKit
├── Studio layer
│   ├── Overview
│   ├── Today
│   ├── All Issues
│   ├── Activity
│   ├── Global Calendar
│   ├── Studio Docs
│   └── Trophy Room
├── Project layer
│   ├── Overview
│   ├── Library
│   │   ├── Project Wiki
│   │   ├── Writing Studio
│   │   └── Quick Notes
│   ├── Workshop
│   ├── Moodboards
│   ├── Assets
│   ├── Chronicle
│   ├── Project Badges
│   └── Project Settings
└── Shared shell
    ├── Project switcher
    ├── Command palette
    ├── Keyboard shortcuts
    ├── Focus timer
    ├── Focus audio
    ├── Notifications
    ├── Onboarding
    └── App Settings

The Core Creative Loop

The most important workflow to explain throughout the wiki is:

Capture → Shape → Execute → Track and reflect

4.1 Capture

Use Quick Notes while an idea is still raw.

Quick Notes are deliberately lightweight. A note can be:

• an idea;
• fragment;
• reference;
• question;
• reminder;
• quote;
• observation.

Notes can be pinned or starred and move through a lightweight lifecycle:

• Fresh
• Exploring
• Used
• Archived

4.2 Shape

Move material into Moodboards when it needs:

• visual reference;
• spatial grouping;
• tone;
• comparison;
• clustering;
• conceptual direction;
• creative context.

Use Library documents when material needs:

• structure;
• long-term reference;
• a project decision record;
• lore, research, systems, briefs, or formal planning;
• long-form writing.

4.3 Execute

Move clear, actionable work into Workshop.

Workshop work items can be:

• Task
• Bug
• Feature
• Improvement
• Note

Workflow states:

• Backlog
• In Progress
• Blocked
• Done

Priority levels:

• Low
• Medium
• High
• Critical

Work items can also have:

• descriptions;
• tags;
• due dates;
• recurrence;
• completion timestamps;
• links back to promoted creative material where applicable.

4.4 Track and Reflect

Once work is moving, the surrounding systems keep progress visible:

• Today surfaces overdue, due-today, in-progress, and upcoming work;
• Calendar turns commitments into real dates;
• Chronicle combines project history and future milestones;
• Activity shows movement across the studio;
• focus sessions record time spent;
• output logs record visible creative production for supported disciplines;
• goals turn focus, completion, and output into daily or weekly targets;
• badges reflect milestones and habits back to the creator.

Connected Artifact Movement

This is one of KazaKit’s strongest differentiators and should receive a dedicated wiki page.

Supported Movement

• Quick Note → Moodboard card
• Quick Note → Workshop task
• Quick Note → Library document
• Moodboard card → Workshop task
• Moodboard card → Library document
• Moodboard card → related Quick Note
• Asset → Moodboard

Why It Matters

Creative ideas change form as they mature. KazaKit lets the user promote an idea instead of copying and retyping it into another disconnected tool.

Promotion preserves useful context such as:

• the original title or a title derived from the content;
• note or card content;
• source URLs;
• card type;
• origin tags;
• source dates;
• a relationship back to the originating note or board card.

Documentation Rule

Do not describe these promotions as automatic AI transformation. They are user-directed workflow actions.