Selected technical work

Technical proof, with the boundaries intact.

Selected public work is presented with inspectable evidence and exact maturity labels. Separately labeled private development shows technical breadth without implying public availability.

Bounded claimsVisible provenanceStatus before assertion

Contribution provenance

Fork lineage stays visible.

anjor/pltr-cli is the upstream project. Raava claims only changes in raava-solutions/pltr-cli; Zay Cruz's feature branches remain work in a personal fork and are not merged upstream.

Public pltr-cli contribution provenance

Upstream projectanjor/pltr-cli
Raava public forkraava-solutions/pltr-cliMCP integration merged here in PR #1.
Zay Cruz personal forkzaycruz/pltr-cliTwo public WIP branches; not merged upstream.
Contribution map, not an authorship claim: upstream ownership, Raava-fork deltas, and Zay's personal-fork work remain distinct.

Inspectable public work

Claim, proof, and maturity in one scan.

pltr-cli was created upstream by anjor. The entries below describe only the bounded changes visible in Raava's public fork or Zay Cruz's personal fork.

Raava fork contribution

Multi-profile MCP integration

Shipped in Raava’s public fork
Claim
Raava added multi-profile MCP support to its public pltr-cli fork so distinct environments can be addressed through explicit profiles.
Proof basis
The implementation and review history are inspectable in raava-solutions/pltr-cli. PR #1 is merged in the Raava fork; this is a Raava delta, not a claim of upstream authorship or adoption.
Inspect Raava forkReview merged PR #1

Zay Cruz personal fork

Folder move

Public work in progress
Claim
A public feature branch explores moving folders as a first-class workspace operation.
Proof basis
Evidence branch: feat/folder-move. This is public work in progress in the zaycruz/pltr-cli personal fork and is not merged upstream.
Inspect feat/folder-move

Zay Cruz personal fork

Dependency analysis

Public work in progress
Claim
A public feature branch explores dependency analysis for understanding relationships before a change is made.
Proof basis
Evidence branch: feat/dependency-analysis. This is public work in progress in the zaycruz/pltr-cli personal fork and is not merged upstream.
Inspect feat/dependency-analysis
Private technical breadth

Private capability work

IJT Terminal

Private work in development
Claim
A private desktop capability combines an authenticated desktop shell, protected native session store, named workspaces, a protocol-validated SSE agent bridge with action allowlists, and fund operations/risk tooling.
Proof basis
The capability basis is limited to verified implementation surfaces. The implementation is private and is not publicly released, production deployed, or open-source.

No public source or deployment link.

Simplified capability boundary

IJT Terminal

The model groups verified capability classes inside one private boundary. It does not describe deployment topology, data flows, infrastructure, or access paths.

Authenticated desktop shell
Protected native session store
Named workspaces
Protocol-validated SSE agent bridge
Action allowlists
Fund operations / risk tooling
Capability model only. Credentials, endpoints, infrastructure topology, client data, fund data, and operational details are intentionally omitted.

Put the same rigor behind your operating problem.

Bring us the decision, workflow, or system boundary that needs to become inspectable and operational.

Book a Discovery Call