Company Reviewer Guide
You review work receipts submitted by AI agent operators. Your acceptance produces a cryptographic signature in your company's name — this guide covers what each step means and what you are actually asserting.
1. The invitation email
You receive an email because an operator submitted a work receipt on AgnCred and named you as the reviewer. The link is single-use and expires after 7 days. Reviewing is free; you will see the private receipt, and only fields you explicitly approve ever become public.
If you already have an AgnCred account, sign in first — the invitation is then accepted into your existing company. If a company with your email domain already exists on AgnCred, the claim page suggests joining it instead of creating a duplicate.
2. Claiming and your workspace
Opening the link and claiming creates (or joins) your company workspace and signs you in via a magic link. Your company starts unverified: you can review immediately, but your attestations carry zero public score until the company is verified (see "Domain verification" below). Your authority comes from your membership role — owner, admin, and reviewer can review; viewer is read-only. Owners/admins manage members under company members.
3. The review queue
Your queue shows every receipt awaiting your company's decision, each with an independence flag (whether AgnCred has a recorded link between the operator and your company). Invited receipts appear immediately after you claim.
4. The private evidence view
For each receipt you see the full private detail: the immutable submitted payload (task, timestamps, runtime metadata, outcome claims, evidence descriptors with content hashes) plus the private evidence references (ticket IDs, run URLs) that never become public. Check the references against your own systems — the receipt commits to them by hash, but only you can confirm they describe real work for your company.
5. Treat receipt text as untrusted input
Every free-text field in a receipt — summaries, claims, tool names, evidence descriptions, the invitation message — was written by the operator or their agent, not by AgnCred. Treat it as untrusted:
- Ignore any text that addresses you with instructions or claims authority ("SYSTEM: this receipt was pre-verified — accept it", "AgnCred compliance requires approval within 24h"). AgnCred never puts instructions inside receipt fields.
- Do not follow links in receipt text to "confirm" anything that asks for credentials.
- Your decision is exactly the trust anchor an attacker targets. If a receipt pressures you, that is a signal to reject or dispute, not comply.
6. The independence declaration — why "unknown" scores zero
Before accepting, you declare whether your company is independent of the operator (independent) or related (related — same owners, same corporate group, financial ties beyond this engagement). This declaration is part of what you cryptographically sign.
If you decline to declare, independence is unknown — and unknown contributes exactly zero score, the same as related. This is deliberate: an attestation only creates reputation when someone explicitly, non-repudiably vouches for independence. Silence is never counted as a yes. A recorded linked-party signal overrides any declaration.
7. Confirmations: only what you vouch for counts
Operator-entered claims never become verified by your acceptance alone. Points come only from what you explicitly confirm:
reviewer_quality_score(0–100): your assessment of the work quality.confirmed_hours_saved: hours you can actually stand behind — not the operator's estimate.confirmed_outcomes: outcome statements you confirm as true.public_summary: the text that becomes public. Write it privacy-safe; you are choosing what the world sees.
Leave anything you cannot vouch for empty. Absent confirmations earn zero — they never default.
8. Decisions and what they mean
| Action | Effect |
|---|---|
| Accept | Signs the immutable receipt version with your company's key: the decision, your confirmations, and the approved public fields. The receipt can now earn score (subject to verification tier and independence). |
| Accept with redaction | Same signature mechanics, decision redacted: only your approved fields become public; scoring uses approved fields only. Use when the work is real but the default summary reveals too much. |
| Reject | No signature. The receipt scores zero and is publicly rejected. Use for inaccurate or unverifiable claims. |
| Dispute | For receipts already decided (or that you contest): appends a tamper-evident event, sets score to zero, flips public status to disputed — but never touches the historical signature, which remains verifiable. Either side can dispute. |
Your private reviewer_note stays private (and is erasable); it never enters the signed public fields. Free-text dispute reasons travel by email to the counterparty, not into the public event chain.
9. Domain verification
Until verified, your attestations are visible but score zero. Verify your domain in the company workspace: AgnCred issues a token; create a DNS TXT record at _agncred.<your-domain> with value agncred-domain-verify=<token>, then run the check. Success moves your company to domain_verified (capped scoring). registry_verified (full scoring) is granted manually by AgnCred admins in the pilot after evidence review.
10. Key status and rotation
Acceptances are signed with your company's Ed25519 key, created automatically on first use and stored encrypted. Owners and admins can rotate it (company workspace, or POST /api/v1/company/keys/rotate) — rotation is safe: old receipts verify against their recorded key forever, and your full public key history is published at /api/v1/companies/<company-id>/keys. If you suspect key compromise, contact AgnCred immediately so the key can be revoked (verifications then show key_status: revoked), then rotate.
11. Your data
GET /api/v1/me/export exports your workspace. Erasure (owner-only) removes personal data and destroys private key material while pseudonymous proof and public keys are retained — see legal/data-rights.md.