Owner: The owner and sole operator (Alpha Covenant Holdings LLC, a Pennsylvania limited liability company, entity 0016032097). Version 2026-10-06. Describes what is actually done; not a certification.
This manual states how Alpha Covenant Holdings keeps the quality of one product: a dated public-record receipt that says what named official files printed on a date, how the match was made, which sources did not answer, and a hash of the page. Quality here means: the receipt says exactly what the source printed, names what it could not read, never adds a verdict, and can be checked by a stranger.
Every procedure that touches a receipt from source file to published page, and every record those procedures create. The hosting provider's internal controls are out of scope and are not attested here.
Print what the file printed, on the date it was read, with the method shown. Where a source cannot be read, say so on the receipt. Never score, clear, verify identity or instruct a hold. When a receipt is found wrong, withdraw it in public, say why, rebuild it. Publish the evidence an auditor would otherwise have to ask for.
Owner-operator (Document Owner and Records Owner for every SOP; no delegate exists). The owner is responsible for: writing and reviewing every SOP; keeping every record in the Records Register current; logging each review; running the monthly management review; and keeping the successor-operator note current. There is no quality manager, no second reviewer and no contractor. This is a stated limitation, not a hidden one.
SOPs live in version control as text (backend/sops.py) and are published at /api/trust/sops. Each carries an id, version (date of last substantive change), effective date, owner, review cadence, and a change log. A change is made by editing the text, committing it with a message, deploying, and confirming the published version. Superseded text remains in version-control history. A review with no change is logged by the owner at POST /api/trust/sops/{id}/reviewed and shown on the SOP. A review past its due date is raised as a Sentinel finding on /audit until the owner acts.
Every record the platform makes is listed in the Records Register with: where it lives, who updates it, what triggers the update, how long it is kept, and whether it is public. The rule for records of what a file printed (receipts, held-file hashes, corrections) is retain, never edit: a wrong record is withdrawn and annotated, not deleted. Customer-submitted files are the exception: deleted within 30 days of termination per the agreement text.
Automatic, daily: the self-audit recomputes every registry hash and anchors the day's archive (SOP-07). Automatic, every 15 minutes: Sentinel (SOP-08). Automatic, weekly: dependency and vulnerability scan (SOP-10). Manual, monthly: the owner's management review (SOP-14) using the checklist in that SOP. Results of all four are public at /audit.
Any receipt or held file found to misstate its source is a Class B incident: withdraw, ticket at /corrections, rebuild, and change the procedure that let it happen (SOP-06). The ticket records the cause and the procedural change. Example on record: PB-CCN-307B0E.
Monthly, by the owner, against SOP-14's checklist: open findings, corrections, source states, review dates due, disk and backup state, customer records, outreach log. The review is written to db.management_reviews and summarized publicly.
Not a certification. No ISO 9001, SOC 2, ISO 27001 or HITRUST assessment has been performed. These documents are the owner's description of what is actually done, written so a reviewer can test each statement against the public evidence linked from it.