What we publish, and what we refuse to.
This publication exists to show, with evidence, that Veho is a technology company. These are the rules that keep it honest. They are not aspirational — a post that breaks one of them does not ship.
Numbers policy
Every production figure runs as a receipt: a date-stamped claim with unit and context. Figures are verified before a post publishes them -- founder-attested or unverified numbers do not run until confirmed.
Named bylines
Every post carries a real name, role, and team. Company-voice authorship is not representable -- if you build it, you can byline it, regardless of title.
The HN bar
Content is non-promotional problem/solution writing that survives Hacker News-grade scrutiny: real trade-offs, real failure modes, no marketing framing.
Single approver + 48h legal SLO48h SLO
Every post has exactly one named approver, never a committee -- the SVP of Engineering/Data Science by default, or a named per-post delegate. Legal has 48 hours to flag concerns; silence is not a veto and never blocks publication indefinitely.
Out-of-scope content
Marketing, trend, and announcement content stays on the corporate blog. There is no internal-only tier, no aggregating externally-hosted team content, and no decorative "AI" tag -- AI work files under the problem pillars, Building at Veho, or the curated AI @ Veho surface.
Data hygiene and corrections
Screenshots and figures must never expose customer or sensitive operational data -- checked on every approval. Errors are fixed by a follow-up PR (revert + redeploy) with a visible correction note; we do not silently edit a published claim.
// No trackers. No cookie banner. Static & instant.
// The analytics are first-party and cookieless.