DCP Flow · Public Handbook

The human manual for the methodology.

Explore the complete institutional Handbook structure through curated public content. This documentation explains DCP Flow; it does not replace its private normative source.

17 entries3 languages14 numbered chapters

Learning path

Start here

If DCP Flow is new to you, begin with foundations and then follow a path based on your goal.

KKai recommended pathRecommended starting path01 → 02 → 03

Documentation

Public Handbook map

01Full public content

DCP Flow: what it is and why it exists

Introduction to DCP Flow, its purpose, origins, and principles for working with AI without losing architecture, governance, or human accountability.

Open →
02Full public content

How DCP Flow works

Explains the DCP Flow operating model, its pragmatic Scrum adaptation, core artifacts, Golden Flows, evidence, and human acceptance.

Open →
03Full public content

How to start a project

Journey from problem and capabilities through discovery, ADR, architecture, Golden Flows, sprint, execution, evidence, and learning.

Open →
04Full public content

Kai and working with AI agents

Distinguishes DCP Flow, Kai, Execution Agents, and humans; explains Human Gates, Execution Contracts, Handoffs, context, routing, and multi-agent work.

Open →
04AFull public content

Kai operational capabilities

Describes Kai capabilities that may be authorized across repositories, Git/GitHub, documentation, audit, Linux, cloud, IaC, and Manual Fallback.

Open →
05Full public content

Institutional Prompt Cookbook

Interaction patterns for audit, discovery, sprint, handoff, parallel work, Git/Kai, infrastructure, incidents, QA, deployment, and release.

Open →
06Full public content

Solution Discovery explained for humans

Problem, Capability Matrix, SaaS, OSS, components, licensing, security, reproducible shortlist, Golden Flows, GAP/TCO/risk, ADR, and ADOPT/CONFIGURE/INTEGRATE/EXTEND/BUILD.

Open →
07Full public content

Architecture, stack, and technology ecosystem

Separates Architecture, Stack, Runtime, Environment, Infrastructure, and Tooling; covers Runtime Profiles, provider neutrality, IaC, CI/CD, observability, and Tool Catalog.

Open →
07AFull public content

Tool & MCP Registry

Operational tool/MCP registry with ADOPTED/EXPERIMENTAL/REJECTED/DEPRECATED/UNKNOWN states, guardrails, and relationships to Skills, Standards, and ADRs.

Open →
07BFull public content

Hostinger MCP for DCP websites and hosting

When Hostinger API MCP applies to Websites, Domains/DNS, shared hosting, and VPS; boundaries against Git/deployment/SSH/IaC, OAuth, minimum scope, and POC.

Open →
08Full public content

Quality Gates, QA, security, and evidence

Risk R0–R3, gates, QA, data safety, browser/runtime validation, artifacts, Truth Labels, Evidence Chain, Independent AI Review, and Known Debt.

Open →
08AFull public content

Quality profiles and testing strategy

How DCP Flow derives a Quality Profile from Delivery Mode, risk, lifecycle, and change surface to require proportional evidence.

Open →
09Full public content

Git, branches, PRs, and multi-agent work

main/dev/working branch, PR/diff, Pre-Merge Audit, technical/logical protection, concurrency contracts, shared interfaces, Break-Glass, and Merge Authority.

Open →
10Full public content

Deploy, release, support, and operational evolution

Deploy ≠ Release; readiness, config/secrets, migrations, backup/recovery, rollback, Release Evidence, production, support, incidents, Operational Debt, and Runbooks.

Open →
10AFull public content

Container First and standardized host operations

Operational convention for reproducible deployments on DCP-controlled infrastructure: Git, repo/deploy, Docker/Compose, /opt/dcp, persistence, and recovery.

Open →
10BFull public content

Practical Container First demo

Pedagogical example of a containerized project with Compose, persistence, backup/restore, and separation between Git definition and operational state.

Open →
11Full public content

How DCP Flow evolves

Learning lifecycle, Lessons Learned, Improvement Proposals, Standard/Blueprint/Skill/Gate/Tool classification, deprecation, version awareness, and knowledge promotion.

Open →
12Full public content

Real cases and lessons learned

Normia, Rewi/MicroPOS, Kai, n8n, and DCP Web S9/S10: evidence, promotion, generalization boundaries, and EspoCRM evolution from validated integration to ADOPTED lightweight CRM stack.

Open →
13Full public content

How to teach DCP Flow

Onboarding, audience learning objectives, Training Paths, workshops, Public Curation, Public-Safe Content, Teaching Examples, editorial classification, and comprehension assessment.

Open →
14Full public content

Practical DCP Flow use cases

Eighteen end-to-end scenarios combining Discovery, architecture/stack/cloud, Quality Gates, Git/multi-agent work, deploy/release, incidents, upgrades, and the website + external CRM case with EspoCRM as a contextual ADOPTED option.

Open →
15Full public content

End-to-end playbooks: Web and Laravel

Complete paths for taking a Web/Astro or Laravel solution from problem and discovery through Foundation Ready, release, smoke, operations, and learning.

Open →
Essential glossary+
DCP Flow

Digital Consulting Plus working and engineering methodology for organizing decisions, execution, evidence, and learning with AI.

Kai

Engineering assistant that interprets and applies DCP Flow within available context and authorization.

Quality Gate

Checkpoint where evidence determines whether work may progress.

Golden Flow

Critical end-to-end journey that must work and produce verifiable evidence.

Evidence

Proof of an observed or executed result; not an agent assertion.