Capability Watch · v0.50.0
Track capability change without turning metadata into authority
RuleOak can build publication-safe capability history from normalized observations. Initial first-seen observations belong in history but are not treated as drift alerts.
Drift examples
- tool removal or reintroduction
- schema change
- authority expansion
- consequence escalation
- current fingerprint change
Publication safety
Public index material omits raw input schemas, credentials, URL secrets, local source paths, source code and prompts. A watch/baseline handoff identifies a capability state; it never grants runtime authority.