Skip to content

README.md

Latest commit

 

History

History
92 lines (71 loc) · 5.79 KB

README.md

File metadata and controls

92 lines (71 loc) · 5.79 KB
Raw

Development Kit Framework Documentation

Welcome to the official documentation for Development Kit Framework v0.12.1 (development-kit@0.12.1).

DKF is evolving into the reliability control plane for agentic software development.

AI can write it. DKF proves it.

The v0.12.0 release added Cost Observatory, Workspace Targets, Execution Capsules and Context Cache, Lifecycle Instances, Discovery/Re-entry, Generic Gate Profiles, Verification SDK, Complexity Delta Guard and a read-only Control Center projection. State Engine V2 (T04), including the full Windows backup-restore durability requirement, is deliberately deferred as the top priority for v0.13.0. Existing stable versioned-snapshot state remains authoritative.

Strategic documents

Current release highlights

| Package Version | 0.12.1 | | Lifecycle Stages | 9 (UNDERSTAND through COMPLETE) | | Workflow Commands | 16 | | Specialist Agents | 18 | | Engineering Skills | 48 | | Native Workflow Adapters | 16 |

  • Reliability Control Plane: approved tasks become fingerprinted Development Contracts before execution.
  • Independent verification: implementation reports remain non-authoritative and cannot self-certify completion.
  • Deterministic acceptance: acceptance is computed from criteria, evidence, required reviews, risk-derived gates, controls, source freshness, Design Authority, architecture drift, traceability, and approvals.
  • Authority Graph: incomplete requirement/task/evidence traceability can block acceptance.
  • Bounded correction: correction loops remain constrained by scope, risk, attempt limits, and repeated-failure detection.
  • Execution safety: destructive and remote commands are evaluated against contract scope and blast radius.
  • Canonical reconciliation: artifact amendments require exact source fingerprints and write/read-back verification.
  • Deterministic PLAN validation: task counts, dependencies, cycles, ownership, and acceptance-criterion coverage are computed rather than trusted from prose.
  • DKF Design Authority: design.md is the authoritative frontend visual source of truth when established for a project.
  • Live UI Preview: UI/design context automatically arms a project-local preview; DKF starts or reuses the declared dev server when runnable and exposes a provider-neutral browser display action while preserving independent VERIFY-time browser checks.
  • Token & Context Efficiency: Development Contract source sections are delivered as bounded excerpts, role contexts report estimated token profiles, and CI gates fixed instruction bloat.
  • DK Intelligence and DK Control Center: durable engineering context plus a local governance and inspection surface.
  • Provider-neutral research: source-backed research retains provenance, uncertainty, and explicit trust boundaries.
  • Numbered Decision Interface: bounded Product Owner choices resolve deterministically from structured runtime state.
  • Release validation: orchestration, execution safety, evidence/control coverage, reliability regressions, Intelligence, Design Authority, installer, documentation, platform adapters, research, Autopilot, and numbered-decision tests are part of the release gate.

Projects installed with earlier versions should follow the Migration Guide.

Reliability architecture

The current control-plane design is documented by:

Roadmap boundary

The v0.11–v1.0 roadmap is planned work, not current functionality.

The planned sequence is intentionally ordered around reliability:

  1. Adaptive Reliability and policy-driven lifecycle compilation.
  2. DKF Proof and Acceptance Certificates.
  3. Repository/PR enforcement.
  4. Public reliability benchmarking.
  5. Isolated execution.
  6. Safe parallelism.
  7. Multi-repository Change Contracts.
  8. Evidence-strength governance and verifier diversity.
  9. Control Center Flight Recorder.
  10. v1.0 only after the reliability claim is externally measurable.

See ROADMAP.md for release-by-release detail.

Documentation quick links

For the complete documentation page tree, see SUMMARY.md.