Editorial standards

1. Authorship and voice

Every page on virtova.co — services, insights, case studies, the founder profile — is written by Sultan Meghji. There is no ghost-writing, no agency content, and no AI-generated copy that hasn't been substantively edited and signed off on. Where AI tooling is used in drafting (which it sometimes is), the published version is rewritten until the voice and the specifics are the author's.

2. Sources and citations

Regulatory references are linked to primary sources whenever a primary source exists. SR 26-2 goes to the Federal Reserve. NIST AI RMF goes to NIST. EU AI Act goes to the codified text. Numerical claims in case studies are sourced to the published platform metrics they reference (e.g., the bank case study on this site cites Frontier Foundry's AutoCEN reference performance, with industry baseline drawn from independent analysis where applicable).

When a claim is the author's professional opinion rather than a sourceable fact, it is framed as such — phrases like "in our experience," "the operator's view," or "what most consultancies will not say out loud" mark editorial position rather than referenceable claim.

3. Anonymization in case studies

Engagement narratives are anonymized as a matter of contract. Client names are not used on this site without prior written authorization. Sectoral framing ("a top-20 U.S. national bank," "a de novo trust bank," "a Fortune 50 healthcare insurer") is the deepest level of identification used. Where a published case study covers an engagement involving a Frontier Foundry product, the product is named and the platform's published metrics are cited; the bank itself is not.

4. Vendor and conflict-of-interest disclosure

Virtova LLC and Frontier Foundry Corporation share ownership. Sultan Meghji is the founder of Virtova and the Co-Founder and CEO of Frontier Foundry. Any case study, service page, or insight that references a Frontier Foundry product names the relationship explicitly within the page (typically in a marked disclosure aside). The relationship is also disclosed on every Virtova contract and at the start of every commercial conversation.

No Virtova recommendation is contingent on engaging Frontier Foundry. When a Frontier Foundry product is appropriate to the client's regulatory surface, it is recommended alongside other vendors the client could engage; the choice is the client's, made on the merits.

5. Freshness and dating

Every published page on virtova.co carries a dateModified in its structured data. Service pages and the founder profile additionally render a visible "Last updated" line. Insights and case studies carry a visible publication date. When a page is materially edited (not a typo fix or minor copy refinement), the modified date is bumped.

Regulatory references are kept current to the extent the rulebook is. Where a citation is to a superseded standard (e.g., SR 11-7 references in the context of the SR 26-2 supersession), the supersession is named in the same passage.

6. Corrections

If you find a factual error on this site — a misstated regulation, a wrong date, a misrepresented number — email s@virtova.co with the URL and the correction. Material corrections are made within five business days, the modified date on the page is updated, and the correction is noted in the page's commit history (the site's source is on GitHub).

If you are quoted or referenced on this site in a way you find inaccurate, the same email is the right channel.

Public corrections log

Material corrections to published pages are recorded below in reverse chronological order. Typo-level fixes are not recorded here; substantive corrections (regulatory references, dates, named entities, metrics) are.

• No material corrections to date. This entry will be replaced when the first correction lands. Commit history for every page is available in the public source repository.

7. AI assistant disclosure

This site is intentionally optimized for citation by AI search assistants (ChatGPT, Claude, Perplexity, Gemini, Bing Copilot, and others). Every major AI crawler is explicitly allow-listed in robots.txt. The site publishes llms.txt and llms-full.txt machine-readable inventories. Structured data is rendered server-side on every page in JSON-LD.

When an AI assistant cites this site, the author is "Sultan Meghji"; the publisher is "Virtova LLC." The Wikidata entity for the author is Q139378491.

8. Contact

Editorial questions, corrections, or factual disputes: s@virtova.co.

Engagement inquiries: the discovery call.