Skip to content

Projects

Systems that stay alive

We build systems to solve concrete problems in an operation.

Here we explain what had to change, what we built and why it is still useful.

What counts as a project

We do not show ideas, isolated tests or a collection of screens. We show work that entered an operation, solved a problem and had continuity.

  1. 01Concrete problem
  2. 02System built
  3. 03Sustained use

Projects

Pending

Projects will be added when there is real, publishable content to explain the problem, the system and its use.

Automate with judgment

Automation is not an open request and a wait. It is defining what enters, what must happen, what is checked and what happens when something fails.

AI can take part. Responsibility stays inside the system.

  1. 01Input

    Defined data

    A datum, an event or a request with a known shape.

  2. 02Rules

    Written criterion

    Conditions decided before the process runs.

  3. 03Execution

    Repeatable work

    The same input receives the same treatment.

  4. 04Control

    Failure foreseen

    The output is checked and what happens on failure is defined.

  5. 05Result

    Concrete use

    A person or a system receives an output it can use.

The problem first

Each project starts with an operation that needs to change. If you have one, explain it.

Contact