AICCP (AI Change Control Protocol)

0. Canonical role

AICCP is the Heptagon component responsible for structured approval and change control around sensitive or irreversible actions.

1. Classification in the ecosystem

Approval and change-control layer.

AICCP should be understood as the component that introduces explicit review, escalation, and approval requirements before selected high-risk actions are allowed to proceed.

2. What this project is

In the ABS ecosystem, AICCP is positioned as the protocol used when runtime policy is not enough on its own and an action requires structured authorization before execution. This is especially relevant for write paths, destructive operations, and other changes that may be difficult to reverse.

3. What it is not

AICCP should not be described here as a universal code-quality platform, a generic DevTools suite, or a complete replacement for software delivery governance. Those descriptions are broader than the current repository-visible material clearly supports.

4. Functional role

AICCP should be described as:

• a structured approval path for sensitive actions,
• a governance layer for irreversible or high-risk changes,
• and a formal input to runtime decision handling when escalation is required.

5. Deployment posture

AICCP fits the broader ABS model of self-hosted or customer-controlled deployment. It should be presented as part of governed execution infrastructure, not as a self-service SaaS workflow product.

6. Documentation discipline

When documenting AICCP, prioritize verified claims about approval flow, escalation boundaries, and structured authorization. Broader claims about universal software quality enforcement, pipeline dominance, or market-wide coverage should be marked as future work unless separately demonstrated.