mirai-graph 1.0.0-rc.1

package/docs/transfer/federation-routing-control-loop-2026-05-31.md

@@ -0,0 +1,28 @@
+# Federation Routing Control Loop Transfer
+
+Date: 2026-05-31
+
+Status: public-safe transfer note
+
+## Transferred Concepts
+
+This transfer generalizes internal federation routing work into public-safe
+Mirai Graph standard drafts:
+
+- route explanation;
+- routing fixtures;
+- forbidden route shapes;
+- federation health dashboard;
+- route regression result;
+- high-risk route preflight boundary.
+
+## Public-Safe Boundary
+
+This transfer does not publish private skill playbooks, customer routes,
+runtime paths, credentials, internal metrics or owner-specific methods.
+
+## Claim Boundary
+
+The transferred artifacts support schema and standard shape claims only. They
+do not prove real-world productivity, runtime safety, scientific validity or
+graph-only source-of-truth readiness.

package/docs/transfer/graph-capability-map-2026-05-29.md

@@ -0,0 +1,126 @@
+# Mirai Graph Public Capability Map
+
+Date: 2026-05-29
+
+Status: public-safe transfer map
+
+## Purpose
+
+This map connects practical `$graph` capability areas to public Mirai Graph
+standard sections, schemas, tooling, examples and evidence artifacts.
+
+It is not a publication of internal skill implementation details. It records
+which reusable ideas are already represented in the open repository and which
+ideas still need public standardization.
+
+## Public Transfer Boundary
+
+Transfer only public-safe concepts:
+
+- implementation-independent model elements;
+- schemas and validators;
+- synthetic examples and benchmarks;
+- adoption guides;
+- research protocols;
+- limited claims backed by public artifacts.
+
+Do not transfer:
+
+- private project data;
+- raw internal chats or handoffs;
+- customer or employee material;
+- secrets or private runtime paths;
+- organization-specific procedures that have not been generalized.
+
+## Capability Coverage
+
+| Practical capability area | Public Mirai Graph coverage | Status | Next public step |
+| --- | --- | --- | --- |
+| Repository as graph source of truth | `docs/repository-purpose.md`, `README.md`, `ROADMAP.md` | covered | Keep purpose, roadmap and release notes aligned. |
+| Core object model | `standard/object-model.md`, `schemas/object.schema.json`, package fixtures | covered with notes | Add richer object-family examples for more profiles. |
+| Typed relation model | `standard/relation-model.md`, `schemas/relation.schema.json`, relation-id validation | covered with notes | Expand impact traversal and change-review semantics. |
+| Evidence and provenance | `standard/evidence-provenance.md`, evidence fields, synthetic source corpus | covered with notes | Add evidence-level taxonomy and validation checks. |
+| Lifecycle and readiness | `standard/lifecycle-readiness.md`, readiness validation, `packages/cli/readiness-score.js` | partial | Standardize readiness-score bands and caps as a first-class section. |
+| Graph DNA | `standard/graph-dna.md` | partial | Add validation examples and DNA-to-seed traceability. |
+| Graph Seed | `standard/graph-seed.md`, `schemas/graph-seed.schema.json`, seed examples, seed validation | covered with notes | Add more negative seed fixtures and adoption walkthroughs. |
+| Graph Embryo | `standard/graph-embryo.md`, `schemas/graph-embryo.schema.json`, seed preview output | covered with notes | Add embryo review-result artifacts and promotion rules. |
+| Canonical graph state | `standard/standard-v0.1.md`, package manifest schema, graph objects/relations | covered with notes | Define canonical write/update proposal format. |
+| Generated context packs | `standard/context-pack-generation.md`, `schemas/context-pack.schema.json`, `packages/cli/context-pack.js`, context-pack validation | covered with notes | Add schema-level fixtures for selection explanation edge cases. |
+| Selection explanations | context-pack `selection.object_explanations` and `selection.relation_explanations` | covered | Add reviewer guidance for interpreting scores. |
+| Safety-sensitive context inclusion | context-pack generation policy and semantic review artifacts | partial | Turn safety inclusion into an explicit standard subsection. |
+| Governance gates | `standard/governance.md`, gate result schema and examples | partial | Add proposal/approval flow with dry-run and apply boundaries. |
+| Profiles | `standard/profiles.md`, `profiles/`, profile validation and profile conformance fixtures | covered with notes | Add organization-governance, research-program and human-AI profiles later. |
+| AI employee graph-as-brain | `profiles/ai-employee/`, `standard/graph-as-ai-brain.md`, `examples/ai-employee-minimal/` | alpha | Validate through Larena/AI pilot before making stronger runtime claims. |
+| Action/runtime boundary | `standard/action-runtime-boundary.md`, AI employee fixture approval gate | alpha | Add proposal/action/result schemas after runtime patterns stabilize. |
+| Feedback learning gate | `standard/feedback-learning-gate.md`, AI employee fixture feedback and lesson proposal | alpha | Add replay/evaluation result artifact schema. |
+| Profile conformance evidence | positive and negative fixtures, `validate-profile-results.js` | covered | Keep stored results regenerated before releases. |
+| Test suite and conformance levels | `standard/test-suite.md`, `standard/conformance-levels.md`, `npm run release:check` | covered with notes | Split release checks into named conformance levels. |
+| Context reduction benchmark | `benchmarks/synthetic-context-reduction-v0/` and result artifacts | covered with limits | Add more benchmark tasks and ablation protocols. |
+| Semantic completeness review | `docs/research/semantic-completeness-review-protocol.md`, review JSON artifacts | partial | Add independent reviewer workflow and disagreement handling. |
+| Measure-convert-optimize cycle | `benchmarks/protocols/measure-convert-optimize.md` | partial | Add a second public benchmark and repeatable result writer. |
+| Adoption path | `docs/adoption/getting-started.md`, `docs/adoption/seed-to-validated-package.md` | covered with notes | Add one complete tutorial from seed to context-pack review. |
+| Federation / cross-graph contracts | not yet public | planned | Draft `standard/federation.md` after core package contracts stabilize. |
+| Runtime enablement policy | represented only indirectly through governance and readiness | planned | Draft public-safe runtime enablement policy without internal runtime details. |
+| Migration/versioning | not yet public as a standard section | planned | Draft `standard/versioning-migrations.md` and migration dry-run artifacts. |
+
+## Current Public Maturity
+
+Current repository maturity:
+
+`public_alpha_standard_with_executable_fixtures`
+
+Reason:
+
+The repository now contains a public standard foundation, schemas, validators,
+context-pack generation, readiness scoring, profiles, synthetic benchmark,
+semantic review artifacts, positive and negative conformance fixtures, and
+release checks.
+
+The repository is not yet:
+
+- a complete standard;
+- a full reference implementation;
+- proof of real-world productivity improvement;
+- a runtime action framework;
+- a publication-ready empirical evidence package.
+
+## Priority Standardization Backlog
+
+### P0: Prepare `v0.1.0-alpha.4`
+
+- summarize completed executable standard improvements;
+- publish release notes;
+- keep claims limited to public alpha tooling and synthetic evidence.
+
+### P1: Human Control And Governance
+
+- proposal/approval flow;
+- dry-run/apply boundary;
+- governance gate result lifecycle;
+- safety and public-release gates.
+
+### P2: Readiness And Review
+
+- readiness score standard section;
+- score bands and caps;
+- semantic review workflow;
+- reviewer disagreement and limitation records.
+
+### P3: Versioning And Federation
+
+- schema versioning;
+- migration reports;
+- cross-graph compatibility;
+- public federation contract.
+
+## Claim Rule
+
+This capability map supports only this claim:
+
+```text
+Mirai Graph has a public alpha mapping from practical graph-method capabilities
+to open standard sections, schemas, tooling and public-safe evidence artifacts.
+```
+
+It does not claim that the practical `$graph` skill is fully public, fully
+standardized or externally validated.

package/docs/transfer/graph-skill-to-mirai-graph.md

@@ -0,0 +1,128 @@
+# From `$graph` Skill To Mirai Graph
+
+Status: initial transfer map
+
+## Purpose
+
+This note defines how reusable knowledge from the practical `$graph` skill
+should move into the public Mirai Graph repository.
+
+## Transfer Rule
+
+`$graph` is the practical methodology owner. Mirai Graph is the public standard
+and adoption layer.
+
+Transfer a concept only when it is:
+
+- reusable outside the original skill;
+- safe for public release;
+- not tied to private SIMAI or customer material;
+- useful for standards, tooling, profiles, examples or research evidence.
+
+## Transfer Classes
+
+### Standard Concept
+
+Belongs in:
+
+- `standard/`
+- `schemas/`
+
+Examples:
+
+- object model;
+- relation model;
+- lifecycle/readiness;
+- evidence/provenance;
+- governance gates;
+- conformance levels.
+
+### Profile Concept
+
+Belongs in:
+
+- `standard/profiles.md`
+- future `profiles/`
+
+Examples:
+
+- software specification profile;
+- project management profile;
+- organization governance profile;
+- research program profile.
+
+### Reference Tooling
+
+Belongs in:
+
+- `packages/`
+- `schemas/`
+- `examples/`
+
+Examples:
+
+- validators;
+- generators;
+- benchmark runners;
+- migration helpers.
+
+### Research Artifact
+
+Belongs in:
+
+- `benchmarks/`
+- `publications/`
+- `docs/research/`
+
+Examples:
+
+- experiment protocol;
+- result note;
+- reproducibility package;
+- validation roadmap.
+
+### Private Or Local Material
+
+Does not belong in public Mirai Graph.
+
+Examples:
+
+- raw internal project materials;
+- internal chats;
+- private skill implementation details not approved for release;
+- customer or employee data;
+- secrets;
+- private metrics without redaction and approval.
+
+## Initial Mapping
+
+| `$graph` Area | Mirai Graph Destination | Notes |
+| --- | --- | --- |
+| Graph Seed | `standard/`, `docs/adoption/` | Should become a public seed method. |
+| Graph Embryo | `standard/`, `docs/adoption/` | Useful for staged graph growth. |
+| Lifecycle/readiness | `standard/lifecycle-readiness.md` | Already started. |
+| Relation/impact model | `standard/relation-model.md` | Needs richer impact semantics. |
+| AI context generation | `standard/context-pack-generation.md` | Needs schema and generator. |
+| Measure-convert-optimize | `docs/research/`, `benchmarks/` | Core validation methodology. |
+| Graph method evolution | `docs/research/` | Core practice-to-science loop. |
+| Federation contracts | future `standard/federation.md` | Later stage. |
+| Runtime policies | future `standard/governance.md` expansion | Public-safe subset only. |
+
+## Next Transfer Batch
+
+1. Draft graph DNA, graph seed and graph embryo public standard sections.
+2. Create graph seed and graph embryo schemas.
+3. Extend the CLI with seed validation.
+4. Draft measure-convert-optimize experiment protocol.
+5. Add profile manifests for the first public profiles.
+
+Current gap report:
+
+`docs/transfer/standard-gap-report-2026-05-28.md`
+
+Current capability map:
+
+`docs/transfer/graph-capability-map-2026-05-29.md`
+
+The dated capability map is the current public-safe transfer state. The
+2026-05-28 gap report is retained as a historical baseline.

package/docs/transfer/project-management-standard-harvest-2026-06-02.md

@@ -0,0 +1,322 @@
+# Project Management Standard Harvest
+
+Date: 2026-06-02
+Status: public-safe transfer note
+
+## Purpose
+
+This note captures public-safe project-management patterns observed in a private
+Mirai Graph pilot. It does not publish private project data, internal paths,
+internal runtime traces, private handoffs or non-synthetic evidence.
+
+The goal is to identify how the current public project-management profile can
+evolve from a small task/decision graph into a stronger operating model for
+managed projects, products and human-AI implementation workflows.
+
+## Existing Public Baseline
+
+Mirai Graph already includes an initial project-management profile:
+
+- `profiles/project-management/profile.json`
+- `profiles/project-management/README.md`
+
+The current profile is intentionally small. It covers:
+
+- goals;
+- tasks;
+- decisions;
+- risks;
+- milestones;
+- stakeholders;
+- evidence;
+- governance gates.
+
+This is enough for small Level 1 project packages, but larger managed projects
+need stronger lifecycle, review, evidence and improvement structures.
+
+## Reusable Management Loop
+
+The private pilot exposed a reusable Mirai Graph project-control loop:
+
+```text
+canonical graph
+-> generated human projection
+-> semantic review
+-> graph update proposal
+-> approved canonical update
+-> regenerated projection
+-> validation
+-> implementation evidence
+-> continuous improvement
+```
+
+This loop keeps the canonical graph structured while still giving humans a
+readable project view and review surface.
+
+## Extension Candidates
+
+### Object Kinds
+
+Candidate object kinds for a richer profile:
+
+- `initiative`
+- `lifecycle_stage`
+- `implementation_cluster`
+- `workflow_batch`
+- `review`
+- `release_gate`
+- `kaizen_item`
+- `sync_proposal`
+- `projection_view`
+- `candidate`
+- `closure_decision`
+
+### Relation Types
+
+Candidate relation types:
+
+- `progresses_to`
+- `implements`
+- `produces_evidence`
+- `requires_review`
+- `requires_gate`
+- `proposes_update_to`
+- `accepted_into`
+- `rejected_from`
+- `supersedes`
+- `closes_candidate`
+- `improves_process`
+
+### Governance Gates
+
+Candidate gates:
+
+- `semantic_review_before_canonical_update`
+- `evidence_pack_before_implementation_status_change`
+- `owner_approval_before_release_gate_pass`
+- `public_safety_review_before_public_transfer`
+- `coordinator_review_before_graph_sync`
+
+## Standard Gaps
+
+### Human Projection Feedback
+
+The public standard already has projection views, but it should also define a
+repeatable feedback loop where generated human-readable documents are reviewed
+against the canonical graph and then converted into explicit update proposals.
+
+Candidate public artifact:
+
+- `standard/human-projection-feedback-loop.md`
+
+### Graph Sync Evidence
+
+Agentic or distributed implementation should not mutate canonical graph state
+directly. Implementers should produce evidence packs and graph sync proposals
+for coordinator review.
+
+Candidate public artifacts:
+
+- `standard/graph-sync-evidence-protocol.md`
+- `schemas/graph-sync-evidence-pack.schema.json`
+- `schemas/graph-sync-proposal.schema.json`
+
+### Candidate Closure
+
+Extraction and review workflows produce uncertain candidates. Mirai Graph needs a
+standard way to close candidates as accepted, already covered, false positive,
+boundary decision or future backlog.
+
+Candidate public artifacts:
+
+- `standard/proposal-candidate-closure.md`
+- `schemas/proposal-candidate-closure.schema.json`
+
+### Continuous Improvement
+
+Meaningful workflows should leave lessons and process improvements in the graph
+without automatically changing canonical project state.
+
+Candidate public artifacts:
+
+- `standard/kaizen-loop.md`
+- `schemas/kaizen-item.schema.json`
+
+## Public Safety Boundary
+
+Safe to publish:
+
+- generalized object kinds;
+- generalized relation types;
+- generalized gates;
+- synthetic examples;
+- schema shapes;
+- validation rules;
+- limited claims about conformance and reproducibility.
+
+Do not publish:
+
+- private project paths;
+- internal company policies;
+- private handoff text;
+- private runtime traces;
+- package-specific implementation decisions from private work;
+- broad claims that a private pilot proves universal effectiveness.
+
+## Recommended Next Public Batch
+
+Create a synthetic project-management example that demonstrates:
+
+```text
+request
+-> graph baseline
+-> generated human projection
+-> semantic review
+-> graph sync proposal
+-> evidence pack
+-> coordinator approval
+-> canonical update
+```
+
+This should be validated separately from the current minimal project-management
+profile so the alpha.6 public surface remains stable while the richer extension
+is tested.
+
+## Batch Result
+
+The first synthetic control-loop example now lives at:
+
+```text
+examples/managed-project-control-loop/
+```
+
+It intentionally uses the current `project_management` profile rather than
+extending `profile.json`. Workflow batches, sync proposals and approval flow are
+represented through existing `task`, `decision`, `evidence`, `milestone`,
+`risk` and `governance_gate` objects. This keeps alpha.6 stable while making the
+future extension gap concrete.
+
+### Implementation Control Profile Result
+
+The public repository now includes a separate implementation-control profile:
+
+```text
+profiles/implementation-control/
+standard/implementation-control.md
+schemas/implementation-control-loop.schema.json
+examples/implementation-control-minimal/
+```
+
+This separates ordinary project management from governed implementation work.
+The new profile models baselines, projection views, semantic reviews, workflow
+batches, evidence packs, sync proposals, approval gates, controlled updates,
+implementation state and improvement items.
+
+Validation coverage:
+
+```bash
+npm run validate:profiles
+npm run validate:implementation-control
+npm run release:check
+```
+
+## Implementation Control Cycle Hardening
+
+The next public-safe hardening step generalized the managed-project pattern into
+reusable implementation-control cycles. This remains a synthetic public
+transfer, not publication of private project evidence.
+
+Added public concepts:
+
+- human projection feedback cycle;
+- implementation planning cycle;
+- bounded work batch cycle;
+- review and evidence cycle;
+- release or publish cycle;
+- runtime feedback cycle;
+- explicit launch, drift, proposal, approval and controlled-update boundaries.
+
+Public artifacts:
+
+```text
+standard/implementation-control-cycles.md
+schemas/implementation-control-cycle.schema.json
+examples/implementation-control-cycles/
+```
+
+Validation coverage:
+
+```bash
+npm run validate:implementation-control-cycles
+npm run release:check
+```
+
+Boundary: public Mirai Graph receives the generalized model, schemas and
+synthetic examples. Private project details, internal paths, runtime traces,
+private transfer notes and organization-specific policies remain outside the
+public repository.
+
+### Cycle Transitions And Kaizen
+
+A later public-safe hardening step generalized continuous-improvement process
+control into:
+
+```text
+cycle completed
+-> transition decision
+-> kaizen review
+-> classified improvement
+-> blocking/non-blocking decision
+-> next governed cycle
+```
+
+Added public concepts:
+
+- cycle transition contract with required outputs, gates, handoff artifact,
+  owner, failure behavior and recovery behavior;
+- `kaizen_improvement` as a meta-cycle separate from runtime feedback;
+- Kaizen finding taxonomy for artifact, graph/spec, process, validator,
+  tooling, DNA alignment, quality, safety, drift and user-value findings;
+- blocking rule for safety, quality, DNA alignment and critical drift findings;
+- fail-closed validation for unknown cycle refs, duplicate transitions and
+  missing transition fields.
+
+Boundary: private pilot evidence remains private. Public Mirai Graph receives
+only the generalized pattern, synthetic example and schema/validator behavior.
+
+## Governance Standards Transfer
+
+The next public-safe transfer generalized the remaining governance patterns
+into universal Mirai Graph standards:
+
+- graph DNA alignment;
+- source boundary contracts;
+- work state machines;
+- recovery and resume records;
+- risk control matrices;
+- multi-agent coordination contracts.
+
+Public artifacts:
+
+```text
+standard/graph-dna-alignment.md
+standard/source-boundary-contract.md
+standard/work-state-machine.md
+standard/recovery-resume.md
+standard/risk-control-matrix.md
+standard/multi-agent-coordination.md
+```
+
+Validation coverage:
+
+```bash
+npm run validate:dna-alignment
+npm run validate:work-state
+npm run validate:risk-control
+npm run validate:source-boundary
+npm run release:check
+```
+
+Boundary: these standards describe reusable project-agnostic governance
+patterns. They do not publish private pilot data, real repository paths,
+organization-specific policies or private execution evidence.