feat(roster): intake RAMZA (planner successor to SPECTRA) as in_construction — Stage 1 + campaign record#433
Merged
Merged
Conversation
…ruction — Stage 1 + campaign record Vivi-pattern succession, Stage 1 only: roster entry (in_construction skips EIIS conformance), roster-health matrix row, CHANGELOG. Presets/routing/cortex untouched until the Stage 2 measurement gates the seat flip; SPECTRA remains the shipped planner and conservative fallback. Campaign record committed under .spectra/plans/spectra-v2/ (committed-artifact discipline — the APIVR digest was lost by not doing this): 3 research dossiers (market plan modes, OSS mechanics + MCP white-space, 2025-26 frontier planning), CURATION.md verdict table (C1-C20, incl. two premise-killing contradictions), GAP-MAP (G-A..G-G), SUCCESSION-BRIEF (name rationale + D1-D8 + staged rollout), REPO-PLAN. Verified: make schema green; eidolons list / roster show ramza render; full bats suite 1447/1447 sequential. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…gates Lite tier (rightsize score 2), complexity 7/12 (extended), 3 hypotheses scored via ramza-score (canary-first-then-scoped-AB wins 79.5 solid; full-matrix-now 62 and ship-and-measure 55 rejected as weak), ramza-lint + ramza-ears-lint clean, confidence 82.5 VALIDATE (human review = this PR), scope declared, criteria frozen (423248b6…), emission gate green. The .state.json is the audit trail; ramza-calibration.jsonl accrues the instrument data from gate one. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…sumer path unblocked) E2E driving 'eidolons init --members ramza' surfaced that strict integrity enforcement blocks consumer installs of metadata-less members even at in_construction. v0.2.0 was cut through the release template (attested), and this records its real manifest values (commit af5f546, tree 80d2410, archive_sha256 6d15577b…). Verified: fresh consumer init installs 10 bin tools; 'eidolons verify' returns 'ramza@0.2.0 verified'; scoped bats 43/43. v0.2.0 also lands the Stage-2 instruments: ramza-adherence (Plan-Phase/Order/ Fidelity composite) and ramza-calibrate + anchors/ (the calibration verb parked since v2.0 Wave 3), suite 76/76 under jq 1.8.1 AND 1.7.1. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Owner
Author
|
Stage-2 preparation landed on this branch (post-review-ready update):
🤖 Generated with Claude Code |
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
1 participant
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.
Summary
Stage 1 of the SPECTRA succession (Vivi-pattern, succession-by-demotion):
roster/index.yamlasin_construction(planner class,Rynaro/Ramza@ v0.1.0, commita9cc640). SPECTRA staysshippedas the conservative fallback — presets, routing, and cortex are deliberately untouched until the Stage 2 measurement gates the seat flip (SUCCESSION-BRIEF §staged rollout).ramza(in_construction ⇒ EIIS conformance skipped, per existing semantics)..spectra/plans/spectra-v2/— committed-artifact discipline (the APIVR overhaul digest was lost by living only in a session): 3 research dossiers (market plan modes; OSS mechanics + MCP white-space scan; 2025-26 frontier planning science),CURATION.md(C1–C20 verdicts incl. two premise-killing contradictions),GAP-MAP.md(G-A…G-G),SUCCESSION-BRIEF.md(name rationale, D1–D8, staged rollout),REPO-PLAN.md.What RAMZA is
The mechanized planner: every gate SPECTRA's prose asked the model to self-police is code in
bin/(bash 3.2 + jq) — right-sizing tier gate, phase state machine (skips-with-reason, refine cap, maker≠checker), rubric arithmetic with calibration logging, EARS criteria lint, SHA-256 criteria freeze with hash-chained amend, plan-vs-diff drift detection (the check no vendor or MCP server ships), and an emission gate. 67 behavioral bats tests green; EIIS 1.4 installer with a post-install every-file assertion (the Vivi v1.0.0 missing-skill lesson).Test plan
make schemagreen (roster + schemas)eidolons list/eidolons roster show ramzarender correctly--forcesmoke installs verified; shellcheck clean (v0.10.0)Rynaro/Ramzapublic, main pushed, tagv0.1.0→a9cc640Follow-ups (measurement-gated, not this PR)
eidolons canary ramzamissions (incl. new rightsize-gate + drift-tamper) and adherence A/B vs SPECTRA 4.11 on the H-WIN instrumenteidolon-release-template.yml+ Roster Intake integrity metadatarouting.yamldefault_for_class: plannerflip + preset/cortex reseat (SPECTRA → named-dispatch fallback)🤖 Generated with Claude Code