mirai-graph 1.3.0 → 2.1.0

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.

package/releases/societal-governance-profile-proposal.md

@@ -1,45 +0,0 @@
-# Societal Governance Profile Proposal
-
-Status: proposal-level profile prepared in repository.
-
-## Summary
-
-This transfer adds a public-safe `societal_governance` proposal profile derived
-from the Mirai AI Governance research track. It is intended for synthetic
-fixtures, non-binding shadow governance and bounded organizational simulation.
-
-The profile extends existing Mirai Graph concepts:
-
-- `organization_governance` for organization-level policy and decision rights;
-- `character_layer` for bounded AI avatar behavior;
-- `process_control` for explicit lifecycle and false-transition guards;
-- evidence and governance gates for traceable decisions and controlled
-  evolution.
-
-## Included Scope
-
-- `profiles/societal-governance/README.md`
-- `profiles/societal-governance/profile.json`
-- `examples/societal-governance-minimal/`
-- invalid fixtures for:
-  - avatar action without consent;
-  - private trace exposure;
-  - rights overridden by weights;
-  - generated context treated as authorization;
-  - missing appeal path;
-  - automatic learning update.
-
-## Claim Boundary
-
-This proposal does not claim legal validity, democratic legitimacy,
-cryptographic completeness, production governance safety or state-scale
-readiness.
-
-It only claims that Mirai Graph now has a validator-backed proposal shape for
-representing bounded governance traces as synthetic, non-binding graph packages.
-
-## Next Evidence Step
-
-The next research/product step is a SIMAI OS shadow pilot on non-sensitive,
-non-binding organizational decisions, with human owner review and no automatic
-canonical updates.

package/schemas/baseline-comparison-result.schema.json

@@ -1,87 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://mirai-graph.dev/schemas/baseline-comparison-result.schema.json",
-  "title": "Mirai Graph Baseline Comparison Result",
-  "type": "object",
-  "additionalProperties": true,
-  "required": [
-    "schema_version",
-    "id",
-    "public_safety",
-    "comparison_type",
-    "task_id",
-    "baseline",
-    "mirai_graph",
-    "outcome",
-    "limitations",
-    "claim_boundary"
-  ],
-  "properties": {
-    "schema_version": { "type": "string", "minLength": 1 },
-    "id": { "type": "string", "minLength": 1 },
-    "public_safety": { "const": "synthetic_public" },
-    "comparison_type": { "const": "baseline_vs_mirai_graph" },
-    "task_id": { "type": "string", "minLength": 1 },
-    "baseline": {
-      "type": "object",
-      "required": [
-        "context_units",
-        "missed_dependencies",
-        "unsupported_assumptions",
-        "evidence_coverage_percent",
-        "false_progress_claims"
-      ],
-      "properties": {
-        "context_units": { "type": "number", "minimum": 0 },
-        "missed_dependencies": { "type": "number", "minimum": 0 },
-        "unsupported_assumptions": { "type": "number", "minimum": 0 },
-        "evidence_coverage_percent": { "type": "number", "minimum": 0, "maximum": 100 },
-        "false_progress_claims": { "type": "number", "minimum": 0 }
-      }
-    },
-    "mirai_graph": {
-      "type": "object",
-      "required": [
-        "context_units",
-        "missed_dependencies",
-        "unsupported_assumptions",
-        "evidence_coverage_percent",
-        "false_progress_claims"
-      ],
-      "properties": {
-        "context_units": { "type": "number", "minimum": 0 },
-        "missed_dependencies": { "type": "number", "minimum": 0 },
-        "unsupported_assumptions": { "type": "number", "minimum": 0 },
-        "evidence_coverage_percent": { "type": "number", "minimum": 0, "maximum": 100 },
-        "false_progress_claims": { "type": "number", "minimum": 0 }
-      }
-    },
-    "outcome": {
-      "type": "object",
-      "required": [
-        "context_reduction_percent",
-        "improved_metrics",
-        "regressed_metrics",
-        "verdict"
-      ],
-      "properties": {
-        "context_reduction_percent": { "type": "number" },
-        "improved_metrics": {
-          "type": "array",
-          "items": { "type": "string", "minLength": 1 }
-        },
-        "regressed_metrics": {
-          "type": "array",
-          "items": { "type": "string", "minLength": 1 }
-        },
-        "verdict": { "type": "string", "minLength": 1 }
-      }
-    },
-    "limitations": {
-      "type": "array",
-      "minItems": 1,
-      "items": { "type": "string", "minLength": 1 }
-    },
-    "claim_boundary": { "type": "string", "minLength": 1 }
-  }
-}

package/schemas/character-layer-integration.schema.json

@@ -1,112 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://mirai-graph.dev/schemas/character-layer-integration.schema.json",
-  "title": "Mirai Graph Character Layer Integration",
-  "type": "object",
-  "required": [
-    "schema_version",
-    "profile",
-    "public_safety",
-    "integration_id",
-    "character_package_ref",
-    "ai_employee_links",
-    "process_control_links",
-    "runtime_context_boundary",
-    "required_gates",
-    "evidence_refs",
-    "limitations"
-  ],
-  "properties": {
-    "schema_version": {
-      "type": "string"
-    },
-    "profile": {
-      "const": "character_layer"
-    },
-    "public_safety": {
-      "const": "synthetic_public"
-    },
-    "integration_id": {
-      "type": "string"
-    },
-    "character_package_ref": {
-      "type": "string"
-    },
-    "ai_employee_links": {
-      "type": "array",
-      "minItems": 1,
-      "items": {
-        "type": "object",
-        "required": [
-          "ai_employee_ref",
-          "role_ref",
-          "role_character_profile_ref",
-          "composition_relations"
-        ],
-        "properties": {
-          "ai_employee_ref": { "type": "string" },
-          "role_ref": { "type": "string" },
-          "role_character_profile_ref": { "type": "string" },
-          "composition_relations": {
-            "type": "array",
-            "minItems": 1,
-            "items": { "type": "string" }
-          }
-        },
-        "additionalProperties": true
-      }
-    },
-    "process_control_links": {
-      "type": "object",
-      "required": [
-        "launch_record_ref",
-        "process_control_contract_ref",
-        "technology_quality_feedback_ref",
-        "transition_gate_refs"
-      ],
-      "properties": {
-        "launch_record_ref": { "type": "string" },
-        "process_control_contract_ref": { "type": "string" },
-        "technology_quality_feedback_ref": { "type": "string" },
-        "transition_gate_refs": {
-          "type": "array",
-          "minItems": 1,
-          "items": { "type": "string" }
-        }
-      },
-      "additionalProperties": true
-    },
-    "runtime_context_boundary": {
-      "type": "object",
-      "required": [
-        "generated_context_ref",
-        "reflection_protocol_ref",
-        "authorization_boundary",
-        "canonical_update_boundary"
-      ],
-      "properties": {
-        "generated_context_ref": { "type": "string" },
-        "reflection_protocol_ref": { "type": "string" },
-        "authorization_boundary": { "type": "string" },
-        "canonical_update_boundary": { "type": "string" }
-      },
-      "additionalProperties": true
-    },
-    "required_gates": {
-      "type": "array",
-      "minItems": 1,
-      "items": { "type": "string" }
-    },
-    "evidence_refs": {
-      "type": "array",
-      "minItems": 1,
-      "items": { "type": "string" }
-    },
-    "limitations": {
-      "type": "array",
-      "minItems": 1,
-      "items": { "type": "string" }
-    }
-  },
-  "additionalProperties": true
-}

package/schemas/character-layer-readiness.schema.json

@@ -1,73 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://mirai-graph.dev/schemas/character-layer-readiness.schema.json",
-  "title": "Mirai Graph Character Layer Readiness",
-  "type": "object",
-  "required": [
-    "schema_version",
-    "profile",
-    "public_safety",
-    "readiness_id",
-    "target_release_track",
-    "readiness_verdict",
-    "completed_capabilities",
-    "validation_commands",
-    "evidence_refs",
-    "claim_boundaries",
-    "remaining_limits"
-  ],
-  "properties": {
-    "schema_version": { "type": "string" },
-    "profile": { "const": "character_layer" },
-    "public_safety": { "const": "synthetic_public" },
-    "readiness_id": { "type": "string" },
-    "target_release_track": { "type": "string" },
-    "readiness_verdict": {
-      "enum": [
-        "ready_for_1_0_candidate",
-        "needs_hardening",
-        "blocked",
-        "insufficient_evidence"
-      ]
-    },
-    "completed_capabilities": {
-      "type": "array",
-      "minItems": 1,
-      "items": {
-        "type": "object",
-        "required": ["id", "status", "evidence_refs"],
-        "properties": {
-          "id": { "type": "string" },
-          "status": { "enum": ["completed", "partial", "missing"] },
-          "evidence_refs": {
-            "type": "array",
-            "minItems": 1,
-            "items": { "type": "string" }
-          }
-        },
-        "additionalProperties": true
-      }
-    },
-    "validation_commands": {
-      "type": "array",
-      "minItems": 1,
-      "items": { "type": "string" }
-    },
-    "evidence_refs": {
-      "type": "array",
-      "minItems": 1,
-      "items": { "type": "string" }
-    },
-    "claim_boundaries": {
-      "type": "array",
-      "minItems": 1,
-      "items": { "type": "string" }
-    },
-    "remaining_limits": {
-      "type": "array",
-      "minItems": 1,
-      "items": { "type": "string" }
-    }
-  },
-  "additionalProperties": true
-}