WoodardPractice ReadinessSynthetic sample

Data boundary

Supported documents

The authenticated seller workspace accepts three defined CSV source classes. Permitted fields and prohibited content are shown before its private file picker.

Three source classes, kept separate.

Each source answers a different question. The system preserves its origin and compares overlapping facts instead of treating one file as automatically authoritative.

01

Profit & loss

Three fiscal years

Period-level operating revenue and expense records used to construct a traceable operating picture.

02

Business tax data

Three fiscal years

Business-level reported figures used as a separate source class. Personal returns are outside the current boundary.

03

De-identified client revenue

Approved period export

Client-level revenue used to inspect concentration without names or direct client identifiers.

Current format availability

“Planned” is not the same as accepted. A hosted release must activate a format only after byte validation, security scanning, extraction, provenance, recovery, deletion, and deployment tests pass for that exact format.

De-identified sample CSV
Available in the public sample for the three documented structural shapes. The repository fixtures are optional templates; matching values and years may differ. The route persists no file or customer case.
Private CSV
Available after seller sign-in, AAL2 verification, and case-specific upload-authority confirmation. Files are structurally validated, stored in private quarantine, and processed locally for the assessment. Each file is limited to 1 MiB.
XLSX, PDF, OCR
Planned document adapters. They are not accepted until their specific policy and protected test corpus are approved.
Accounting exports
Provider and export schemas require separate approval. A filename or extension never makes an unknown export supported.

Current owner CSV processing declaration

The content-free processing declaration approves the three CSV shapes, parser, size, purpose, and local processor. It does not pre-approve or publish a customer byte corpus. A separate case-specific authority confirmation is still required before upload.

Structural processing policy
owner_csv_structural · 2026-08-09.1
Processing policy digest
sha256:c623e4821eccd7117c3f9c1517c05a05088fe30235208a2c62c4a5994b57c02e
Release boundary
The anonymous sample accepts only the narrow de-identified schemas, uses canonical non-identifying filenames, and persists nothing. Authenticated owner intake remains a separate case-scoped quarantine and processing path.
Case authority declaration
2026-08-09.owner-csv.1
Separate case confirmation

Confirm authority before uploading

  1. I am authorized to provide the selected records for this private assessment.
  2. I will upload only records for this practice in the supported CSV shapes, and I have removed client names, email addresses, Social Security numbers, tax IDs, bank details, and other direct identifiers.
  3. I understand the files are processed only for this assessment under the processing and retention terms shown on this page.

Without this confirmation, document upload remains unavailable.

Before an authenticated owner upload

The authenticated workspace repeats the active policy and requires separate upload authority before the picker. Use the public sample only for the documented de-identified shapes; use the private workspace for authorized owner records.

Leave out

Client-identifying and unrelated data

  • Do not include client names, emails, addresses, tax IDs, or bank details.
  • Do not include personal tax returns, credentials, or access tokens.
  • Do not upload files whose origin or authority is uncertain.
What the product will show

Purpose, processing, and status before selection

  • Allowed class, fields, format, and size for the active release.
  • Purpose, processor/region, retention, and prohibited-content summary.
  • Persisted quarantine, processing, review, failure, and recovery state.