Luxor Contact →

The canon

Five phases. The same that built Luxor.

R.A. Schwaller de Lubicz spent twelve years measuring Luxor Temple and showed that its stones encoded the intelligence that built them. Every proportion was a witness; the temple was its own audit trail. We apply the same discipline to software — every commission runs through the same five phases, in order, with the principal signing at each gate.

1

Canon

Spec

Your intent, codified once. We sit with you until we can write down what the work is supposed to do, in language the principal would sign without amendment.

The pharaonic canon of proportion — the rule the work is measured against.

2

Proportion

Plan

An architecture and scope plan measured against the canon. Nothing in the plan that is not traceable to a canonical line. Anything that does not measure gets cut here, not later.

Schwaller's twelve years of measuring Luxor Temple — proportion as the audit of intent.

3

Operations

Build

The day's work. AI agents execute under human direction on a tight loop — you see iterations land on your stack within days, not quarters. Every diff has a person responsible for it.

The temple workshop — disciplined craft, repeated daily.

4

Witness

Audit trail

A living record of every decision and every change, queryable later by you, your auditor, your successor. The conversation IS the record — we don't reconstruct it after the fact.

The temple as its own record — every stone a witness to the intelligence that placed it.

5

Cartouche

Release

The signed, dated release. The principal's name on the work. Lifecycle ownership without giving up authority — we stay in the loop on the schedule you set.

The pharaoh's seal on the work — the principal owns the artifact and stands behind it.

Inside the frame

Six principles. No ceremony.

The phases above name what we do. These principles name how we run inside them, day to day, on every commission.

  • —We work in the channels you already use — WhatsApp, email, wherever the conversation lives.
  • —Days, not quarters. New requests become working iterations in days.
  • —Humans direct AI, not the other way around. Every diff has a name.
  • —Builds land on infrastructure you own — your domain, your data, your boundary.
  • —The conversation is the record. The day you need to explain a decision, nothing has to be reconstructed.
  • —You can leave whenever. The code is yours from commit one.
Commission a work