@astrosheep/keiyaku 4.6.3 → 4.6.4
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/build/integrations/marketplace/plugins/keiyaku/skills/keiyaku-akuma/SKILL.md +4 -3
- package/build/integrations/marketplace/plugins/keiyaku/skills/keiyaku-akuma/references/automation.md +2 -2
- package/build/integrations/marketplace/plugins/keiyaku/skills/keiyaku-babysit/SKILL.md +1 -1
- package/build/integrations/marketplace/plugins/keiyaku/skills/keiyaku-bind/SKILL.md +1 -1
- package/build/integrations/marketplace/plugins/keiyaku/skills/keiyaku-workflow/SKILL.md +34 -22
- package/package.json +1 -1
|
@@ -1,8 +1,9 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: keiyaku-akuma
|
|
3
3
|
description: >-
|
|
4
|
-
|
|
5
|
-
|
|
4
|
+
Use when the work involves Akuma or Aku, or when you want other hands on
|
|
5
|
+
it: delegating a job, or fanning out research, checks, or other parallel
|
|
6
|
+
work.
|
|
6
7
|
---
|
|
7
8
|
|
|
8
9
|
# Keiyaku Akuma
|
|
@@ -22,7 +23,7 @@ waiting for the first answer. Use explicit `--wait <duration>` when this
|
|
|
22
23
|
invocation should block while observing that initial work. `--wait` only bounds
|
|
23
24
|
this command; it never stops the Akuma. Read `call --help` for flag syntax,
|
|
24
25
|
defaults, and action vocabulary.
|
|
25
|
-
|
|
26
|
+
To hand a Contract role to an Akuma, use the grant table in `keiyaku-workflow`.
|
|
26
27
|
|
|
27
28
|
The selected Akuma name is a reusable worker configuration, not an individual.
|
|
28
29
|
Calling it again creates an independent Akuma. Use different names for
|
package/build/integrations/marketplace/plugins/keiyaku/skills/keiyaku-akuma/references/automation.md
CHANGED
|
@@ -46,8 +46,8 @@ skeptics to break the finalists, and generate replacements only for the
|
|
|
46
46
|
identified weaknesses. Bound rounds and cost; "keep improving" is not a useful
|
|
47
47
|
stop condition.
|
|
48
48
|
|
|
49
|
-
|
|
50
|
-
|
|
49
|
+
Blind comparisons and adversarial checks need separate contexts. Create
|
|
50
|
+
separate Akuma for them. Reuse an identity for follow-up
|
|
51
51
|
investigation, not as a supposedly fresh judge of its own earlier answer.
|
|
52
52
|
|
|
53
53
|
## Public Entry And A Single Structured Turn
|
|
@@ -52,7 +52,7 @@ does not move without you.
|
|
|
52
52
|
| Observed shape | First response |
|
|
53
53
|
| --- | --- |
|
|
54
54
|
| Silent wedge: initial answer empty and worktree clean | Inspect status and history, then send one steering `tell`. If the worker remains unresponsive, `kill` and call a new Akuma; an empty answer alone is not proof the Contract failed. |
|
|
55
|
-
| Verdict record refused with `not-allowed` | Read the worker's analysis in history
|
|
55
|
+
| Verdict record refused with `not-allowed` | Read the worker's analysis in history. Record the verdict yourself if you did not deliver the candidate, or call a new Reviewer with the grant from `keiyaku-workflow` and have it inspect current work and record a fresh verdict. The refused request wrote no Contract testimony. |
|
|
56
56
|
| Review stale after changed candidate tender | Normal content-currentness result. Give the same Reviewer the changed diff and current terms with `tell`; have it re-examine and record current testimony. A target move alone does not stale review. |
|
|
57
57
|
| Target moved under the appointed worktree | Have the Deliverer inspect target movement and merge the target branch (main when selected) in that worktree when required; resolve conflicts there, then audit again. Do not resolve against a stale integration preview. |
|
|
58
58
|
| Typed refusal names its rule | Fix the named input or physical condition, then retry from a fresh observation. Do not repeat the same request blindly. |
|
|
@@ -205,7 +205,7 @@ waiting, the stated prerequisites remain; do not bind a duplicate Contract.
|
|
|
205
205
|
|
|
206
206
|
The holder now owns the lifecycle:
|
|
207
207
|
|
|
208
|
-
1. Start the work directly or delegate Tasks, Arc chapters, Akumas, or
|
|
208
|
+
1. Start the work directly or delegate Tasks, Arc chapters, Akumas, or Contract roles.
|
|
209
209
|
2. Run independent work in parallel and let it converge on the one acceptance
|
|
210
210
|
boundary.
|
|
211
211
|
3. Prepare and deliver the candidate.
|
|
@@ -38,13 +38,26 @@ to create parallel work.
|
|
|
38
38
|
Use `after` only when one `kei` requires another to be accepted first. Ordinary
|
|
39
39
|
overlap is not a dependency.
|
|
40
40
|
|
|
41
|
-
## 3.
|
|
41
|
+
## 3. Roles
|
|
42
42
|
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
43
|
+
A `kei` has three roles. They are responsibilities, not people, and one agent
|
|
44
|
+
may fill more than one of them, with one exception below.
|
|
45
|
+
|
|
46
|
+
- **Holder:** exactly one per `kei`. Owns the fulfillment loop and acceptance
|
|
47
|
+
until the Contract is accepted or abandoned. Handing work to others never
|
|
48
|
+
transfers this responsibility.
|
|
49
|
+
- **Deliverer:** produces the candidate in the appointed worktree and tenders
|
|
50
|
+
it with `deliver`.
|
|
51
|
+
- **Reviewer:** judges the complete Contract against its acceptance conditions
|
|
52
|
+
and records the verdict with `review`.
|
|
53
|
+
|
|
54
|
+
Review is independent when the Reviewer did not deliver the candidate under
|
|
55
|
+
review. That is the whole requirement. The holder may review its own `kei`; a
|
|
56
|
+
fresh Akuma is not what makes review independent. Keiyaku does not check who
|
|
57
|
+
reviews, so keeping the Reviewer apart from the Deliverer is the holder's duty.
|
|
58
|
+
|
|
59
|
+
Any role may be filled directly or handed to an Akuma. Hand one over when other
|
|
60
|
+
hands help the work, not to make review count.
|
|
48
61
|
|
|
49
62
|
## 4. Lifecycle
|
|
50
63
|
|
|
@@ -78,31 +91,30 @@ Placement judges declared gates, not the producer's identity. Review does not
|
|
|
78
91
|
replace Verification; audit never requests placement. Read the final receipt
|
|
79
92
|
for stops and reconciliation lag after an admitted act.
|
|
80
93
|
|
|
81
|
-
## 5.
|
|
94
|
+
## 5. Handing A Role To An Akuma
|
|
82
95
|
|
|
83
96
|
This is the one commissioning map. `call --help` owns the exact action
|
|
84
|
-
vocabulary and default set.
|
|
97
|
+
vocabulary and default set. The flagship acting directly needs no grant.
|
|
98
|
+
Birth freezes an Akuma's actions; `--contract` records association, not
|
|
99
|
+
authority.
|
|
85
100
|
|
|
86
|
-
|
|
|
101
|
+
| Role | Grant at birth | Return |
|
|
87
102
|
| --- | --- | --- |
|
|
88
|
-
| Holder |
|
|
89
|
-
| Deliverer | The ordinary baseline
|
|
90
|
-
| Reviewer |
|
|
103
|
+
| Holder | The actions the delegated loop will perform; include `contract.review` when this holder will review. Commission with the `kei`, current Arc when one exists, appointed worktree, and holder duties. | Acceptance or abandonment, with receipts. |
|
|
104
|
+
| Deliverer | The ordinary baseline: every Task mutation, Contract audit and delivery, and Akuma management. `keiyaku -C <repo> call worker --alias @deliverer --contract <kei/...> --workdir <appointed-path> -` | The delivery receipt. |
|
|
105
|
+
| Reviewer | `--allowed contract.review`: `keiyaku -C <repo> call review-akuma --alias @reviewer --contract <kei/...> --workdir <appointed-path> --allowed contract.review -` | The verdict receipt. Without the grant, `not-allowed` refuses and no verdict is recorded. |
|
|
91
106
|
|
|
92
|
-
An Archetype's explicit allowed set replaces the ordinary baseline
|
|
107
|
+
An Archetype's explicit allowed set replaces the ordinary baseline; check
|
|
93
108
|
`status` for effective actions. `tell` and `fork` cannot add a grant to a live
|
|
94
|
-
Akuma
|
|
95
|
-
parent's actions.
|
|
96
|
-
|
|
97
|
-
## 6. Delegate the Work
|
|
109
|
+
Akuma, so call a fresh one with the grant. Nested calls cannot exceed their
|
|
110
|
+
direct parent's actions.
|
|
98
111
|
|
|
99
112
|
Commission with a clear objective, current Arc when one exists, appointed
|
|
100
|
-
worktree, and expected result.
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
command help for exact syntax.
|
|
113
|
+
worktree, and expected result. Never ask the Akuma that delivered a candidate
|
|
114
|
+
to review it. Use `keiyaku-akuma` for invocation and observation, and command
|
|
115
|
+
help for exact syntax.
|
|
104
116
|
|
|
105
|
-
##
|
|
117
|
+
## 6. Decide What Happens Next
|
|
106
118
|
|
|
107
119
|
The holder checks candidate, verification, review, prerequisites, and gates.
|
|
108
120
|
|