Trust as a service
Named Trust-as-a-Service across 43 occurrences in the source material. The register splits into a risk-acceptor role and a fact-certifier role — distinct, payable, and warranted, not a courtesy credential.
The fact-certifier as a payable role
A fact-certifier does not just state an opinion about a claim's reliability; the design specifies two prices for the service, and a warranted output — a certification that carries consequence if it turns out to be wrong, not a disclaimed guess. The stated aim: "trade on facts and evidence rather than attention." An outlet's business today is largely attention; this design proposes a parallel market trading directly on verified facts and evidence packs instead.
Decoupling weight from rank
Credibility, under this design, is a track record over time, calibrated by outcomes rather than assigned by title. The explicit goal: it "decouples the weight a statement carries from the volume, power, or rank of the person making it, so the quiet person who is usually right is heard and the loudest or most senior voice does not automatically win." A junior analyst with a strong, checkable track record on a narrow domain could, in principle, carry more calibrated weight on a claim in that domain than a senior figure with a weaker record on it.
The liability the corpus notes but does not size
Selling trust makes the seller a target. A fact-certifier issuing warranted output has created a liability surface for themselves — a wrong certification is not just an embarrassment, it is a claim against a warranty. The source material notes this tension explicitly and does not attempt to size it: how large the liability exposure actually is, and what insures against it, is not specified anywhere in the corpus.
For an agent
No fact-certifier role, warranted certification, or Trust-as-a-Service product exists or runs on any sgit.ai property today — this page describes a design. See /shipped/.