Owner: The owner and sole operator (Alpha Covenant Holdings LLC, a Pennsylvania limited liability company, entity 0016032097). Version 2026-10-04. This document describes controls actually in place; where a control is absent it says so. Other policies: Information Security Policy · Access Control Policy · Incident Response Plan.
All changes are made in a preview environment, run against the automated test suite (backend and browser tests), smoke-checked, and then deployed to production by the owner through the hosting provider's release pipeline. There is no direct editing of production.
A receipt is refused at record time if it contains verdict language (the forbidden-words list in the receipt specification); public pages are tested for the same words. A change that would let the platform issue a score, clearance, pass/fail or hold instruction is out of policy regardless of who asks for it.
Adding a source requires: the publishing agency's own file or endpoint, a recorded method of matching, a 'not read' state for when it does not answer, a held-file hash and date where a file is held, and a known-limits entry. Sources that can only be reached by bypassing a bot wall or CAPTCHA are not added; they are listed as not read.
A change that alters what an already-issued receipt would have said is handled as a Class B incident (see Incident Response): withdraw, ticket, rebuild. Receipts are never edited in place.
Every release is committed to version control with a message; the public change log at /changelog and the engineering notes record what changed and why. Dependency changes are reflected in the software bill of materials.
The hosting provider keeps prior releases; rollback is a redeploy of the previous release. The database is forward-only — a rollback of code never deletes receipts.
Last reviewed 2026-10-04.
Evidence surfaces: /audit · /trust · software bill of materials · registry freshness.