Skip to content

HCI Software Development Standards ​

Last Updated Nov 11, 2026

Purpose and Scope ​

Definition of Production-Ready ​

These standards define what production-ready means for software at HCI.

Software is ready when it is:

  • Secure
  • Maintainable
  • Tested and able to scale

Software is not ready simply because it works or looks finished.

Development Modalities ​

HCI welcomes all modalities of software development: human-driven, AI-assisted, and AI-driven development.

We do not have different quality standards for one modality versus another. All must maintain the same high standards outlined in this document.

The reason why is trust.

AI tools let teams build, test and review software far faster than before. These standards are written to make that speed safe: they are also published in a form AI agents can load directly, and most of the checks they describe are automated.

Scope and Applicability ​

These standards apply to every internal software project. That covers platform work and integrations as well as one-off tools, websites and AI-assisted projects.

The standards are principles, not a technology stack. Teams choose their own languages, frameworks and tools. Product-specific developer guides, such as the Hope.Cloud guide, can add stricter rules for their own platforms, but none can lower the bar set in this document.

Standard Levels ​

The standards have three levels:

  • Requirements apply to every project and are checked before a production release.
  • Recommendations are good practice whatever the stack: a project that does not follow one records the reason in its documentation.
  • Preferences are the default choices at HCI where several good options exist: a project is free to choose differently and simply notes what it chose.

Maintained by the HCI software department.