Protocol Wealth Operating System (PWOS) is the integrated advisor IDE, client portal, and compliance engine Protocol Wealth built for its own SEC-registered investment advisory practice.
PWOS is architecturally an integration wrapper around open-source primitives. The open primitives (pwos-core Apache 2.0, nexus-core Apache 2.0) are published and inspectable without an NDA. The integration logic on top is what turns those open primitives into a governed system operated inside a live SEC-registered practice.
Structural layers
| Layer | What it does | Basis |
|---|---|---|
| Zero Data Retention (ZDR) | Anthropic ZDR posture, enforced contractually at the API workspace level. Inputs and outputs are not retained beyond the duration of a single inference request; content is contractually excluded from training, fine-tuning, and model improvement. Inference runs on US-based infrastructure. | Contracted at the workspace level; effective April 21, 2026 |
| Schema-level PII tagging | Client-data fields are classified at ingestion as high, medium, or low sensitivity. Before text is sent to an AI provider, identifiers PWOS recognizes, such as Social Security numbers, account numbers, credentials, tokens and cryptographic keys, are replaced with placeholders. Recognition is by pattern, is not complete, and does not remove names; PDF and image attachments are not scanned. | Pattern-based replacement in the AI request path |
| Independent PII egress canary | A second-layer guard whose pattern set is deliberately re-implemented independently, so the two layers cannot share a single bug. It can block outbound requests when residual sensitive patterns are detected. It does not check PDF or image attachments. | Defense-in-depth |
| WORM audit retention | A retention-locked, write-once object store mirrors rows written to the firm's canonical audit log. Bucket-level retention lock means no PW operator — including a full cloud-organization administrator — can delete or modify an object within the window. Each object carries a content hash and the source revision in metadata. | The firm's own recordkeeping obligation as an adviser is SEC Rule 204-2 |
| Sentinel-row reconciliation | Reconciliation of a failed mirror write cannot UPDATE the audit log (the table is immutable at the database-trigger level). Instead, a new sentinel row referencing the failed row's ID is written when the mirror write fails. |
Append-only audit log |
What runs today
These onboarding steps run on PWOS today:
- Portal authentication — a passkey, Google sign-in, or a one-time link sent to the client's email address.
- Identity verification — document and biometric identity checks through Veriff, when an advisor turns them on.
- Risk-tolerance assessment — a questionnaire producing a composite score, which an advisor can override.
- Account-data aggregation — read-only aggregation of client-held accounts.
- Onboarding status — a single view of where each new relationship stands.
How to verify any of this
Qualified partners and institutional reviewers may request supporting diligence materials under NDA, as the public security posture describes (/security § "Verify"): vendor due-diligence evidence, anonymized audit-log samples, the ISO-aligned Statement of Applicability, the Risk Register, and security-policy artifacts.
Open source
pwos-core— Apache 2.0-licensed; compliance audit-logging patterns + PII redaction toolkit. Reference code, not deployed.nexus-core— Apache 2.0 defensive licensing; MCP server foundation; ~243 financial-data tools surfaced; live at nexusmcp.site.
The intent is not marketing surface; it is to show the audit-logging and redaction patterns in code.
Cross-references
- Public security posture:
/security - Form ADV Part 2A: adviserinfo.sec.gov/firm/brochure/335298
- Subprocessor list: protocolwealthllc.com/subprocessors
Protocol Wealth, LLC · SEC-Registered Investment Adviser · CRD #335298 Engineering substrate transparency · aggregate substrate material · not investment advice · not advisory performance.