mirai-graph 1.4.0 → 2.1.0

package/pilots/independent-implementation-005-organization-governance/graph-seed.json

@@ -1,97 +0,0 @@
-{
-  "schema_version": "0.1.0",
-  "seed_id": "seed.organization_governance_pilot",
-  "target_graph_id": "graph.organization_governance_pilot",
-  "purpose": "Create a public-safe Mirai Graph package for organization governance.",
-  "target_profile": "profile.organization_governance",
-  "target_mode": "pilot",
-  "graph_dna": {
-    "purpose": "Keep mission, strategy, decision rights, risks, controls, metrics and improvement proposals connected.",
-    "evolution_vector": "Grow from a small governance pilot into a repeatable operating model for organization-scale control.",
-    "non_negotiable_principles": [
-      "The pilot must remain synthetic and public-safe.",
-      "Decision rights must be explicit before policy or portfolio changes.",
-      "Feedback and evidence may inform proposals but cannot automatically update canonical state."
-    ]
-  },
-  "source_boundaries": {
-    "allowed_sources": [
-      "synthetic organization governance brief",
-      "public Mirai Graph organization-governance profile",
-      "public Mirai Graph governance standard docs"
-    ],
-    "excluded_sources": [
-      "private company data",
-      "employee records",
-      "customer records",
-      "internal policy text",
-      "private workflow traces",
-      "secrets or credentials"
-    ],
-    "canonical_write_allowed": false
-  },
-  "growth_rules": {
-    "allowed_object_families": [
-      "organization",
-      "mission",
-      "strategy",
-      "portfolio",
-      "department",
-      "program",
-      "objective",
-      "policy",
-      "decision_right",
-      "governance_gate",
-      "role",
-      "capability",
-      "risk",
-      "control",
-      "metric",
-      "feedback",
-      "kaizen_item",
-      "evidence"
-    ],
-    "allowed_relation_families": [
-      "aligns_with",
-      "owns",
-      "belongs_to",
-      "governs",
-      "requires_approval",
-      "controls",
-      "mitigates",
-      "measures",
-      "supports",
-      "depends_on",
-      "blocks",
-      "escalates_to",
-      "produces_feedback",
-      "improves",
-      "evidences",
-      "related_to"
-    ],
-    "max_initial_objects": 20,
-    "depth_mode": "standard"
-  },
-  "review_gates": [
-    "strategy_alignment_before_portfolio_change",
-    "decision_right_before_policy_change",
-    "risk_control_before_cross_department_action",
-    "evidence_before_governance_decision",
-    "kaizen_before_process_promotion",
-    "no_generated_context_as_authorization",
-    "no_feedback_as_automatic_update"
-  ],
-  "generated_views": [
-    "strategy_alignment_view",
-    "decision_rights_view",
-    "risk_control_view",
-    "metric_dashboard_view",
-    "kaizen_queue_view"
-  ],
-  "stop_conditions": [
-    "private_company_data_requested",
-    "decision_right_missing_for_policy_change",
-    "feedback_treated_as_automatic_update",
-    "secret_or_credential_detected"
-  ]
-}

package/pilots/independent-implementation-005-organization-governance/graph.json

@@ -1,37 +0,0 @@
-{
-  "$schema": "https://mirai-graph.dev/schemas/graph-manifest.schema.json",
-  "format": "mirai-graph",
-  "schema_version": "2.0.0",
-  "id": "package.organization_governance_pilot_005",
-  "aliases": [],
-  "title": "Organization Governance Pilot 005",
-  "scope": "package",
-  "kind": "graph_package",
-  "owner": "mirai-graph",
-  "profiles": [
-    "organization_governance"
-  ],
-  "graph": {
-    "root": "graph",
-    "source_of_truth": [
-      "graph"
-    ],
-    "objects": [
-      "graph/objects.json"
-    ],
-    "relations": [
-      "graph/relations.json"
-    ],
-    "schemas": [],
-    "generated": [],
-    "raw_sources": [
-      "README.md"
-    ]
-  },
-  "imports": [],
-  "version": "0.1.0",
-  "conformance_level": "level_1",
-  "description": "A synthetic independent implementation pilot for organization-level governance.",
-  "license": "CC-BY-4.0",
-  "public_safety": "synthetic_public"
-}

package/pilots/independent-implementation-005-organization-governance/reports/pilot-report.md

@@ -1,47 +0,0 @@
-# Pilot Report: Organization Governance
-
-Status: public-safe alpha pilot
-
-## Question
-
-Can Mirai Graph model organization-level governance with explicit strategy
-alignment, decision rights, controls, metrics, feedback and Kaizen?
-
-## Setup
-
-The pilot uses a synthetic organization governance program. The graph connects:
-
-- organization and mission;
-- strategy and objective;
-- department and program;
-- policy and decision right;
-- risk and control;
-- metric and governance review;
-- feedback and Kaizen improvement queue.
-
-## Result
-
-The package validates against the public `organization_governance` profile. The
-graph shows how organization governance can make promotion gates, decision
-rights and feedback boundaries explicit.
-
-## Evidence Boundary
-
-This pilot demonstrates public profile applicability and validation shape. It
-does not claim organization performance improvement, legal compliance,
-production governance safety or external validity.
-
-## Reproducibility
-
-```bash
-node packages/cli/validate-mirai-graph.js seed pilots/independent-implementation-005-organization-governance/graph-seed.json
-node packages/cli/validate-mirai-graph.js pilots/independent-implementation-005-organization-governance
-node packages/cli/validate-mirai-graph.js --markdown pilots/independent-implementation-005-organization-governance
-```
-
-## Limitations
-
-- The scenario is synthetic.
-- No private organization materials are included.
-- The graph models governance structure, not jurisdiction-specific compliance.
-- Feedback and evidence remain bounded and do not authorize canonical updates.

package/pilots/independent-implementation-005-organization-governance/results/profile-conformance-result.json

@@ -1,29 +0,0 @@
-{
-  "schema_version": "0.1.0",
-  "result_id": "profile_conformance.package.organization_governance_pilot_005",
-  "checked_at": "2026-06-03",
-  "fixture": "pilots/independent-implementation-005-organization-governance/",
-  "package_id": "package.organization_governance_pilot_005",
-  "profile": "organization_governance",
-  "conformance_level": "level_1",
-  "validator": "packages/cli/validate-mirai-graph.js",
-  "command": "node packages/cli/validate-mirai-graph.js pilots/independent-implementation-005-organization-governance",
-  "valid": true,
-  "errors": [],
-  "warnings": [],
-  "checks": [
-    "required package, object, relation and gate-result fields",
-    "unique object and relation ids",
-    "relation source and target existence",
-    "relation id consistency",
-    "readiness and gate verdict values",
-    "organization_governance object-kind conformance",
-    "organization_governance relation-type conformance",
-    "decision-right and feedback boundary represented"
-  ],
-  "claim_supported": "The package follows the declared Mirai Graph profile shape checked by the current validator.",
-  "limitations": [
-    "The pilot is synthetic and does not prove organization performance.",
-    "The profile models governance structure, not local legal, HR or operational policy."
-  ]
-}

package/playground/README.md

@@ -1,78 +0,0 @@
-# Mirai Graph Playground
-
-Status: 1.0 release-candidate deterministic runnable demo
-
-This directory is a playground package for public-safe Mirai Graph demos. The
-current 1.0 release-candidate playground is CLI-based and deterministic:
-runnable examples live in `examples/`, `benchmarks/` and `pilots/`, and the
-generated report is stored as `playground/demo-report.md`.
-
-## Quick Runs
-
-Validate a minimal graph package:
-
-```bash
-npm run validate:minimal
-```
-
-Preview a graph seed:
-
-```bash
-npm run seed:preview
-```
-
-Generate a synthetic context pack:
-
-```bash
-npm run context:generate
-```
-
-Generate the end-to-end playground report:
-
-```bash
-npm run playground:demo
-npm run playground:report
-```
-
-Validate implementation-control and process-control examples:
-
-```bash
-npm run validate:implementation-control
-npm run validate:implementation-control-cycles
-npm run validate:launch-record
-npm run validate:process-transition
-npm run validate:process-control
-```
-
-Run negative fixtures:
-
-```bash
-npm run test:negative
-npm run test:process-transition-negative
-```
-
-Run the full release-candidate suite:
-
-```bash
-npm test
-```
-
-## Demo Paths
-
-- `examples/minimal-graph/`
-- `examples/graph-seed-minimal/`
-- `examples/implementation-control-minimal/`
-- `examples/implementation-control-cycles/`
-- `examples/launch-record-minimal/`
-- `examples/process-transition-minimal/`
-- `examples/process-control-contract-minimal/`
-- `benchmarks/synthetic-context-reduction-v0/`
-- `benchmarks/synthetic-context-reduction-v0/results/baseline-comparison-result.json`
-- `playground/demo-report.md`
-
-## Future Work
-
-A hosted or interactive playground can be added later. Until then, this index
-keeps the public README honest: Mirai Graph has a deterministic local report with
-transition explanation and baseline comparison, but not yet a separate
-interactive application.

package/playground/demo-report.md

@@ -1,84 +0,0 @@
-# Mirai Graph Playground Demo Report
-
-Status: deterministic 1.0.0-rc.6 demo
-
-## Control Loop
-
-```text
-seed -> graph -> context -> launch -> transition explanation -> cockpit -> traceability -> multi-source feedback -> evidence -> kaizen -> baseline comparison
-```
-
-## Demo Inputs
-
-- Synthetic package: `benchmarks/synthetic-context-reduction-v0`
-- Objects: `12`
-- Relations: `8`
-- Context pack: `context_pack.task_notify_after_approval`
-- Launch record: `launch_record.synthetic_batch`
-- Transition request: `transition_request.release_ready_to_released`
-- Transition explanation: `transition_explanation.release_ready_to_released`
-- Process-control contract: `process_control_contract.synthetic_executable_process`
-- Development cockpit: `cockpit_report.synthetic_delivery`
-- Feature traceability: `trace_report.synthetic_feature_delivery`
-- Multi-source feedback: `feedback_report.synthetic_multi_source`
-- Baseline comparison: `baseline_comparison.synthetic_notify_after_approval`
-
-## Commands
-
-```bash
-npm run validate:minimal
-npm run seed:preview
-npm run context:generate
-npm run validate:launch-record
-npm run validate:process-transition
-npm run validate:process-transition-report
-npm run validate:process-control
-npm run validate:instrumentation-layer
-npm run validate:instrumentation-report
-npm run validate:implementation-control-cycles
-npm run validate:baseline-comparison
-```
-
-## Transition Explanation
-
-- Requested transition: `release_ready -> released`
-- Matched transition: `true`
-- Required evidence: `release_evidence`
-- Missing evidence: `0`
-- Kaizen decision: `satisfied`
-
-## Instrumentation
-
-- Cockpit production readiness: `not_ready`
-- Cockpit next action: `promote_to_review_ready_after_transition_validation`
-- Feature mappings: `1`
-- Evidence-backed mappings: `1`
-- Multi-source feedback verdict: `accepted_for_transition`
-- Blocking findings: `0`
-- Kaizen refs: `kaizen.synthetic_traceability_checklist`
-
-## Baseline Comparison
-
-- Baseline context units: `620`
-- Mirai Graph context units: `270`
-- Context reduction: `56.4516%`
-- Baseline missed dependencies: `2`
-- Mirai Graph missed dependencies: `0`
-- Verdict: `synthetic_mirai_graph_result_stronger_with_limits`
-
-## What This Demonstrates
-
-- Mirai Graph can validate a graph package.
-- Mirai Graph can generate task-specific context from graph state.
-- Launch records describe bounded work permission.
-- Process transitions are checked and explained against an executable state machine.
-- Process-control contracts bind launch, evidence, recovery and Kaizen policy.
-- Instrumentation connects cockpit signals, feature traceability and multi-source feedback.
-- Baseline comparison records synthetic measurement boundaries.
-
-## Boundaries
-
-- This is a public-safe synthetic demo.
-- Generated context is not canonical state.
-- Evidence and proposals do not authorize canonical updates.
-- Synthetic evidence is not broad scientific proof.

package/profiles/README.md

@@ -1,28 +0,0 @@
-# Mirai Graph Profiles
-
-Profiles adapt Mirai Graph to a domain without changing the core standard.
-Use [Profile Boundaries](../standard/profile-boundaries.md) before adding a new
-profile: most new ideas should become an extension, validator, example or
-proposal before they become another profile.
-
-Current release-candidate profiles:
-
-- [software-specification](software-specification/README.md)
-- [project-management](project-management/README.md)
-- [ai-employee](ai-employee/README.md)
-- [character-layer](character-layer/README.md)
-- [skill-runtime](skill-runtime/README.md)
-- [implementation-control](implementation-control/README.md)
-- [organization-governance](organization-governance/README.md)
-
-Proposal/experimental profile:
-
-- [societal-governance](societal-governance/README.md)
-
-Each release-candidate profile declares allowed object kinds, relation types,
-default readiness and governance gates. Proposal/experimental profiles are
-public-safe exploration surfaces and are not core `1.0.0-rc.1` conformance
-requirements.
-
-Executable profile examples and anti-examples are documented in
-[Profile Conformance Fixtures](../docs/adoption/profile-conformance-fixtures.md).

package/profiles/ai-employee/README.md

@@ -1,132 +0,0 @@
-# AI Employee Profile
-
-Status: 1.0 release-candidate profile
-
-## Purpose
-
-The `ai_employee` profile adapts Mirai Graph to AI employees, AI departments and
-federated AI-service systems.
-
-It treats an AI employee as a governed runtime over an evolutionary graph:
-
-- the graph stores canonical state, roles, skills, knowledge, memory, tools,
-  policies, workflows and lessons;
-- generated context helps a task;
-- runtime execution happens through tools, approvals and audit;
-- feedback proposes learning but does not mutate the graph automatically.
-
-## Object Kinds
-
-Initial allowed object kinds:
-
-- `ai_employee`;
-- `ai_department`;
-- `role`;
-- `specialization`;
-- `skill`;
-- `knowledge`;
-- `memory`;
-- `event`;
-- `signal`;
-- `action`;
-- `tool`;
-- `capability`;
-- `policy`;
-- `workflow`;
-- `automation_rule`;
-- `result`;
-- `feedback`;
-- `lesson`;
-- `delegation`;
-- `federation_endpoint`;
-- `governance_gate`.
-
-## Relation Types
-
-Initial allowed relation types:
-
-- `has_role`;
-- `has_specialization`;
-- `has_skill`;
-- `uses_knowledge`;
-- `requires_capability`;
-- `can_execute`;
-- `requires_approval`;
-- `triggered_by`;
-- `responds_to`;
-- `delegates_to`;
-- `escalates_to`;
-- `supervises`;
-- `learns_from`;
-- `updates_behavior`;
-- `belongs_to_department`;
-- `federates_with`;
-- `produces`;
-- `governs`;
-- `related_to`.
-
-## Governance Gates
-
-Initial gates:
-
-- `human_review_before_canonical_write`;
-- `approval_before_external_action`;
-- `feedback_learning_before_behavior_update`;
-- `public_safety_before_release`.
-
-## Runtime Boundary
-
-The profile does not make the graph a runtime by itself.
-
-Use this separation:
-
-```text
-canonical graph state
--> generated context
--> runtime decision
--> proposed action
--> approval gate
--> executed action
--> audited result
--> feedback
--> learning proposal
--> canonical graph update
-```
-
-## Minimal Useful Package
-
-A Level 1 AI-employee package should include:
-
-- one `ai_employee`;
-- one `role`;
-- one `skill`;
-- one `tool`;
-- one `capability`;
-- one `policy`;
-- one `workflow`;
-- one `action`;
-- one `result`;
-- one `feedback`;
-- one `lesson`;
-- one `governance_gate`;
-- evidence objects or source records where claims need support.
-
-## Current Limitations
-
-The profile does not yet standardize:
-
-- provider-specific LLM capabilities;
-- queue or worker implementation;
-- authentication and authorization runtime;
-- tool sandboxing;
-- long-term memory storage engines;
-- user interface requirements;
-- federation trust protocols.
-
-These belong to implementation profiles or future standard sections.
-
-## Example
-
-Minimal synthetic fixture:
-
-`examples/ai-employee-minimal/`

package/profiles/ai-employee/profile.json

@@ -1,58 +0,0 @@
-{
-  "id": "profile.ai_employee",
-  "name": "AI Employee",
-  "version": "0.1.0",
-  "description": "Profile for modeling AI employees, roles, skills, tools, policies, workflows, actions, feedback and learning gates.",
-  "allowed_object_kinds": [
-    "ai_employee",
-    "ai_department",
-    "role",
-    "specialization",
-    "skill",
-    "knowledge",
-    "memory",
-    "event",
-    "signal",
-    "action",
-    "tool",
-    "capability",
-    "policy",
-    "workflow",
-    "automation_rule",
-    "result",
-    "feedback",
-    "lesson",
-    "delegation",
-    "federation_endpoint",
-    "governance_gate",
-    "evidence"
-  ],
-  "allowed_relation_types": [
-    "has_role",
-    "has_specialization",
-    "has_skill",
-    "uses_knowledge",
-    "requires_capability",
-    "can_execute",
-    "requires_approval",
-    "triggered_by",
-    "responds_to",
-    "delegates_to",
-    "escalates_to",
-    "supervises",
-    "learns_from",
-    "updates_behavior",
-    "belongs_to_department",
-    "federates_with",
-    "produces",
-    "governs",
-    "related_to"
-  ],
-  "default_readiness": "draft",
-  "governance_gates": [
-    "human_review_before_canonical_write",
-    "approval_before_external_action",
-    "feedback_learning_before_behavior_update",
-    "public_safety_before_release"
-  ]
-}