Subject expertise
Checks the substance, examples and definitions against the glossary.
Authors and review
Who writes, who checks, who approves.
Every piece of Aive content follows the same path: a brief, primary evidence, answer-first drafting and several reviews before publication. Sensitive pages are reviewed on a fixed schedule.
How is Aive content written and checked?
Aive content starts from an intent brief and an inventory of primary evidence. It is written answer-first, then reviewed by an expert, by Product for availability, by Legal and Security for statements and data, and by SEO. After design and accessibility QA, it is published, noted in the changelog and reviewed on schedule.
- Primary evidence
- The original source of a statement: documentation, contract, Trust Center, customer case or dated press release.
- Periodic review
- A check at 90 days for prices, engines, comparisons and integrations, and at 180 days for other pages.
Editorial process
Ten steps, from brief to review.
- 01Intent and audience briefThe question to address, the intended reader and the decision they are preparing.
- 02Primary evidence inventoryThe sources available for each planned statement.
- 03Answer-first draftingQuestion, self-contained answer, definitions, limits, proof, steps and FAQ.
- 04Expert reviewAccuracy of substance, checked by someone competent on the subject.
- 05Product reviewAvailability and status of every capability mentioned.
- 06Legal / Security reviewStatements, data, security, trademarks and publication conditions.
- 07SEO reviewIntent, internal linking, metadata, hreflang and structured data.
- 08Design, Accessibility, Performance QAReadability, contrast, keyboard navigation and rendering.
- 09Publication and changelogDated go-live and a note of the change.
- 10Review at 90 or 180 days90 days for prices, engines, comparisons and integrations; 180 days for other pages.
Reviewing roles
Every review has an owner.
Product
Confirms each capability’s status: available, to be validated, in development or not public.
Legal and Security
Checks statements, data, security, logos, third-party mentions and publication conditions.
SEO and QA
Checks intent, linking, metadata, hreflang, schema, accessibility and performance.
On every page
What the reader can check.
- Named authors and reviewers, once profiles are published
- Publication date and last update date
- Primary sources for statements
- Status of every capability mentioned
- Method and limits for every indicator
- Demos labelled “Demo data”
Author profiles
Profiles published with a verifiable bio.
Author and reviewer profiles will be published on this page with a verifiable bio, their area of expertise and the content they sign or review.
No profile is published without the agreement of the person concerned. In the meantime, every page shows its update date and points to its sources and to the methodology.
Frequently asked questions
Why are the authors not named yet?
Because an author profile must rest on a verifiable identity, bio and expertise, published with the person’s agreement. Profiles will be added as these validations are completed.
Who decides the status of a capability mentioned?
The Product review, with Legal and Security for sensitive statements. An unconfirmed capability is presented with its real status, never in the present tense if it is still in development.
How do I report an error on a page?
Contact the Aive team via the contact page, stating the page and passage concerned. The correction follows the same review path and is noted in the changelog.