Trust layer · version 1.0

What can be verified in QazReport

Public transparency does not mean disclosing clients or sensitive data. It means separating facts, analytical assessments, scenarios, data cut-off dates, and methodological limits.

Six mandatory rules

A public page that fails a rule should not be used as evidence of the product's current state.

01

No invented authorship

Materials are attributed to QazReport or the analytical group. Personal names appear only when confirmed and approved.

02

As-of date

Every dated dataset or dashboard carries a cut-off date. An archive snapshot is not called live.

03

Method version

Experimental models are clearly marked; changes in thresholds or inputs require a new version.

04

Evidence and provenance

A traceable conclusion points to the source, selection rule, and known sample limitations.

05

Access level

Public, reference, and client are distinct. `noindex` is not a protected client channel.

06

Brief privacy

The public brief stores nothing on the site; it prepares a message in the user's mail client.

Roles are stated more precisely than promises

Project staffing depends on the assignment. The public site does not invent employees or disclose clients.

Public

Functional roles: political analysis, media intelligence, NLP, data, and infrastructure. General: info@qaz.report; research: research@qaz.report; data: data@qaz.report.

Project proposal

Named staffing, accountability, timing, legal framework, confidentiality, and delivery rules are agreed for the specific assignment.

Machine-readable verification

Public artefact map and checksums: artifacts.json. Research catalogue: research.html.