Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .agents/plugins/development-kit/plugin.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "development-kit",
"version": "0.11.1",
"version": "0.11.2",
"description": "DKF is an agent-independent reliability control plane for AI software development, with Development Contracts, independent verification, deterministic acceptance, design governance, persistent intelligence, Secrets & Configuration Readiness Gate, Live UI Preview, and safe autonomous workflows.",
"author": "Juan-Pierre Eybers",
"skills": [
Expand Down
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and

## [Unreleased]

## [0.11.2] - 2026-10-01

### Added
- **Development Modes**: Five project-owned development methodologies (Rapid, Balanced, Specification-Driven, Documentation-Driven, Maintenance & Evolution) with revisioned persistence, deterministic policy resolution, mode-aware artifact/planning behavior and immutable Development Contract mode snapshots.
- **IDEA Authority Runtime**: Explicit requirement provenance, persisted one-question-at-a-time numbered interactions, exact interaction fingerprints, crash-safe discovery journaling, replay-protection receipts, Product Owner-bound Design Authority disposition and source-bound Idea Brief approval.
Expand Down
21 changes: 14 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,21 +38,29 @@ DKF is designed around that problem.

It provides an agent-independent engineering runtime that binds work to explicit contracts, preserves provenance, isolates verification, computes control coverage, detects drift and stale authority, and derives acceptance from evidence.

The current release line is **v0.11.1**.
The current release line is **v0.11.2**.

v0.11 introduces the **Secrets & Configuration Readiness Gate**, a non-bypassable runtime control-plane gate that detects when project development depends on external configuration or secrets requiring Product Owner action (API keys, database credentials, public environment variables, tenant IDs, OAuth secrets, generated application secrets, or provider consoles).

v0.11.1 adds **Live UI Preview & Visual Verification** and **Token & Context Efficiency Hardening**.

v0.11.2 integrates **Development Modes** (Rapid, Balanced, Specification-Driven, Documentation-Driven, Maintenance & Evolution) and **IDEA Authority Hardening** (provenance tracking, fingerprinted interactions, replay protection, and source-bound Idea Brief approvals).

> **Completion is a computed state, not an agent assertion.**

DKF is not a project-management dashboard and is not intended to replace engineering judgment. It is a reliability and execution-governance layer for turning intent into evidence-backed, release-ready software changes.

---

## Current release: v0.11.1
## Current release: v0.11.2

The current released baseline is **v0.11.2**.

The current released baseline is **v0.11.1**.
### v0.11.2 — Development Modes & IDEA Authority Hardening

v0.11.2 ships the integrated methodology and requirements authority controls:
- **Development Modes**: Five developer methodologies with revisioned project configuration (`.development-kit/development-mode.json`), mode-aware artifact and planning rules, and immutable contract mode snapshots.
- **IDEA Authority Hardening**: Bounded one-question-at-a-time interactions, cryptographic interaction fingerprints, replay-protection receipts, crash-safe journal persistence, Product Owner-bound Design Authority disposition, and canonical Idea Brief approval locked to exact artifact/design/discovery fingerprints.

### v0.11.1 — Live UI Preview & Token Efficiency

Expand Down Expand Up @@ -183,14 +191,13 @@ The long-term architecture focuses on:

Read the full [DKF Strategic Direction](STRATEGY.md).

### Post-v0.11.1 mainline additions
### v0.11.2 release highlights

The published release remains **v0.11.1**. Current `main` also contains two fully integrated, release-gated additions that are **not yet part of a published package release**:
The published release is **v0.11.2**, consolidating:

- **Development Modes** — Rapid, Balanced, Specification-Driven, Documentation-Driven, and Maintenance & Evolution; persisted methodology policy is revisioned and immutably bound into new Development Contracts without weakening mandatory DKF controls.
- **IDEA Authority Hardening** — explicit requirement provenance, Product Owner-bound transitions, one persisted fingerprinted interaction at a time, crash-safe discovery journaling, replay-proof consumption receipts, Design Authority binding, and Idea Brief approval bound to exact discovery/design/artifact fingerprints.

Both additions passed the repository's full Ubuntu and Windows release-validation matrix before merge. Their presence on `main` does not imply npm/GitHub release publication until the next versioned release is explicitly created.
- **Workflow Modernization** — GitHub Actions workflows updated to current actions (`checkout@v7`, `setup-node@v7`, `configure-pages@v6`, `upload-pages-artifact@v5`, `deploy-pages@v5`), removing deprecated Node 20 runtime warnings.

---

Expand Down
35 changes: 3 additions & 32 deletions ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This roadmap is directional. It distinguishes current capability from planned wo

---

## Current baseline — v0.11.1
## Current baseline — v0.11.2

The current release provides the reliability foundation:

Expand All @@ -29,6 +29,8 @@ The current release provides the reliability foundation:
- Secrets & Configuration Readiness Gate;
- Live UI Preview for UI/design work;
- Token/context efficiency hardening with scoped authoritative-source delivery, role token profiles, compact runtime prompts, and CI budgets;
- Development Modes (Rapid, Balanced, Specification-Driven, Documentation-Driven, Maintenance & Evolution);
- IDEA Authority Hardening with requirement provenance, crash-safe journal recovery, and replay-protection receipts;
- structured idea-suggestion promotion;
- adversarial regression testing;
- cross-platform agent integrations.
Expand All @@ -37,37 +39,6 @@ The remaining roadmap is about making this reliability model **adaptive, portabl

---

## Integrated post-v0.11.1 mainline work

The published baseline remains **v0.11.1**, while current `main` contains the following release-gated additions awaiting a future versioned release:

### Development Modes

- five developer-facing methodologies with Balanced as the default;
- revisioned project-owned mode state and explicit mode-change history;
- deterministic policy resolution and recommendation;
- mode-aware specification, artifact and planning behavior;
- immutable Development Contract mode snapshots;
- Maintenance & Evolution repository-audit obligations;
- preservation of all mandatory reliability, evidence, safety and Product Owner controls.

Development Modes was integrated through PR #53 after the full Ubuntu/Windows release-validation matrix passed.

### IDEA Authority Hardening

- explicit USER_STATED / USER_CONFIRMED / AI_PROPOSED / RESEARCH_DERIVED / ASSUMED provenance;
- Product Owner-bound legal transitions and scope decisions;
- one persisted, fingerprinted numbered interaction at a time;
- journal-first discovery persistence and restart recovery;
- hash-chained replay-protection receipts;
- Product Owner-bound Design Authority disposition;
- canonical Idea Brief approval tied to exact artifact/discovery/design fingerprints;
- direct-edit, stale-source, replay and corruption fail-closed behavior.

IDEA Authority Hardening was integrated through PR #54 after the full Ubuntu/Windows release-validation matrix passed.

---

## v0.12 — Adaptive Reliability

### Objective
Expand Down
8 changes: 5 additions & 3 deletions STRATEGY.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,9 @@ That is the category DKF is designed to own.

---

## 1. Current baseline: v0.11.1
## 1. Current baseline: v0.11.2

The current released baseline is **v0.11.1**.
The current released baseline is **v0.11.2**.

DKF already includes the foundations of the reliability-control-plane model:

Expand All @@ -35,9 +35,11 @@ DKF already includes the foundations of the reliability-control-plane model:
- a non-bypassable Secrets & Configuration Readiness Gate that prevents invented credentials/configuration and keeps secret values outside AI context;
- Live UI Preview for continuous rendered frontend visibility;
- token/context efficiency through scoped authority, compact role prompts, measurable context budgets, and structured reference-first handoffs;
- **Development Modes** with project-owned methodology policies and immutable contract mode snapshots;
- **IDEA Authority Hardening** with requirement provenance, crash-safe journal recovery, and replay-protection receipts;
- adversarial regression coverage based on real development failures.

These are implemented capabilities in the published v0.11.1 release line. Current `main` additionally contains release-gated Development Modes and IDEA Authority Hardening; they are integrated source capabilities but must not be presented as published v0.11.1/npm functionality until a subsequent versioned release is created. The roadmap below describes later evolution and likewise must not be interpreted as already-published functionality.
These are implemented capabilities in the published v0.11.2 release line. The roadmap below describes later evolution and must not be interpreted as already-published functionality.

---

Expand Down
4 changes: 2 additions & 2 deletions docs/01-overview/framework-at-a-glance.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# Framework at a Glance

A quick-reference summary of **Development Kit** (`v0.11.1`):
A quick-reference summary of **Development Kit** (`v0.11.2`):

| Aspect | Summary Metric / Value |
| :--- | :--- |
| **Framework Version** | `0.11.1` |
| **Framework Version** | `0.11.2` |
| **Node Requirement** | `>=18.0.0` |
| **Commands** | 16 commands (`/dk-autopilot`, `/dk-idea`, `/dk-research`, `/dk-spec`, `/dk-design`, `/dk-design-system`, `/dk-tasks`, `/dk-build`, `/dk-build-auto`, `/dk-test`, `/dk-review`, `/dk-simplify`, `/dk-debug`, `/dk-ship`, `/dk-control`, `/dk-status`) |
| **Agents** | 18 specialized roles (`development-conductor`, `repository-scout-agent`, `specification-agent`, `implementation-agent`, `code-reviewer`, `security-reviewer`, etc.) |
Expand Down
2 changes: 1 addition & 1 deletion docs/01-overview/what-is-development-kit.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# What is Development Kit?

**Development Kit** (`development-kit@0.11.1`) is an opinionated, installable AI software-development methodology and skill collection designed for **Antigravity**, **OpenCode**, and leading AI coding environments.
**Development Kit** (`development-kit@0.11.2`) is an opinionated, installable AI software-development methodology and skill collection designed for **Antigravity**, **OpenCode**, and leading AI coding environments.

It equips AI agents with senior software-engineering discipline, preventing common failure modes such as hallucinated architectures, unverified implementations, scope creep, over-engineering, visual design drift, assumptions drift, unsafe host-level commands, stale artifact amendments, and agent self-certification.

Expand Down
2 changes: 1 addition & 1 deletion docs/02-user-guide/prerequisites.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Prerequisites

Before installing Development Kit (`development-kit@0.11.1`), ensure your environment meets the following requirements:
Before installing Development Kit (`development-kit@0.11.2`), ensure your environment meets the following requirements:

## System & Software Requirements

Expand Down
4 changes: 2 additions & 2 deletions docs/02-user-guide/verifying-installation.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Verifying Installation

Use the checks below after installing Development Kit v0.11.1.
Use the checks below after installing Development Kit v0.11.2.

## Verify the published package

Expand All @@ -11,7 +11,7 @@ npm view development-kit version
Expected current version:

```text
0.11.1
0.11.2
```

## Verify framework integrity
Expand Down
2 changes: 1 addition & 1 deletion docs/03-reference/configuration/manifests-and-configs.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Reference for the configuration files that define Development Kit packaging and
| Field | Current value | Notes |
|---|---|---|
| `name` | `development-kit` | Public npm package name |
| `version` | `0.11.1` | Current package version and `v0.11.1` release |
| `version` | `0.11.2` | Current package version and `v0.11.2` release |
| `description` | Disciplined AI software-development workflow for Antigravity and OpenCode | Public package description |
| `license` | `MIT` | Root license file is included in the package |
| `bin` | `development-kit` to `scripts/install-antigravity.mjs` | Enables `npx development-kit init` |
Expand Down
6 changes: 3 additions & 3 deletions docs/08-maintenance-release/npm-publishing.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,10 @@ Verify the current public version with:
npm view development-kit version
```

For the v0.11.1 release, the expected value is:
For the v0.11.2 release, the expected value is:

` ext
0.11.1
```text
0.11.2
```

## Required credentials
Expand Down
40 changes: 40 additions & 0 deletions docs/08-maintenance-release/release-notes-v0.11.2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
# Release Notes v0.11.2

**Released:** 1 October 2026

## Development Modes, IDEA Authority Hardening & Workflow Modernization

Development Kit v0.11.2 integrates project-owned Development Modes and comprehensive IDEA Authority Hardening on top of the v0.11.1 Live UI Preview and Token Efficiency foundation, along with modernizing GitHub Actions workflow runtimes.

### Development Modes

- Five developer-facing methodologies: **Rapid**, **Balanced** (default), **Specification-Driven**, **Documentation-Driven**, and **Maintenance & Evolution**.
- Revisioned project-owned mode state (`.development-kit/development-mode.json`) with deterministic policy resolution, recommendation heuristics, and explicit change-control history.
- Mode-aware specification, artifact planning, and task decomposition behavior.
- Immutable Development Contract mode snapshots (`modeSnapshot`) with fingerprint verification; mode changes apply forward to new contracts without retroactively modifying existing contracts.
- Maintenance & Evolution mode enforces repository audit obligations before implementing changes.
- Mandatory reliability, verification, security, and Product Owner approval controls remain strictly non-bypassable across all modes.

### IDEA Authority Hardening

- Explicit requirement provenance tracking: `USER_STATED`, `USER_CONFIRMED`, `AI_PROPOSED`, `RESEARCH_DERIVED`, and `ASSUMED`.
- Bounded interaction flow presenting one persisted numbered interaction at a time with cryptographic interaction fingerprints.
- Journal-first, hash-chained persistence for discovery state with crash recovery and corruption fail-closed protection.
- Interaction consumption protected by hash-chained receipts preventing replay attacks.
- Design Authority applicability and disposition bound to Product Owner authority; mock authority state is rejected.
- Canonical Idea Brief (`docs/01-concept/idea-brief.md`) approval bound to exact artifact, discovery, and design fingerprints.
- Fails closed on stale sources, direct manual edits, replay attempts, or authority chain tampering.

### Modernization & Reliability

- Development Contract schema updated to v1.2.0 for mode-snapshot binding while maintaining backward compatibility with v1.0 and v1.1 contracts.
- Suggestion promotion strictly requires explicit Product Owner authority.
- GitHub Actions modernized to current actions (`checkout@v7`, `setup-node@v7`, `configure-pages@v6`, `upload-pages-artifact@v5`, `deploy-pages@v5`), eliminating deprecated Node 20 runtime warnings.

### Release Facts

- Package version: `0.11.2`.
- Public command surface: 16 workflow commands.
- Canonical engineering-skill count: 48.

See `CHANGELOG.md` for the complete change record.
6 changes: 3 additions & 3 deletions docs/README.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# Development Kit Framework Documentation

Welcome to the official documentation for **Development Kit Framework v0.11.0** (`development-kit@0.11.0`).
Welcome to the official documentation for **Development Kit Framework v0.11.2** (`development-kit@0.11.2`).

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

> **AI can write it. DKF proves it.**

The current v0.11.1 release brings together the Secrets & Configuration Readiness Gate (v0.11.0), Live UI Preview visual verification, and Token & Context Efficiency hardening. It already provides Development Contracts, independent verification, deterministic acceptance, execution-safety controls, DKF Design Authority, DK Intelligence, DK Control Center, and the Numbered Decision Interface. The future direction is published separately so planned capabilities are never confused with implemented behavior.
The current v0.11.2 release brings together Development Modes and IDEA Authority Hardening on top of the Live UI Preview visual verification, Token & Context Efficiency hardening, and the Secrets & Configuration Readiness Gate. It provides Development Contracts, independent verification, deterministic acceptance, execution-safety controls, DKF Design Authority, DK Intelligence, DK Control Center, and the Numbered Decision Interface. The future direction is published separately so planned capabilities are never confused with implemented behavior.

## Strategic documents

Expand All @@ -16,7 +16,7 @@ The current v0.11.1 release brings together the Secrets & Configuration Readines

## Current release highlights

| Package Version | 0.11.1 |
| Package Version | 0.11.2 |
| Lifecycle Stages | 9 (UNDERSTAND through COMPLETE) |
| Workflow Commands | 16 |
| Specialist Agents | 18 |
Expand Down
1 change: 1 addition & 0 deletions docs/SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -310,6 +310,7 @@
* [Release Notes (v0.10.1 superseded candidate)](08-maintenance-release/release-notes-v0.10.1.md)
* [Release Notes (v0.11.0)](08-maintenance-release/release-notes-v0.11.0.md)
* [Release Notes (v0.11.1)](08-maintenance-release/release-notes-v0.11.1.md)
* [Release Notes (v0.11.2)](08-maintenance-release/release-notes-v0.11.2.md)

## 09. Contributing
* [Contribution Overview](09-contributing/contribution-overview.md)
Expand Down
6 changes: 3 additions & 3 deletions memory.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,14 +2,14 @@

## Published Baseline

- **Current published release:** v0.11.1 (30 September 2026).
- **Package version on `main`:** 0.11.1 until the next explicit versioned release.
- **Current published release candidate:** v0.11.2 (1 October 2026).
- **Package version:** 0.11.2.
Comment on lines +5 to +6

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Reconcile project memory with the v0.11.2 release state

After changing the baseline here to a v0.11.2 release candidate, this file still labels Development Modes and IDEA Authority Hardening as post-v0.11.1 mainline work and states at lines 59 and 66 that v0.11.1 is published while those capabilities remain unpublished; meanwhile README, STRATEGY, ROADMAP, and the new release notes now describe v0.11.2 as released. This leaves the repository's release authority contradictory both before publication and afterward, so these remaining sections should consistently describe either a candidate or the completed v0.11.2 release.

Useful? React with 👍 / 👎.

- **Core lifecycle:** `UNDERSTAND → DEFINE → DESIGN → PLAN → IMPLEMENT → VERIFY → REVIEW → SIMPLIFY → COMPLETE`.
- **Public command surface:** 16 workflow commands.
- **Engineering skills:** 48.
- **Primary position:** DKF is the reliability control plane for agentic software development — **AI can write it. DKF proves it.**

## Published v0.11.1 Reliability Controls
## v0.11.2 Reliability Controls

- Development Contracts with authoritative-source fingerprints.
- Independent verification and deterministic `BLOCKED / PENDING / ACCEPTED` acceptance.
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "development-kit",
"version": "0.11.1",
"version": "0.11.2",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Publish the new capabilities under a minor version

This release adds user-facing runtime capabilities—Development Modes and IDEA Authority Hardening—while changing 0.11.1 to the patch version 0.11.2. The repository's docs/08-maintenance-release/versioning-policy.md explicitly reserves MINOR releases for backward-compatible runtime capabilities and user-facing features, and PATCH releases for fixes, documentation, validation, and maintenance. Publishing these additions as 0.11.2 therefore violates the advertised compatibility contract and cannot be repaired after that npm version is published; use the next minor version and align the other release references.

Useful? React with 👍 / 👎.

"description": "DKF is an agent-independent reliability control plane for AI software development, with Development Contracts, independent verification, deterministic acceptance, design governance, persistent intelligence, Secrets & Configuration Readiness Gate, Live UI Preview, and safe autonomous workflows.",
"author": "Juan-Pierre Eybers",
"license": "MIT",
Expand Down
2 changes: 1 addition & 1 deletion runtime/autopilot/transition-model.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ export function createInitialState(options = {}, rootDir = process.cwd()) {
stateRevision: 1,
createdAt: now,
updatedAt: now,
frameworkVersion: '0.11.1'
frameworkVersion: '0.11.2'
};
}

Expand Down
Loading