Skip to content

Everything-as-code workflow

Kido Code

Coding

Everything-as-code work through a Brain, branch, merge request and Workflow.

Concept study
Kido Code: Work that leaves a reviewable recordA branching work surface carries a Brain record toward an MR/PR review gate. The gate represents human approval, not an automatic merge. A conceptual illustration, not a released architecture or deployment diagram.BrainApprovalBranch / MR / PR

Work that leaves a reviewable record

  • Brain & worktree
  • Branch & MR/PR
  • Human approval

Conceptual illustration. See current scope & status below.

What is Kido Code?

Kido Code is Kido’s everything-as-code way of working: source, decisions and persistent working memory live in git. Work is organized as a kido, a story-sized unit with its own Brain, branch and worktree, and moves through a Workflow from story and development to review and close. The code mode runs this way of working with the full harness and forge; Kido Code is not the name of the client or just a code editor.

What it is designed to do

  • Manage git-kept work, including software and knowledge proposals, with a Brain that preserves its plan, decisions, progress and handoff.
  • Use the code preset’s full harness and forge access to produce a branch, merge/pull request and Brain record.
  • Move work between Profiles through declared Workflow transitions and approval gates, with the forge record first and the Brain as fallback.

Illustrative use case

How it could fit into your work

A planned kido is implemented in its worktree, reviewed through a merge request, approved by a human and closed with its Brain updated. Git-managed knowledge proposals also use Kido Code, through the Knowledge Workflow for schema checks, expert review and human approval.

An example of the intended role, not a claim of a released workflow.

Foundations of Kido Code

Brain keeps the working record. Skill carries the procedure. Both support the workflow without becoming additional modes or runtimes.