Skip to main content
Protocol Wealth

PWOS governance layer

Governance and safety primitives for AI-enabled advisory work

pwos-core publishes reusable TypeScript packages and reference patterns for PII boundaries, audit evidence, gated tools, workflow controls, documents, and related operational safeguards.

Repository
pwos-core
Implementation
TypeScript
License
Apache-2.0

Role in the system

One bounded layer, not the whole stack

This is the governance and safety substrate in the public stack. It defines reusable controls around other applications and agent runtimes; it is not the client portal, the research engine, or a complete deployment of Protocol Wealth's private operating environment.

Current repository posture: The repository describes itself as a public reference and starting point under active development. Adopters remain responsible for their own security, compliance, deployment, and review.

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.

PII boundary primitives

The package workspace includes deterministic PII-guard patterns that downstream applications can call before data reaches an AI workflow.

Check: Inspect packages/pii-guard and its tests. If inputs can pass the documented direct-identifier tripwires unchanged, this claim fails.

Reconstructable audit evidence

Audit-log primitives provide typed structures for recording governed events and their provenance.

Check: Inspect packages/audit-log and the validation paths. If a downstream event cannot carry the documented audit fields, this description is too broad.

Registered MCP tool surface

The public package map includes MCP tool registration patterns so capabilities can be declared and governed rather than invented at runtime.

Check: Inspect packages/mcp-tools. If tool definitions bypass the declared registry and policy metadata, the control boundary does not hold.

Composable operational packages

Auth, compliance, document, workflow, planning-contract, security-header, and related packages can be adopted independently.

Check: Compare the README package map with packages/. A named capability without a corresponding inspectable package is a documentation defect.

Reality check

What this page does not establish

  • A public control library does not prove that every private application or workflow uses every package correctly.
  • Deterministic PII detection is a tripwire, not proof that arbitrary data has been de-identified.
  • The repository does not include client records, production credentials, private deployment configuration, or a turnkey compliance program.

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.