mirai-graph 1.0.0-rc.1

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

@@ -0,0 +1,14 @@
+{
+  "id": "package.organization_governance_pilot_005",
+  "name": "Organization Governance Pilot 005",
+  "version": "0.1.0",
+  "profile": "organization_governance",
+  "conformance_level": "level_1",
+  "description": "A synthetic independent implementation pilot for organization-level governance.",
+  "license": "CC-BY-4.0",
+  "public_safety": "synthetic_public",
+  "graph": {
+    "objects": "graph/objects.json",
+    "relations": "graph/relations.json"
+  }
+}

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

@@ -0,0 +1,47 @@
+# 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

@@ -0,0 +1,29 @@
+{
+  "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

@@ -0,0 +1,78 @@
+# 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

@@ -0,0 +1,84 @@
+# Mirai Graph Playground Demo Report
+
+Status: deterministic 1.0.0-rc.1 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

@@ -0,0 +1,19 @@
+# Mirai Graph Profiles
+
+Profiles adapt Mirai Graph to a domain without changing the core standard.
+
+Current public 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)
+
+Each profile declares allowed object kinds, relation types, default readiness
+and governance gates.
+
+Executable profile examples and anti-examples are documented in
+[Profile Conformance Fixtures](../docs/adoption/profile-conformance-fixtures.md).

package/profiles/ai-employee/README.md

@@ -0,0 +1,132 @@
+# AI Employee Profile
+
+Status: alpha 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

@@ -0,0 +1,58 @@
+{
+  "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"
+  ]
+}

package/profiles/character-layer/README.md

@@ -0,0 +1,143 @@
+# Character Layer Profile
+
+Status: alpha profile
+
+## Purpose
+
+The `character_layer` profile adapts Mirai Graph to model-independent AI
+character governance.
+
+It treats character as graph state:
+
+- constitution;
+- principles;
+- character virtues;
+- character boundaries;
+- role character profiles;
+- reflection protocols;
+- fixtures;
+- violation patterns;
+- correction loops;
+- evidence and governance gates.
+
+## Non-Goals
+
+The profile does not:
+
+- train or fine-tune a base model;
+- prove alignment or behavior quality;
+- authorize tool use, external actions or canonical writes;
+- replace action gates, runtime policy or human approval;
+- replace the `ai_employee`, `skill_runtime` or `organization_governance`
+  profiles;
+- publish private operational constitution content.
+
+## Object Kinds
+
+Initial allowed object kinds:
+
+- `character_constitution`;
+- `character_principle`;
+- `character_virtue`;
+- `character_boundary`;
+- `role_character_profile`;
+- `character_decision_rule`;
+- `reflection_protocol`;
+- `character_fixture`;
+- `violation_pattern`;
+- `correction_loop`;
+- `governance_gate`;
+- `evidence`.
+
+## Relation Types
+
+Initial allowed relation types:
+
+- `defines_principle`;
+- `promotes_virtue`;
+- `sets_character_boundary`;
+- `specializes_character`;
+- `resolves_character_conflict`;
+- `uses_reflection_protocol`;
+- `tests_character`;
+- `describes_violation_of`;
+- `corrects_violation`;
+- `updates_character`;
+- `evidences_character`;
+- `governs_role`;
+- `governs_employee`;
+- `requires_escalation_to`;
+- `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`;
+- `scientific_claim_before_publication`.
+
+## Runtime Boundary
+
+The profile models character state and review boundaries. It does not make
+generated context an authorization source.
+
+Use this separation:
+
+```text
+canonical character graph
+-> generated character context
+-> runtime reflection
+-> proposed answer or action
+-> policy or action gate
+-> output or execution
+-> reviewed result
+-> feedback
+-> correction proposal
+-> owner-approved canonical update
+```
+
+## Semantic Validation
+
+The reference validator applies additional fail-closed checks for this profile:
+relation directions must match the Character Layer contract, generated context
+or evidence cannot authorize action, feedback cannot automatically update
+canonical character state, `role_character_profile` cannot grant runtime/tool
+permission, and `correction_loop` must preserve owner or human review before
+canonical character updates.
+
+## Minimal Useful Package
+
+A Level 1 character-layer package should include:
+
+- one `character_constitution`;
+- several `character_principle` objects;
+- at least one `character_virtue`;
+- at least one `character_boundary`;
+- one `reflection_protocol`;
+- one `role_character_profile`;
+- one `character_fixture`;
+- one `violation_pattern`;
+- one `correction_loop`;
+- one `governance_gate`;
+- evidence objects or source records for the public boundary.
+
+## Current Limitations
+
+The profile does not yet standardize:
+
+- provider-specific behavior controls;
+- runtime policy enforcement engines;
+- human trust or calibration measurement;
+- cross-model evaluation;
+- product UI requirements;
+- private operational constitutions.
+
+## Example
+
+Minimal synthetic fixture:
+
+`examples/character-layer-minimal/`

package/profiles/character-layer/profile.json

@@ -0,0 +1,46 @@
+{
+  "id": "profile.character_layer",
+  "name": "Character Layer",
+  "version": "0.1.0",
+  "description": "Profile for modeling model-independent AI character, principles, character virtues, character boundaries, reflection protocols, fixtures, violations and correction loops.",
+  "allowed_object_kinds": [
+    "character_constitution",
+    "character_principle",
+    "character_virtue",
+    "character_boundary",
+    "role_character_profile",
+    "character_decision_rule",
+    "reflection_protocol",
+    "character_fixture",
+    "violation_pattern",
+    "correction_loop",
+    "governance_gate",
+    "evidence"
+  ],
+  "allowed_relation_types": [
+    "defines_principle",
+    "promotes_virtue",
+    "sets_character_boundary",
+    "specializes_character",
+    "resolves_character_conflict",
+    "uses_reflection_protocol",
+    "tests_character",
+    "describes_violation_of",
+    "corrects_violation",
+    "updates_character",
+    "evidences_character",
+    "governs_role",
+    "governs_employee",
+    "requires_escalation_to",
+    "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",
+    "scientific_claim_before_publication"
+  ]
+}