How we write, source, and correct published content
This is the working policy for everything published under the QUANT LAB USA brand — blog posts, case studies, service pages, and city pages. It is also the standard our reviewers hold every draft against before publish.
Last updated:
Principles
Named authors only
Every long-form post on this site is attributed to a real, named author with a /authors/<slug> bio. We do not publish ghostwritten or AI-generated bylines, and we do not buy guest posts from link-builders.
Written from inside the work
Posts come out of live engagements — quotes we have received or sent, code we have shipped, pentests we have run. When we cite a number, range, or methodology, it reflects work we have done or are doing.
Cite authoritative sources
Any claim that is not common knowledge gets an inline citation to a primary source. We prefer .gov, .edu, peer-reviewed material, official vendor documentation, and standards bodies (OWASP, NIST, MITRE, CISA) over secondary blog posts.
Editorial review before publish
Every post is reviewed by at least one additional engineer or security practitioner on staff before publish. Reviewers check technical accuracy, citation integrity, and whether the conclusion actually follows from the evidence.
Corrections are public and dated
When we get something wrong — a number, a name, a methodology — we update the post in place, add a dated correction note at the bottom, and re-issue the modifiedTime in the article schema. We do not silently delete or rewrite errors.
The 5-step editorial process
1. Draft
An author writes the post from a working knowledge of the topic. Quotes from live work are anonymized only when client confidentiality requires it.
2. Source pass
Every factual claim that is not common engineering knowledge is annotated with a citation candidate. The author finds the highest-authority primary source available and links inline.
3. Technical review
A second engineer or security practitioner on staff reviews the post for accuracy, validates citations, and challenges weak conclusions.
4. Copy & schema
Final pass on copy, byline, dates, reading-time estimate, JSON-LD Article and Person schema, and the editorial footer.
5. Publish & monitor
Post goes live. We monitor for reader feedback at beltz@quantlabusa.dev and update the post (with a dated correction note) when needed.
AI usage disclosure
We use AI tooling (Claude, GitHub Copilot, ChatGPT) the same way a working engineer uses any IDE plugin — for drafting, rewording, and surfacing relevant references. AI-generated prose is always reviewed, edited, and signed off by a named human author before publish. We do not autopublish AI output under a real byline, and we do not invent author personas.
Where a post or section is materially the result of AI synthesis (e.g. a large summary of public benchmarks), we disclose it inline.
Sponsorship, advertising, and affiliate disclosure
QUANT LAB USA does not run paid advertising on the blog and does not accept sponsored posts. Tooling and vendors mentioned in posts (Next.js, Stripe, Vercel, Postgres, Resend, Sentry, etc.) appear because we use them in client builds, not because of any commercial relationship.
Where an affiliate or referral arrangement exists, the post will say so inline. As of the last-updated date above, no such arrangements are active.
Conflicts of interest
QUANT LAB USA INC is a software and security services firm. Posts that recommend buying or building a system are written with the obvious caveat that we sell those services. We try to declare it openly — if a post points you at our service page, it is also pointing you at a billable engagement. When the honest answer is "you don't need us," we say so directly.
Corrections & takedown requests
See something wrong? Email beltz@quantlabusa.dev with the URL and the issue. We respond to genuine correction requests within five business days and update the post in place with a dated correction note at the bottom.
For full takedown requests (e.g. a former client wants their name removed from a case study), see the contact line above — we generally honor reasonable requests.
Read about the team
Bios, credentials, and expertise areas for every author who publishes on this site.