{{ theme.skipToContentLabel || 'Skip to content' }}

Source and Community Contribution

Status: published 0.3.0 stable release. Supported platforms: Windows and Linux. macOS is not yet officially supported.

Purpose

Change CoreMind source within its frozen public contracts, one-way dependencies, test-first workflow, bilingual material contract, and release authorization boundary, with repeatable proof that same-commit source, npm packages, the Python wheel, the independent source ZIP, and the documentation site agree.

Public interfaces

  • npm run build
  • npm test
  • npm run check
  • npm run check:modules
  • npm run docs:build
  • npm run docs:audit
  • npm run test:stability
  • npm run test:coverage
  • npm run baseline:check
  • npm run baseline:update -- --reason "approved change reason"
  • npm run release:check-npm
  • npm run release:test-npm
  • npm run release:test-source
  • npm run release:check-wheel
  • npm run providers:matrix
  • npm run release:preflight
  • npm run release:sync-version -- <semver>
  • npm run acceptance:rc
  • npm run release:bundle -- --tag <tag>

Errors and boundaries

  • Dependencies must remain config to tools to templates to runtime to facade/CLI/worker
  • Never push, tag, or publish without authorization
  • Preserve unrelated user changes
  • Update the frozen baseline only for an approved contract change with an explicit reason. Never lower a gate merely to make a failing result pass.
  • The current development commit, capture time, platform, and build hashes are trace evidence. The Release Tag target, Release Manifest digest, public APIs, schemas, dependency combinations, acceptance matrix, and quality floors are blocking contracts.
  • .scratch is reserved for ignored local acceptance evidence and isolated tool environments; it is excluded from Git, static checks, and artifacts.
  • Provider discovery is not certification; releases require live evidence
  • One passing test run does not replace three consecutive Windows/Linux runs. Record honest per-platform coverage floors below target, allow them only to increase, and set the generic fallback to their per-metric minimum.
  • Release artifacts must pass file allowlists, type resolution, clean installation, and bundled Worker startup.
  • Release Please creates a draft release PR only; maintainers still approve tags and publication.
  • External Actions use full commit SHAs and Dependabot proposes reviewable upgrades.
  • npm, Python build, and upload tools use explicit versions. If a registry yanks one, the RC must move to a verified non-yanked version and rerun artifact gates.
  • npm/PyPI trusted-publishing identity binds the workflow filename and protected environment; any mismatch stops publication.
  • Artifacts must come from one clean tag with SHA-256, a manifest, and build attestation.

CoreMind supplies mechanisms, quality guardrails, and development guidance. Users or business owners retain control of goals, rules, data fields, approval ownership, and final acceptance.

Source, tests, and examples

{{ theme.lastUpdated?.text || theme.lastUpdatedText || 'Last updated' }}:

Released under the MIT License.