ADOPT
Use an existing solution with minimal changes when it reasonably covers the outcome.
Knowledge · Glossary
A shared language for working with DCP Flow.
Public reusable definitions that reduce ambiguity across methodology, architecture, evidence, agents and operations.
ADOPTED
State of a tool validated and accepted for a defined use.
Where it appears 1
ADR
Record of a material architecture decision, its context, and rationale.
AGENTS.md
Repository-level operational contract translating DCP Flow, Blueprints, ADRs and Project/Repository Truth into immediate instructions for agents.
Architecture
Structure of responsibilities, boundaries, and relationships in a solution.
BUILD
Create a custom implementation when ADOPT, CONFIGURE, INTEGRATE, and EXTEND do not reasonably solve the outcome or an explicit material justification exists.
Capability vs Authorization
An available technical capability does not imply current authorization to use it.
Where it appears 1
CONFIGURE
Solve the outcome through supported configuration of an existing solution.
Container First
DCP operational default for reproducible and normally containerized deployments on directly controlled Linux infrastructure, unless a documented technical exception applies.
DCP Flow
Digital Consulting Plus working and engineering methodology for organizing decisions, execution, evidence, and learning with AI.
Where it appears 10
handbook01 · DCP Flow: what it is and why it existshandbookHow DCP Flow workshandbookHow DCP Flow evolveshandbookHow to teach DCP FlowhandbookPractical DCP Flow use caseslearning-pathFoundationslearning-pathTechnical implementationlearning-pathExternal audiencereferenceAGENTS.mdevolutionDCP Flow Evolution
Delivery Mode
Solution path —ADOPT, CONFIGURE, INTEGRATE, EXTEND, or BUILD— describing how a capability is delivered and shaping its validation profile.
Where it appears 1
Deployment
Technical act of placing a version into an environment.
DEPRECATED
State of knowledge or a tool that should no longer be used for new work.
Where it appears 1
EspoCRM
DCP Flow ADOPTED / EVOLVING BY EVIDENCE lightweight CRM stack. It is a standard option for a decoupled commercial lifecycle, but it is not mandatory and remains subject to Solution Discovery and Project Truth.
Evidence
Proof of an observed or executed result; not an agent assertion.
Where it appears 10
handbook01 · DCP Flow: what it is and why it existshandbook02 · How DCP Flow workshandbook08 · Quality Gates, QA, security, and evidencehandbook10B · Practical Container First demohandbookReal cases and lessons learnedcaseNormia — intent, implementation and evidenceuse-caseStart a new productuse-caseMulti-agent developmentlearning-pathExternal audienceevolutionDCP Flow Evolution
Evidence Promotion
Process of promoting proven learning from a project into reusable knowledge.
Where it appears 1
Execution Agent
Agent that executes bounded technical work under defined context, scope, and permissions.
Where it appears 1
Execution Contract
Execution contract defining objective, scope, boundaries, evidence, and acceptance conditions.
EXPERIMENTAL
State of a tool still under evaluation or POC.
Where it appears 1
EXTEND
Expand a platform through supported extension mechanisms to cover real gaps.
Foundation Ready
State in which the technical and governance foundation is sufficient to start a functional vertical without rediscovering or rebuilding project foundations.
Where it appears 1
GAP
Difference between required capabilities and those available in an evaluated alternative.
Where it appears 1
Generalization Boundary
Explicit boundary defining how far a lesson may be reused without overgeneralizing.
Where it appears 1
Golden Flow
Critical end-to-end journey that must work and produce verifiable evidence.
Handoff
Explicit transfer of context, scope, state, and evidence between people or agents.
Where it appears 7
handbook04 · Kai and working with AI agentshandbook05 · Institutional Prompt CookbookhandbookDeploy, release, support, and operational evolutionhandbookContainer First and standardized host operationshandbookEnd-to-end playbooks: Web and LaravelcaseKai — technical capability is not authorizationuse-caseMulti-agent development
Human Gate
Point where a material decision requires human acceptance or authorization.
IaC
Infrastructure as code: versioned, reproducible infrastructure definition.
Where it appears 1
IMPLEMENT
Historical terminology: former umbrella term for implementing an existing solution; superseded by ADOPT / CONFIGURE / INTEGRATE / EXTEND / BUILD.
Improvement Proposal
Explicit proposal to change or extend DCP Flow from verifiable learning.
Where it appears 1
Infrastructure Analysis
Analysis of infrastructure, runtime, network, cloud, hosting, or IaC within available scope.
Where it appears 1
INTEGRATE
Connect existing capabilities or systems when the governed combination solves the outcome.
Kai
Engineering assistant that interprets and applies DCP Flow within available context and authorization.
Knowledge Lifecycle
Lifecycle through which knowledge moves from signal to proposal, validation, adoption, deprecation, or archive.
Where it appears 1
Lesson Learned
Evidence-derived learning that may stay local or be proposed for reuse.
Where it appears 1
Manual Fallback
Explicit, verifiable manual procedure used when Kai cannot execute an action directly.
MCP
Interface/protocol for exposing tools and resources to AI agents in a structured way.
Observability
Ability to understand system state through logs, metrics, traces, and signals.
Where it appears 1
Operational Handoff
Explicit transfer of a system from delivery into operations and support.
Pre-Merge Audit
Pre-integration review for conflicts, regressions, known debt, and missing evidence.
Project Truth
Durable, verifiable project state that should prevail over temporary memory or assumptions.
Public Curation
Editorial process for turning institutional knowledge into safe, faithful public content.
Where it appears 1
Public-Safe Content
Publishable content that preserves value without exposing sensitive or private details.
Where it appears 1
Quality Gate
Checkpoint where evidence determines whether work may progress.
Where it appears 7
Quality Profile
Validation profile derived from Delivery Mode, risk, lifecycle, and change surface; defines the QA/testing capabilities and evidence required.
Where it appears 1
Reference Evidence
Historical evidence reusable as precedent when context is comparable.
Where it appears 1
Release
Controlled decision to make a version available to users or production.
Repository Truth
Verifiable repository state: code, configuration, schema, history and evidence describing what actually exists.
Where it appears 2
Rollback
Controlled return to a previous state when a delivery is unacceptable.
Where it appears 1
Runtime Profile
Reproducible profile of the runtime environment required by a solution.
Solution Discovery
Process of investigating real alternatives and proportionally evaluating ADOPT → CONFIGURE → INTEGRATE → EXTEND → BUILD before a material decision.
Stack
Set of concrete technologies used to implement an architecture.
TCO
Total cost of ownership including operation, maintenance, dependency, and evolution.
Teaching Example
Pedagogical example used to explain a concept; not equivalent to real evidence.
Where it appears 1
Tool Catalog
Governed registry of known tools and their status within DCP Flow.
Where it appears 1
Training Path
Recommended content sequence for a specific audience or learning objective.
Where it appears 1
Use Case
Practical scenario showing when and how to combine parts of DCP Flow.
Where it appears 1
No terms found.