01The practice
Expertise, not headcount.
Koinon Engineering is a boutique practice across five disciplines, staffed by the people who do the work. No pyramid, no deck, and no juniors learning on your budget.
Book a 30-minute diagnostic, opens cal.com in a new tab01.1Why the work exists
Eleven systems, eleven answers
Each answer is correct inside the system that holds it. None of them was ever agreed. One of them is the number the board saw. The disagreement surfaces the week a regulator asks, and by then it is a year old.
- Koinon
- One agreed definition. A named owner, a date, and all eleven tracing back to it.
Illustrative of the pattern, not a record of one organisation.
01.2The governed spine
Governance is the discipline underneath the other four
Every practice at Koinon answers to the same test: when two systems disagree, is there a written way to resolve it. This is not a compliance exercise. A business that knows what its own terms mean can change course in a quarter, where one that does not spends the quarter arguing.
A system that cannot show all three when a regulator, an auditor, or a new engineer asks has not finished, whatever it does in production.
- 01
Definition register
Names what a term means and who owns it. One place a disagreement gets settled, rather than five reinterpretations downstream.
- 02
Lineage map
Shows which systems use that definition, and every hop a number takes to reach a report. Traceable to source, not to two transformations back.
- 03
Decision record
Shows when a definition changed and why, written at the point the call was made rather than reconstructed from a chat log six months later.
01.3Practice
The five, and the problem each one answers
- 02.AAI and Data GovernancePrivacy Act 1988, automated decisions from Dec 2026Not a policy document, and not a committee. The written way a disagreement between two systems gets settled, and the practice the other four are built on.
- 02.BData EngineeringConsumer Data Right, ACCC accredited clientsAsk most data teams where a number in a monthly report came from, and the honest answer stops two transformations back. These pipelines answer the whole way to source.
- 02.CData VisualisationOne agreed definition before the first chartTwo dashboards can show two different figures for the same quarter, both technically correct, because nobody agreed the term before either was built.
- 02.DSoftware EngineeringOne decision record, dated at the callMost enterprise software carries decisions nobody can find again. These systems keep the record after the person who made the call has gone.
- 02.EAgentic AI EngineeringAPRA CPS 230, operational riskAn agent that can act is not the hard part. An agent that can prove, afterward, exactly why it acted is.
01.4Method
Three stages, and each one hands something over
Every engagement runs the same three stages, whether it builds a pipeline, a dashboard, or an agent. What changes is the artefact in the middle.
01Entry
- Produces
- A written map of where your definitions already disagree, and a brief naming what the work will leave alone.
- Hands over
- The brief, before any build starts.
02Delivery
- Produces
- The system, and the record of what changed and why, written as it happens.
- Hands over
- The decision record as it grows.
03Handover
- Produces
- The three artefacts, written up as a package your team owns.
- Hands over
- Your engineers answering a question using only the record, with nobody from Koinon in the room.
01.5Commission the work
Systems that can answer for themselves.
Koinon is not built to stay. Every engagement ends with your own team able to run what was built, extend it, and answer for it.
A 30-minute diagnostic, not a sales call. You state the problem and leave with an opinion, including the opinion to take the work elsewhere. No proposal deck, no sales pitch, no wasted time.
Book a 30-minute diagnostic, opens cal.com in a new tabOr write, if a booking widget is blocked where you work. [email protected]
Sheet 04, the whole approach