mirai-graph 1.4.0 → 2.1.0

package/releases/1.0.0-rc.2.md

@@ -1,79 +0,0 @@
-# Mirai Graph v1.0.0-rc.2
-
-Status: release candidate prepared in repository; tag, GitHub Release and npm
-publish require separate release execution.
-
-## Theme
-
-Self-Service Onboarding And Public Documentation Hardening.
-
-This release candidate builds on `v1.0.0-rc.1` by making Mirai Graph easier to
-adopt from an external project checkout while keeping the same safety boundary:
-Mirai Graph validates graph-managed structure, evidence, process state and
-governance gates; it does not execute production actions or authorize canonical
-updates by itself.
-
-## Added
-
-- Self-service onboarding CLI flow:
-  - `mirai-graph init`;
-  - `mirai-graph detect`;
-  - `mirai-graph bootstrap`.
-- Synthetic self-service onboarding fixtures for:
-  - project without a graph;
-  - existing graph;
-  - stale or incomplete graph;
-  - generated bootstrap proposal.
-- GitHub Action starter for validating a Mirai Graph package.
-- "Connect A Project In 15 Minutes" tutorial.
-- Developer-first entry guide explaining concrete problems, created files,
-  expected outputs and AI-assisted development use cases.
-- Documentation map in `docs/README.md`.
-- Public-safe Societal Governance proposal profile and synthetic fixtures.
-- Negative fixtures for proposal-level societal-governance safety boundaries.
-
-## Changed
-
-- Public README is now a shorter landing page with npm-first quickstart,
-  developer-first problem framing, created-file expectations, role paths and a
-  "what should I read first" table.
-- Adoption docs now distinguish npm usage from contributor checkout usage.
-- Release notes and roadmap now reflect self-service onboarding as part of the
-  release-candidate surface.
-- Societal Governance is explicitly marked proposal/experimental, not a core
-  `1.0.0` conformance profile.
-
-## Validation
-
-```bash
-npm test
-npm run release:check
-npm run validate:self-service-onboarding
-npm run validate:init-fixtures
-npm run validate:bootstrap-fixtures
-npm run validate:societal-governance
-npm run test:societal-governance-negative
-npm run validate:release-state
-```
-
-## Claim Boundary
-
-This release candidate supports the claim that Mirai Graph has a coherent,
-validator-backed public standard shape and a usable self-service onboarding
-path for external review.
-
-It does not claim:
-
-- peer-reviewed scientific proof;
-- broad external validity;
-- production autonomous execution safety;
-- final stable `1.0.0`;
-- core conformance for the proposal-level Societal Governance profile;
-- automatic canonical updates from generated context, evidence, feedback,
-  cockpit metrics or proposals;
-- npm package publication until npm release-state checks confirm publication.
-
-## Release Execution Boundary
-
-This file is release preparation only. Creating a git tag, GitHub Release or npm
-publication must happen as a separate explicit release execution step.

package/releases/1.0.0-rc.3.md

@@ -1,51 +0,0 @@
-# Mirai Graph v1.0.0-rc.3
-
-Status: release candidate prepared in repository; tag, GitHub Release and npm
-publish require separate release execution.
-
-## Theme
-
-Developer-First Onboarding.
-
-This release candidate makes the repository easier for an ordinary developer to
-understand before reading the full standard. It explains the concrete software
-project problems Mirai Graph solves, what can be done in 10 minutes, what files
-are created and how graph structure helps AI-assisted development.
-
-## Added
-
-- Developer-focused guide:
-  [Mirai Graph For Developers](../docs/adoption/for-developers.md).
-- README sections for:
-  - concrete project problems;
-  - developer use cases;
-  - current npm publication status;
-  - created files and generated bootstrap proposal output;
-  - how Mirai Graph helps AI assistants.
-
-## Changed
-
-- README now starts from developer value instead of abstract standard framing.
-- Documentation map links to the developer entry point.
-- Getting-started and 15-minute tutorial now point developers to the practical
-  guide and state the current pre-npm publication boundary.
-- Playground and active evidence docs are aligned to `1.0.0-rc.3`.
-
-## Validation
-
-```bash
-npm test
-npm run release:check
-npm run validate:release-state
-```
-
-## Claim Boundary
-
-This release candidate improves onboarding and documentation clarity. It does
-not claim final stable `1.0.0`, npm publication, peer-reviewed proof,
-production autonomous execution safety or automatic canonical updates.
-
-## Release Execution Boundary
-
-This file is release preparation only. Creating a git tag, GitHub Release or npm
-publication must happen as a separate explicit release execution step.

package/releases/1.0.0-rc.4.md

@@ -1,70 +0,0 @@
-# Mirai Graph 1.0.0-rc.4
-
-Status: release-candidate
-Date: 2026-06-16
-
-## Summary
-
-`1.0.0-rc.4` adds the proposal/experimental Dynamic Episode Layer. This layer
-records how a concrete event moves through a Mirai Graph-governed process:
-which objects, relations, policies, gates and technology steps activate, which
-path is selected, which alternatives are blocked, what evidence is produced and
-which findings should route to feedback, Kaizen or replay/regression.
-
-The release keeps the central Mirai Graph boundary:
-
-```text
-episode trace = evidence
-episode trace != authorization
-episode trace != canonical graph update
-```
-
-## Added
-
-- Dynamic Episode standard documents:
-  - [Dynamic Episode Layer](../standard/dynamic-episode-layer.md)
-  - [Episode Trace](../standard/episode-trace.md)
-  - [Dynamic Layer For AI-Assisted Code Generation](../standard/dynamic-layer-code-generation.md)
-- Dynamic episode trace schema:
-  - [dynamic-episode-trace.schema.json](../schemas/dynamic-episode-trace.schema.json)
-- Synthetic dynamic episode example:
-  - [dynamic-episode-minimal](../examples/dynamic-episode-minimal/README.md)
-- Positive validation and negative fixtures for:
-  - canonical write allowed;
-  - evidence treated as authorization;
-  - missing event;
-  - missing selected path;
-  - unclassified finding.
-
-## Changed
-
-- CLI validation supports:
-
-```bash
-npx mirai-graph report dynamic-episode examples/dynamic-episode-minimal/results/dynamic-episode-trace.json
-node packages/cli/validate-mirai-graph.js dynamic-episode-trace examples/dynamic-episode-minimal/results/dynamic-episode-trace.json
-```
-
-- `npm test` includes Dynamic Episode positive, report and negative checks.
-- README, docs map, CLI docs, roadmap and test-suite documentation now mention
-  the Dynamic Episode Layer as proposal/experimental.
-- Architecture-boundary guidance now documents profile boundaries,
-  extension-before-profile, core/proposal/experimental status separation and
-  anti-RAG/anti-bulk-content Hybrid SOT rules.
-
-## Validation
-
-Release consolidation checks:
-
-```bash
-npm test
-npm run release:check
-git diff --check
-```
-
-## Claim Boundary
-
-This release validates the public shape and safety boundaries of Dynamic Episode
-tracing. It does not claim that real AI-assisted code generation drift is
-reduced. That requires private or public pilot evidence with replay/regression
-metrics.

package/releases/1.0.0-rc.5.md

@@ -1,88 +0,0 @@
-# Mirai Graph 1.0.0-rc.5
-
-Status: release-candidate
-Date: 2026-06-27
-
-## Summary
-
-`1.0.0-rc.5` adds Semantic Intent Resolution as an input-control extension
-contract and adds Goal Vector Quality Control as a quality-control extension
-contract.
-
-The contract turns a free-form request into a governed decision before
-execution starts:
-
-```text
-request
--> intent hypothesis
--> work scale
--> owner/process decision
--> context-slot check
--> clarification, brief, workflow restore or safe execution
-```
-
-This is not a new standalone profile and not a knowledge-storage layer. It is a
-control boundary that helps projects, organizations and AI employees avoid
-starting the wrong process from an ambiguous request.
-
-## Added
-
-- Standard document:
-  - [Semantic Intent Resolution](../standard/semantic-intent-resolution.md)
-- Schema:
-  - [semantic-intent-resolution.schema.json](../schemas/semantic-intent-resolution.schema.json)
-- Synthetic example:
-  - [semantic-intent-resolution-minimal](../examples/semantic-intent-resolution-minimal/README.md)
-- Negative fixtures for:
-  - low confidence allowing execution;
-  - generated proposal treated as canonical update.
-- Goal Vector Quality Control standard:
-  - [Goal Vector Quality Control](../standard/goal-vector-quality-control.md)
-- Schema:
-  - [goal-vector-quality-control.schema.json](../schemas/goal-vector-quality-control.schema.json)
-- Synthetic example:
-  - [goal-vector-quality-control-minimal](../examples/goal-vector-quality-control-minimal/README.md)
-- Negative fixtures for:
-  - missing batch vector link;
-  - completion without evidence;
-  - tests treated as acceptance;
-  - missing reverse audit;
-  - correction finding without route.
-
-## Changed
-
-- `package.json` version is now `1.0.0-rc.5`.
-- CLI validation supports:
-
-```bash
-node packages/cli/validate-mirai-graph.js semantic-intent-resolution examples/semantic-intent-resolution-minimal/results/semantic-intent-resolution.json
-```
-
-- `npm test` includes Semantic Intent Resolution positive and negative checks.
-- `npm test` includes Goal Vector Quality Control positive and negative
-  checks.
-- README and documentation map now list the contract in the core standard
-  navigation.
-
-## Validation
-
-Release consolidation checks:
-
-```bash
-npm run validate:semantic-intent-resolution
-npm run test:semantic-intent-resolution-negative
-npm run validate:goal-vector-quality-control
-npm run test:goal-vector-quality-control-negative
-npm test
-npm run release:check
-git diff --check
-```
-
-## Claim Boundary
-
-This release validates the public shape and safety boundaries of Semantic
-Intent Resolution and Goal Vector Quality Control. It does not prove that AI
-agents always choose the correct process, does not prove broad real-world drift
-reduction, does not authorize live or destructive actions, does not update
-canonical graph state from generated briefs, evidence, audits or proposals and
-does not prove production readiness.

package/releases/1.0.0-rc.6.md

@@ -1,76 +0,0 @@
-# Mirai Graph 1.0.0-rc.6
-
-Status: release-candidate
-Date: 2026-06-27
-
-## Summary
-
-`1.0.0-rc.6` consolidates the anti-drift / quality-control contour across
-existing Mirai Graph release-candidate layers:
-
-```text
-Semantic Intent Resolution
--> Process and Technology Control
--> Dynamic Episode Trace
--> Goal Vector Quality Control
--> Technology Quality Feedback
--> Kaizen / Replay / Regression Candidate
-```
-
-This release does not introduce a new authorization layer. It presents already
-validator-backed public artifacts as one coherent model for inspecting whether
-AI-assisted work started from the right intent, followed the declared process,
-recorded what happened, advanced the final outcome and routed drift findings to
-correction.
-
-## Consolidated Standard Surface
-
-- [Semantic Intent Resolution](../standard/semantic-intent-resolution.md)
-  checks the input decision before execution starts.
-- [Dynamic Episode Layer](../standard/dynamic-episode-layer.md) records what
-  happened in one governed event and why a path was selected or blocked.
-- [Goal Vector Quality Control](../standard/goal-vector-quality-control.md)
-  checks whether meaningful work moved toward the final outcome.
-- [Technology Quality Feedback](../standard/technology-quality-feedback.md)
-  checks whether the declared technology or method was followed before
-  acceptance or release.
-- [Process Control Contract](../standard/process-control-contract.md) keeps
-  launch, transition, evidence and false-transition guards explicit.
-
-## Publication Foundations
-
-This release adds public-safe foundations for two article candidates:
-
-- [Semantic Intent And Goal Vector Control](../publications/semantic-intent-goal-vector-control/README.md)
-- [Observable Self-Correcting AI Workflows](../publications/observable-self-correcting-ai-workflows/README.md)
-
-Both foundations are scaffolds, not submitted papers. They define research
-questions, hypotheses, artifact inventory, metrics, limitations and next
-evidence needed before publication claims.
-
-## Validation
-
-Release consolidation checks:
-
-```bash
-npm run validate:semantic-intent-resolution
-npm run validate:goal-vector-quality-control
-npm run validate:dynamic-episodes
-npm run validate:technology-quality-feedback
-npm test
-npm run release:check
-git diff --check
-```
-
-## Claim Boundary
-
-This release validates public shapes, examples, negative fixtures and
-documentation alignment for the consolidated anti-drift contour.
-
-It does not prove broad real-world drift reduction, does not prove autonomous
-production safety, does not authorize live or destructive actions, does not
-update canonical graph state from generated briefs, traces, evidence, audits or
-proposals and does not claim peer-reviewed scientific proof.
-
-Sanitized pilot/replay evidence is still required before stronger effectiveness
-claims.

package/releases/1.0.0-rc.8.md

@@ -1,17 +0,0 @@
-# Mirai Graph 1.0.0-rc.8
-
-This release candidate introduces one public Project Technology mechanism for
-projects, skills, platforms and federations while preserving their separate
-domain graphs and Hybrid Source Of Truth boundaries.
-
-## Verified outcome
-
-- one `graph.json` manifest and one `mirai.project_technology` extension;
-- task-scoped context and safe tracked-file inventory;
-- complete target provider export and consumer binding;
-- forward-only, idempotent refresh-binding;
-- read-only diagnostics alongside fail-closed significant work;
-- no private source or full graph copied into bounded exports.
-
-Stable `1.0.0` remains deferred until this RC has been exercised by the SIMAI
-Federation and all release-managed skills.

package/releases/1.0.0-rc.9.md

@@ -1,14 +0,0 @@
-# Mirai Graph 1.0.0-rc.9
-
-This release candidate fixes the public Project Technology CLI boundary found
-during the Federation migration pilot.
-
-## Verified outcome
-
-- a command run from a project without a repository argument uses that project;
-- an explicit `.` is resolved from the caller's working directory;
-- absolute repository paths keep working;
-- the Project Technology contract and safety gates are unchanged from RC.8.
-
-Stable `1.0.0` remains deferred until this RC has been exercised by the SIMAI
-Federation and all release-managed skills.

package/releases/1.0.0.md

@@ -1,23 +0,0 @@
-# Mirai Graph 1.0.0
-
-Mirai Graph 1.0.0 is the first stable public release.
-
-## What is stable
-
-- one `graph.json` manifest and exact `graph.lock.json` imports;
-- public Project Technology CLI and programmatic API;
-- task-scoped context, accepted target and architecture checks;
-- bounded provider export/import and safe refresh-binding;
-- fail-closed verification for stale, incomplete or tampered contracts;
-- read-only diagnostics and idempotent transactional operations.
-
-## Verified use
-
-The release-candidate series was integrated into Federation 8.20.0 across 25
-managed skills. Stable 1.0 keeps the same public schema and safety boundaries.
-
-## Claim boundary
-
-Stable status covers the published contracts, CLI and release checks. Project
-results still require project-specific goals, evidence, tests and human
-decisions at product or architecture boundaries.

package/releases/1.1.0.md

@@ -1,36 +0,0 @@
-# Mirai Graph 1.1.0
-
-Mirai Graph 1.1.0 adds universal, sequential context traversal to the existing
-Project Technology mechanism.
-
-## What changed
-
-- A caller can discover top-level candidates, expand selected branches to any
-  depth, compile the mandatory closure and verify actual use.
-- The same protocol is available through the CLI and JavaScript API.
-- Required processes, constraints and validators are included independently of
-  a model's selection.
-- Context packs are deterministic, revision-bound and safe to transfer without
-  copying private source content.
-
-## What was validated
-
-- Software, research, organization, platform, skill-like and
-  multi-repository fixtures.
-- Sequential and batched expansion equivalence.
-- Fail-closed behavior for incomplete, stale, blocked, deprecated, conflicting,
-  cyclic, tampered and over-budget context.
-- Zero-write read-only behavior and compatibility with the existing Project
-  Technology provider/consumer contract.
-- A dedicated traversal job on macOS, Linux and Windows.
-
-## Compatibility
-
-`graph.json` remains schema `2.0.0`; the Project Technology activation contract
-remains `1.0.0`; existing graphs do not require migration.
-
-## Claim boundary
-
-The release proves deterministic contract behavior on the maintained fixtures.
-It does not claim that automatic ranking alone understands every domain or that
-a generated context pack authorizes changes.

package/releases/1.1.1.md

@@ -1,25 +0,0 @@
-# Mirai Graph 1.1.1
-
-Mirai Graph 1.1.1 is a compatibility correction for sequential context
-traversal.
-
-## What changed
-
-- Existing graph 2.0.0 object and relation aliases are normalized in memory.
-- Skill-style `implements`, `has_capability`, `validates` and related accepted
-  relations retain their structural or mandatory meaning.
-- Accepted historical readiness levels remain executable, while incomplete and
-  unsafe states still block compilation.
-
-## Why this patch is needed
-
-The 1.1.0 traversal fixtures used the newest field names, while long-lived
-graphs used accepted older aliases. The result was a false loss of nested
-context and two blocked repositories. This patch fixes the reader instead of
-forcing every consumer to rewrite its graph.
-
-## Evidence boundary
-
-The release candidate is accepted only when the full test suite and real
-multi-repository consumer harness are green. Publication remains a separate
-external action.

package/releases/1.2.0.md

@@ -1,19 +0,0 @@
-# Mirai Graph 1.2.0
-
-Mirai Graph 1.2.0 adds portable project continuity to the existing Project
-Technology mechanism.
-
-Verified outcomes, requirements, evidence and reusable cases can now be stored
-in `graph/specs` and discovered automatically by a later task. The mechanism
-does not store chat transcripts and does not introduce a second memory database.
-
-Mutable receipts and rollback data remain on the current host. Git repositories
-and ordinary shared folders use the same canonical graph contract; shared-folder
-writes additionally use a lease and compare-and-swap digest.
-
-Goals, architectural decisions and owner or source-of-truth changes remain
-proposals until explicitly accepted. A generated context document remains a
-readable projection rather than a source of truth or write authorization.
-
-`graph.json` remains schema `2.0.0` and
-`mirai.project_technology.contract_version` remains `1.0.0`.

package/releases/1.3.0.md

@@ -1,16 +0,0 @@
-# Mirai Graph 1.3.0
-
-Mirai Graph 1.3.0 adds generic immutable releases for file bundles to the
-existing Project Technology engine.
-
-Projects can inspect a bundle, preview or create a release, compare two
-releases and verify stored files against their manifest. The graph stores only
-safe lineage, state, references and checksums; protected artifact content
-remains outside graph data.
-
-The release supports direct files, directories, ZIP, TAR and TAR.GZ, with
-fail-closed archive checks, transactional activation, rollback, concurrency
-protection and idempotent repeats.
-
-The public `graph.json` schema remains `2.0.0`. The Project Technology
-activation contract remains `1.0.0`.

package/releases/README.md

@@ -1,135 +0,0 @@
-# Mirai Graph Release Process
-
-Status: stable 1.0 release process
-
-## Purpose
-
-This directory records public release notes for Mirai Graph tags.
-
-Release notes must separate:
-
-- what changed;
-- what was validated;
-- what remains limited;
-- which claims are supported by the current evidence.
-
-## Release Notes
-
-- [v1.2.0](1.2.0.md) - portable task-boundary project continuity in Project
-  Technology.
-- [v1.1.0](1.1.0.md) - universal sequential context traversal and usage
-  verification in Project Technology.
-- [v1.0.0](1.0.0.md) - stable Project Technology, CLI and public contract.
-- [v1.3.0](1.3.0.md) - immutable artifact releases in Project Technology.
-- [v1.0.0-rc.6](1.0.0-rc.6.md) - anti-drift / quality-control release
-  consolidation across Semantic Intent, Dynamic Episode, Goal Vector and
-  Technology Quality Feedback.
-- [v1.0.0-rc.5](1.0.0-rc.5.md) - Semantic Intent Resolution input-control
-  contract release candidate.
-- [v1.0.0-rc.4](1.0.0-rc.4.md) - Dynamic Episode proposal/experimental
-  tracing release candidate.
-- [v1.0.0-rc.3](1.0.0-rc.3.md) - developer-first onboarding release
-  candidate.
-- [v1.0.0-rc.2](1.0.0-rc.2.md) - self-service onboarding and public
-  documentation hardening release candidate.
-- [v1.0.0-rc.1](1.0.0-rc.1.md) - 1.0 release candidate consolidating the
-  public standard, profiles, executable process control, instrumentation,
-  Character Layer, self-service onboarding, adopter kit and evidence
-  boundaries.
-- [Societal Governance profile proposal](societal-governance-profile-proposal.md)
-  - proposal-level transfer note for the public-safe experimental governance
-  profile; not a core `1.0.0` profile requirement.
-- [v0.1.0-alpha.9](0.1.0-alpha.9.md) - Mirai Graph naming, repository,
-  package and CLI identity consolidation.
-- [v0.1.0-alpha.10](0.1.0-alpha.10.md) - Adopter Workflow, release-state
-  reporting and self-service starter path.
-- [v0.1.0-alpha.11](0.1.0-alpha.11.md) - Instrumentation release candidate for
-  development cockpits, feature traceability and multi-source quality feedback.
-
-## Release Checklist
-
-Before creating a tag:
-
-1. Move relevant `CHANGELOG.md` entries from `[Unreleased]` to the target
-   version.
-2. Update `package.json` version.
-3. Add `releases/<version>.md`.
-4. Run:
-
-```bash
-npm run release:check
-npm run validate:release-state
-```
-
-5. Run a public-safety scan for private paths and obvious secrets.
-6. Verify `git diff --check`.
-7. Commit release preparation.
-8. Create an annotated tag:
-
-```bash
-git tag -a v<version> -m "Mirai Graph <version>"
-```
-
-9. Push `main` and the tag.
-10. Publish GitHub Release notes using `releases/<version>.md`.
-11. After the GitHub Release exists, run:
-
-```bash
-node packages/cli/mirai-graph.js release state --markdown
-node packages/cli/mirai-graph.js release state --require-github-release --markdown
-```
-
-The release-state report must distinguish GitHub Release state, npm registry
-state and npm authentication state. A missing npm login or pending npm package
-publication is a blocker for npm publish, not permission to expose credentials.
-
-## GitHub Release Notes
-
-GitHub Release notes should use the matching file from this directory.
-
-They should include:
-
-- release type;
-- summary;
-- added or changed artifacts;
-- validation command and expected result;
-- important limitations.
-
-Do not claim:
-
-- peer review;
-- real-world productivity improvement;
-- external validity;
-- runtime safety;
-- universal applicability;
-
-unless the release includes evidence that directly supports that claim.
-
-## Public-Safety Scan
-
-Use a targeted scan over public files before release. Keep local private-path
-and credential patterns outside committed documentation:
-
-```bash
-rg -n "<local-private-path-pattern>|<credential-pattern>|<restricted-data-pattern>" .github README.md ROADMAP.md CHANGELOG.md docs standard schemas benchmarks examples packages profiles pilots publications releases package.json .env.example .gitignore
-```
-
-Review matches manually. Maintainers may add local private-path patterns to
-their own release checklist, but local filesystem paths and exact credential
-patterns should not be embedded in public release notes.
-
-## Version Policy
-
-During alpha:
-
-- patch alpha releases may include schema, CLI, documentation and synthetic
-  evidence changes;
-- release notes must state limitations;
-- tags should not be rewritten after publication.
-
-For `1.0.0-rc.*`:
-
-- the package may be reviewed as a release candidate;
-- release notes must still state limitations and publication boundaries;
-- final `1.0.0` requires a separate tag, GitHub Release and npm publication
-  decision after release-state checks.