Reply to a package

If your lab received a candidate package by email, this is the way its result gets back into the system. Each package carries a token of the form OMEGA-xxxxxxxxxxxx (twelve hex characters — the prefix is unchanged, so a token from a package you already hold still works) and states the measurement that would refute it. Your reply is recorded against that package and nothing else: one verdict for the package as a whole, with the per-candidate values and verdicts in the notes.

POST /api/labs/reply

It is in the subject line and body of the package email. Case does not matter.

Verdict

The verdict is for the package as a whole and is the only thing recorded as the result; a mixed package (some candidates held, some did not) is inconclusive with the split in the notes. A refutation is recorded exactly as a confirmation is. Either one is the outcome the package was sent to obtain.

0 / 64000

What happens to a reply

  • The reply is written to file only if the token belongs to a package a person has marked as sent and the verdict is one of the words above. A token of a package not yet marked sent is refused (HTTP 409) with that reason; an unknown token is refused (HTTP 404). Otherwise nothing is written and this page tells you why.
  • On the next ingestion pass it is matched to its package by the token, and the verdict you chose is recorded against the package: confirmed, refuted, or inconclusive. The notes travel with it and cannot change it.
  • A second reply for the same package is accepted as a correction and says so: the latest reply is the one that counts, and every earlier one stays on file.
  • The count of results received on the home page counts packages answered, one per package however many replies it received. It is the only outcome this system reports.
  • A reply you cannot make here, or a result that needs a file attached: write to [email protected] quoting the token. A person reads it.