rhachet-roles-bhuild 0.14.4 → 0.14.5
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.
- package/dist/domain.operations/behavior/init/templates/3.3.1.blueprint.product.v1.guard.heavy +13 -0
- package/dist/domain.operations/behavior/init/templates/3.3.1.blueprint.product.v1.guard.light +13 -0
- package/dist/domain.operations/behavior/init/templates/5.1.execution.phase0_to_phaseN.v1.guard +6 -0
- package/dist/domain.operations/behavior/init/templates/5.2.evaluation.v1.stone +11 -9
- package/dist/domain.operations/behavior/init/templates/5.3.verification.v1.guard +6 -0
- package/dist/domain.operations/behavior/init/templates/5.5.playtest.v1.guard +6 -0
- package/package.json +4 -4
package/dist/domain.operations/behavior/init/templates/3.3.1.blueprint.product.v1.guard.heavy
CHANGED
|
@@ -11,6 +11,19 @@ reviews:
|
|
|
11
11
|
say: |
|
|
12
12
|
try hard to delete before you optimize:
|
|
13
13
|
|
|
14
|
+
## features
|
|
15
|
+
|
|
16
|
+
for each feature in the blueprint, ask:
|
|
17
|
+
- does this feature trace to a requirement in the criteria?
|
|
18
|
+
- did the wisher explicitly ask for this feature?
|
|
19
|
+
- or did we assume it was needed?
|
|
20
|
+
|
|
21
|
+
if a feature has no traceability to vision or criteria:
|
|
22
|
+
1. delete it
|
|
23
|
+
2. or flag it as an open question for the wisher
|
|
24
|
+
|
|
25
|
+
## components
|
|
26
|
+
|
|
14
27
|
for each component, ask:
|
|
15
28
|
- can this be removed entirely?
|
|
16
29
|
- if we deleted this and had to add it back, would we?
|
package/dist/domain.operations/behavior/init/templates/3.3.1.blueprint.product.v1.guard.light
CHANGED
|
@@ -11,6 +11,19 @@ reviews:
|
|
|
11
11
|
say: |
|
|
12
12
|
try hard to delete before you optimize:
|
|
13
13
|
|
|
14
|
+
## features
|
|
15
|
+
|
|
16
|
+
for each feature in the blueprint, ask:
|
|
17
|
+
- does this feature trace to a requirement in the criteria?
|
|
18
|
+
- did the wisher explicitly ask for this feature?
|
|
19
|
+
- or did we assume it was needed?
|
|
20
|
+
|
|
21
|
+
if a feature has no traceability to vision or criteria:
|
|
22
|
+
1. delete it
|
|
23
|
+
2. or flag it as an open question for the wisher
|
|
24
|
+
|
|
25
|
+
## components
|
|
26
|
+
|
|
14
27
|
for each component, ask:
|
|
15
28
|
- can this be removed entirely?
|
|
16
29
|
- if we deleted this and had to add it back, would we?
|
package/dist/domain.operations/behavior/init/templates/5.1.execution.phase0_to_phaseN.v1.guard
CHANGED
|
@@ -1,6 +1,12 @@
|
|
|
1
1
|
# guard for execution stone
|
|
2
2
|
# includes standardized self-review frame
|
|
3
3
|
|
|
4
|
+
artifacts:
|
|
5
|
+
# track execution progress
|
|
6
|
+
- "$route/5.1.execution.phase0_to_phaseN.v1.i1.md"
|
|
7
|
+
# track actual implementation in src/
|
|
8
|
+
- "src/**/*"
|
|
9
|
+
|
|
4
10
|
reviews:
|
|
5
11
|
self:
|
|
6
12
|
# 1. minimalism - yagni
|
|
@@ -3,8 +3,9 @@ evaluate what was implemented against the blueprint
|
|
|
3
3
|
.what = articulate exactly what was implemented, then check for divergences from blueprint.
|
|
4
4
|
|
|
5
5
|
.why = the blueprint declared what the execution would adhere to.
|
|
6
|
-
- divergences
|
|
7
|
-
-
|
|
6
|
+
- divergences are NOT allowed
|
|
7
|
+
- default action is REPAIR — fix implementation to match blueprint
|
|
8
|
+
- if repair is impossible, raise BLOCKER and request human approval
|
|
8
9
|
- this gate prevents silent deviations from approved design
|
|
9
10
|
|
|
10
11
|
---
|
|
@@ -68,20 +69,21 @@ for each section (summary, filediff, codepath, test coverage), compare:
|
|
|
68
69
|
|
|
69
70
|
### divergence resolution
|
|
70
71
|
|
|
71
|
-
for each divergence
|
|
72
|
+
for each divergence:
|
|
72
73
|
|
|
73
|
-
**repair** — fix the implementation to match the blueprint:
|
|
74
|
+
**repair** (default) — fix the implementation to match the blueprint:
|
|
74
75
|
- what needs to change to match blueprint?
|
|
75
76
|
- make the change, then update the "as implemented" section above
|
|
76
77
|
|
|
77
|
-
**
|
|
78
|
-
- why
|
|
79
|
-
-
|
|
80
|
-
-
|
|
78
|
+
**blocker** (only if repair is impossible) — request human approval:
|
|
79
|
+
- why is repair impossible?
|
|
80
|
+
- what constraint prevents adherence to blueprint?
|
|
81
|
+
- run `rhx route.stone.set --as blocked` to declare yourself blocked and request human approval
|
|
82
|
+
- STOP and await human decision before you proceed
|
|
81
83
|
|
|
82
84
|
| divergence | resolution | rationale |
|
|
83
85
|
|------------|------------|-----------|
|
|
84
|
-
| ... | repair/
|
|
86
|
+
| ... | repair/blocker | ... |
|
|
85
87
|
|
|
86
88
|
---
|
|
87
89
|
|
package/package.json
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"name": "rhachet-roles-bhuild",
|
|
3
3
|
"author": "ehmpathy",
|
|
4
4
|
"description": "roles for building resilient systems, via rhachet",
|
|
5
|
-
"version": "0.14.
|
|
5
|
+
"version": "0.14.5",
|
|
6
6
|
"repository": "ehmpathy/rhachet-roles-bhuild",
|
|
7
7
|
"homepage": "https://github.com/ehmpathy/rhachet-roles-bhuild",
|
|
8
8
|
"keywords": [
|
|
@@ -89,11 +89,11 @@
|
|
|
89
89
|
"esbuild-register": "3.6.0",
|
|
90
90
|
"husky": "8.0.3",
|
|
91
91
|
"jest": "30.2.0",
|
|
92
|
-
"rhachet": "1.
|
|
92
|
+
"rhachet": "1.38.0",
|
|
93
93
|
"rhachet-brains-anthropic": "0.4.0",
|
|
94
|
-
"rhachet-roles-bhrain": "0.
|
|
94
|
+
"rhachet-roles-bhrain": "0.23.8",
|
|
95
95
|
"rhachet-roles-bhuild": "link:.",
|
|
96
|
-
"rhachet-roles-ehmpathy": "1.
|
|
96
|
+
"rhachet-roles-ehmpathy": "1.34.9",
|
|
97
97
|
"tsc-alias": "1.8.10",
|
|
98
98
|
"tsx": "4.20.6",
|
|
99
99
|
"typescript": "5.4.5",
|