delta

Evaluate receipts against verdicts to coordinate coherence-cell boundary decisions.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill delta-usurobor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delta
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.cdd/skills/cdd/delta
Command: npx skills add https://github.com/usurobor/cnos --skill delta-usurobor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

δ is the boundary actor for the coherence-cell cycle, coordinating receipt validation and verdicts to decide what crosses between scopes and enabling controlled overrides when decisions degrade.

Core Features & Use Cases

  • Outward boundary decisions derived from a ValidationVerdict to determine acceptance, release, rejection, or repair_dispatch.
  • Inward dispatch enrichment: review of γ's implementation-contract to pin execution details before routing to α.
  • Override protocol: structured override blocks that record justification and preserve the original verdict for traceability.

Quick Start

Use a test receipt and verdict pair to exercise δ's boundary decision workflow in a controlled CDD cycle.

Frequently Asked Questions about delta

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle boundary decisions for coherence cells when receipt validation verdicts degrade?

Boundary decisions for coherence cells are handled by evaluating receipts against verdicts to trigger accept, release, reject, or repair_dispatch actions. When verdicts degrade, structured override blocks record justification while preserving the original verdict for traceability.

What is inward dispatch enrichment and how does it work with implementation contracts?

Inward dispatch enrichment reviews implementation contracts to pin execution details before routing tasks. This ensures precise coordination within role-local cycles by verifying execution parameters against contract specifications prior to dispatch.

How to apply override authority when boundary validation verdicts fail?

Apply override authority by generating structured override blocks that explicitly record justification for crossing boundaries. This protocol preserves the original degraded validation verdict within the decision record to maintain full audit traceability.

When do I need boundary decision recording in a CDD cycle?

Boundary decision recording is needed when coordinating outward boundary gating and inward dispatch enrichment within role-local cycles. It records triggers for accept, release, override, reject, and repair_dispatch actions to maintain coherence.

Can I use boundary override blocks without receipt validation?

Boundary override blocks interlock directly with receipt validation protocols and coherence cell normal forms. They are designed to function within this validation cycle, recording justifications specifically when validation verdicts degrade.

Why does boundary gating reject or repair dispatch instead of accepting?

Boundary gating rejects or triggers repair dispatch when validation verdicts indicate insufficient coherence. This mechanism prevents invalid data from crossing scopes, ensuring only verified receipts pass outward boundary decisions.