Planning interface layer
pwplan-core is a React and Vite planning interface whose public contract accepts de-identified planning variables and rejects named direct-identifier keys before those values reach the planning engine.
Role in the system
This repository is the human-facing planning layer. The same UI contract can target a public demo engine or a separately authenticated private gateway, while identity mapping, client records, advice, and books-and-records controls remain outside the public browser application.
Current repository posture: The public build is for fake or de-identified demonstration data. The README explicitly separates it from authenticated private-client infrastructure.
Inspectable capabilities
Each capability is paired with a concrete inspection test. If the source does not support the claim, the page should change.
Planning requests use an explicit contract of planning variables rather than an open-ended client record.
Check: Inspect src/contract/planning.ts. If the request shape accepts named identity fields without a contract change, the boundary has drifted.
Client-side compliance checks reject a defined set of direct-identifier keys before sending a planning request.
Check: Inspect src/lib/compliance.ts and its tests. Adding a blocked key to a request should fail before the engine call.
The public demo and separately authenticated private gateway share a UI contract while keeping identity and production controls outside the public build.
Check: Compare the documented gateway configuration paths. If public code embeds private credentials or identity mapping, the separation fails.
The interface makes planning inputs and outputs inspectable without requiring users to operate the Python engine directly.
Check: Run the documented build with fake data. If a core planning route cannot render without client identity, this claim is incorrect.
Primary sources
Repository README →
Identity boundary, deployment split, compliance scope, and engine contract.
Planning contract →
The typed request and response boundary used by the public UI.
Compliance tripwire →
The defined direct-identifier checks before planning calls.
Source tree →
The React interface, contract, libraries, and supporting implementation.
Reality check
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
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.