Code Reality · Public sample · not the full book
What actually exists in the code?

CODE
REALITY

AI did not kill code. It removed the friction of generating it.

Generating code became easy. Deciding what deserves to survive became the hard part.

A controlled public sample from the bilingual book about code review, reality checks, and governance in AI-first projects.

Public sample · controlled excerpt
The central question

What actually exists in the code?

Not what the landing page promises. Not what the README describes. Not what the agent says it implemented. What exists.

The method

Four realities, two operational extensions, and one decision layer.

  1. Code Reality
  2. Flow Reality
  3. Memory Reality
  4. Promise vs Reality
  5. Secrets Reality
  6. Graph Reality
  7. Nex

Contents

Part I · The illusion and the new role

  1. Introduction
  2. Code That Looks Like a Product
  3. The collapse of traditional code review
  4. The engineer as guarantor

Part II · The realities of the system

  1. Code Reality
  2. Flow Reality
  3. Memory Reality
  4. Secrets Reality
  5. Graph Reality

Part III · Decision, governance, and application

  1. Nex
  2. Agents reviewing agents
  3. Review protocols
  4. Promise vs Reality
  5. Field Kit
  6. Closing

Appendices · Autopsies and Case Files

  1. Appendix A · The Syntax Autopsy
  2. Appendix B · Code Reality Case Files
Sample 1 · Chapter 4 · Code Reality

Written Does Not Mean Real

A file can exist in the repository and still not exist in the product. A component can be well written and never rendered. A route can be declared and never reached. A provider can be configured and never used. An endpoint can respond locally and still not participate in the real flow. A test can exist and still protect nothing important.

The common mistake is treating presence as proof.

Presence is only inventory.

Reality requires participation.

Code participates when it has a verifiable relationship with a real flow: it is called, rendered, reached, receives data, transforms state, produces an outcome, handles error, sustains a promise, protects a rule, or removes ambiguity.

If none of that happens, perhaps it will be useful one day. Perhaps it is an idea. Perhaps it is a draft. Perhaps it is residue. Perhaps it is decoration. But it is not yet operational reality.

Sample 2 · Chapter 5 · Flow Reality

The Happy Path Is Not Enough

Many products seem to work because someone tested the happy path.

The happy path is simple: correct user, correct data, correct environment, correct connection, correct key, correct response, correct expectation.

But real products live outside that comfort.

The user makes mistakes. The browser reloads. Payment takes longer. Email lands in spam. A field is left blank. The key expires. The integration responds slowly. The endpoint fails. The user does not know whether the process is complete. The admin receives nothing. The founder believes it works because it worked once.

A system that only works on the happy path has not been reviewed. It has only been demonstrated.

Field Kit preview

Code Reality Check

Use this when a feature, file, route, component, provider, integration, or test appears to exist, but you need to confirm whether it participates in the real product.

What actually exists in the code?

  1. Choose a promise or feature.
  2. Find where it appears publicly.
  3. Find the corresponding path in the code.
  4. Confirm whether it creates a consequence.
  5. Classify its state.
  6. Decide what to do.

This sample is not the full book.

Code Reality does not merely deliver a file. It gives you a method for reviewing reality in AI-first software.

AI generates. Nex decides. You are accountable.

Full edition: 583 pages, 14 chapters, two appendices, a bilingual glossary containing 62 terms and 372 definitions, PDF, EPUB, and a Field Kit with 33 controlled files.

The full edition is individually licensed and includes a named licence, watermark, and a controlled path for corrections and edition updates. A protected online reader is a future evolution.