Repository navigation
docs: production roadmap & ecosystem architecture - #49
Merged
Merged
Conversation
Plans the path from the current pre-1.0 engine to production, and specifies how plasma integrates with the estate: the agent-honesty trio (somethings-fishy, did-you-actually-do-that), the boj-server cartridge/MCP surface, the Hypatia neurosymbolic scanner (logtalk renderer + autofix backend), and reposystem contractiles (policies as the evaluation engine). Covers engine completeness, hardening/distribution, the formal core as the 1.0 gate, the three stable interchange contracts (FactSet, Evaluation, SARIF) plus a proposed run-record/attestation, and a phased v0.3→v1.0 plan. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JSVSF9HhKUhDrEV4xkMEXq
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
docs/PRODUCTION-ROADMAP.adoc— a planning artifact (requested) for taking plasma from the current pre-1.0 engine to production, and for the attendant estate architecture.Contents
Part 1 — Production readiness (plasma itself)
file-matches-pattern, release facts,consistent-with/decision registries, overlaymodify/override, more actions).plasma.tomlpolicy pinning,.gitignore-aware walking, typed exit-code contractparse_spdx_expr/load_policy_str), property tests, a CI determinism gate, MSRV + benchescargo-deny, published JSON Schemasengine-v0-design.adoc) as the 1.0 gatePart 2 — Attendant architecture
plasmacartridge (mirroring the existingssg-mcptrigger) + a thin MCP server (plasma_check/facts/fix_plan)--format logtalkrenderer +plasma fix/checkas autofix backend/gatePart 3 — Phased plan: v0.4 (integration surfaces + trio contracts) → v0.5 (MCP + boj cartridge + logtalk) → v0.6 (governance) → v0.9 (hardening) → v1.0 (formal parity).
Part 4 — Cross-cutting standards: SemVer + schema versioning, determinism as a CI invariant, frozen interchange contracts, supply chain, observability.
Notes
Documentation only — no code changes; grounded in the repo's own declarations (
boj-build.yml,integrations/*.a2ml,NEUROSYM.a2ml,.hypatia/,contractiles.adoc). Wire formats for the sibling repos are inferred from those declarations; they can be firmed up against the real interfaces if access to did-you-actually-do-that / somethings-fishy / boj-server is available.🤖 Generated with Claude Code
https://claude.ai/code/session_01JSVSF9HhKUhDrEV4xkMEXq
Generated by Claude Code