mirror of
https://github.com/PR0M3TH3AN/TORCH.git
synced 2026-11-03 03:11:57 +00:00
Align lock roster with scheduler prompts
This commit is contained in:
1 parent
c7ce9dbbd0
commit
75094a4520
6 files changed
+162
-19
No files matched your search
+12
-1
@@ -9,7 +9,7 @@ TORCH is a decentralized task-locking protocol for multi-agent software developm
|
||||
node src/nostr-lock.mjs check --cadence daily
|
||||
|
||||
# Claim a task
|
||||
AGENT_PLATFORM=codex node src/nostr-lock.mjs lock --agent documentation-agent --cadence daily
|
||||
AGENT_PLATFORM=codex node src/nostr-lock.mjs lock --agent docs-agent --cadence daily
|
||||
|
||||
# List all active locks
|
||||
node src/nostr-lock.mjs list
|
||||
@@ -35,6 +35,17 @@ node src/nostr-lock.mjs list
|
||||
- `NOSTR_LOCK_WEEKLY_ROSTER`
|
||||
- `AGENT_PLATFORM`
|
||||
|
||||
## Roster precedence
|
||||
|
||||
The lock CLI resolves roster names in this order:
|
||||
|
||||
1. `NOSTR_LOCK_DAILY_ROSTER` / `NOSTR_LOCK_WEEKLY_ROSTER` (comma-separated env overrides).
|
||||
2. `src/prompts/roster.json` (`daily` / `weekly` canonical scheduler roster).
|
||||
3. Built-in fallback roster (used only if `src/prompts/roster.json` is unreadable).
|
||||
|
||||
`lock --agent` validates names against the resolved cadence roster, and `check`/`list` report lock events whose agent names do not match scheduler roster entries exactly.
|
||||
|
||||
|
||||
## Exit codes
|
||||
|
||||
- `0`: success
|
||||
|
||||
Reference in new issue
Block a user