Trust record / Editorial

Published standard

Editorial trust begins with a clear record.

SecFlow states how learning material is presented today, which controls are visible and which evidence is still being formalised.

Published by
SecFlow Content Team, a collective product-team label
Certification status
Independent; no certification-body endorsement
Correction channel
hello@secflow.app

Authorship

The current byline is collective, not credential evidence.

Public learning pages identify the SecFlow Content Team as author. Named individual authors, qualifications and per-item reviewers are not currently published. The collective byline should not be read as evidence of a specific professional credential or independent review.

Publication standard

Content should make its scope and status legible.

Scope

State the decision skill or governance topic the material is intended to practise.

Status

Use Available, Beta, Preview or Planned without presenting future depth as current.

Independence

Do not imply endorsement by ISACA, ISC2 or another certification body.

Claims

Avoid guarantees, unsupported usage statements and unverified originality claims.

AI assistance

Do not imply that lesson feedback is generated live when it is stored content.

Corrections

Provide a contact route and revise material when a substantive issue is confirmed.

Evidence status

Provenance and review records are not yet complete across the catalog.

Until those records are available, SecFlow should not describe every item as independently reviewed or make a catalog-wide originality claim.

Current

Structured lesson fields and stored coaching are visible in the product. Public pages can describe those mechanics directly.

To formalise

Per-item source records, named reviewers, review dates, correction status and publication eligibility require a consistent catalog-wide record.

Corrections

Report a factual, attribution or quality concern.

Send the page or lesson reference, the specific concern and any supporting source to hello@secflow.app. Support questions can be sent to support@secflow.app.

See also the responsible-AI disclosure.