pi-herdsman 0.36.3 → 0.38.0

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/README.md CHANGED
@@ -122,6 +122,26 @@ See [Coordination](docs/concepts/coordination.md) for the mental model and
122
122
  [Project orchestration](docs/guides/project-orchestration.md) for the Manager
123
123
  workflow.
124
124
 
125
+ ## Project status & roadmap
126
+
127
+ Pi Herdsman is actively evolving. Core orchestration workflows are available today,
128
+ while other areas are being refined or expanded.
129
+
130
+ | Area | Status | What to expect |
131
+ | ------------------------------ | -------------------- | ---------------------------------------------------------------------------------------------------------- |
132
+ | **Lead & Agent orchestration** | ✅ **Core complete** | Background and nested delegation, result handoffs, and peer communication. Ongoing reliability fixes. |
133
+ | **Manager orchestration** | ✨ **Polishing** | Branch-based delegation, supervision, and integration are implemented. Refining recovery and usability. |
134
+ | **Chief coordination** | 🚧 **In progress** | Supervision is available. Repository provisioning and Manager lifecycle orchestration are being developed. |
135
+
136
+ **On the roadmap:** [Coordination profiles](https://github.com/boadij/pi-herdsman/issues/734)
137
+ (replacing the current role-definition terminology),
138
+ [cross-build messaging](https://github.com/boadij/pi-herdsman/issues/688), and
139
+ [portable project state](https://github.com/boadij/pi-herdsman/issues/755).
140
+
141
+ **Early-stage project:** Core features are usable today, but pre-1.0 releases may
142
+ introduce breaking changes as configuration and runtime conventions evolve.
143
+ See the [changelog](CHANGELOG.md) for release changes and migration guidance.
144
+
125
145
  ## Choose your next step
126
146
 
127
147
  | Goal | Start here |
package/SKILL.md CHANGED
@@ -287,7 +287,8 @@ Every assignment gets one bounded objective with:
287
287
 
288
288
  ## Delegation locality
289
289
 
290
- A lead session may delegate to any discovered definition.
290
+ A Lead may delegate to available definitions permitted by its effective
291
+ `agents` field; omission permits all, while an empty list permits none.
291
292
 
292
293
  A delegating agent may delegate only to definitions listed in its effective
293
294
  `agents` field and owns only its direct agents. Agent-started agents are
@@ -536,10 +537,11 @@ Pi Herdsman uses one durable vocabulary:
536
537
  owns their Agents.
537
538
 
538
539
  The `agents` frontmatter field names permitted direct Agent definitions for a
539
- delegating Agent, or the fresh-delegation allowlist for Manager/Chief. For
540
- supervisors it is independent of ordinary `tools`: `tools: []` does not disable
541
- authorized Agent coordination, and an absent or empty list disables fresh
542
- delegation only, not management of existing owned work. A delegation-capable
540
+ delegating Agent, or the fresh-delegation allowlist for a Lead, Manager, or
541
+ Chief. For these roles it is independent of ordinary `tools`: `tools: []` does
542
+ not disable authorized Agent coordination. An empty list disables fresh
543
+ delegation only, not management of existing owned work; omission also disables
544
+ fresh delegation for Manager and Chief, but not for Leads. A delegation-capable
543
545
  managed session remains an Agent at every depth.
544
546
  Every managed agent receives `ask_owner`. A non-empty effective `agents` list
545
547
  is necessary but not sufficient to enable the nine Agent ownership tools: