Zain Dana Harperauthorized private practice

Detailed enough to evaluate, bounded enough to publish.

Seed, Array, Sofer, Bounds, and ORCA are described here as public contract surfaces. The page explains purpose, components, workflow, evidence state, limitations, and engagement boundary without exposing protected material or runnable public commands.

The boundary is simple: written authorization first, non-public detail second.

controlled-private · one public-safe registry record · evidenceDate 2026-08-27

Practice map.

Seed Purpose: controlled starting-state and scenario generation for repeatable review work. Components: scenario intake, fixture seed, scope notes, and repeatability receipt. Bounded workflow: define the lawful surface, create a repeatable starting state, run only agreed checks, and preserve a re-readable receipt. Evidence state: private system described from operator context only. Limitations: no public source, no runnable public command, and no third-party acceptance claim.
Array Purpose: compare many runs, artifacts, and reviewer notes without losing provenance. Components: run ledger, artifact table, review note map, and handoff index. Bounded workflow: collect authorized evidence, compare outputs by receipt, mark gaps, and hand off only public-safe or authorized material. Evidence state: private system described from operator context only. Limitations: no public source, no runnable public command, and no third-party acceptance claim.
Sofer Purpose: shape review packets where wording, evidence order, and revision history matter. Components: source notes, claim ledger, revision pass, and public-safe packet. Bounded workflow: separate verified facts from assumptions, draft from evidence, review every claim boundary, and export only the approved packet. Evidence state: private system described from operator context only. Limitations: no public source, no runnable public command, and no third-party acceptance claim.
Bounds Purpose: record what is in bounds, what is out, and which claims can be made. Components: authority statement, allowed surface, excluded surface, and stop conditions. Bounded workflow: record authority, record exclusions, run only permitted checks, and stop when the written boundary ends. Evidence state: private system described from operator context only. Limitations: no public source, no runnable public command, and no third-party acceptance claim.
ORCA Purpose: oversight and run capture for authorized adversarial evaluation and high-consequence technical review. Components: review objective, run capture, witness notes, and handoff packet. Bounded workflow: confirm scope, capture the authorized review run, attach witness notes, and hand off the bounded packet. Evidence state: private system described from operator context only. Limitations: no public source, no runnable public command, and no third-party acceptance claim.

Shared engagement boundary.

Purpose Turn sensitive review work into scoped, testable, recorded engagements where every claim has a source and every output has a boundary.
Problem High-consequence security and AI review work can fail at handoff through unclear authority, missing provenance, weak run records, or claims that outgrow their evidence.
Components Scenario setup, artifact intake, scope rules, run ledger, reviewer notes, acceptance checks, and final packet assembly.
Bounded workflow Define the authority, define the surface, run only within that surface, record the result, and stop when the written scope ends.
Intended users Lawful organizations that need disciplined adversarial evaluation, sensitive-system review, market-risk tooling review, or high-assurance technical evidence.
Testing approach Fixture-first tests, deterministic replay, artifact hashes, reviewer checklists, and evidence packets that can be re-read without trusting a chat transcript.
Non-sensitive deployment model Run inside the authorized environment or as an offline review packet. Public material excludes protected infrastructure, counterparties, and environment facts.
Limitations No public release, no public source, no public walkthrough, and no claim that any system is accepted by a third party.
Engagement boundary A written scope and lawful authority are prerequisites. A request without those facts receives only public material.

Contact route.

For work that fits this boundary, start with the public hiring map or email. State the role, the lawful basis, and the review objective at a high level.