First submission checklist
What a good first run looks like
- One real case, not a demo-only folder.
- A small set of evidence you already exported from your workflow.
- Enough context that you can explain internally what the package is meant to prove.
- Browser upload first. API later only if you want automation.
Checklist before you click Upload
- Choose a real submission you already have.
- If your files are already zipped, upload the ZIP as-is.
- If not, select the individual files directly in the Buyer Console.
- Prefer source evidence over screenshots alone.
- Keep the first upload simple so the result is easy to interpret.
What to expect after upload
- PASS means AttestLayer issues a signed kit plus supporting downloads.
- FAIL means you receive a blocker list showing what to fix next.
- FAIL burns 0 credits.
- You do not need to understand every artifact name on the first run. Start with the main result.
If the first run fails
Treat FAIL as a to-do list, not a dead end. Fix the named blockers first, then resubmit.
Read Understand PASS / FAIL for what the result means in plain language.