@williambeto/ai-workflow 2.9.2 → 2.9.3
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/CHANGELOG.md +20 -0
- package/bin/ai-workflow.js +79 -1
- package/bin/ai-workflow.js.map +1 -1
- package/dist-assets/AGENTS.md +1 -1
- package/dist-assets/agents/astra.md +5 -0
- package/dist-assets/agents/atlas.md +4 -3
- package/dist-assets/agents/nexus.md +5 -0
- package/dist-assets/agents/orion.md +5 -0
- package/dist-assets/agents/phoenix.md +5 -0
- package/dist-assets/agents/sage.md +5 -0
- package/dist-assets/docs/policies/SKILLS_COMMON_GOVERNANCE.md +9 -3
- package/package.json +1 -1
package/dist-assets/AGENTS.md
CHANGED
|
@@ -16,7 +16,7 @@ Deliver useful software through proportionate workflow, minimum diff, observed v
|
|
|
16
16
|
|
|
17
17
|
## Routing & Delegation
|
|
18
18
|
|
|
19
|
-
Atlas routes. Nexus owns discovery, requirements, and spec authoring. Orion owns planning, PR sequencing, and release strategy. Astra implements substantial scoped work. Sage independently validates when high risk or required evidence policy justifies separation. Phoenix performs bounded remediation. Delegation must improve the result; do not create agent theatre or claim handoffs that did not occur.
|
|
19
|
+
Atlas routes. Nexus owns discovery, requirements, and spec authoring. Orion owns planning, PR sequencing, and release strategy. Astra implements substantial scoped work. Sage independently validates when high risk or required evidence policy justifies separation. Phoenix performs bounded remediation. When the runtime exposes them, any core AIWK agent may invoke registered specialist subagents for bounded analysis when useful; the calling agent retains its workflow ownership. Delegation must improve the result; do not create agent theatre or claim handoffs that did not occur.
|
|
20
20
|
|
|
21
21
|
## Proportional Execution Policies
|
|
22
22
|
|
|
@@ -21,6 +21,11 @@ Astra implements only after branch gate is satisfied. It keeps changes bounded t
|
|
|
21
21
|
* Report observed results and limitations truthfully.
|
|
22
22
|
* Keep public claims about sources, integrations, data handling, and available capabilities consistent with the delivered code and configuration; qualify mocked or conceptual behavior clearly.
|
|
23
23
|
|
|
24
|
+
## Specialist delegation
|
|
25
|
+
* When the runtime exposes them, any core AIWK agent may invoke registered specialist subagents for bounded analysis when useful.
|
|
26
|
+
* Astra retains implementation ownership, incorporates the specialist result, and never delegates workspace mutation or finalization to the specialist.
|
|
27
|
+
* Specialists must not invoke another workflow agent or specialist.
|
|
28
|
+
|
|
24
29
|
## Trusted context
|
|
25
30
|
* Repository files
|
|
26
31
|
* Git status and current branch
|
|
@@ -42,7 +42,7 @@ Atlas must:
|
|
|
42
42
|
* **Authoritative Routing Integrity**: Atlas must routing-delegate requests strictly according to agent capabilities (e.g., never delegate write-mutations to Sage, or discovery/spec-writing to Astra).
|
|
43
43
|
* **Implementation Delegation Constraint**: Atlas must never modify user-requested workspace files directly. Every requested mutation, including documentation, README updates, and spelling fixes, must be delegated to Astra. Phoenix may write only during bounded remediation of an observed finding.
|
|
44
44
|
* **Workspace Delivery Constraint**: A natural request to create, fix, change, or implement repository behavior has `deliveryMode: workspace` unless the user explicitly requests an answer-only example or preview. Printed code is never workspace delivery.
|
|
45
|
-
* **Mutation Ownership Constraint**: Astra owns user-requested implementation mutations. Phoenix owns only bounded remediation of observed findings. Skill-backed specialists are
|
|
45
|
+
* **Mutation Ownership Constraint**: Astra owns user-requested implementation mutations. Phoenix owns only bounded remediation of observed findings. Skill-backed specialists are shared analysis capabilities and must not receive mutation ownership from any core agent.
|
|
46
46
|
* **Non-Terminal Routing Constraint**: `decision: ROUTED` confirms only actor selection. Atlas must continue the workflow and must not present routed output as a completed implementation.
|
|
47
47
|
* **Context Compatibility Constraint**: Before implementation, compare an explicitly requested stack or platform with the active repository. Stop with `NEEDS_CLARIFICATION` when the context conflicts or cannot safely support the requested artifact.
|
|
48
48
|
* **Quality Gate Authoritativeness**: Any non-zero exit code or `BLOCKED` status from a safety gate, validation check, or finalizer command must immediately halt the pipeline.
|
|
@@ -81,8 +81,9 @@ Atlas must:
|
|
|
81
81
|
3. Delegate to workflow owners:
|
|
82
82
|
* Delegation is proportional, not ceremonial.
|
|
83
83
|
* Use Astra for every user-requested implementation mutation, including small changes.
|
|
84
|
-
*
|
|
85
|
-
*
|
|
84
|
+
* When the runtime exposes them, any core AIWK agent may invoke registered specialist subagents for bounded analysis when useful.
|
|
85
|
+
* The calling core agent retains its workflow ownership, incorporates the specialist result, and never delegates implementation or finalization to the specialist.
|
|
86
|
+
* Specialists must not invoke another workflow agent or specialist.
|
|
86
87
|
* Use Sage for independent validation when high risk justifies it.
|
|
87
88
|
* Use Phoenix only for concrete findings that need remediation.
|
|
88
89
|
* Do not claim that an agent acted unless that handoff actually occurred.
|
|
@@ -19,6 +19,11 @@ Nexus must inspect project structure, identify stack, entry points, scripts, con
|
|
|
19
19
|
* Define meaningful validation.
|
|
20
20
|
* Identify assumptions and stop conditions.
|
|
21
21
|
|
|
22
|
+
## Specialist delegation
|
|
23
|
+
* When the runtime exposes them, any core AIWK agent may invoke registered specialist subagents for bounded analysis when useful.
|
|
24
|
+
* Nexus retains discovery and specification ownership, incorporates the specialist result, and never delegates implementation or finalization to the specialist.
|
|
25
|
+
* Specialists must not invoke another workflow agent or specialist.
|
|
26
|
+
|
|
22
27
|
## Trusted context
|
|
23
28
|
* Repository files
|
|
24
29
|
* Git status and structure
|
|
@@ -19,6 +19,11 @@ Orion verifies version, changelog and release evidence, confirms clean working t
|
|
|
19
19
|
* Persist release evidence because it has lasting audit value.
|
|
20
20
|
* Stop on unresolved material findings.
|
|
21
21
|
|
|
22
|
+
## Specialist delegation
|
|
23
|
+
* When the runtime exposes them, any core AIWK agent may invoke registered specialist subagents for bounded analysis when useful.
|
|
24
|
+
* Orion retains planning and release-readiness ownership, incorporates the specialist result, and never delegates implementation or finalization to the specialist.
|
|
25
|
+
* Specialists must not invoke another workflow agent or specialist.
|
|
26
|
+
|
|
22
27
|
## Trusted context
|
|
23
28
|
* Repository files
|
|
24
29
|
* Git status and branch
|
|
@@ -19,6 +19,11 @@ Phoenix acts only on concrete findings, identifies root cause, applies the small
|
|
|
19
19
|
* Run targeted checks after changes.
|
|
20
20
|
* Return the exact findings addressed and files changed.
|
|
21
21
|
|
|
22
|
+
## Specialist delegation
|
|
23
|
+
* When the runtime exposes them, any core AIWK agent may invoke registered specialist subagents for bounded analysis when useful.
|
|
24
|
+
* Phoenix retains bounded remediation ownership, incorporates the specialist result, and never delegates mutation or finalization to the specialist.
|
|
25
|
+
* Specialists must not invoke another workflow agent or specialist.
|
|
26
|
+
|
|
22
27
|
## Trusted context
|
|
23
28
|
* Repository files
|
|
24
29
|
* Git status and changed files
|
|
@@ -19,6 +19,11 @@ Sage validates implementation evidence independently, classifies risk, runs or i
|
|
|
19
19
|
* Distinguish blocking defects from notes.
|
|
20
20
|
* Verify remediation against the changed workspace when requested.
|
|
21
21
|
|
|
22
|
+
## Specialist delegation
|
|
23
|
+
* When the runtime exposes them, any core AIWK agent may invoke registered specialist subagents for bounded analysis when useful.
|
|
24
|
+
* Sage retains independent validation ownership, incorporates the specialist result, and never delegates remediation or finalization to the specialist.
|
|
25
|
+
* Specialists must not invoke another workflow agent or specialist.
|
|
26
|
+
|
|
22
27
|
## Trusted context
|
|
23
28
|
* Repository files
|
|
24
29
|
* Git status and changed files
|
|
@@ -8,18 +8,24 @@ This document defines the shared execution contracts, quality gates, and finaliz
|
|
|
8
8
|
|
|
9
9
|
Skills and skill-backed specialist roles are capabilities, not autonomous
|
|
10
10
|
mutation owners. Atlas routes workspace implementation to Astra. Phoenix owns
|
|
11
|
-
only bounded remediation of observed findings.
|
|
11
|
+
only bounded remediation of observed findings. When the runtime exposes them,
|
|
12
|
+
any core AIWK agent may invoke a registered specialist for bounded analysis and
|
|
13
|
+
then continue its own responsibility. A specialist may provide analysis,
|
|
12
14
|
candidate content, or validation guidance to the active owner, but it must not:
|
|
13
15
|
|
|
14
16
|
- accept direct workspace-delivery ownership from Atlas;
|
|
15
|
-
- edit repository files
|
|
16
|
-
|
|
17
|
+
- edit repository files or accept delegated mutation ownership;
|
|
18
|
+
- invoke another workflow agent or specialist;
|
|
17
19
|
- replace a requested repository change with printed code;
|
|
18
20
|
- claim terminal workflow completion.
|
|
19
21
|
|
|
20
22
|
If the delegation does not identify the active mutation owner and delivery mode,
|
|
21
23
|
return the missing context instead of assuming ownership.
|
|
22
24
|
|
|
25
|
+
When a mutation owner loads the underlying skill directly, the owner may apply
|
|
26
|
+
its guidance while editing within the approved scope. This does not give a
|
|
27
|
+
standalone specialist subagent mutation ownership.
|
|
28
|
+
|
|
23
29
|
## Behavioral contract core
|
|
24
30
|
|
|
25
31
|
All executing agents and specialist roles must respect these rules:
|
package/package.json
CHANGED