mirai-graph 1.0.0-rc.1

package/profiles/software-specification/README.md

@@ -0,0 +1,142 @@
+# Software Specification Profile
+
+Status: initial public profile
+
+## Purpose
+
+The software-specification profile adapts Mirai Graph to software packages,
+features, requirements, constraints, risks, implementation tasks and evidence.
+
+It helps connect:
+
+- package scope;
+- requirements;
+- features;
+- components;
+- constraints;
+- risks;
+- implementation tasks;
+- decisions;
+- evidence.
+
+## Object Kinds
+
+Initial allowed object kinds:
+
+- `package`;
+- `feature`;
+- `requirement`;
+- `constraint`;
+- `risk`;
+- `component`;
+- `task`;
+- `decision`;
+- `evidence`.
+
+## Relation Types
+
+Initial allowed relation types:
+
+- `implements`;
+- `depends_on`;
+- `blocks`;
+- `evidences`;
+- `generates`;
+- `related_to`;
+- `supersedes`.
+
+## Governance Gates
+
+Initial gates:
+
+- `human_review_before_canonical_write`;
+- `public_safety_before_release`.
+
+Domain-specific projects may add gates such as:
+
+- `requirement_traceability_before_implementation`;
+- `security_review_before_release`;
+- `acceptance_criteria_before_development`;
+- `test_evidence_before_acceptance`.
+
+## Traceability Guidance
+
+For implementation work, prefer explicit task traceability:
+
+```text
+task -> implements -> feature
+task -> depends_on -> requirement
+feature -> implements -> requirement
+component -> implements -> feature
+constraint -> blocks -> risk
+decision -> blocks -> risk
+```
+
+This makes generated context packs less likely to omit the underlying
+requirement when the task title only matches an implementation detail.
+
+## Readiness Guidance
+
+Use:
+
+- `draft` for early requirements, components, decisions and task plans;
+- `review_ready` when a requirement, feature, task or risk is ready for owner
+  review;
+- `accepted` only after review evidence exists;
+- `blocked` when missing requirement, security, acceptance or test evidence
+  prevents progress;
+- `deprecated` when a requirement, feature or decision is superseded.
+
+## Recommended Minimal Package
+
+A useful Level 1 software-specification package should include:
+
+- at least one `package`;
+- at least one `requirement`;
+- at least one `feature`;
+- at least one implementation `task`;
+- at least one `evidence` object;
+- direct traceability from task to feature and requirement;
+- constraints and risks when safety, privacy, security or reliability matters;
+- gate results for public safety or requirement traceability when the package
+  is used as evidence.
+
+## Current Limitations
+
+The profile does not yet define first-class object kinds for:
+
+- API endpoints;
+- acceptance criteria;
+- test cases;
+- verification results;
+- non-functional requirement categories;
+- owners or reviewers.
+
+Use `requirement`, `constraint`, `task`, `decision` and `evidence` until these
+extensions are standardized.
+
+## Adoption Path
+
+Recommended path:
+
+1. Start with a graph seed.
+2. Draft package, requirement, feature, component, task, risk and evidence
+   objects.
+3. Add direct task-to-requirement traceability before using the graph for
+   implementation context.
+4. Add constraints and risks for security, reliability or privacy concerns.
+5. Run package validation and readiness scoring.
+6. Generate a context pack for one implementation task.
+7. Review omissions before using the context pack for work.
+
+## Pilot Evidence
+
+Pilot 002 uses this profile:
+
+`pilots/independent-implementation-002-software-specification/`
+
+Pilot finding:
+
+The profile is sufficient for a small Level 1 package, but needs richer
+modeling for acceptance criteria, API contracts, non-functional requirements,
+test evidence and conformance fixtures.

package/profiles/software-specification/profile.json

@@ -0,0 +1,31 @@
+{
+  "id": "profile.software_specification",
+  "name": "Software Specification",
+  "version": "0.1.0",
+  "description": "Profile for modeling software packages, features, constraints, risks and evidence.",
+  "allowed_object_kinds": [
+    "package",
+    "feature",
+    "requirement",
+    "constraint",
+    "risk",
+    "component",
+    "task",
+    "decision",
+    "evidence"
+  ],
+  "allowed_relation_types": [
+    "implements",
+    "depends_on",
+    "blocks",
+    "evidences",
+    "generates",
+    "related_to",
+    "supersedes"
+  ],
+  "default_readiness": "draft",
+  "governance_gates": [
+    "human_review_before_canonical_write",
+    "public_safety_before_release"
+  ]
+}

package/publications/README.md

@@ -0,0 +1,24 @@
+# Publications
+
+This directory tracks public publications, preprints, citation metadata and
+reproducibility notes related to Mirai Graph.
+
+## Current Status
+
+The model is being prepared as an open research and standardization project.
+Publication links should be added only when the public page, DOI or venue record
+is confirmed.
+
+Do not describe a preprint as peer reviewed unless the venue record explicitly
+states peer-reviewed publication status.
+
+For the current public evidence framing, see
+`docs/research/scientific-evidence-package.md`.
+
+## Planned Records
+
+- initial preprint record;
+- preprint outline;
+- public citation note;
+- reproducibility package note;
+- future journal manuscript records.

package/publications/preprint-note.md

@@ -0,0 +1,11 @@
+# Preprint Note
+
+Status: placeholder
+
+Mirai Graph is related to the Evolutionary Object Graph research program.
+
+Public preprint records, DOI links and citation notes should be added here only
+after the public venue page and metadata are confirmed.
+
+Do not describe a preprint as peer reviewed unless the venue record explicitly
+states peer-reviewed publication status.

package/publications/preprint-outline.md

@@ -0,0 +1,45 @@
+# Mirai Graph Preprint Outline
+
+Status: draft outline
+
+## Working Title
+
+Mirai Graph: An Executable Evolutionary Graph Standard For Governed Human-AI Work
+
+## Abstract Shape
+
+This preprint introduces Mirai Graph, an evolutionary graph operating model for
+managing complex systems through typed objects, relations, evidence, generated
+context, readiness states and governance gates. It presents the public alpha
+standard, schemas, validators, synthetic benchmarks and public-safe pilots. The
+paper focuses on reproducible method structure and early evidence, not broad
+claims of effectiveness.
+
+## Proposed Sections
+
+1. Introduction and motivation.
+2. Related work and positioning.
+3. Mirai Graph model.
+4. Evidence, readiness and governance.
+5. Executable process control.
+6. Context-pack generation.
+7. Synthetic benchmark.
+8. Public-safe pilots.
+9. Limitations and threats to validity.
+10. Future work.
+
+## Candidate Contributions
+
+- Implementation-independent standard draft.
+- Public schemas and validators.
+- Executable governance model for launch records and process transitions.
+- Public-safe synthetic benchmark.
+- Evidence package and reproducibility protocol.
+
+## Required Before Publication
+
+- Complete baseline comparison report.
+- Add independent public-safe pilot evidence.
+- Finalize limitations table.
+- Add citations and related-work map.
+- Confirm publication venue and licensing constraints.

package/releases/0.1.0-alpha.0.md

@@ -0,0 +1,45 @@
+# Mirai Graph 0.1.0-alpha.0
+
+Release type: initial public foundation
+
+## Summary
+
+This alpha release establishes the public Mirai Graph repository as a starting
+point for standardization, developer adoption and reproducible synthetic
+examples.
+
+## Included
+
+- Public README and roadmap.
+- Repository purpose brief.
+- Concept and terminology docs.
+- Initial standard draft.
+- Object and relation models.
+- Lifecycle/readiness, evidence/provenance, governance and conformance sections.
+- Context-pack generation, profiles and test-suite direction.
+- JSON schemas for core package elements.
+- CLI validator.
+- Minimal graph example.
+- Synthetic context-reduction benchmark.
+- Initial adoption and contribution guides.
+
+## Validation
+
+Run:
+
+```bash
+npm test
+```
+
+Expected:
+
+- minimal graph validates;
+- synthetic benchmark validates;
+- synthetic context-reduction calculation returns `56.4516%`.
+
+## Important Limitations
+
+- This is an alpha foundation, not a stable standard.
+- Synthetic benchmark evidence is not external validation.
+- The project does not yet include an independent implementation pilot.
+- Context-pack generation has a documented model but no automated generator.

package/releases/0.1.0-alpha.1.md

@@ -0,0 +1,63 @@
+# Mirai Graph 0.1.0-alpha.1
+
+Release type: standard, tooling and pilot evidence alpha
+
+## Summary
+
+This release turns the initial public foundation into a more usable
+research-engineering alpha. It adds graph seed/embryo methods, transfer mapping
+from the practical `$graph` skill, alpha tooling, profiles, research protocols
+and the first independent implementation pilot.
+
+## Added
+
+- Practice-and-science program framing.
+- `$graph` to Mirai Graph transfer map.
+- Standard gap report.
+- Graph DNA, Graph Seed and Graph Embryo standard sections.
+- Graph seed and graph embryo schemas.
+- Minimal graph seed example.
+- Seed preview CLI command.
+- Readiness score CLI command.
+- Context-pack generator alpha command.
+- Profile validation command.
+- Context-pack, profile and readiness score schemas.
+- Software specification and project management profiles.
+- Measure-convert-optimize benchmark protocol.
+- Semantic completeness review protocol.
+- Independent implementation pilot plan.
+- Independent implementation pilot 001 for synthetic conference planning.
+- Worked tutorial from graph seed to validated package.
+- Negative validation fixtures.
+- `release:check` script.
+- GitHub Actions CI workflow.
+
+## Validation
+
+Run:
+
+```bash
+npm run release:check
+```
+
+Expected:
+
+- minimal graph validates;
+- synthetic benchmark validates;
+- graph seed validates;
+- profiles validate;
+- seed preview emits a graph embryo;
+- context-pack generator emits a context pack;
+- readiness score returns a capped pilot score for synthetic evidence;
+- synthetic benchmark returns `56.4516%`;
+- negative fixture fails as expected;
+- whitespace check passes.
+
+## Important Limitations
+
+- Context-pack generation is still alpha and includes the full package graph.
+- Readiness scoring is a navigation signal, not approval.
+- Pilot 001 is synthetic; it validates package creation, not real-world
+  productivity.
+- Broader scientific claims require current-mode vs graph-mode comparisons,
+  semantic completeness reviews and cross-domain replication.

package/releases/0.1.0-alpha.10.md

@@ -0,0 +1,93 @@
+# Mirai Graph v0.1.0-alpha.10
+
+Status: GitHub prerelease prepared; npm publication pending registry
+authentication.
+
+## Theme
+
+Adopter Workflow.
+
+Alpha.10 makes Mirai Graph easier to apply without author-side guidance. The
+release turns the current standards, profiles, templates, examples and CLI
+validators into a clearer self-service adoption path.
+
+## Included Scope
+
+### Adopter Journey
+
+- A concise profile-selection guide for developers, researchers, product teams
+  and organization-governance adopters.
+- A runnable path from starter template to validated package.
+- A single practical workflow:
+
+```text
+choose profile -> copy starter -> fill graph package -> validate -> generate report -> launch work -> record evidence -> run feedback/kaizen
+```
+
+### CLI Usability
+
+- `mirai-graph choose-profile` for role/profile/starter selection.
+- `mirai-graph adopter plan <role-or-profile>` for next-command guidance.
+- `mirai-graph adopter report <template-dir>` for a readable starter report.
+- `mirai-graph release state` for non-secret release-state checks across the
+  package version, git tag, GitHub Release, npm registry and npm auth boundary.
+- `validate:adopter-workflow` for command-level regression checks.
+- `validate:release-state` for pre-tag release-state report regression checks.
+- `mirai-graph release state --require-github-release` for post-GitHub-Release
+  verification.
+- Import/export helper skeletons remain a follow-up unless they directly
+  support the adopter happy path.
+
+### Adoption Evidence
+
+- Clearer organization-governance validation report.
+- Updated public-safe adopter examples.
+- Research evidence notes that distinguish synthetic evidence, pilot evidence
+  and scientific proof boundaries.
+
+## Out Of Scope
+
+- Runtime autonomy.
+- Production execution.
+- Automatic canonical updates from evidence, feedback or proposals.
+- Private SIMAI/Larena/skill-federation payloads.
+- Broad scientific proof claims.
+
+## Done
+
+- A new adopter can pick a profile and run a complete local validation path.
+- The CLI has a documented happy path for the starter templates.
+- Validation reports are readable enough to support review without inspecting
+  raw JSON first.
+- Organization-governance adoption has a stronger public-safe example/report.
+- Release-state reporting separates GitHub Release readiness, npm registry
+  state and npm authentication state.
+- `npm test` and `npm run release:check` pass.
+
+## Release State
+
+- GitHub repository: `zabarov/mirai-graph`.
+- Git tag: `v0.1.0-alpha.10`.
+- GitHub Release: `v0.1.0-alpha.10`.
+- NPM package: pending publication until npm registry authentication is
+  available.
+
+## Validation
+
+```bash
+npm run validate:adopter-workflow
+npm run validate:release-state
+npm run validate:cli-unified
+npm run validate:templates
+npm run release:check
+node packages/cli/mirai-graph.js release state --require-github-release --markdown
+```
+
+## Claim Boundary
+
+This release supports public alpha claims for starter-template adoption,
+role/profile selection, readable local reports and release-state visibility.
+
+It does not claim npm publication, peer-reviewed proof, runtime autonomy,
+production safety or automatic canonical updates from generated context,
+evidence, feedback or proposals.

package/releases/0.1.0-alpha.11.md

@@ -0,0 +1,114 @@
+# Mirai Graph v0.1.0-alpha.11
+
+Status: release candidate prepared in repository; tag, GitHub Release and npm
+publish require separate release execution.
+
+## Theme
+
+Instrumentation Layer.
+
+Alpha.11 prepares Mirai Graph to model not only governed process transitions,
+but the instruments used to steer them: development cockpit signals, feature
+implementation traceability and multi-source quality feedback.
+
+It also adds a role-oriented adopter kit that connects starter templates, CLI
+commands, validation checks and public-safety boundaries into a single entry
+point for external evaluators.
+
+The current alpha.11 evidence index is
+`docs/research/evidence-package-v0.3.md`, which connects synthetic benchmarks,
+instrumentation artifacts, public-safe pilots and claim boundaries.
+
+## Included Scope
+
+### Development Cockpit
+
+- New standard: `standard/development-cockpit.md`.
+- New schema: `schemas/development-cockpit.schema.json`.
+- New result validator mode: `development-cockpit`.
+- Synthetic report in `examples/instrumentation-layer-minimal`.
+
+The cockpit is an instrument panel. It can recommend a bounded next action, but
+it cannot authorize execution, acceptance, release or canonical graph update.
+
+### Feature Implementation Traceability
+
+- New standard: `standard/feature-implementation-traceability.md`.
+- New schema: `schemas/feature-implementation-traceability.schema.json`.
+- New result validator mode: `feature-implementation-traceability`.
+
+The traceability layer connects feature intent to implementation references,
+tests, review, documentation and evidence. It keeps `specified`, `mapped`,
+`implemented`, `tested`, `reviewed`, `accepted` and `released` separate.
+
+### Multi-Source Quality Feedback
+
+- New standard: `standard/multi-source-quality-feedback.md`.
+- New schema: `schemas/multi-source-quality-feedback.schema.json`.
+- New result validator mode: `multi-source-quality-feedback`.
+
+The feedback layer combines tests, validators, cockpit signals, traceability,
+human review and runtime observations into classified findings and transition
+routes. Blocking findings stop the transitions they block.
+
+### Synthetic Example
+
+- New package: `examples/instrumentation-layer-minimal`.
+- New npm checks:
+  - `validate:development-cockpit`;
+  - `validate:feature-implementation-traceability`;
+  - `validate:multi-source-quality-feedback`;
+  - `validate:instrumentation-layer`;
+  - `validate:instrumentation-report`;
+  - `test:instrumentation-layer-negative`.
+
+### Readable Reports And Playground
+
+- `mirai-graph report instrumentation examples/instrumentation-layer-minimal`
+  produces a readable instrumentation report.
+- `docs/adoption/adopter-kit.md` gives developers, researchers, AI product
+  teams and organization adopters a one-hour and one-day adoption path.
+- `docs/research/evidence-package-v0.3.md` summarizes public evidence maturity,
+  pilot coverage, current measured signals and reproducibility commands.
+- The deterministic playground now includes:
+
+```text
+seed -> graph -> context -> launch -> transition explanation -> cockpit -> traceability -> multi-source feedback -> evidence -> kaizen -> baseline comparison
+```
+
+### Negative Fixtures
+
+Alpha.11 fails closed on these instrumentation mistakes:
+
+- cockpit next action without required gates;
+- feature implementation mapping without evidence;
+- accepted transition feedback while a blocking finding exists;
+- process improvement without Kaizen route.
+
+## Out Of Scope
+
+- Runtime autonomy.
+- Production execution.
+- Automatic canonical updates from evidence, feedback, cockpit metrics or
+  proposals.
+- Private pilot payloads or private runtime traces.
+- Peer-reviewed scientific proof.
+
+## Validation
+
+```bash
+npm run validate:instrumentation-layer
+npm run validate:instrumentation-report
+npm run test:instrumentation-layer-negative
+npm test
+npm run release:check
+```
+
+## Claim Boundary
+
+This layer supports public alpha claims for observable process steering and
+reproducible instrumentation artifacts.
+
+It does not claim that synthetic cockpit scores predict real production
+outcomes, that tests are acceptance, or that evidence/proposals authorize
+canonical updates.

package/releases/0.1.0-alpha.2.md

@@ -0,0 +1,37 @@
+# Mirai Graph 0.1.0-alpha.2
+
+Release type: context selection and profile documentation alpha
+
+## Summary
+
+This release improves the alpha context-pack generator and documents the first
+project-management profile lessons from independent implementation pilot 001.
+
+## Added
+
+- Token matching and one-hop relation expansion for context-pack generation.
+- Updated generated context-pack artifacts.
+- Project-management profile documentation.
+- Pilot report and adoption guide wording updated to reflect alpha context
+  selection instead of full-graph-only context generation.
+
+## Validation
+
+Run:
+
+```bash
+npm run release:check
+```
+
+Expected:
+
+- all existing package, seed and profile validation checks pass;
+- context generation succeeds;
+- synthetic benchmark remains reproducible;
+- negative fixture fails as expected.
+
+## Important Limitations
+
+- Context selection is heuristic.
+- Selection explanations are not yet detailed enough for semantic review.
+- Semantic completeness must still be reviewed separately.

package/releases/0.1.0-alpha.3.md

@@ -0,0 +1,61 @@
+# Mirai Graph 0.1.0-alpha.3
+
+Release type: profile conformance, semantic review and release-process alpha
+
+## Summary
+
+This release strengthens Mirai Graph as a public research-engineering package.
+It adds a second independent implementation pilot, executable profile
+conformance checks, semantic-completeness review artifacts and a public release
+process.
+
+## Added
+
+- Independent implementation pilot 002 for a synthetic software specification
+  workflow.
+- Software-specification profile documentation.
+- Profile conformance fixture guide.
+- Validator checks for:
+  - relation id consistency with source, type and target;
+  - profile object-kind conformance;
+  - profile relation-type conformance.
+- Negative fixtures for profile and relation-id failures.
+- Semantic-completeness review artifacts for:
+  - synthetic benchmark context pack;
+  - software-specification pilot context pack.
+- Safety-context inclusion policy for context-pack generation.
+- Public release process and GitHub Release notes policy.
+
+## Validation
+
+Run:
+
+```bash
+npm run release:check
+```
+
+Expected:
+
+- package, seed, profile and pilot validation passes;
+- context-pack generation succeeds;
+- readiness score remains reproducible;
+- synthetic benchmark remains reproducible;
+- negative fixtures fail as expected;
+- whitespace check passes.
+
+## Evidence Notes
+
+- Pilot 002 supports the limited claim that a valid Level 1 Mirai Graph package
+  can be created for a small synthetic software specification.
+- Semantic review of pilot 002 improved from `13/16` to `15/16` after
+  safety-sensitive context inclusion.
+- The synthetic benchmark semantic review records `15/16`.
+
+## Important Limitations
+
+- Evidence remains synthetic and public-safe.
+- This release does not prove real-world productivity improvement.
+- Context-pack selection still lacks per-object explanations and relevance
+  scores.
+- Semantic review artifacts are maintained review records, not automated
+  consensus or peer review.