@alphazede/bearing-lite 0.2.0 → 0.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -23,9 +23,18 @@ the five artifacts, and generates `implementation.json` and two-state
23
23
 
24
24
  1. Cross-validate the five canonical artifacts. Copy design-lens names
25
25
  from design.md; never invent lens IDs.
26
- 2. Generate `implementation.json` and `review.html` (`planning-review`,
26
+ 2. For `journey_type: specification`, default an Expedition wave to scaffold →
27
+ author from the gated register → Test Engineer verification cases → bind to the host
28
+ → readback of the bound revision and digest from the host → Park
29
+ Ranger with both named in the review request → owner decision. A deviation
30
+ is a planning-review finding.
31
+ 3. Generate `implementation.json` and `review.html` (`planning-review`,
27
32
  then `final-closeout`) when inputs are stable.
28
- 3. Request a Planning Test Engineer delta after relevant decision,
33
+ 4. Classify every slice `work_class: light` or `judgement` with a
34
+ `work_class_reason`, using the five criteria in `skills/light-implementer`.
35
+ Light slices carry the Light Implementer role and at least one
36
+ `command_id`; the freeze rejects any other light slice.
37
+ 5. Request a Planning Test Engineer delta after relevant decision,
29
38
  requirement, or design changes. Do not author V&V.
30
39
 
31
40
  ## Return and recovery
@@ -0,0 +1,57 @@
1
+ ---
2
+ name: requirements-engineer
3
+ description: >
4
+ One Requirements Engineer role, planning stage only. Use for the
5
+ requirement register quality gate after Gather Supplies and before the
6
+ Systems Modeler finalizes mappings. Do not use inside an Expedition wave,
7
+ or for V&V, SysML modeling, implementation, defect review, or publication.
8
+ ---
9
+
10
+ # Requirements Engineer
11
+
12
+ One role, one planning session. It owns requirement quality: every statement
13
+ is precise, measurable, traceable, allocated, and verification-ready.
14
+ Requirements are fixed at plan approval; an Expedition wave stores, binds,
15
+ adds verification cases, and publishes approved statements and never re-gates
16
+ them (the Assurance Test Engineer re-verifies at wave end). It never persists
17
+ SDoc, publishes, selects models or lineups, or writes tests.
18
+
19
+ ## Inputs and match
20
+
21
+ - **Inputs:** settled owner decisions, the requirement register as a planning
22
+ artifact (UID, statement, rationale, verification method, allocation: a
23
+ draft `.sdoc`, since Markdown rows are invisible to the lint), the plan's `AC-*`
24
+ and `RISK-*` rows, published-standard citations, the
25
+ `requirements-engineering` method skill, `lint-sdoc.py --profile library`
26
+ output, compact return schema.
27
+ - **Match:** a planning package whose requirement register needs a
28
+ quality-gate verdict before the integrated owner review.
29
+ - **Non-match:** any Expedition wave, design, SEIT, implementation, Park
30
+ Ranger, Surveyor.
31
+
32
+ ## Algorithm
33
+
34
+ 1. Run after Gather Supplies and before the Systems Modeler finalizes
35
+ mappings, on the requirement statements themselves: gate every register
36
+ row's statement, rationale, verification method, and allocation, and the
37
+ `AC-*`/`RISK-*` rows that cite them, against the NASA-adapted checklist;
38
+ reject escape clauses and undefined terms; every row cites its register
39
+ identity or is marked Journey-local.
40
+ 2. Cite the mechanical output (`lint-sdoc.py --profile library` over the
41
+ register: EARS, banned terms, glossary references) and judge only what the
42
+ tool cannot decide. Missing tool output is `NEEDS_MORE_EVIDENCE`.
43
+ 3. When a published standard is cited, verify the document and clause.
44
+ 4. Return the smallest set of failing rows. Never rewrite silently: propose
45
+ the corrected statement and let the author apply it.
46
+
47
+ ## Return and recovery
48
+
49
+ Return `PASS`, `REPAIRABLE_FAILURE`, `NEEDS_MORE_EVIDENCE`, or
50
+ `NEEDS_OWNER_DECISION` with verdict, candidate_ref, changed_paths, per-row
51
+ findings, and blocker. Rerun the gate on each corrected register within Map the
52
+ Route's correction rounds. Exhaustion with fixable rows returns
53
+ `NEEDS_OWNER_DECISION` listing those rows, never silent acceptance. Missing
54
+ `requirements-engineering` method skill is a typed capability gap.
55
+
56
+ Never implement, model, self-certify, persist or publish SDoc, or grant
57
+ owner-only approval.
@@ -22,6 +22,10 @@ Event side lane. Transcribes; cannot activate authority.
22
22
 
23
23
  1. Append owner decisions, authority events, ledger snapshots, lineup
24
24
  selections, and configuration digest to `journey.json` history.
25
+ Follow `../bearing-lite/references/owner-stops.md` for typed owner-stop
26
+ records: preserve question and round-trip IDs, record actual asked/answered
27
+ UTC times and explicit fully blocked intervals, and never infer missing
28
+ times. Automatic resolutions and owner steering are not invented questions.
25
29
  2. Do not activate authority or invent unresolved choices.
26
30
  3. Do not write Journey selections into `lineups.json` unless the owner
27
31
  asks to save a reusable profile.
@@ -15,19 +15,28 @@ Fresh planning node. The Router announces `Setting Our Bearings in <repo>.`
15
15
 
16
16
  - **Inputs:** confirmed repository root, owner-confirmed plan directory, Journey
17
17
  title, visible existing artifacts, repository rules, and return schema.
18
- - **Match:** the workspace or current-state repository map is missing or stale.
18
+ - **Match:** the workspace or repository map is missing or stale.
19
19
  - **Non-match:** both are current and usable by Gather Supplies or Map the Route.
20
20
 
21
21
  ## Algorithm
22
22
 
23
23
  1. Re-read the exact confirmed root and plan directory; never derive a different
24
24
  root, slug, suffix, or sibling workspace.
25
- 2. Preserve every existing artifact and unrelated edit. Resume rather than
26
- replace an existing Journey.
27
- 3. Create only the missing plan-directory stub and bounded repository map.
28
- 4. Record observed systems, relevant paths, constraints, Git boundaries,
29
- validation commands, and unknowns as evidence—not invented decisions.
30
- 5. Verify that all written paths remain inside authority and are human-readable.
25
+ 2. If `workspace.md` exists in the plan directory, verify recorded root and plan
26
+ directory match confirmed inputs; a mismatch returns `BLOCKED`. Run `git
27
+ status --porcelain` scoped to mapped inputs; if unmodified, return
28
+ `WORKSPACE_RESUMED` (1 read, 1 status).
29
+ 3. Bound discovery: depth 2, max 40 paths, max 64 KiB, read-only. Anchors are
30
+ root manifest, task runner, CI entrypoint, top-level instructions, and root
31
+ test configs. Strictly prohibit discovery traversal into repo-relative
32
+ `src/`, `lib/`, `vendor/`, and `docs/`.
33
+ 4. If bounds are exhausted before required anchors are found, return
34
+ `NEEDS_EVIDENCE` naming the missing anchor. Never compose unobserved commands.
35
+ 5. Create missing plan directory or update `workspace.md` in place, preserving
36
+ existing recorded evidence and unrelated edits. Initialize a missing file
37
+ from `templates/workspace.md`. Quote validation commands with source and mark
38
+ `[observed, not run]`. Drop detail before Constraints and Unknowns.
39
+ 6. Verify written paths remain inside authority and return `WORKSPACE_READY`.
31
40
 
32
41
  ## Return and recovery
33
42
 
@@ -0,0 +1,28 @@
1
+ # Workspace Environment: <journey-topic>
2
+
3
+ ## Repository Identity
4
+ - Root: `<repository-root>`
5
+ - Plan directory: `<plan-directory>`
6
+
7
+ ## Mapped Inputs
8
+ - `<relative-path>`: `<what it establishes>`
9
+
10
+ ## Observed Systems
11
+ - `<relative-directory>`: `<subsystem>`
12
+
13
+ ## Constraints and Git Boundaries
14
+ - Branch / Worktree: `<branch>` (clean | dirty)
15
+ - Rules: `<applicable-rules>`
16
+
17
+ ## Validation Commands [observed, not run]
18
+ - Test: `<command>` (source: `<anchor-file>`) [observed, not run]
19
+ - Lint: `<command>` (source: `<anchor-file>`) [observed, not run]
20
+ - Build: `<command>` (source: `<anchor-file>`) [observed, not run]
21
+
22
+ ## Unknowns
23
+ - `<unknown or none observed>`
24
+
25
+ ## Map Freshness
26
+ - Tier 1: Recorded root and plan directory match confirmed inputs.
27
+ - Tier 2: `git status --porcelain` scoped to mapped inputs shows no modifications.
28
+ - Note: Does not detect committed changes postdating this observation.
@@ -27,6 +27,8 @@ separate catalog roles.
27
27
  reconciliation and performs delta reconciliation after relevant
28
28
  decision, requirement, or design changes. Do not invent missing
29
29
  method-skill behavior.
30
+ Expedition in-document verification cases are authored only against the
31
+ approved, planning-gated register.
30
32
  2. Assurance Test Engineer starts a fresh session; reject author ancestry;
31
33
  evaluate the exact stable candidate at the declared phase or wave end only.
32
34
  VALIDATING is owned here.
@@ -1,32 +0,0 @@
1
- # Bearing Lite global defaults
2
-
3
- Store the user-owned copy at
4
- `~/.agents/bearing-lite/default-role-lineup.md`. The Router displays it before
5
- implementation and asks whether it is good for the current Journey. Never fill
6
- agent, model, or reasoning values on the user's behalf.
7
-
8
- ```markdown
9
- review_cadence: at-end
10
-
11
- | Role | Primary agent/harness | Primary model | Primary reasoning | Fallback agent/harness | Fallback model | Fallback reasoning |
12
- | --- | --- | --- | --- | --- | --- | --- |
13
- | Router | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
14
- | Explorer | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
15
- | Crewmate | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
16
- | Test Engineer | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
17
- | Scribe | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
18
- | Plan Integrator | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
19
- | Systems Modeler | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
20
- | Integration Engineer | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
21
- | Park Ranger | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
22
- | Surveyor | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
23
- ```
24
-
25
- Navigator is not a normal lineup role. Existing plans that still assign it use
26
- the Navigator compatibility diagnostic; treat the assignment as unused.
27
- Validator is not a normal lineup role. Existing plans that still assign it use
28
- the Validator compatibility diagnostic; treat the assignment as unused.
29
-
30
- Journey artifacts copy the confirmed values and mark named instances active,
31
- standby, or unused. Only verified primary unavailability activates its approved
32
- fallback. If both are unavailable, return `OWNER_DECISION_REQUIRED`.