@evoclock/pi-agentic-driver 0.9.0 → 0.9.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.
- package/.agentic-driver/router.defaults.json +64 -0
- package/LICENSE +11 -8
- package/README.md +94 -29
- package/extensions/attended-authority-guard.ts +1 -1
- package/extensions/code-phage.js +1 -1
- package/extensions/herdr-communication.ts +9 -2
- package/extensions/herdr-dispatch.ts +1 -1
- package/extensions/herdr-lifecycle.ts +5 -4
- package/extensions/linux-microvm.ts +1 -1
- package/extensions/pulse.ts +105 -0
- package/extensions/task-board.ts +1 -1
- package/lib/adapters/diff-scope.mjs +1 -1
- package/lib/adapters/evidence.mjs +1 -1
- package/lib/adapters/narrative.mjs +1 -1
- package/lib/adapters/review-feedback.mjs +1 -1
- package/lib/adapters/visualization.mjs +1 -1
- package/lib/code-phage-core.mjs +1 -1
- package/lib/python_ast_metrics.py +1 -1
- package/lib/typescript_ast_metrics.mjs +1 -1
- package/package.json +17 -3
- package/scripts/aidr_writing_review.js +1 -1
- package/scripts/enforcement/attended_authority_guard.js +1 -1
- package/scripts/enforcement/guest_containment_taxonomy.v1.json +1 -1
- package/scripts/enforcement/herdr_async_dispatch_pi.js +66 -4
- package/scripts/enforcement/herdr_communication_pi.js +55 -19
- package/scripts/enforcement/herdr_lifecycle_pi.js +3 -3
- package/scripts/enforcement/linux_microvm_cutover_pi.js +1 -1
- package/scripts/enforcement/native_tui_context.js +1 -1
- package/scripts/enforcement/pulse_core_pi.js +292 -0
- package/scripts/enforcement/pulse_scheduler_pi.js +1083 -0
- package/scripts/enforcement/router_engine_pi.js +483 -0
- package/scripts/enforcement/router_ranking_pi.js +146 -0
- package/scripts/enforcement/router_replacement_pi.js +98 -0
- package/scripts/enforcement/router_runtime_pi.js +299 -0
- package/scripts/enforcement/router_schemas_pi.js +604 -0
- package/scripts/enforcement/router_store_pi.js +438 -0
- package/scripts/enforcement/task_board_core_pi.js +597 -48
- package/skills/pulse/SKILL.md +39 -0
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
// SPDX-FileCopyrightText: 2026 Julen Gamboa <j.a.r.gamboa@gmail.com>
|
|
2
|
+
// SPDX-License-Identifier: AGPL-3.0-only
|
|
3
|
+
|
|
4
|
+
# Pulse
|
|
5
|
+
|
|
6
|
+
Board Pulse moves authorised Kanban work through available role/model capacity
|
|
7
|
+
with little ceremony. Use this skill when the user asks to "check the board",
|
|
8
|
+
"work through the ready cards", or asks about board scheduling capacity.
|
|
9
|
+
|
|
10
|
+
Board Pulse is capacity scheduling. It is not worker liveness observation —
|
|
11
|
+
that is the separate Herdr `pulse`.
|
|
12
|
+
|
|
13
|
+
## When to use what
|
|
14
|
+
|
|
15
|
+
- "Check the board" → call `agentic_kanban_pulse` with `action: "check"`.
|
|
16
|
+
This is a pure observation: it reports card results, capacity, and what
|
|
17
|
+
could be proposed, and it claims nothing.
|
|
18
|
+
- "Work through the ready cards" → the interactive `run` action (not yet
|
|
19
|
+
implemented; report that it is not available in this rollout step).
|
|
20
|
+
- Enable/disable/configure Pulse → the policy actions (not yet implemented;
|
|
21
|
+
the board-bound automation policy is the only policy store).
|
|
22
|
+
|
|
23
|
+
## Reading a check result
|
|
24
|
+
|
|
25
|
+
The result is a closed scan shape:
|
|
26
|
+
|
|
27
|
+
- `cards[]`: one result per card — `READY_FOR_NEXT`, `BLOCKED`, `STALE`,
|
|
28
|
+
`DENIED`, or `REVIEW_REQUIRED` — with a short human reason. Card IDs and
|
|
29
|
+
hashes stay internal; speak in titles.
|
|
30
|
+
- `capacity[]`: per role/model route — configured ceiling, active claims,
|
|
31
|
+
free slots, and availability (`available`, `full`, `unauthenticated`,
|
|
32
|
+
`unavailable`, `unknown`).
|
|
33
|
+
- `proposedDispatches[]`: what the scheduler would propose next (titles,
|
|
34
|
+
roles, models, placement).
|
|
35
|
+
|
|
36
|
+
Pulse is off unless the board's automation policy enables it. Without it,
|
|
37
|
+
every card reports `REVIEW_REQUIRED` and nothing is proposed. A check never
|
|
38
|
+
claims work, never spawns workers, and never completes cards — completion
|
|
39
|
+
remains an explicit human board transition.
|