| name | monitor |
| description | Watch Gradient repo signals after a docs/schema/profile/harness change.
Trigger: /monitor.
|
| argument-hint | [change-ref|paths] [--grace <duration>] |
/monitor
There is no production service to watch. Monitoring here means watching for
contract drift and governance regressions after a change lands.
Signals
- Public-safe violations in newly added text or fixtures.
- Lifecycle vocabulary drift across docs.
- Profile/schema mismatch.
- Harness skill gate drift.
- New unverified validation paths.
- Git history that lands contract changes without evidence.
Procedure
- Identify the landed change or local diff.
- Re-run the manual gate checks applicable to the touched files.
- Compare terminology against the repo brief and
docs/architecture.md.
- Escalate to
/diagnose for contradictions or missing evidence.
- Close with a short monitor receipt.
Gate
The load-bearing ship gate is ./scripts/validate.sh, plus reviewer
judgment for lifecycle semantics in docs/architecture.md and
docs/module-contracts.md when docs change.
