Documentación de DIXI Spec Kit English · Código en GitHub

Esta página está disponible solo en inglés; el resumen en español, si existe, está al final.

DIXI Spec Kit v1.0.0 publication gate

Purpose

Define concrete evidence per phase: preparation before creating the repository, configuration before exposing it, and verification of the launch. The user authorized its creation when ready; there is no need to request that general authorization again. Status as of 2026-11-08: v1.0.0 published. Still open: manual evaluation of the commands in Claude Code and full validation of ADR-101 (policy sets, outside v1.0.0).

The product/license, technical evidence and documentation/maintenance sections are entry requirements for publication. The creation of the repository and of the release are checked afterwards, in their own phases; they are not requirements for starting their own creation.

B1 local progress — 2026-11-06

Open direction and incremental start authorized. B1 verified: 43 tests, local wheel/sdist, clean installs, no-agent mode and make verify of the documentary project. This evidence is partial with respect to the launch requirements below; it does not confirm the full scope, upgrade, adapters, rights/license or publication controls. The global checkboxes remain open when they include work from later blocks.

Update 2026-11-07: B2a verified extends the suite to 71 cases and adds lookup/preparation of eight common procedures. It does not yet accredit agent execution/evaluation nor close global requirements.

Update 2026-11-08: the comparison with GitHub Spec Kit and ADR-102 propose reducing the minimum scope. Validated by the responsible person the same day, together with the MIT + DCO license and upgrade deferred to v1.1. The checkboxes that depended on the previous scope are adjusted to ADR-102.

Product and license

Technical evidence

Documentation and maintenance

Publication entry and repository configuration

The distributable selection and the clean history are reviewed before creating the remote. The protective configuration must be verified before exposing or announcing the repository. If it is first created as private to configure protections, the switch to public happens after reviewing the final content.

Launch