The MoonShot Engineered Standard
MoonFactory X — MoonShot
We moonshot. We don't wow. MoonFactory X builds production software against a single standard: executed precisely to specification, or razed and rebuilt. There is no partial credit, no diminished version, no MVP. What we ship runs in production, bears real load, and withstands scrutiny from anyone who opens it. We choose depth over spectacle and candor over polish. We tell clients what is true, build what was agreed, and own every layer of the work, from architecture to infrastructure to the last line deployed.
MoonShot or don't ship.
MoonFactory X — Human in the Loop
We engineer AI systems in the rare air where most never build and fewer still ship. One line holds without exception: the human stays in the loop. Our machines extend judgment; they never replace it. Every system we deploy defers to the person it serves, by design and by conviction.
The human decides. Always.
MoonFactory X — The MoonShot Engineered Standard
Definition. The MoonShot Engineered Standard is the condition a system must meet before MoonFactory X calls it finished. A system meets the Standard when it does exactly what was specified, under real load, in a hostile environment, and every decision inside it can be traced, explained, and defended. A system that meets part of the Standard does not meet it.
I. Specification Is Law. Every system begins with a written specification agreed upon before work starts. We build to it exactly. Any deviation requires a written amendment approved by the human who owns that decision. Undocumented behavior is a defect, even when it works.
II. Human Authority. Every AI system defers to the person it serves. No machine takes an irreversible action on its own. Any machine output that affects a person, money, data, or production is a proposal until a human approves it. Every AI decision can be explained, inspected, and overridden.
III. Hostile by Default. We assume the network is compromised, every input is adversarial, every dependency is suspect, and any operator can be impersonated. Trust is never inherited. It is verified at every boundary. Every process, account, key, and agent runs with the least privilege its job requires. Encryption in transit and at rest is the floor.
IV. Defense in Depth. No single control protects anything alone. We design so that any one layer can fail without the system failing. Each layer assumes the layer outside it has already failed.
V. Provenance. Every line of code, dependency, artifact, and configuration has a known origin. We pin versions, verify signatures, and make builds reproducible. If we cannot say where something came from, it does not ship.
VI. Traceability. Every change traces to a requirement, an author, a reviewer, and a commit. Every action in production traces to an identity and a timestamp. Logs are tamper-evident and retained. If an action cannot be reconstructed, the system is not finished.
VII. Two-Person Integrity. A system under Critical Designation operates under two-person integrity: no change reaches production on one person's authority, someone who did not write the code reviews every merge, and a second person witnesses every privileged action. Critical Designation is written into the specification before work begins, on this ground alone: failure of the system would be irreversible, or would touch life or money, or production at scale. The client sees the designation and the reason for it, and the designation is lifted only by written amendment. Every merge, designated or not, is reviewed by someone who did not write it. No machine is a person under this article.
VIII. Known Failure. We list every failure mode before launch. Each one fails safe, fails loudly, and can be recovered from. An unknown failure state is a defect. A backup counts only after we have restored from it.
IX. Proven Under Load. We test every system against the load it will carry, plus margin, and against the inputs built to break it. A path we have not tested is a path we do not ship.
X. Total Ownership. We own every layer we deliver, from architecture to infrastructure to the last line deployed. There is no “not our layer,” and we ship no black box we cannot open.
XI. Candor. We disclose defects when we find them, to the client, in plain language. Status is reported as it is, not as we wish it were.
XII. Raze and Rebuild. Work that fails the Standard is never patched into compliance. We destroy it and do it again.
Engineered to the Standard, or not at all.