What to send, what to hold back, and when.

Start with a description of the work. Existing headers can help clarify fit. Before any private sample or export moves, agree disclosure permission, purpose, handling and retention in writing.

Operalith does not need credentials, a full ERP export, or a standing feed to check one bounded operational view.

01Start here

Send the structure, not the archive.

The exact operational question the output should answer
Existing column headers, if useful; no fabricated sample required
How often the export is produced and who reviews the result
Existing source and target exports only after disclosure permission and a private route are agreed

Describe the work first. Operalith can create fictional examples from the structure when needed; you do not need to clean a sample or prepare an identifier crosswalk.

02Do not send

Keep secrets, broad exports, and unrelated records out.

Passwords, tokens, administrator links, or API keys
Customer names, personal contact data, payment details, or private screenshots during fit review
Large archives or administrator exports unrelated to the accepted path
Anything outside the named workflow, columns, and decision without discussing it first

03After scope

Each private item needs a purpose and an exit.

Before private material moves, the written scope should name why it is needed, how it will be transferred, who can handle it, and the retention-review date. Findings remain human-reviewed before discussion or delivery.

04Deletion

The closeout record includes the evidence decision.

At the agreed review point, material is returned, deleted, or retained only under the written engagement record. Questions or deletion requests can be sent to dylan@info.operalith.com.

Next record

Begin with the smallest useful surface.

Describe the export, the recurring decision, and the output the operator needs to trust.

Request a fit check Read the privacy record