Evidence policy

Every factual statement on this site comes with its evidence, labelled with one of four statuses. The labels say what kind of evidence it is, not how good the result is.

The four labels

• Documented design. The statement describes how the platform is built, taken from its own configuration or documentation. It shows the design exists, not how well it works.
• Internal measurement. A figure from the platform’s own records, such as gate results or evaluation runs. It is self-reported and has not been reviewed by an independent party.
• Owner-reported. A statement made by the owner from their own knowledge, not drawn from a system record. It is published only with a date and scope.
• External context. Published research or vendor documentation that explains a problem or a practice. It never validates this implementation.

Dates

Three dates can appear, and they mean different things. Evidence as of is when a fact was observed. Reviewed is when the page was checked editorially. Published is when it appeared here. Rebuilding the site never changes the evidence date.

What is not claimed

• No figure on this site is independently audited.
• No figure is a productivity multiple. Counts of commits, lines of code, machines or gate runs describe activity, not outcomes or speed.
• Alignment with a standard is not certification. No standard has been assessed.
• Customer outcomes are not reported unless the customer has agreed.

Where a figure is disputed

Where two sources disagree about a number or a status, the figure is left out until the disagreement is resolved and recorded. A qualitative account is given instead.

Corrections

If you find a statement you believe is wrong, email craig.spong@syntegra.solutions. Corrections are made openly; earlier claims are corrected rather than silently changed.