Logo
Back to Proofs

Reflect Mode

The System Can See Its Own Structure, Safely

A read-only view that lets the system, and the people who build it, look at its own structure the same way they look at any other project, without the risk of changing anything by accident while looking.

What Reflect Mode Actually Is

The system's own structure is available through the same query view that is used for ordinary projects. It appears there as a separate, clearly marked entry, so it is never mixed in with regular work, and it cannot be edited through this view.

What this makes possible:

  • The system's own structure (its records and how they connect) can be looked at; it is not a black box
  • Every look is written to a permanent audit record that cannot be deleted
  • Any attempt to change data or send a message while in Reflect Mode is rejected, not just discouraged

Why Read-Only Enforcement Is the Point

This is not a dashboard added for show. The rule is enforced in the server, not only hidden in the interface:

  • Requests to change data or send messages are rejected with a clear error while Reflect Mode is on. The check happens in the server, not just in a disabled button.
  • The audit record of every look is protected by a database rule that blocks deletion, so the record of who looked at what, and when, cannot be quietly erased.
  • Sign-in is still required underneath Reflect Mode. Looking does not bypass access control; it adds a further limit on top of it.

What This Made Possible

Looking at its own structure safely was a prerequisite for later work, not an isolated feature:

  • Versioned change: comparing two states of its own structure needs a safe, read-only way to see both
  • Dated snapshots: keeping a copy of its structure at a point in time depends on being able to read it consistently
  • Safe creation of new specialized parts: copying part of its structure into a new part starts with being able to see that structure clearly

What This Proves, and What It Doesn't

This proves the system can be inspected safely: the read-only rule is enforced in the server, so looking does not mean touching, and the audit record of every look cannot be deleted. It does not, on its own, mean the system is running continuously or serving any customer traffic. It is a capability that exists and has been verified, like everything else on this page. It was certified on 2026-05-31 against 8 independent criteria (one combined query view, read-only enforcement on both the change and the message endpoints, an audit trail that cannot be deleted, and response-time limits), and all of them passed.

How It Works

These pages explain how each claim is designed to work. We are adding evidence you can look at yourself, one proof at a time.