mirai-graph 1.3.0 → 2.1.0

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.

package/profiles/project-management/profile.json

@@ -1,38 +0,0 @@
-{
-  "id": "profile.project_management",
-  "name": "Project Management",
-  "version": "0.1.0",
-  "description": "Profile for modeling goals, tasks, decisions, risks, milestones and evidence in a project.",
-  "allowed_object_kinds": [
-    "system",
-    "goal",
-    "task",
-    "decision",
-    "risk",
-    "milestone",
-    "stakeholder",
-    "evidence",
-    "governance_gate",
-    "project_dna",
-    "stage",
-    "batch",
-    "requirement",
-    "method",
-    "lesson",
-    "regression_case"
-  ],
-  "allowed_relation_types": [
-    "depends_on",
-    "blocks",
-    "supports",
-    "evidences",
-    "belongs_to",
-    "governs",
-    "related_to"
-  ],
-  "default_readiness": "draft",
-  "governance_gates": [
-    "human_review_before_canonical_write",
-    "owner_approval_before_action"
-  ]
-}

package/profiles/skill-runtime/README.md

@@ -1,99 +0,0 @@
-# Skill Runtime Profile
-
-Status: 1.0 release-candidate profile
-
-The `skill_runtime` profile models a governed skill, capability module or
-service as a Mirai Graph-managed runtime context.
-
-It is designed for systems where the graph helps with routing, capability
-selection, policy reminders, readiness, evidence and generated context, while
-raw source material remains authoritative for detailed domain meaning.
-
-## Object Kinds
-
-The profile includes:
-
-- `skill`;
-- `capability`;
-- `activity`;
-- `rule`;
-- `owner_domain`;
-- `source_boundary`;
-- `raw_source`;
-- `runtime_context`;
-- `projection_view`;
-- `quality_gate`;
-- `adoption_report`;
-- `effectiveness_report`;
-- `semantic_review`;
-- `runtime_policy`;
-- `fallback`;
-- `handoff`;
-- `learning_proposal`;
-- `federation_contract`;
-- `governance_gate`;
-- `evidence`.
-
-## Relation Types
-
-The profile includes relation types for:
-
-- owner boundaries;
-- capabilities and activities;
-- rules and quality gates;
-- raw-source fallback;
-- generated runtime context;
-- semantic preservation;
-- effectiveness measurement;
-- routing and handoff;
-- federation contracts;
-- learning proposals.
-
-## Hybrid SOT Boundary
-
-This profile uses [Hybrid Source Of Truth](../../standard/hybrid-source-of-truth.md).
-
-```text
-graph context can route and orient work
-raw source remains authoritative for domain meaning
-```
-
-Generated runtime context must not rewrite skill sources or grant canonical
-write permission.
-
-## Runtime Boundary
-
-Runtime use follows [Runtime Enablement](../../standard/runtime-enablement.md).
-
-Graph-mode can become the primary context only for a declared task and scope
-after runtime preflight. Sensitive work requires fallback to raw sources and
-the relevant approval gates.
-
-The profile does not provide a separate runtime engine. Skills use the public
-[Project Technology](../../standard/project-technology.md) extension for
-inventory, task-scoped context, synchronization and verification. The profile
-continues to own the vocabulary of skill capabilities, rules and relations.
-
-## Federation Routing Control Loop
-
-When a skill runtime participates in a larger federation, routing should be
-auditable through:
-
-- [Route Explanation](../../standard/route-explanation.md);
-- [Routing Fixtures](../../standard/routing-fixtures.md);
-- [Federation Health](../../standard/federation-health.md);
-- [Route Regression](../../standard/route-regression.md).
-
-These artifacts explain and test routing behavior. They do not authorize
-execution or source rewrites.
-
-## Minimal Fixture
-
-The executable fixture is:
-
-```text
-examples/skill-runtime-minimal/
-```
-
-It proves only profile shape conformance. It does not prove semantic
-completeness, operational effectiveness or runtime safety.

package/profiles/skill-runtime/profile.json

@@ -1,58 +0,0 @@
-{
-  "id": "profile.skill_runtime",
-  "name": "Skill Runtime",
-  "version": "0.1.0",
-  "description": "Profile for modeling a governed skill, capability module or service as a Hybrid Source Of Truth runtime context.",
-  "allowed_object_kinds": [
-    "skill",
-    "capability",
-    "activity",
-    "rule",
-    "owner_domain",
-    "source_boundary",
-    "raw_source",
-    "runtime_context",
-    "projection_view",
-    "quality_gate",
-    "adoption_report",
-    "effectiveness_report",
-    "semantic_review",
-    "runtime_policy",
-    "fallback",
-    "handoff",
-    "learning_proposal",
-    "federation_contract",
-    "governance_gate",
-    "evidence"
-  ],
-  "allowed_relation_types": [
-    "owns_domain",
-    "has_capability",
-    "supports_activity",
-    "uses_rule",
-    "requires_gate",
-    "requires_fallback",
-    "reads_source",
-    "generates_context",
-    "projects_view",
-    "evidences",
-    "preserves_semantics",
-    "measures_effectiveness",
-    "routes_to",
-    "hands_off_to",
-    "exports_contract",
-    "federates_with",
-    "proposes_learning",
-    "governs",
-    "related_to"
-  ],
-  "default_readiness": "draft",
-  "governance_gates": [
-    "human_review_before_canonical_write",
-    "semantic_preservation_before_runtime",
-    "effectiveness_before_federation",
-    "runtime_enablement_before_primary_context",
-    "fallback_required_for_sensitive_tasks",
-    "public_safety_before_release"
-  ]
-}

package/profiles/societal-governance/README.md

@@ -1,129 +0,0 @@
-# Societal Governance Profile
-
-Status: proposal/experimental profile
-
-The societal-governance profile models governance systems where humans,
-bounded AI avatars, norms, initiatives, decisions, execution and outcome
-learning form a controlled evolutionary graph.
-
-It extends the existing `organization_governance`, `character_layer`,
-`process_control` and evidence-control patterns. It does not claim legal,
-democratic, cryptographic or public-governance validity.
-
-## Scope
-
-Use this profile for synthetic or bounded shadow-governance models such as:
-
-- organization governance experiments;
-- SIMAI OS shadow governance;
-- non-binding municipal or public-policy simulations;
-- research fixtures for rights, consent, privacy, appeal and learning gates.
-
-Do not use this profile as a production public-governance authority model.
-
-## Typical Objects
-
-- `governance_dna`
-- `governance_level`
-- `participant`
-- `stakeholder_group`
-- `ai_avatar`
-- `avatar_contract`
-- `delegation_scope`
-- `consent_receipt`
-- `private_decision_journal`
-- `initiative`
-- `simulation`
-- `legitimacy_gate`
-- `rights_gate`
-- `privacy_gate`
-- `affectedness_gate`
-- `anti_capture_gate`
-- `participation_signal`
-- `decision`
-- `decision_trace`
-- `execution_mandate`
-- `outcome_evidence`
-- `appeal`
-- `harm_report`
-- `learning_proposal`
-- `amendment_proposal`
-- `evidence`
-
-## Typical Relations
-
-- `defined_by_dna`
-- `member_of_level`
-- `represented_by_avatar`
-- `bound_by_contract`
-- `delegates_scope_to`
-- `has_consent_receipt`
-- `requires_reconsent`
-- `opens_initiative`
-- `affects_group`
-- `requires_gate`
-- `passes_gate`
-- `fails_gate`
-- `uses_simulation`
-- `uses_evidence`
-- `casts_signal`
-- `summarizes_private_proof`
-- `supports_decision_trace`
-- `authorizes_decision`
-- `creates_execution_mandate`
-- `assigned_to_executor`
-- `produces_outcome`
-- `has_appeal_path`
-- `triggers_appeal`
-- `reports_harm`
-- `creates_learning_proposal`
-- `proposes_dna_amendment`
-- `approved_update_to`
-
-## Governance Gates
-
-- Rights before optimization.
-- Consent before avatar action.
-- Re-consent after model, scope or authority change.
-- Privacy before public trace.
-- Affectedness before weighted decision.
-- Anti-capture before weight change.
-- Human owner before binding action.
-- Evidence before execution mandate.
-- Appeal path before governed decision.
-- Outcome evidence before learning update.
-- Generated context is not authorization.
-- Feedback is not automatic graph update.
-
-## Conformance Levels
-
-- `G0_concept`: model is described, no executable trace.
-- `G1_structured_shadow`: non-binding traces on non-sensitive cases.
-- `G2_assisted_internal`: human-owned internal decisions with AI-assisted
-  traces.
-- `G3_governed_internal`: bounded organizational governance with policy, audit,
-  rollback and evidence.
-- `G4_public_simulation`: public-policy simulations with no binding authority.
-- `G5_limited_public_pilot`: legally and ethically reviewed civic pilot.
-- `G6_constitutional_governance`: formal public governance; out of scope for
-  current evidence.
-
-This proposal profile is intended for `G0_concept` and `G1_structured_shadow`
-fixtures until independent review and pilot evidence exist.
-
-## Boundaries
-
-- AI avatars can explain, recommend, summarize and submit signals only inside
-  explicit consent and delegation scopes.
-- AI avatars and generated context cannot authorize decisions.
-- Contribution, expertise or implementation weights cannot override protected
-  rights.
-- Private decision journals must not be exposed in public traces.
-- Decisions require appeal or reopen paths.
-- Outcome evidence creates learning proposals; it does not update canonical
-  graph state automatically.
-- Public examples must remain synthetic and non-binding.
-
-## Example
-
-See [Societal Governance Minimal](../../examples/societal-governance-minimal/README.md).