mirai-graph 1.3.0 → 2.1.0

package/releases/0.1.0-alpha.8.md

@@ -1,92 +0,0 @@
-# Mirai Graph v0.1.0-alpha.8
-
-Status: release preparation notes
-
-## Theme
-
-Adopter kit and executable technology-quality control.
-
-This alpha keeps Mirai Graph CLI-first and public-safe while making adoption
-more practical through starter templates, organization-governance pilot
-coverage, a unified CLI wrapper and a technology quality feedback gate that
-checks whether work followed the declared process before acceptance or release.
-
-## Included Since v0.1.0-alpha.7
-
-### Adopter Kit
-
-- Added starter templates for software projects, research programs,
-  AI employees and organization governance.
-- Added unified `mirai_graph` CLI wrapper for common validation, report and
-  process-transition explanation commands.
-- Added organization-governance pilot coverage.
-- Added Evidence Package v0.2 as the current public research evidence
-  entrypoint.
-
-### Technology Quality Feedback
-
-- Added `standard/technology-quality-feedback.md`.
-- Added `schemas/technology-quality-feedback.schema.json`.
-- Added synthetic example:
-  `examples/technology-quality-feedback-minimal/`.
-- Added CLI mode:
-  `node packages/cli/validate-mirai-graph.js technology-quality-feedback <file>`.
-- Added `validate:technology-quality-feedback` and
-  `test:technology-quality-feedback-negative`.
-- Added fail-closed negative fixtures for blocking findings, missing process
-  steps, unclassified findings, missing Kaizen routes, unresolved spec gaps,
-  missing feedback reports and evidence-as-authorization errors.
-
-### Process-Control Integration
-
-- Process-control docs now state that significant acceptance, approval or
-  release transitions should require technology quality feedback.
-- The implementation-control profile now includes technology contracts,
-  technology quality feedback reports and quality findings.
-- The process-control contract schema supports an optional
-  `technology_quality_feedback_policy`.
-
-## Validation
-
-Validate with:
-
-```bash
-npm test
-npm run release:check
-```
-
-Targeted alpha.8 checks:
-
-```bash
-npm run validate:technology-quality-feedback
-npm run test:technology-quality-feedback-negative
-npm run validate:process-control
-npm run validate:cli-unified
-```
-
-## Claim Boundary
-
-This release should claim only:
-
-```text
-Mirai Graph v0.1.0-alpha.8 adds public alpha readiness for adopter templates,
-unified CLI entrypoints, organization-governance pilot coverage and executable
-technology-quality feedback gates.
-```
-
-It should not claim:
-
-- peer-reviewed proof of effectiveness;
-- production runtime safety;
-- autonomous execution readiness;
-- graph-only runtime readiness;
-- automatic acceptance from passing tests;
-- automatic canonical update from generated context, feedback, evidence,
-  runtime results or proposals.
-
-## Known Limits
-
-- CLI remains reference tooling, not a full SDK.
-- Technology quality feedback validates report shape and boundary rules; it
-  does not prove semantic correctness by itself.
-- Public examples remain synthetic and require external replication.

package/releases/0.1.0-alpha.9.md

@@ -1,80 +0,0 @@
-# Mirai Graph v0.1.0-alpha.9
-
-Status: published GitHub prerelease; npm publication pending registry
-authentication.
-
-## Theme
-
-Public naming consolidation under Mirai Graph.
-
-This alpha consolidates the public standard, package, repository and CLI
-identity around the `mirai-graph` slug.
-
-## Included Since v0.1.0-alpha.8
-
-### Rename Transition
-
-- Public standard name is now Mirai Graph.
-- Package name is now `mirai-graph`.
-- Primary CLI entrypoint is now `packages/cli/mirai-graph.js`.
-- Preferred package manifest is now `mirai-graph-package.json`.
-- The underscore CLI alias `packages/cli/mirai_graph.js` is available for local
-  environments that prefer identifier-style command names.
-
-### Command Surface
-
-- `packages/cli/mirai-graph.js` is the primary local CLI.
-- `packages/cli/mirai_graph.js` delegates to the primary CLI as an underscore
-  alias.
-- Validators use `mirai-graph-package.json`.
-- `npm test` includes a smoke check for the primary CLI, underscore alias and
-  current manifest filename.
-
-### Documentation
-
-- Added a transition guide:
-  `docs/adoption/mirai-graph-transition.md`.
-- Updated README, CLI docs, citation metadata, changelog and release navigation
-  for Mirai Graph naming.
-
-### Release State
-
-- GitHub repository: `zabarov/mirai-graph`.
-- GitHub release:
-  `https://github.com/zabarov/mirai-graph/releases/tag/v0.1.0-alpha.9`.
-- Git tag: `v0.1.0-alpha.9`.
-- NPM package: pending publication until npm registry authentication is
-  available.
-
-## Validation
-
-Validate with:
-
-```bash
-npm run validate:mirai-graph-compat
-npm test
-npm run release:check
-```
-
-## Claim Boundary
-
-This release should claim only:
-
-```text
-Mirai Graph v0.1.0-alpha.9 consolidates public naming, package identity and
-local CLI surfaces around Mirai Graph.
-```
-
-It should not claim:
-
-- schema namespace ownership has been finalized;
-- npm package publication has happened;
-- historical evidence payloads were regenerated;
-- peer-reviewed proof of effectiveness.
-
-## Known Limits
-
-- NPM publish remains pending registry authentication.
-- Schema `$id` namespace migration remains pending domain confirmation.
-- The underscore CLI alias is an implementation convenience, not a separate
-  public standard.

package/releases/1.0.0-rc.1.md

@@ -1,121 +0,0 @@
-# Mirai Graph v1.0.0-rc.1
-
-Status: release candidate prepared in repository; tag, GitHub Release and npm
-publish require separate release execution.
-
-## Theme
-
-1.0 Release Candidate.
-
-This release candidate consolidates the public Mirai Graph standard from the
-alpha line into a single verifiable package for external review. It does not
-change the core claim 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.
-
-## Included Scope
-
-### Core Standard
-
-- Object model.
-- Relation model.
-- Lifecycle and readiness.
-- Evidence provenance.
-- Context-pack generation.
-- Governance and conformance levels.
-- Graph seed and graph embryo.
-- Hybrid source-of-truth boundary.
-
-### Domain Profiles
-
-- Software specification.
-- Project management.
-- AI employee.
-- Character Layer.
-- Skill runtime.
-- Implementation control.
-- Organization governance.
-
-### Executable Process Control
-
-- Implementation control cycles.
-- Launch records.
-- Work state machine.
-- Process-control contract.
-- Process-transition validation and readable explanations.
-- Technology quality feedback.
-- Recovery/resume.
-- Risk-control matrix.
-- Source-boundary contract.
-- Multi-agent coordination.
-
-### Instrumentation And Quality Feedback
-
-- Development cockpit.
-- Feature implementation traceability.
-- Multi-source quality feedback.
-- Instrumentation readable report.
-- Negative fixtures that fail closed on missing gates, missing evidence and
-  blocked acceptance.
-
-### Character Layer
-
-- Public `character_layer` profile.
-- Character Layer starter pack.
-- Semantic anti-fixtures.
-- Cross-layer integration artifact for AI employee, process control,
-  technology quality feedback and runtime context.
-- Model-portability evidence shape.
-- Character Layer readiness artifact for the Mirai Graph 1.0 track.
-
-### Adoption And Reproducibility
-
-- Self-service onboarding commands: `detect`, `bootstrap` and `init`.
-- GitHub Action starter for package validation.
-- "Connect A Project In 15 Minutes" tutorial.
-- Role-based adopter kit.
-- Starter templates for developer, researcher, AI employee, behavior governance
-  and organization governance paths.
-- Deterministic playground report.
-- Synthetic baseline comparison.
-- Public-safe pilot packages.
-- Evidence package v0.3 and bounded scientific claim framing.
-
-### Proposal / Experimental Surface
-
-- Societal Governance profile proposal and synthetic fixtures are included as a
-  proposal-level public-safe exploration surface. They are not core
-  `1.0.0-rc.1` conformance requirements.
-
-## Validation
-
-```bash
-npm test
-npm run release:check
-npm run validate:release-state
-npm run validate:character-layer-readiness
-npm run validate:instrumentation-layer
-npm run validate:technology-quality-feedback
-npm run validate:baseline-comparison
-```
-
-## Claim Boundary
-
-This release candidate supports the claim that Mirai Graph has a coherent,
-validator-backed public standard shape for graph-managed knowledge, process,
-AI-employee behavior, implementation control, instrumentation and evidence.
-
-It does not claim:
-
-- peer-reviewed scientific proof;
-- broad external validity;
-- production autonomous execution safety;
-- model-backend equivalence;
-- 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.10.md

@@ -1,14 +0,0 @@
-# Mirai Graph 1.0.0-rc.10
-
-This release candidate completes the public Project Technology pilot against
-the real Federation graph.
-
-## Verified outcome
-
-- commands without a repository argument use the caller's project;
-- large tracked-file inventories are read completely;
-- accepted target objects cannot disappear because of a process-output limit;
-- the Project Technology contract and fail-closed safety rules are unchanged.
-
-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.11.md

@@ -1,14 +0,0 @@
-# Mirai Graph 1.0.0-rc.11
-
-This release candidate closes the final architecture-owner gap found by the
-real Federation process resolver.
-
-## Verified outcome
-
-- complete large-repository target discovery;
-- exact human architecture owner in the bounded contract;
-- component, package, capability and operational ownership remain digest-bound;
-- no private source or full provider graph is exported.
-
-Stable `1.0.0` remains deferred until Federation 8.20.0 and all managed skills
-complete their release checks.

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.