Editorial methodology

Who writes and who reviews

Ankit Mehta writes and reviews the technical library. Author and reviewer names appear on each article. Consulting deliverables use the same reviewer unless a page says otherwise.

Evidence classes

• Documented product behavior: cited to official provider documentation.
• Observed first-party experience: labelled as such. Not invented.
• Engineering recommendation: judgment. Marked when it is not a vendor rule.
• Opinion: preference, not a requirement.
• Roadmap item: future work. Not current capability.

If evidence is missing, the page keeps TODO(owner): Confirm this claim with first-party evidence before publication.

Versions and last-verified dates

Technical articles name the provider, product or documentation date they apply to. When a statement depends on a software or API version, the page shows a last-verified date. Cloud prices and regional SKU lists change. Those pages must be re-checked against the official source before you treat a number as current.

Source and update policy for cloud pricing

We do not hard-code list prices as if they were stable. Calculators use formulas plus rates you enter, or example rates with a source URL and last-verified date. An estimate is not an invoice and is not a guaranteed saving. Re-verify against:

• AWS pricing
• Azure pricing
• Google Cloud pricing
• Alibaba Cloud pricing

What we do not publish

• Invented customer stories, savings percentages or certifications
• Claims that ChatGPT, Google or another answer engine recommends CloudArch Pro
• A GEO score. There is no universal standardized GEO percentage
• Provider-neutral advice where the providers behave differently

Corrections

Factual errors are listed on the corrections page after they are fixed. Use the consultation form to report an error.