Engineering evidence

Open work should prove capability, not inflate repository count.

We publish reusable working assets and technical thinking so clients can inspect how we structure discovery, governance and evidence before buying consulting.

Free reusable toolkits

AI use-case register

Track purpose, owner, provider/model, autonomy, human review, risk and evaluation.

Download CSV

Technology inventory

Record systems, ownership, cost, data, integrations, criticality, recovery and exit method.

Download CSV

Transformation evidence register

Separate baseline evidence, expected/modelled value, assumptions, confidence and measured outcomes.

Download CSV

Publication standard

  • Clear README, scope and intended users
  • Reproducible setup and test instructions
  • Security policy and responsible disclosure route
  • Automated CI and dependency monitoring where appropriate
  • SBOM and provenance for releasable software where practical
  • Versioned releases and changelogs
  • Licensing stated explicitly
  • No client secrets, private data or proprietary client material

External contribution principle

Accepted contributions to third-party projects are stronger evidence than forks or badges. We only count an upstream contribution when it is genuinely useful and accepted by the external project.