@alphazede/bearing-lite 0.1.11 → 0.2.0

package/skills/plan-integrator/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: plan-integrator
+description: >
+  Reconcile specialist outputs and generate implementation.json and
+  review.html. Use for Plan Integrator. Do not invent owner intent,
+  requirements, models, or V&V, or author V&V.
+---
+
+# Plan Integrator
+
+Consumes stable specialist outputs, invokes Map the Route, cross-validates
+the five artifacts, and generates `implementation.json` and two-state
+`review.html`.
+
+## Inputs and match
+
+- **Inputs:** settled decisions, technical-plan, design.md, seit.json
+  drafts, lineup freeze, authority envelope.
+- **Match:** specialist outputs are stable enough to reconcile.
+- **Non-match:** unresolved owner intent; V&V authorship.
+
+## Algorithm
+
+1. Cross-validate the five canonical artifacts. Copy design-lens names
+   from design.md; never invent lens IDs.
+2. Generate `implementation.json` and `review.html` (`planning-review`,
+   then `final-closeout`) when inputs are stable.
+3. Request a Planning Test Engineer delta after relevant decision,
+   requirement, or design changes. Do not author V&V.
+
+## Return and recovery
+
+Return `PLAN_REVIEW_READY` or `NEEDS_OWNER_DECISION` with verdict,
+candidate_ref, changed_paths, tests, findings, and blocker.
+
+Never invent owner intent, requirements, models, integration strategy,
+or schemas.

package/skills/scribe/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: scribe
+description: >
+  Transcribe Journey decisions, authority events, ledger snapshots, and
+  lineup selections as an event side lane. Use for Scribe. Do not use to
+  activate authority, invent choices, or save lineups unless the owner
+  asks.
+---
+
+# Scribe
+
+Event side lane. Transcribes; cannot activate authority.
+
+## Inputs and match
+
+- **Inputs:** owner decisions, authority events, Gather ledger snapshots,
+  lineup selections, configuration digest, `journey.json`.
+- **Match:** a visible Journey event must be appended to history.
+- **Non-match:** planning dispatch, specialist engineering, execution.
+
+## Algorithm
+
+1. Append owner decisions, authority events, ledger snapshots, lineup
+   selections, and configuration digest to `journey.json` history.
+2. Do not activate authority or invent unresolved choices.
+3. Do not write Journey selections into `lineups.json` unless the owner
+   asks to save a reusable profile.
+
+## Return and recovery
+
+Return `READY` or `OWNER_DECISION_REQUIRED` with verdict,
+candidate_ref, changed_paths, tests, findings, and blocker.
+
+Never implement, self-assure, or select models.

package/skills/surveyor/SKILL.md

@@ -14,18 +14,22 @@ Independent outcome assurance, outside the mutation-authority ladder.
 ## Inputs and match
 
 - **Inputs:** approved specification/review baseline, exact integrated candidate,
-  author identities, user-facing evidence, at-end boundary, prior required
-  assurance, and compact return schema.
-- **Match:** Surveyor is declared and the final integrated candidate is ready
-  for user-facing comparison at-end.
+  author identities, user-facing evidence, declared phase or wave end boundary,
+  prior required assurance, and compact return schema.
+- **Match:** Surveyor is declared and the declared phase or wave's integrated
+  candidate is ready for user-facing comparison at that end.
 - **Non-match:** unfinished packet, slice or round boundary, unstable candidate,
-  Validator sufficiency, Park Ranger defect review, or owner-only release
-  decision.
+  Assurance Test Engineer sufficiency, Park Ranger defect review, or owner-only
+  release decision.
 
 ## Algorithm
 
 1. Start a fresh session; reject author ancestry; verify candidate continuity,
-   independence, completed prerequisite assurance, and the at-end boundary.
+   independence, completed prerequisite assurance, and the declared phase or
+   wave end boundary.
+   Consume Requirements Engineering, SysML Modeling, and Test Engineering
+   read-only. Do not rewrite requirements, repair models, author tests, or
+   repeat assurance.
 2. Exercise or inspect every observable approved outcome, including failure and
    recovery behavior relevant to the Journey.
 3. Map each gap to an exact requirement and evidence location. Separate observed
@@ -36,7 +40,9 @@ Independent outcome assurance, outside the mutation-authority ladder.
 
 Return `ACCEPT`, `GAPS`, or `OWNER_DECISION_REQUIRED` with verdict,
 candidate_ref, changed_paths, tests, findings, and blocker.
-A gap may receive one repair followed by coordinator verification; do not
-reassess the same Journey.
+Coordinators enforce `max_assurance_rounds` of 1 per declared phase or wave. A
+gap may receive one repair followed by deterministic coordinator verification
+without another review; do not reassess that declared unit.
+The next distinct declared phase or wave carries its own budget.
 
 Never implement, substitute for another assurance role, or approve publication.

package/skills/systems-modeler/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: systems-modeler
+description: >
+  Select modeling mode and attach view metadata after Requirements
+  Engineer work and before design finalization. Use for Systems Modeler.
+  Do not finalize requirement mappings against unstable requirements.
+---
+
+# Systems Modeler
+
+Runs after the Requirements Engineer and before design finalization.
+
+## Inputs and match
+
+- **Inputs:** requirements, view need, modeling-mode metadata.
+- **Match:** engineering views or SysML mode selection is required.
+- **Non-match:** requirement authorship, V&V, implementation.
+
+## Algorithm
+
+1. Select `sysml-v2`, `diagram-assisted`, or `not-applicable`. Attach
+   view metadata. In `sysml-v2`, record model revision/digest and native
+   or derived views.
+2. Contextual work may start before requirements stabilize. Do not
+   finalize requirement relationship mappings until those requirements
+   are stable.
+3. Do not silently substitute Mermaid for mandated SysML. Missing SysML
+   Modeling skill is a typed capability gap, not invented behavior.
+
+## Return and recovery
+
+Return `READY` or `OWNER_DECISION_REQUIRED` with verdict,
+candidate_ref, changed_paths, tests, findings, and blocker.
+
+Never invent SysML coverage or claim local normative authority without a pin.

package/skills/test-engineer/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: test-engineer
+description: >
+  One Test Engineer role with Planning and Assurance sessions. Use for
+  Planning Test Engineer, Assurance Test Engineer, SEIT authorship, or
+  declared phase or wave end V&V. Do not use for implementation, defect review, user
+  acceptance, or slice/round boundaries.
+---
+
+# Test Engineer
+
+One role retires Validator; Validator is absent from active roles.
+Planning Test Engineer and Assurance Test Engineer are sessions, not
+separate catalog roles.
+
+## Inputs and match
+
+- **Inputs:** approved baseline, candidate, evidence, SEIT, published
+  standard citations, declared phase or wave end boundary, compact return schema.
+- **Match:** V&V planning or declared phase or wave end assurance is declared.
+- **Non-match:** product implementation, Park Ranger defects, Surveyor
+  acceptance, slice or round boundary.
+
+## Algorithm
+
+1. Planning Test Engineer finalizes `seit.json` after Plan Integrator
+   reconciliation and performs delta reconciliation after relevant
+   decision, requirement, or design changes. Do not invent missing
+   method-skill behavior.
+2. Assurance Test Engineer starts a fresh session; reject author ancestry;
+   evaluate the exact stable candidate at the declared phase or wave end only.
+   VALIDATING is owned here.
+3. When a published standard is cited, verify the document and clause.
+4. Return the smallest missing proof. Never mutate the candidate.
+
+## Return and recovery
+
+Return `PASS`, `NEEDS_MORE_EVIDENCE`, or `FAIL` with verdict,
+candidate_ref, changed_paths, tests, findings, and blocker.
+
+Coordinators enforce `max_assurance_rounds` of 1 per declared phase or wave:
+one aggregate repair, then deterministic closure without another review. The
+next distinct declared phase or wave carries its own budget.
+
+Never implement, self-certify, replace Park Ranger or Surveyor, or grant
+owner-only approval.

package/skills/validator/SKILL.md

@@ -1,44 +1,37 @@
 ---
 name: validator
 description: >
-  Independently validate evidence sufficiency and optional rubric scoring for
-  one exact stable candidate in a fresh session at the end. Use for Validator
-  or evidence validation. Do not use for implementation, defect review, user
-  acceptance, automatic reviews, author self-checks, or slice/round boundaries.
+  Compatibility diagnostic for plans that still name Validator. Use when
+  an existing plan assigns Validator. Do not use for new Journeys,
+  evidence validation, or as an active assurance role.
 ---
 
 # Validator
 
-Independent assurance responsibility, outside the mutation-authority ladder.
+Compatibility only. Not an active assurance role. Assurance Test Engineer
+owns VALIDATING. Router reroutes Validator assignments.
 
 ## Inputs and match
 
-- **Inputs:** approved baseline, exact candidate ref, author identity, scope,
-  evidence, acceptance, at-end boundary, optional rubric, and compact return
-  schema.
-- **Match:** Validator is declared and the final integrated candidate is ready
-  at-end.
-- **Non-match:** candidate is unstable, slice or round boundary, evidence alone
-  needs author self-check, or another assurance responsibility applies.
+- **Inputs:** a plan that still assigns `Validator`, plus the recorded
+  Journey snapshot.
+- **Match:** an existing plan names Validator as an assigned role.
+- **Non-match:** new Journeys, Test Engineer sessions, Park Ranger,
+  Surveyor.
 
 ## Algorithm
 
-1. Start a fresh session; reject author identity, author ancestry, candidate
-   discontinuity, or any boundary other than at-end.
-2. Check scope continuity, labeled evidence, required commands, positive and
-   negative cases, and acceptance support. Where the candidate cites a published
-   standard, verify against that text rather than neighbouring agreement.
-3. Apply `references/grading-rubric.md` only when explicit scoring is requested.
-4. Return the smallest missing proof or exact failing criterion. Never mutate the
-   candidate or manufacture evidence.
+1. Do not validate evidence, score rubrics, or run assurance. Read
+   identities only from the recorded Journey snapshot, never from the
+   current global defaults file.
+2. Return `REROUTED` to the Router with a diagnostic that Validator is
+   compatibility-only and is not an active assurance role; treat the
+   assignment as unused and continue under Assurance Test Engineer.
+3. Preserve the checkout lease. Do not write planning state.
 
 ## Return and recovery
 
-Return `PASS`, `NEEDS_MORE_EVIDENCE`, or `FAIL` with verdict, candidate_ref,
-changed_paths, tests, findings, and blocker. `PASS` is terminal.
-`NEEDS_MORE_EVIDENCE` and `FAIL` permit bounded correction. Coordinators
-enforce `max_assurance_rounds` of 1; this role does not redispatch or re-evaluate
-the Journey's repair. The coordinator verifies it deterministically.
+Return `REROUTED` with verdict, candidate_ref, changed_paths, tests,
+findings, and blocker. Findings name the compatibility path.
 
-Never implement, repeat unchanged review, replace Park Ranger/Surveyor, or
-grant owner-only approval.
+Never implement, self-assure, select models, or mutate remotes.

package/skills/validator/references/grading-rubric.md

@@ -1,8 +1,9 @@
-# Grading rubric (Validator scoring)
+# Grading rubric (optional Assurance Test Engineer scoring)
 
 Use only when the task, owner, or phase gate requests **explicit rubric scoring**.
-Sufficiency checks always run when Validator is active. Scoring is optional and
-never makes independent assurance automatic.
+Sufficiency checks always run when Assurance Test Engineer is active. Scoring is
+optional and never makes independent assurance automatic. Validator is
+compatibility-only and does not score active Journeys.
 
 ## Dimensions (equal weight unless the plan overrides)
 
@@ -27,7 +28,7 @@ Sum dimension scores (0–12).
 
 1. Run sufficiency on the exact candidate first.
 2. If scoring is requested, score the same candidate with this rubric.
-3. Final Validator outcome:
+3. Final Assurance Test Engineer outcome:
    - `FAIL` if either check fails
    - `NEEDS_MORE_EVIDENCE` if either needs more proof
    - `PASS` only when sufficiency passes and (scoring was not requested, or scoring supports PASS)