mirai-graph 1.4.0 → 2.1.0

package/profiles/character-layer/README.md

@@ -1,143 +0,0 @@
-# Character Layer Profile
-
-Status: 1.0 release-candidate 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

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

package/profiles/implementation-control/README.md

@@ -1,174 +0,0 @@
-# Implementation Control Profile
-
-Status: 1.0 release-candidate profile
-
-## Purpose
-
-The implementation-control profile adapts Mirai Graph to governed implementation
-workflows where generated context, human review, evidence, proposals and gates
-must be separated from canonical updates and executed actions.
-
-It is the profile to use when the hard question is not "what are the project
-tasks?" but "is this work allowed to move from knowledge or planning into
-bounded execution, implementation state, release readiness or canonical graph
-change?"
-
-It is useful when a project needs to coordinate:
-
-- implementation baselines;
-- generated human projections;
-- semantic reviews;
-- workflow batches;
-- implementation cycles;
-- technology contracts and technology quality feedback;
-- graph DNA alignment;
-- source boundary contracts;
-- work state machines;
-- recovery records;
-- risk controls;
-- multi-agent coordination contracts;
-- evidence packs;
-- graph sync proposals;
-- launch gates;
-- approval gates;
-- controlled canonical updates;
-- drift checks;
-- continuous-improvement items.
-
-## Core Pattern
-
-```text
-baseline
--> projection view
--> semantic review
--> launch gate
--> workflow batch
--> evidence pack
--> technology quality feedback
--> sync proposal
--> approval gate
--> controlled update
--> drift check
--> improvement item
-```
-
-`ready_to_execute` and `ready_to_code` are readiness states. They are not the
-same as `executed`, `implemented`, `evidence_ready` or `release_ready`.
-
-## Object Kinds
-
-Initial allowed object kinds:
-
-- `implementation_baseline`;
-- `projection_view`;
-- `semantic_review`;
-- `workflow_batch`;
-- `implementation_cycle`;
-- `technology_contract`;
-- `technology_quality_feedback`;
-- `quality_finding`;
-- `graph_dna`;
-- `component_dna`;
-- `dna_alignment`;
-- `source_boundary_contract`;
-- `source_boundary`;
-- `work_state_machine`;
-- `work_state`;
-- `recovery_record`;
-- `risk_control`;
-- `agent_reservation`;
-- `coordination_contract`;
-- `evidence_pack`;
-- `sync_proposal`;
-- `launch_gate`;
-- `approval_gate`;
-- `controlled_update`;
-- `implementation_state`;
-- `drift_check`;
-- `validator`;
-- `risk`;
-- `blocker`;
-- `review`;
-- `release_gate`;
-- `kaizen_item`;
-- `evidence`.
-
-## Relation Types
-
-Initial allowed relation types:
-
-- `derives_projection`;
-- `reviews_projection`;
-- `produces_evidence`;
-- `proposes_update`;
-- `requires_gate`;
-- `launches_batch`;
-- `requires_launch_record`;
-- `checks_transition`;
-- `checks_conformance_to`;
-- `classifies`;
-- `routes_to`;
-- `requires_technology_feedback`;
-- `requires_kaizen_closure`;
-- `approves_update`;
-- `updates_baseline`;
-- `checks_drift`;
-- `validates_cycle`;
-- `progresses_to`;
-- `promotes_feedback`;
-- `aligns_with`;
-- `owns_scope`;
-- `excludes_scope`;
-- `defines_boundary`;
-- `transitions_to`;
-- `resumes_from`;
-- `controls_risk`;
-- `reserves_scope`;
-- `coordinates_with`;
-- `blocks`;
-- `mitigates`;
-- `records_state`;
-- `requires_review`;
-- `requires_release_gate`;
-- `improves_process`;
-- `evidences`;
-- `related_to`.
-
-## Governance Gates
-
-Initial gates:
-
-- `semantic_review_before_sync_proposal`;
-- `evidence_pack_before_approval`;
-- `launch_gate_before_work_batch`;
-- `approval_before_canonical_update`;
-- `drift_check_before_state_promotion`;
-- `technology_quality_feedback_before_acceptance`;
-- `public_safety_before_public_transfer`;
-- `no_generated_context_as_authorization`;
-- `no_feedback_as_automatic_update`.
-
-## Relationship To Project Management
-
-Use `project-management` for ordinary project goals, tasks, risks, milestones
-and stakeholder coordination.
-
-Use `implementation-control` when the critical question is whether a proposed
-implementation or graph update is sufficiently evidenced, reviewed and approved
-to affect canonical state.
-
-In short: `project-management` coordinates work; `implementation-control`
-governs movement from plans and generated context into bounded action,
-evidence, approved updates and process learning.
-
-The shared [Project Technology](../../standard/project-technology.md) extension
-supplies inventory, task context and exact accepted-target verification. It
-does not replace this profile's launch, transition and evidence rules.
-
-## Public Example
-
-Executable example:
-
-```text
-examples/implementation-control-minimal/
-```

package/profiles/implementation-control/profile.json

@@ -1,108 +0,0 @@
-{
-  "id": "profile.implementation_control",
-  "name": "Implementation Control",
-  "version": "0.1.0",
-  "description": "Profile for governed implementation workflows that separate baselines, projections, reviews, evidence, proposals, approval gates and controlled updates.",
-  "allowed_object_kinds": [
-    "implementation_baseline",
-    "projection_view",
-    "semantic_review",
-    "workflow_batch",
-    "implementation_cycle",
-    "launch_record",
-    "process_control_contract",
-    "process_transition_request",
-    "process_transition_result",
-    "technology_contract",
-    "technology_quality_feedback",
-    "quality_finding",
-    "development_cockpit",
-    "cockpit_instrument",
-    "feature_implementation_trace",
-    "implementation_mapping",
-    "multi_source_quality_feedback",
-    "feedback_source",
-    "kaizen_review",
-    "graph_dna",
-    "component_dna",
-    "dna_alignment",
-    "source_boundary_contract",
-    "source_boundary",
-    "work_state_machine",
-    "work_state",
-    "recovery_record",
-    "risk_control",
-    "agent_reservation",
-    "coordination_contract",
-    "evidence_pack",
-    "sync_proposal",
-    "launch_gate",
-    "approval_gate",
-    "controlled_update",
-    "implementation_state",
-    "drift_check",
-    "validator",
-    "risk",
-    "blocker",
-    "review",
-    "release_gate",
-    "kaizen_item",
-    "evidence",
-    "regression_case",
-    "lesson"
-  ],
-  "allowed_relation_types": [
-    "derives_projection",
-    "reviews_projection",
-    "produces_evidence",
-    "proposes_update",
-    "requires_gate",
-    "launches_batch",
-    "requires_launch_record",
-    "checks_transition",
-    "checks_conformance_to",
-    "classifies",
-    "routes_to",
-    "requires_technology_feedback",
-    "measures",
-    "traces_implementation",
-    "aggregates_feedback",
-    "calibrates_transition",
-    "requires_kaizen_closure",
-    "approves_update",
-    "updates_baseline",
-    "checks_drift",
-    "validates_cycle",
-    "progresses_to",
-    "promotes_feedback",
-    "aligns_with",
-    "owns_scope",
-    "excludes_scope",
-    "defines_boundary",
-    "transitions_to",
-    "resumes_from",
-    "controls_risk",
-    "reserves_scope",
-    "coordinates_with",
-    "blocks",
-    "mitigates",
-    "records_state",
-    "requires_review",
-    "requires_release_gate",
-    "improves_process",
-    "evidences",
-    "related_to"
-  ],
-  "default_readiness": "draft",
-  "governance_gates": [
-    "semantic_review_before_sync_proposal",
-    "evidence_pack_before_approval",
-    "approval_before_canonical_update",
-    "launch_gate_before_work_batch",
-    "drift_check_before_state_promotion",
-    "technology_quality_feedback_before_acceptance",
-    "public_safety_before_public_transfer",
-    "no_generated_context_as_authorization",
-    "no_feedback_as_automatic_update"
-  ]
-}

package/profiles/organization-governance/README.md

@@ -1,60 +0,0 @@
-# Organization Governance Profile
-
-Status: 1.0 release-candidate profile
-
-The organization-governance profile models how an organization coordinates
-mission, strategy, departments, portfolios, projects, policies, decision rights,
-risks, evidence, feedback and improvement.
-
-It is broader than `project-management`, but it does not replace operational,
-legal, financial or domain-specific governance systems. Mirai Graph provides the
-graph contract and validation surface for connecting them.
-
-## Typical Objects
-
-- `organization`
-- `mission`
-- `strategy`
-- `portfolio`
-- `department`
-- `program`
-- `project`
-- `objective`
-- `policy`
-- `decision_right`
-- `governance_gate`
-- `risk`
-- `control`
-- `metric`
-- `feedback`
-- `kaizen_item`
-- `evidence`
-
-## Typical Relations
-
-- `aligns_with`
-- `owns`
-- `belongs_to`
-- `governs`
-- `requires_approval`
-- `controls`
-- `mitigates`
-- `measures`
-- `supports`
-- `escalates_to`
-- `produces_feedback`
-- `improves`
-- `evidences`
-
-## Boundaries
-
-- Readiness is not execution.
-- Evidence is not authorization.
-- Feedback is not an automatic policy or process update.
-- Generated context is not canonical organizational state.
-- Country-scale or public-sector governance requires additional law, audit,
-  accountability and public legitimacy layers outside this alpha profile.
-
-## Example
-
-See [Organization Governance Minimal](../../examples/organization-governance-minimal/README.md).

package/profiles/organization-governance/profile.json

@@ -1,56 +0,0 @@
-{
-  "id": "profile.organization_governance",
-  "name": "Organization Governance",
-  "version": "0.1.0",
-  "description": "Profile for modeling organization-level governance across mission, strategy, departments, portfolios, policies, decision rights, risks, evidence, feedback and improvement gates.",
-  "allowed_object_kinds": [
-    "organization",
-    "mission",
-    "strategy",
-    "portfolio",
-    "department",
-    "program",
-    "project",
-    "objective",
-    "policy",
-    "decision_right",
-    "governance_gate",
-    "role",
-    "capability",
-    "risk",
-    "control",
-    "metric",
-    "feedback",
-    "kaizen_item",
-    "evidence"
-  ],
-  "allowed_relation_types": [
-    "aligns_with",
-    "owns",
-    "belongs_to",
-    "governs",
-    "requires_approval",
-    "controls",
-    "mitigates",
-    "measures",
-    "supports",
-    "depends_on",
-    "blocks",
-    "escalates_to",
-    "produces_feedback",
-    "improves",
-    "evidences",
-    "related_to"
-  ],
-  "default_readiness": "draft",
-  "governance_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"
-  ]
-}
-

package/profiles/project-management/README.md

@@ -1,119 +0,0 @@
-# Project Management Profile
-
-Status: 1.0 release-candidate profile
-
-## Purpose
-
-The project-management profile adapts Mirai Graph to small project and workflow
-management.
-
-It helps connect:
-
-- goals;
-- tasks;
-- decisions;
-- risks;
-- milestones;
-- stakeholders;
-- evidence;
-- governance gates.
-
-## Object Kinds
-
-Initial allowed object kinds:
-
-- `system`;
-- `goal`;
-- `task`;
-- `decision`;
-- `risk`;
-- `milestone`;
-- `stakeholder`;
-- `evidence`;
-- `governance_gate`.
-
-## Relation Types
-
-Initial allowed relation types:
-
-- `depends_on`;
-- `blocks`;
-- `supports`;
-- `evidences`;
-- `belongs_to`;
-- `governs`;
-- `related_to`.
-
-## Governance Gates
-
-Initial gates:
-
-- `human_review_before_canonical_write`;
-- `owner_approval_before_action`.
-
-Domain-specific projects may add gates such as:
-
-- `owner_approval_before_schedule_publish`;
-- `privacy_review_before_public_release`;
-- `budget_owner_approval_before_commitment`.
-
-## Readiness Guidance
-
-Use:
-
-- `draft` for early tasks, decisions and risks;
-- `review_ready` when the object is ready for owner review;
-- `accepted` only after owner or reviewer acceptance;
-- `blocked` when missing evidence or approval prevents progress;
-- `deprecated` when the item is superseded but should remain traceable.
-
-## Adoption Path
-
-Recommended path:
-
-1. Start with a graph seed.
-2. Generate or manually draft a graph embryo.
-3. Accept only reviewed objects and relations into canonical graph state.
-4. Add governance gates for decisions or actions.
-5. Generate context packs for concrete tasks.
-6. Record readiness score and gaps.
-
-## Pilot Evidence
-
-Pilot 001 uses this profile:
-
-`pilots/independent-implementation-001-conference-planning/`
-
-Pilot finding:
-
-The profile is sufficient for a small Level 1 package, but needs richer
-modeling for milestones, owners, task status vs readiness and action records.
-
-## Next Extension Candidates
-
-Larger managed projects need a richer project-control model than the initial
-Level 1 profile. Public-safe harvest work identified the following extension
-candidates:
-
-- lifecycle stages;
-- implementation clusters;
-- workflow batches;
-- human projection feedback loops;
-- review records;
-- release gates;
-- graph sync proposals;
-- candidate closure decisions;
-- continuous-improvement items.
-
-These candidates are not yet part of `profile.json`. They should be introduced
-through a future profile extension or a separate implementation-control profile
-after synthetic examples and validation rules are added.
-
-See:
-
-- `docs/transfer/project-management-standard-harvest-2026-06-02.md`
-- `examples/managed-project-control-loop/README.md`
-
-Repository execution uses the shared
-[Project Technology](../../standard/project-technology.md) extension. This
-profile still owns goals, stages, tasks, decisions and delivery meaning.