Compare commits

...
Author SHA1 Message Date
dev-guard b71ff1bab3 docs(cli): show a complete periodic-reminder registration 2026-11-11 20:15:22 +00:00
5 changed files with 62 additions and 4 deletions

No files matched your search

+28
View File
@@ -296,3 +296,31 @@ Unknown: not said yet.
delivery guarantee.
- **Transcript bytes as "usage".** `context-usage-threshold` measures an agent's transcript, not an account's
allowance. For an allowance, see "A usage warning" above.
## Recurring reminders for agents
An agent-to-agent reminder can repeat until stopped. This is separate from
[a person's one-shot watch](#setting-a-watch), which uses `rig queue block --wake-after`.
Save this as `periodic-reminder.yaml`, replacing the example session names with your own:
```yaml
policy: periodic-reminder
target:
session: worker@my-team
message: "Finish the current action, then check the pending work."
```
Register it with all five required flags:
```bash
rig watchdog register --spec periodic-reminder.yaml --policy periodic-reminder \
--target-session worker@my-team --interval-seconds 600 \
--registered-by coordinator@my-team
```
At registration, `--policy` selects the policy; the YAML `policy` field is not the
selector. YAML `target.session` takes precedence over `--target-session`, so keep them
aligned. If YAML omits the target, the CLI target is the fallback. Put a non-empty
`message` in YAML: `--message` is a shortcut only for `context-usage-threshold`.
The first reminder is due after the interval; this example repeats every 600 seconds.
+22 -2
View File
@@ -85,7 +85,7 @@ export function watchdogCommand(depsOverride?: WatchdogDeps): Command {
"Context transcripts measured 113K–153K tokens/MB. The margin is the protection " +
"because prompt-bound consumers act only at turn boundaries",
)
.option("--spec <path>", "Path to YAML spec file (optional for context-usage-threshold)")
.option("--spec <path>", "YAML spec file (required except for context-usage-threshold)")
.requiredOption("--policy <policy>", "Policy name (one of: periodic-reminder, artifact-pool-ready, edge-artifact-required, workflow-keepalive, idle-gate-qitem, context-usage-threshold)")
.requiredOption("--target-session <session>", "Canonical <member>@<rig> target")
.requiredOption("--interval-seconds <n>", "Evaluation interval (positive integer)")
@@ -100,7 +100,27 @@ export function watchdogCommand(depsOverride?: WatchdogDeps): Command {
.option("--active-wake-interval-seconds <n>", "(pool-ready-specific) wake-up cadence when actionable artifacts exist")
.option("--scan-interval-seconds <n>", "(pool-ready-specific) artifact pool scan cadence")
.option("--json", "JSON output for agents")
.addHelpText("after", "\nTranscript density varies by session shape; do not tune a context threshold near the context wall.\n\nThe returned job id can be attached to a deliberate park with: rig queue block <qitemId> --on <blocker> --continuation <what-resumes> --wake-watchdog <jobId>")
.addHelpText("after", `
Recurring reminder for an agent (not a person's one-shot queue watch):
Save periodic-reminder.yaml:
policy: periodic-reminder
target:
session: worker@my-team
message: "Finish the current action, then check the pending work."
rig watchdog register --spec periodic-reminder.yaml --policy periodic-reminder \\
--target-session worker@my-team --interval-seconds 600 \\
--registered-by coordinator@my-team
All five flags above are required for periodic-reminder. At registration,
--policy selects the policy; a YAML policy field is not the selector.
YAML target.session takes precedence over --target-session; keep them aligned.
Put the reminder message in YAML. --message is only a context-usage-threshold shortcut.
For a person's one-shot watch, use rig queue block --wake-after instead.
Transcript density varies by session shape; do not tune a context threshold near the context wall.
The returned job id can be attached to a deliberate park with: rig queue block <qitemId> --on <blocker> --continuation <what-resumes> --wake-watchdog <jobId>`)
.action(async (opts: {
spec?: string;
policy: string;
@@ -94,6 +94,11 @@ pools and missing edge artifacts.
## Active surface
For a worked `periodic-reminder` YAML spec, full registration command and required
flags, read `rig context get reference/keeping-a-watch.md#recurring-reminders-for-agents`.
This is an agent's recurring reminder. A person's watch uses the one-shot queue
pattern in `rig context get reference/keeping-a-watch.md#setting-a-watch`.
Daemon `rig watchdog` is the active host coordination surface for new
work. History records only loud evaluations (`sent` / `terminal`);
quiet skip reasons are NOT recorded — POC parity so agents are not
+2 -2
View File
@@ -26,7 +26,7 @@
"core/session-source-fork/SKILL.md": "c5381d130e0a58c2dd6669770a391314b0db0797df07641cf2d3f9804fac21a2",
"core/specification-system/SKILL.md": "5226d6e8b1362df89ba3d5afd82e4b4add355870132ca4b140d7f9f4324ffdc1",
"core/topology-mutation-and-seat-management/SKILL.md": "527ca074432ce6513fb25cd27e8c709dabe0c91361b8999e09b272f3813abe62",
"core/watchdog/SKILL.md": "24b2e756e3e9d067fa93a4b5fa5f48a5cce511e8b1a5b360b1c39bc09bc95d82",
"core/watchdog/SKILL.md": "88e097e7fe7321e166541b9eac42016fa7a3d362a86fde8946e666f22409f145",
"core/working-with-an-openrig-team/SKILL.md": "01b0aaeb3454bbb4b881dba058022d5a80e62da15516be7db8390b281dd3a228",
"pm/backlog-capture/SKILL.md": "345c2b47fc85e48c15c0d42bbb48fb27dd3b0ceec36bf59dc6ed20daaea47a84",
"pm/context-builder/SKILL.md": "0134c9b0a9f196565109f7f51b6ec78d5c3e4b5982a0d7105a93b29952625b3c",
@@ -131,7 +131,7 @@
"core/session-source-fork/SKILL.md": "c5381d130e0a58c2dd6669770a391314b0db0797df07641cf2d3f9804fac21a2",
"core/specification-system/SKILL.md": "5226d6e8b1362df89ba3d5afd82e4b4add355870132ca4b140d7f9f4324ffdc1",
"core/topology-mutation-and-seat-management/SKILL.md": "527ca074432ce6513fb25cd27e8c709dabe0c91361b8999e09b272f3813abe62",
"core/watchdog/SKILL.md": "24b2e756e3e9d067fa93a4b5fa5f48a5cce511e8b1a5b360b1c39bc09bc95d82",
"core/watchdog/SKILL.md": "88e097e7fe7321e166541b9eac42016fa7a3d362a86fde8946e666f22409f145",
"core/working-with-an-openrig-team/SKILL.md": "01b0aaeb3454bbb4b881dba058022d5a80e62da15516be7db8390b281dd3a228",
"pm/backlog-capture/SKILL.md": "345c2b47fc85e48c15c0d42bbb48fb27dd3b0ceec36bf59dc6ed20daaea47a84",
"pm/context-builder/SKILL.md": "0134c9b0a9f196565109f7f51b6ec78d5c3e4b5982a0d7105a93b29952625b3c",
+5
View File
@@ -94,6 +94,11 @@ pools and missing edge artifacts.
## Active surface
For a worked `periodic-reminder` YAML spec, full registration command and required
flags, read `rig context get reference/keeping-a-watch.md#recurring-reminders-for-agents`.
This is an agent's recurring reminder. A person's watch uses the one-shot queue
pattern in `rig context get reference/keeping-a-watch.md#setting-a-watch`.
Daemon `rig watchdog` is the active host coordination surface for new
work. History records only loud evaluations (`sent` / `terminal`);
quiet skip reasons are NOT recorded — POC parity so agents are not