KCP Playground Β· 10 / 11 Β· the enabler

The Research Assistant

Governance isn't a brake. A read-only research skill runs a whole plan β€” recall, load governed sources, summarise, remember β€” at full speed with zero blocks, and every step still lands in the audit chain. When a skill is bounded, the adjudicator has nothing to stop, so the agent just runs β€” and you still get a receipt for every action. Each β€œallowed” is computed by the real checkConformance tools/paths logic from kcp-harness, and the run is signed & verified with genuine crypto.subtle.

Press β–Ά Run research. The skill declares a read-only action_scope, so every step it plans is already in-bounds β€” watch it run clean, then read the audit chain. Flip let it try to write to see the one guardrail bite.

skill Β· action_scope.read_only

sources to consult

iso-27001.md evidence-log.md data-retention.md

Every source you add lands under kcp/knowledge/ β€” inside the read-only scope. That's the point: within the skill's bounds, more work just means more clean receipts.

the plan

no run yet β€”
the skill is loaded & bounded
no receipt yet β€”
the printer is warm
audit chain Β· last rungoverned:0 blocked:0 tickets:0

Station 10 of 11. Each step's verdict = the real checkConformance tools/paths logic from kcp-harness (verbatim: fail-closed hasScope β†’ tool allowlist β†’ path-prefix with normalizePath/matchesPrefix). A read-only skill's actions all fall inside its declared scope, so all pass β€” and every one is still checked, stamped, and signed. The write action is the lone out-of-scope tool; when attempted it's held. Run record signed & verified with genuine crypto.subtle.