Changelog¶
All notable changes to the foundation package are documented here.
[Unreleased]¶
Added¶
- twelve executable Milestone 11 whole-system scenarios spanning the documented web, package, service, worker, pipeline, embedded, framework, and legacy contexts;
- a deterministic evaluation runner with semantic assertions, scenario selection, and JSON reports.
Changed¶
make validatenow executes the whole-system evaluation suite and repository validation enforces complete Milestone 11 scenario structure and coverage.
[0.10.0] — 2026-08-07¶
Added¶
- six extended Core Skill packages covering dependency boundaries, state and side effects, API compatibility, performance and resources, distributed reliability, and engineering review lenses;
- eight artifact profiles for plugins, data pipelines, background workers, distributed systems, real-time systems, prototypes, CLI applications, and infrastructure tools;
- ten normative modifier packages with explicit activation, machine-readable Skill-mode effects, required decisions, prohibited decisions, and evaluation coverage;
- component scenarios covering every new Core Skill mode family, extended profile, and modifier;
- Milestone 9 and 10 validation for package completeness, catalogue parity, documentation, references, examples, and evaluation coverage.
Changed¶
- the orchestrator recognizes all extended artifact profiles, selects prototype work from lifecycle evidence, loads modifier effects from package metadata, and includes required decisions and prohibitions in resolved policy;
- controlled distributions and project documentation now include modifiers and all extended packages;
- foundation, schema, and component metadata versions advance to
0.10.0.
[0.8.0] — 2026-08-01¶
Added¶
- production-shaped React, Next.js, Vue, Nuxt, Angular, Symfony, and Drupal framework adapter packages with normative guidance, schema-validated metadata, and positive and negative decision examples;
- framework-specific policies for component and reactive state ownership, effects, server/client execution, SSR and hydration, caching, actions, DI, forms, messaging, persistence, extension APIs, entities, hooks, configuration, and cacheability metadata;
- seven framework evaluation scenarios and Milestone 8 validation of package completeness, focus coverage, evaluation coverage, dependency relationships, examples, and dependency acyclicity.
Changed¶
- controlled distributions, documentation maps, catalogue status, and project status now include all seven framework adapters;
- foundation and component metadata versions advance to
0.8.0.
[0.7.0] — 2026-08-01¶
Added¶
- production-shaped JavaScript, PHP, and Go language adapter packages with normative guidance, schema-validated metadata, and positive and negative decision examples;
- JavaScript refinements for runtime validation, coercion, mutation, promises, errors, modules, and package contracts, forming the implemented runtime parent of TypeScript;
- PHP refinements for strict typing limitations, value objects, exceptions, Composer packages, attributes and reflection, long-running processes, and framework interoperability;
- Go refinements for consumer-defined interfaces, explicit errors, context propagation, goroutine lifecycle, channels and shared state, package visibility, and benchmark-backed allocation decisions;
- evaluation scenarios demonstrating distinct JavaScript, PHP, and Go resolutions for the same reusable-library profile and task;
- Milestone 7 validation of adapter completeness, focus coverage, evaluation variance, TypeScript inheritance, and dependency acyclicity.
Changed¶
- controlled distributions, documentation maps, catalogue status, and project status now describe all six implemented target language adapters;
- foundation and component metadata versions advance to
0.7.0.
[0.6.0] — 2026-08-01¶
Added¶
- production-shaped TypeScript, Python, and C++ language adapter packages with normative guidance, schema-validated metadata, and positive and negative decision examples;
- language-specific refinements for runtime validation, typing, domain modeling, errors, resources, concurrency, packaging, public APIs, ABI, and undefined behavior;
- evaluation scenarios demonstrating distinct TypeScript, Python, and C++ resolutions for the same reusable-library profile and task;
- Milestone 6 validation of adapter completeness, focus coverage, catalogue inheritance, evaluation coverage, cross-language variance, and dependency acyclicity.
Changed¶
- controlled distributions, documentation maps, catalog status, and project status now include the representative language adapters;
- foundation and component metadata versions advance to
0.6.0.
[0.5.0] — 2026-08-01¶
Added¶
- five language-independent Project Profile MVP packages for browser, full-stack, backend service, reusable library, and legacy-modernization work;
- profile-specific evaluation scenarios that resolve the same DRY-versus-YAGNI conflict differently;
- validation of profile package completeness, documented modes, language independence, and cross-profile resolution variance.
Changed¶
- the orchestrator now loads default Core Skill modes from implemented profile metadata;
- controlled distributions and project status now include Project Profiles MVP content.
[0.4.0] — 2026-07-31¶
Added¶
- six language-independent Core Skill MVP packages covering clarity, abstraction and reuse, modular design, contracts and errors, testing strategy, and safe change;
- documented selection behavior for every supported mode, concrete conflict-resolution rules, positive and negative decision examples, and eighteen evaluation scenarios;
- validation of Core Skill package layout, catalogue consistency, conflict counts, documented modes, example polarity, and evaluation coverage.
Changed¶
- repository status now reflects completion of Milestone 4, and Core Skills are included in controlled distributions.
[0.3.0] — 2026-07-31¶
Added¶
- deterministic Orchestrator MVP with repository evidence detection, confidence-preserving context normalization, artifact-driven profile selection, modifier and adapter activation, override merging, conflict records, schema-validated resolved policies, and compact visible summaries;
tools/orchestrate.pyCLI with YAML, JSON, and summary output plus repository and user context inputs;- conservative
general-softwarefallback profile for materially uncertain artifact evidence; - repository-wide reference, identifier, dependency-cycle, duplicate-key, and Markdown-anchor validation;
- optional normative-keyword linting and continuous integration validation;
- negative fixtures covering malformed documents, schema violations, duplicate identifiers, dependency cycles, broken references, broken Markdown links, and normative-keyword casing.
Fixed¶
- resolved-policy examples now use canonical Core Skill, mode, and principle identifiers.
[0.2.0] — 2026-07-30¶
Added¶
- self-contained canonical registry containing 72 engineering entries;
- generated human-readable compendium and category indexes;
- explicit classification model for principles, heuristics, techniques, methods, properties, laws, patterns, and umbrella concepts;
- canonical rejected interpretations, trade-offs, conflicts, examples, and AI guidance;
- Core Skill, profile, modifier, language, and framework blueprint catalogues;
- Python as a first-class language adapter target alongside JavaScript, TypeScript, PHP, Go, and C++;
- principle, registry, relationship, modifier, and evaluation schemas;
- compendium generation, validation, and packaging tools;
- self-containment and knowledge-model documents;
- active-principle output in resolved policy examples.
Changed¶
- the project is explicitly both an AI policy system and a human-readable engineering compendium;
- external Skills are prohibited as normative dependencies;
- adapters refine canonical meaning but cannot redefine it;
- the project is named Code Principles and uses
code-principlesas its repository and package name; - plugin installation is described as planned rather than currently supported;
- release archives and manifests use an explicit distribution allowlist;
- generated-output freshness and version consistency are validated;
- the project is licensed under the MIT License.
[0.1.0] — 2026-07-30¶
Initial specification foundation with orchestrator, schemas, examples, and core architecture documents.