Skip to content

FAQ

What to send, what not to send, and what an assessment can tell you.

The practical questions people ask before requesting a review: what to share in the first conversation, how access to detailed materials gets arranged, and what an assessment can and can't establish.

Practical details

Information, access and handling.

  • Scoping checklist
  • What not to send guidance
  • NDA and data-handling expectations
  • Production access guidance
  • Report and limitation explanation

01

Common questions

What should the first message include?

The workflow, the systems, the connected tools, the kinds of data, your decision deadline and the report you need. Keep it high-level; detail comes later through an agreed channel.

What shouldn't be sent?

Secrets, credentials, regulated data, customer PII, payloads or confidential files. None of that belongs in the public contact form.

Do you need production access?

Not always. Many reviews start from architecture, configuration, logs, transcripts, prompts and staged access, and only consider production access after that.

Does an assessment include certification?

No. An assessment reports findings for the systems and conditions we reviewed. It doesn't certify general safety or future versions. No AgentBoundary certifications have been issued or published; the program work available today is assessment or readiness review.

Next step

Ready to describe the work?

Request written scope