documents: brief: verifier.md

The exact instructions every agent role received (briefs), the verification prompt, the extraction protocol, screening criteria and the release datasheet.

Data license: Not yet licensed — internal review only · Data source: Ahmed ElBatanony, Innopolis University

This data as json

name	text
brief: verifier.md	# Verifier brief (pub-10 main run, v1, 21.10.2026) Working directory: `/home/bat/dev/phd`. For each application id you are given: 1. Read the fixed instructions in `data/business-apps/verification-prompt.md` and follow them exactly. 2. Input statements: `data/business-apps/run/<id>/candidates.json`, field `statements` (use `id`, `statement`, `excerpt`). They come from two independent extraction runs (ids with `A` and `B`), so many capabilities appear twice: keep the first and reject later ones with reason `duplicate of <id>`. 3. Source: every file `data/business-apps/sources/<id>/.txt`, read in full, for judging support and for the missed-capability pass. 4. Do not read `extract-.json`, `adjudication.json` or any other application's files. 5. Write the JSON output (the shape in the instructions; `missed[].appId` = the id) to `data/business-apps/run/<id>/verify.json` with the Write tool. Every input id must appear exactly once in `verdicts`. Missed excerpts must be copied character for character from a source file. Final answer: one line per application, `<id> <confirmed>/<corrected>/<rejected> missed=<n>`. Nothing else.

name

text

brief: verifier.md

# Verifier brief (pub-10 main run, v1, 21.10.2026) Working directory: `/home/bat/dev/phd`. For each application id you are given: 1. Read the fixed instructions in `data/business-apps/verification-prompt.md` and follow them exactly. 2. Input statements: `data/business-apps/run/<id>/candidates.json`, field `statements` (use `id`, `statement`, `excerpt`). They come from **two independent extraction runs** (ids with `A` and `B`), so many capabilities appear twice: keep the first and reject later ones with reason `duplicate of <id>`. 3. Source: every file `data/business-apps/sources/<id>/*.txt`, read in full, for judging support and for the missed-capability pass. 4. Do not read `extract-*.json`, `adjudication.json` or any other application's files. 5. Write the JSON output (the shape in the instructions; `missed[].appId` = the id) to `data/business-apps/run/<id>/verify.json` with the Write tool. Every input id must appear exactly once in `verdicts`. Missed excerpts must be copied character for character from a source file. Final answer: one line per application, `<id> <confirmed>/<corrected>/<rejected> missed=<n>`. Nothing else.