Project publication policy

Evidence supports results. Authorization enables publication.

Published accounts distinguish client deliveries, anonymized client deliveries and capability demonstrations. Demonstration data does not substitute for client results.

A business team reviewing the implementation scope

Publication boundaries

A public source can establish a project’s name, problem, scope and workflow. It does not automatically establish client authorization, acceptance or outcome evidence.

  • Teaching cases remain explicitly hypothetical and are not presented as client deliveries.
  • Product projects and engineering methods are not presented as client success stories.
  • Figures and client testimonials are not added when the source does not provide them.
  • Projects containing only placeholder information are not listed as completed deliveries.