Company stage · First-party evidence
Noetfield as Customer Zero
Noetfield operates its own technology on its own real workflows before asking anyone else to. In enterprise practice this operating model has a name; this page states exactly what it proves and what it does not.
The practice, as the industry defines it
IBM describes operating IBM on its own technology across real internal workflows as being Client Zero. Microsoft calls the internal deployment of its products before customer release Customer Zero. GitLab defines Customer 0 as internal teams acting as first customers during validation, while noting explicitly that internal users do not replace actual customers. The terms describe each company's published practice; no affiliation or endorsement is implied.
What Noetfield runs on itself
Noetfield's own delivery pipeline is the first deployment of the Noetfield runtime. Software changes to Noetfield's systems run as governed software changes: scoped goals, bounded execution, separate-verifier acceptance, bounded repair, human promotion, and preserved receipts. The public website ships through claim gates that block unsupported statements. The completed governed replacement below is one such run, published with its verification history and receipt.
What this proves
The runtime performs real work under its stated controls for its first operator, with inspectable receipts, at founder-operated alpha stage.
Does not prove
External adoption, customers, revenue, certification, or performance at third parties. Internal use does not replace actual customers. A receipt is not certification.