flintspark Book a demo

Editorial and AI-use policy

This policy says how flintspark's content is written and checked. AI agents draft most of it, and a person on the team reviews and approves each page. Claims are checked against our architecture documents, and statistics are sourced and dated.

  • Who writesThe flintspark team
  • AI in draftingAgents draft; a person approves
  • ClaimsChecked against the docs
  • StatisticsSourced and dated
  • CorrectionsEmail us

Who writes flintspark's content?

The flintspark team, with AI agents drafting most pages. Pages carry no personal bylines; the author is "the flintspark team".

Every page is read and approved by a person on the team before it is published.

A sketch of the process, not a screen from the product.

How is AI used in our writing?

AI agents draft most pages; a person on the team reviews and approves each one. The agents do not decide what is true.

  • AI is not used to invent statistics, quotes, people, reviews or customers.
  • Anything an AI tool suggests is checked against the sources below, like any other draft.
  • This site is written for people, and nothing on it is hidden or addressed to AI systems.

How are claims checked?

Every statement about what flintspark does is checked against our architecture documents and a table of approved claims before it is published.

Planned work is labelled in words, so a reader can tell what exists today from what does not.

  1. BuiltWorks today and is described in the architecture docslabel
  2. In buildBeing made now; not available yetlabel
  3. On the roadmapPlanned worklabel
  4. Under considerationNo committed planlabel

How are statistics sourced?

An outside statistic goes on the site only after we have checked it at its primary source, and it always shows who published it, the title, the publication date and the date we accessed it.

We re-check statistics within 180 days, and we do not round figures up or merge two figures into one claim. Product figures come from our own run reports, are labelled as demo runs, and are never presented as customer results.

How a source line reads

Publisher, title of the report, publication date. Accessed on the date we checked it.

The pattern, not a real citation.

How are corrections made?

If you find something wrong, email us with the subject "Correction" and tell us the page and the line. We check it against the sources, fix the page, and reply to you.

When a correction changes what a page says, we note the change on the page.

Email a correction

For how flintspark itself keeps people in control, see the trust and safety page.

See Flint run

Bring one workflow you'd rather not do by hand. We'll show Flint learning one like it, and stopping before anything it can't undo.

We reply from hello@flintspark.ai.