RED PRESS
Our standards
Red Press is written to a public sourcing standard. Every claim is traced, dated, and checkable. Holding ourselves to rules readers can inspect is what makes the section worth citing.
The sourcing standard
Three tiers, and what each is allowed to carry.
Regulator reports, court filings, company disclosures, official post-incident reports, standards bodies, peer-reviewed research, and - for our own claims - first-party records disclosed as such.
May carry a claim on its own. Always linked and dated. Required for any claim about a named company or product (or Tier 2 verified against Tier 1).
Established press and research houses with named authors and editorial standards.
Does not alone carry a claim about a named company or product - pair with or verify against Tier 1.
Posts, newsletters, blogs, podcasts, vendor research.
Never carries a claim alone. Quoted as opinion, attributed, linked to the original and to a third-party archived copy.
Hard rules
- Every claim traces to its origin. If we cannot reach the origin, the claim does not ship.
- Claims about named companies or products require Tier 1 evidence (or Tier 2 verified against Tier 1).
- Day-of-citation archives are taken through third-party archive services and linked. We do not host copies of third-party articles.
- Numbers carry dates. Estimates are marked as estimates and show their working.
- No superlative ships without a benchmark behind it.
- Corrections are public. Each piece carries a revision note; material corrections are logged on the corrections page. We aim to correct within 48 hours of confirmation.
- Every piece is dated. Publish date and last material revision are visible on the page.
- Every piece is versioned. Nothing is silently overwritten; changed pieces carry a revision note.
- Every piece carries a named author with a real profile. No team bylines.
Our own records
Claims about Red First can be sourced to documents we control - disclosed as ours, dated, attested by a named person with a public author profile, and marked for whether the capability is shipping or still design. That is Tier 0. Publishing the quoted line here turns a private record into something a reader can hold us to. Later pieces cite these excerpts the ordinary way.
A published excerpt is a one-way door: it is quotable against us forever. Material corrections go through Corrections, not silent edits.
Published excerpts
Each entry is the load-bearing sentence from an internal record, with its ratification date, attestation, maturity, and how you could check it.
-
One environment per client
ShippingOne client's data is invisible to every other client, enforced at the database itself, not just in application code.
-
The work spine
Agreed designWork is organised as a connected chain - North Star → Objective → Milestone → Task - and agents are given that chain as context before they start, rather than working from a prompt alone.
-
Removing personal data before the model sees it
Agreed designIdentifying details are stripped out before a prompt is sent to an outside model, and put back before the answer is shown to the person who asked for it.
-
Bringing an existing agent in
Designed, not builtAgents built in other tools are appraised and mapped into governed versions carrying an owner, a budget, an approval route and a scope - and the shape of that intake is defined as a schema rather than as a description of a process.
-
Where our agent layer came from
ShippingRedOS's agent layer originally forked Nous Research's Hermes Agent - a different project from OpenClaw. It was phased out as RedOS moved to a multi-tenant governed architecture and no longer forms part of the codebase.
When we get it wrong
Material errors are logged publicly. We aim to correct within 48 hours of confirmation. Corrections are never silently deleted. Until the corrections log ships fully, write to hello@redfirst.ai or see Corrections.