Skip to content
QAISSStart

QAISS — A technology engineering company.

  1. Measure.
  2. Reason.
  3. Engineer.

The discipline behind systems that have to be right.

We build complete systems from nothing, and make existing ones legible again. Same method, same order, either way.

Inside a difficult system: The behavior that matters is emergent. Nothing is built yet, and every early decision forecloses ten later ones. The documentation describes a system that no longer exists. Everyone is right about their part and wrong about the whole. It has to be right the first time, in a domain nobody here has measured. Every proposed fix is defensible. None of them are measured. It cannot be stopped to be understood. The cost of being wrong is not on any dashboard. Difficult systems are not argued into order. They are measured into it.

02

The QAISS Loop

The order in which we are willing to do things.

Readings from the real system. Each carries its error bar.

The first engagement

One discipline. Two ways in.

The order never changes. What changes is what there is to measure on the first day.

A

Measurement period

A system already exists.

It runs, and something about it can no longer be explained.

We instrument what is already there until its behavior is visible, under real load, and produce a baseline with a written statement of what we found. It is frequently the point at which the original brief is revised.

  • A baseline taken under real load
  • A written statement of what we found
  • The instruments, documented and yours
Start with a measurement

B

Definition period

It does not exist yet.

There is nothing to measure — so we measure the ground it has to stand on.

Who it is for, what it must never get wrong, and what has to be true for it to work at all. Then we build it: interface, services, data, deployment — the whole system, with its instruments in it from the first commit rather than retrofitted after it hurts someone.

  • The constraints, written down and agreed
  • A complete first system, running in production
  • Measurement built in, not bolted on
Start something new

Both are defined in advance, bounded, and stoppable by either party at the end of the period. What we build to see your system stays with you.

03

Six disciplines. One machine.

The same way of working, pointed at six layers of the same system.

3.1

Software Engineering

Structure that survives the next ten changes.

We do notpropose a rewrite for a system we have not measured.

They are not bought separately, because they do not work separately.

04

The engine

We build the method systems are built with.

01 / 04

Operation yields readings.

In force

§ 8

Build Once. Learn Forever.

Decisions are recorded with their reasoning, so that a future change can tell whether the constraint still holds. Methods that prove themselves are written into the way the next project starts, which is what makes this Playbook a document that changes.

The Playbook — eight principles, Rev. 1

Still open

We would rather this section stay empty than fill it with work we have not done.

Labs — the open register

Order is measured into being.

Most companies build software.

QAISS engineers systems.

Most companies sell capability.

QAISS practices a discipline.

Most companies present outcomes.

QAISS makes decisions defensible.

Most systems are instrumented after they hurt someone.

QAISS builds them measurable from the first commit.

06

The platform

Five parts. Each is a different answer to the same discipline.

07

Open a technical conversation

Two ways in. Pick the one you recognize.

Select one

It changes the questions, nothing else. Both reach the same engineers.

Neither fits

Write a paragraph in whatever form it comes out, to the address below. A message that does not answer any of these questions is still a message we will read and reply to.

[email protected]