---
title: "Fourteen Hours Building an Infra Page, Then an Audit of the Code"
canonical: https://dxdev.com/blog/building-ui-validates-architecture/
datePublished: 2026-08-16
---
Building the Infra page took 14 hours 44 minutes, and reading the client's code afterward corrected several stale facts.

## A prototype loaded with real data

The task was a customer Infra page. It started as a prototype, and I loaded it with one client's real infrastructure. Then I iterated on it hard on feedback, until the page opened as seven collapsed categories. Each one drills into a detail page with linked cross-references and full history.

I also added staff view-as deep links, so a client's page can be shared straight into.

## Stepping back to read the code

With the page working, I stepped back and did a deep audit of the client's repo, to answer what the admin app actually does. The audit corrected several stale facts.

## Two reviewers

Then came a two-reviewer design pass. One was a [Manus run](/blog/manus-file-exchange/). The other was a [Codex run at high effort](/blog/separate-build-model-from-review-model-codex/). Manus said to revise before expanding the prototype, and to use a governed, first-class Infra graph while preserving the existing `Record` type and its slot taxonomy. Codex said to revise before implementation.

The design pass settled on an architecture that carries audit, handoff, and a customer's own AI.

## From prototype to a filed program

The work is now a filed program: a set of tickets in dependency order, gated on standing up a real test database. The ledger for the whole program sits on a single ticket, so a fresh session can pick it up cold. Two findings from the client repo went into separate tickets, because they need my partner.

The test database comes first.