Skip to main content
Protocol Wealth

Agent control layer

Portable control-plane contracts for agent interfaces and runtimes

pwcli-core specifies intent, policy, primitive, runtime-adapter, redaction, approval, provenance, and content-minimized receipt boundaries that can sit above existing agent loops.

Repository
pwcli-core
Implementation
JSON Schema / TypeScript / Python
License
Apache-2.0 OR MIT-0

Role in the system

One bounded layer, not the whole stack

This repository standardizes the envelope around an agent runtime rather than replacing the runtime. The runtime owns its loop, context, tools, and sessions; pwcli-core describes how a host can make intent, side effects, approvals, data boundaries, and evidence legible.

Current repository posture: The project labels its standards by maturity and treats adapters as reference paths. The initial Claude Agent SDK examples are deliberately read-only and use fake runtime calls in repository validation.

Inspectable capabilities

Claims you can try to disprove

Each capability is paired with a concrete inspection test. If the source does not support the claim, the page should change.

Machine-readable control contracts

JSON Schemas define portable intent, policy, primitive, runtime, redaction, artifact, provenance, and run-receipt shapes.

Check: Inspect schemas/ and run the validator. A fixture that violates a required boundary should fail validation.

Runtime adapter boundary

Adapter metadata separates the agent execution engine from the host policy and data-governance layer.

Check: Inspect schemas/runtime-adapter.schema.json. If an adapter can silently elevate its declared side effects or data classes, the contract is insufficient.

Equivalent Claude SDK references

Python and TypeScript examples apply the same read-only tool, auth, hook, redaction, approval-decision, and receipt policy around the official Claude Agent SDK.

Check: Run npm run validate. Both suites should deny mutation and sensitive paths, redact tripwires, reject unsupported intent, and omit raw content from receipts.

Content-minimized evidence

Run receipts record policy decisions and hashes without retaining prompts, model output, tool arguments, file contents, or credentials.

Check: Inspect schemas/run-receipt.schema.json and the tests. Searching a receipt for synthetic secret, prompt, output, or tool content should return nothing.

Reality check

What this page does not establish

  • A schema or permission setting is not an operating-system sandbox; hosts must separately constrain process, filesystem, credentials, and network egress.
  • The read-only reference adapters do not implement edits, shell execution, interactive approvals, remote access, or unattended mutation.
  • Provider compatibility does not authorize extraction or reuse of consumer subscription credentials; integrations must follow the provider’s documented authentication terms.

The repository is open-source software provided under its stated license and without warranty. It is not investment, legal, tax, or cybersecurity advice. Protocol Wealth is an investment adviser, not a software vendor; publishing this code does not create a support, hosting, or implementation agreement.

Next

Verify the source, then follow the boundary

Start with the README, inspect the implementation and validation paths, and open an issue in the repository if the public description and source do not agree.