An engineering control system built by one founder — covering humans, AI, evidence and long-term engineering reality.
$10,000 AGREED · $6,000 PAID — $6,000 IN CASH, BEFORE A PRODUCT EXISTED
A Las Vegas travel wholesaler with more than a decade of operating history agreed to pay $10,000 for the system and paid $6,000 of it in cash before any product existed. The customer also supplied the development hardware and a phone, and covers the monthly AI tooling cost. The balance is due when the system is usable. There is no written contract — the agreement is verbal, and it has been honoured in cash. The $10,000 covers their use of the system; there is no separate licence fee on top of it. The founder sends a development update every week. The customer has also agreed to introduce other businesses in the travel industry once the system is ready. No introduction has produced revenue yet, and commercial terms for those introductions have not been set.
This is one customer, in one industry, buying the business system. It is presented as a real prepayment and a real relationship — not as product-market fit, and not as a purchase of the engineering control layer.
This is what actually happened in the conversation that ended with $6,000 in cash.
I explained what the system does and why it is built differently. He was interested.
Then I asked him how his business actually runs.
He told me, one piece at a time. I spent at least thirty minutes just aligning with him. I did not know his vocabulary; he explained it and I still only half understood.
So I started mapping it in front of him — acting as the process analyst, while thinking about how the thing would have to be governed and operated.
When he finished, he said: the others are messy too, and every one of us does it differently.
I asked how messy. He said: let me show you the sheet.
Then he said: this sheet is only part of it. There is far more old, unresolvable mess behind it.
Every month, money is under-counted.
And to reconcile anything, someone has to go dig through chat histories across every tool they use.
That sheet is the data measured below.
One of those channels leaves no record at all. A spoken phone call is not a weak record — it is an absent one. Everything downstream is then a reconstruction that nobody can verify.
One sheet, several people. Whoever has time does it. In the end nobody can read it.
That sentence is the cause. The twenty-two different header structures measured below are the effect. He said it before anyone counted them.
He was not shown a product. He was shown his own business, laid out, for the first time. He paid $6,000 in cash.
Four years of booking records from a live travel wholesale operation, provided by the customer. The figures below were computed from the files themselves, not supplied as a summary.
| 2023 | 12,492 bookings61,066 travelers |
|---|---|
| 2024 | 13,740 bookings75,786 travelers+24.1% YoY |
| 2025 | 13,151 bookings79,994 travelers+5.6% YoY |
| Total | 39,383 bookings216,846 travelers+31.0% over three years |
| Period covered | 2022-01 → 2025-12 |
|---|---|
| Booking records | 39,383 |
| Traveler count | 216,846 |
| Monthly worksheets | 37 |
| Partner company name strings | 1,420 |
| Top 3 partners | 48.8% |
| Top 10 | 67.5% |
| Top 20 | 79.2% |
| 823 partners appearing once, combined | 2.1% |
| Peak month vs quietest | May 4,912 · Jan 1,646 — 3.0× |
| Distinct header structures across 37 sheets | 22 |
|---|---|
| Records with the traveler name missing | 10,902 · 27.7% |
| Values in the phone column that are not phone numbers | 88.5% |
| Company names appearing exactly once | 823 of 1,420 |
| Near-duplicate company names in a 600-name sample | 43 pairs |
| Records with no confirmation number | 958 · 2.4% |
| Records in the 2025 workbook whose tour date is 2024 | 5,322 · 40% of that file |
| Records in the 2023 workbook dated 2022 | 933 |
| Distinct tour codes for 39,000 records | 19,607 — each used 2.0 times on average |
| Cell comments — people writing notes inside the grid | 3,750 |
|---|---|
| Cells with a background colour | 50,909 · 6.3% |
| Distinct fill colours used as status | 37 |
| Anywhere recording what each colour means | none |
| Formula cells — calculation logic scattered across the grid | 88,269 · 4.9% |
| Values found in the column headed “Phone number” | 确认 · sz确认 · SZ确认 · 没收到voucher |
| Distinct departure times in use | 21 |
A colour is a decision. A comment is a conversation. A formula is a rule. All three are real business logic, and none of them can be queried, exported, verified or handed to the next person. When the person who chose the colour leaves, the meaning leaves with them.
| Upper RT — one product, four column names | 100 / 110 / 120 / 130 Upper RT |
|---|---|
| Upper PT — one product, four column names | 120 / 130 / 140 / 150 Upper PT |
| Times the Upper RT column was renamed in three years | 8 |
| Names used for the phone field in 2023 alone | Phone number → Cell → Phone → Phone number |
| Distinct column names across 36 sheets | 47 |
| Of those, columns that appear in fewer than 30 sheets | 33 |
| Column count per sheet | 19 / 20 / 21 / 22 |
To answer "how many Upper RT tours did we sell", someone has to know that four differently-named columns are the same product.
Nothing in the file records that.
There is no product entity here. A product is a column heading, and it changes whenever the price does.
That is where twenty-two header structures come from — and why the count comes out different every time someone does it by hand.
This is one customer's data. It is not a claim about the industry, and no other company's data is being described here.
The founder analysed these three files and showed the customer what was actually inside them: twenty-two different header structures in one year's workbook, a phone column where 88.5% of the values are not phone numbers, and no way to answer how many partners the business actually has.
The customer paid $6,000 in cash before any product existed.
They had not seen a product. They had seen their own data.
Only counts and percentages are published. No names, phone numbers, invoice values or revenue figures from this dataset appear on this site or in any export.
The following is the account of an operator with more than a decade in this industry — someone who knows not only how his own company runs, but how his peers run theirs. It was given in conversation. It is informed testimony, not market research: no survey was conducted and no other company was asked directly.
NGF is positioned as “Weave your enterprise truth.” Describing their own operation, the operator described the exact absence of it: one sheet, several people, whoever is free does it — and in the end nobody can read it.
Two hours of conversation. No product. The customer said the system would help a lot of people — and paid $6,000 in cash.
Recorded as one person's account of their own market. It is not presented as verified industry data.
These figures come from a database audit of NGF dated 2026-08-08, not from a summary written for this website. Every one of them is recomputable from the schema.
This is system scale, not data volume. It shows how large the built system is. The customer's nearly five years of real operating data is a separate fact, stated separately.
For years I sat where the money had already been spent and the system was already live, and no one could prove it was working. Then I came to the United States and started building. There is no team here — I am the only developer I know. Architecture, governance, RCA, evidence, interface, across all three systems: one person carried it. So I built the control tower before the features, because I had nobody to catch me when I drifted. Now it catches me. What I want is simple. The thing that exists only in your head — you should be able to build it, with the best engineers standing beside you the whole way. That is what this is. When you use it, I am standing there too.
| Worked in | Ritz-Carlton · JW Marriott · Accor · Pullman · Novotel |
|---|---|
| In the U.S. | Licensed business owner and operator, 10 years |
| Experience | 15+ years |
Problem → Observation → Abstraction → Architecture → Build → Failure → RCA → Correction → Evidence → Next abstraction
The differentiator is not that one person worked hard. It is that repeated engineering pressure across three heavyweight systems was converted into reusable control architecture, then used to govern the next development cycle.
NGF and NAO are two heavyweight commercial systems, written by one person, for real businesses. Building them alone is what made the missing layer impossible to ignore: direction drifted, the AI reported success it had not earned, and nothing existed that could prove what was actually true. NCT is that missing layer. It now governs its own development, and the other two are migrating into it.
Short answers, consistent with the rest of this site. Where something is not proven yet, it says so.
An AI coding assistant writes code. NCT governs what happens around the code: project identity, relationships, authority, evidence, root causes, technical debt and memory. It does not replace the AI you use — it keeps a record of what was actually intended, changed, proven and accepted, so a session ending does not erase the project's history.
Adding a second or third model raises the odds of catching a mistake, but it does not change the structure: you cannot govern something that drifts with something else that drifts. The layer underneath has to be deterministic, and it has to keep growing as the models get stronger.
It is not accepted on the AI's word. NCT keeps AI self-report, test results, evidence, version identity, permission, authority and human acceptance as separate facts. A published case on this site records a delivery claimed as 22/22 where verification found 20/22, and the status stayed PARTIAL.
No. Decisions, requirements, failures, RCA, evidence, recovery points and handoff position belong to the project, not to any AI conversation. Storage location is not project identity, and changing the model does not mean re-telling the project's history.
There is one. A Las Vegas travel wholesaler with more than a decade of operating history agreed to pay $10,000 and paid $6,000 of it in cash before any product existed, and also supplied development hardware, a phone and the AI subscription. The agreement is verbal; there is no written contract. NCT itself has crossed into self-bootstrap — it now governs its own development, and two other commercial systems are migrating into it.
Because the discipline is applied to its own development first, where nobody can be exempted. The build archive runs from B0001 to B0133 with no missing numbers, no duplicates, and build numbers and timestamps in strict order. Every claim on the site has a proof entry stating what the evidence is and whether it can be shown.
Four cumulative editions — Entry, Standard, Professional, Enterprise — plus a separate workspace axis (W1–W3) based on responsibility rather than job title. Higher editions unlock interpretation, never history: the entry tier records the same base engineering facts as the top tier. NCT is not sold as AI tokens; customers bring the AI resources they choose.
The project's engineering reality stays with the project. NCT is designed around local, project-owned memory: a project can live on an internal drive, an external disk, an SD card, a NAS or a disk array, and moving it does not change what it is.