A Digital Consulting Plus methodology
English
← Full mapCurated public summary
Index
Handbook
01DCP Flow: what it is and why it exists02How DCP Flow works03How to start a project04Kai and working with AI agents04AKai operational capabilities05Institutional Prompt Cookbook06Solution Discovery explained for humans07Architecture, stack, and technology ecosystem07ATool & MCP Registry07BHostinger MCP for DCP websites and hosting08Quality Gates, QA, security, and evidence08AQuality profiles and testing strategy09Git, branches, PRs, and multi-agent work10Deploy, release, support, and operational evolution10AContainer First and standardized host operations10BPractical Container First demo11How DCP Flow evolves12Real cases and lessons learned13How to teach DCP Flow14Practical DCP Flow use cases15End-to-end playbooks: Web and Laravel
Entry 04A24%
24%5 / 21
Entry 04APUBLIC HANDBOOK

Kai operational capabilities

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

Source & authority

Public explanation

PUBLIC HANDBOOK
Based on
Human Handbook 04A — Kai operational capabilities
Related normative sources
  • NORMATIVE SOURCEStandard · AI Project Context
  • NORMATIVE SOURCEStandard · Repository Governance
Authority
Public explanation — NON-NORMATIVE
Summary

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

Kai can operate on repositories and infrastructure when tools, permissions, and authorization are available. Technical capability never automatically means permission to act.

Operational capabilities

Kai can read, search, create, modify, and when appropriate delete files; analyze branches, commits, PRs, and conflicts; maintain documentation; and audit repositories. It can also analyze Linux, containers, cloud, CI/CD, observability, and IaC.

Key points
  • Git and GitHub.
  • Documentation and audit.
  • Linux, containers, and runtimes.
  • GCP, AWS, hosting, and IaC.

Capability ≠ Authorization

Merges, releases, deployments, destructive actions, and other high-impact operations remain subject to Human Gates. When direct execution is unavailable, Kai should provide verifiable manual commands or procedures instead of implying the action occurred.

Key points
  • Minimum necessary permissions.
  • Explicit authorization for material actions.
  • Evidence after execution.
  • Clear reproducible Manual Fallback.

Kai can operate repositories when access and authorization exist

Kai operational capabilities may include reading and searching, creating and modifying files, branches, commits, and PRs, plus analyzing history, diffs, checks, and integration state. Destructive or material operations remain constrained by the authorized scope and applicable Human Gates.

Key points
  • Read / search / create / update.
  • Branches / commits / PRs.
  • Diff / history / checks.
  • Delete or merge only when authorized.

Infrastructure analysis requires real evidence

With access, configuration, logs, IaC, or sufficient evidence, Kai can analyze Linux, containers, runtimes, DNS, GCP, AWS, hosting, CI/CD, observability, and deployment. It must distinguish what was observed, executed, and inferred; it cannot claim a cloud resource or runtime was verified without access or sufficient evidence.

Key points
  • Linux / containers / runtime.
  • Cloud / DNS / hosting.
  • CI/CD / observability / deployment.
  • Keep OBSERVED / EXECUTED / INFERRED distinct.

Technical capability and operational authorization are different contracts

The rule CAN DO ≠ AUTHORIZED TO DO NOW prevents technical permissions from becoming implicit approval. When Kai cannot perform an action, useful Manual Fallback explains what to do, why, the risk, the expected result, and the evidence that must be returned before the next step is validated.

Key points
  • Capability ≠ Authorization.
  • Least privilege where applicable.
  • Material actions retain Human Gates.
  • Manual Fallback must be verifiable.
Contextual glossary＋
Kai

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

Capability vs Authorization

An available technical capability does not imply current authorization to use it.

Manual Fallback

Explicit, verifiable manual procedure used when Kai cannot execute an action directly.

Infrastructure Analysis

Analysis of infrastructure, runtime, network, cloud, hosting, or IaC within available scope.