Review Request

Tell us what you need reviewed

This is a fit check, not evidence intake. Describe the questionnaire, server, launch, incident, access change or bounded workflow you need reviewed. No files, logs, screenshots, exports, credentials, private keys, MFA codes or customer evidence are needed for the first fit check.

Fallback contact: send the same non-secret fit check to engage@mail.witnessops.com. Do not send passwords, private keys, API keys, recovery codes, session tokens or other secrets.

Start with a short, non-secret fit check.

Describe what you need reviewed; do not paste source material. No files and no evidence upload. Save questionnaires, logs, screenshots, exports, credentials, private keys, MFA codes and customer evidence for the scoped intake after handling is agreed.

Your name (required)

Work email (required)

Company or team (optional)

What do you need reviewed? (required)

Describe one review need at a high level. Do not paste secrets, source exports, full logs, screenshots, credentials, private keys, MFA codes, or customer evidence.

Situation and affected system (required)

Boundary and approval (required)

Evidence available (required)

Submitting this form only opens fit and scope review. No review starts until scope, price, timing and evidence handling are agreed.

Email follow-upengage@mail.witnessops.com

Do not send passwords, private keys, API keys, recovery codes, session tokens or other secrets.

What happens next

01We check whether the technical action is bounded enough for one review package.
02We confirm the system boundary, action path, likely evidence sources, and obvious gaps.
03We reply with fit, scope, fee, and next action before any source materials are accepted.

First message only

Do not submit secrets, credentials, private keys, MFA codes, source exports, full logs, screenshots, customer records, or unrelated production data. Name evidence types only; source materials are handled after scope is agreed.

Commercial scope

Fee, timing, and evidence handling are confirmed by email after the first fit check.

No work starts from this form. No proof run or target-facing check starts from this form.

No customer evidence is accepted until scope is agreed.

Typical bundle

✓ACTION_BOUNDARY.json
✓AUTHORITY_MAP.json
✓EVIDENCE_MANIFEST.json
✓RECEIPT.json
✓VERIFY_RESULT.json

Inspect sample package

Boundary kept clear

Not a production deployment claim.

Not a legal compliance claim.

Not a complete AI governance program.

Need help? Support./Disclosure: Security.

What a bounded review package can include

Boundary map

What action is in scope, who approved it, who acted, and where authority stops.

Action path

The one workflow, tool path, or touched system under review.

Evidence manifest

Available artifact classes, source references, hashes where available, and known gaps.

Receipt artifact and verifier path

Package artifacts that name approval, action, evidence references, limits, and challenge path when the scope supports them.