Skip to content
Content under review: biographies await validation and some images are placeholders.

Engineering principles

Our values guide how we understand a problem, make decisions and care for what we build. We put them into practice with technical rigour, international engineering standards as a reference and artificial intelligence applied with sound judgement and accountability.

Quality from the start

Quality is built into the earliest decisions. We address requirements, architecture, security and reliability from the start, with checks and traceable evidence throughout the lifecycle.

Shift leftWe bring quality, security and reliability checks into requirements and design.

  1. Requirements

    Clear needs and verifiable acceptance criteria.

  2. Design

    Architecture, threats and reliability objectives.

  3. Build

    Reviewed code and automated checks.

  4. Verify

    Tests and evidence linked to requirements.

  5. Release

    Reproducible deployments and rollback mechanisms.

  6. Operate

    Observability, incident response and learning.

Evidence accompanies every stage. Lessons from operations feed back into requirements and design.

Engineering practices

Quality engineering

Verifiable requirements, planned testing and traceability from requirement to test to evidence.

Security

Threat modelling at design time, code review and dependency and secret management from the start.

Service reliability and operations (SRE)

We set availability and response-time objectives, monitor how the service behaves in production and prepare reversible deployments. We learn from incidents to improve reliability.

Artificial intelligence with sound judgement

We use AI to support analysis, development and verification. We check its outputs, retain evidence and keep decisions and accountability with people.

Twelve values, twelve engineering principles

Each Principia value becomes a concrete software engineering principle, so the values show in how we specify, build, test and operate.

  1. 01

    Truth

    Evidence-based decisions

    Decisions and reports rest on traceable evidence. What is not known is declared unknown, never assumed.

  2. 02

    Practical wisdom

    Think before building

    Requirements, design and threats are reviewed before code is written; architecture decisions are recorded.

  3. 03

    Justice

    Honour what is due

    Respect for requirements, contracts, licences, privacy and accessibility: every party receives what it is owed.

  4. 04

    Courage

    Face the hard things early

    Risks and technical debt are tackled as they appear; failures are made visible and systems are designed to withstand them.

  5. 05

    Temperance

    Simplicity and bounded scope

    No over-engineering or speculative features: the least that solves the problem, done well.

  6. 06

    Humility

    Review and learning

    Peer review, retrospectives and blameless incident reviews: correction is welcome and we improve.

  7. 07

    Accountability

    End-to-end ownership

    Whoever builds takes responsibility for their work. Critical decisions have an identified owner and are documented.

  8. 08

    Hope

    Design for change

    Incremental delivery, reversible deployments and evolutionary architecture so the system can grow.

  9. 09

    Love

    Care for users and maintainers

    Usability, accessibility and support for users; code and documentation written for whoever maintains them.

  10. 10

    Gratitude

    Acknowledge what we receive

    Responsible use of open source: licences, attribution and dependencies kept maintained and up to date.

  11. 11

    Craftsmanship

    Craft and work well done

    Automated tests, continuous integration and clear criteria for deciding when a delivery is complete, applied consistently.

  12. 12

    Beauty

    Clarity and coherence

    Clean architecture, readable documentation and coherent interfaces that make the quality of the work visible.

From values to practice

  1. PrincipiaShared mission and values.
  2. Aelium engineering principlesStandards, quality, security and operations.
  3. QualitasAI agents and rule-based checks that put the principles into practice with evidence.

Reference standards

ISO/IEC/IEEE 29148

Requirements engineering.

ISO/IEC/IEEE 42010

Architecture description.

ISO/IEC 25010

Product quality model.

ISO/IEC/IEEE 29119

Software testing.

ISO/IEC/IEEE 12207

Software life cycle processes.

ISTQB

Testing terminology and good practice.

These references describe the framework our work is aligned with. They do not imply certification or accredited conformity.

Qualitas: our software factory

We are developing Qualitas, our software factory, to support work with reviewed requirements, documented decisions and traceable verification. It combines specialist AI agents and tools that check against explicit rules, with professional review and human accountability for the results.