The company is the demo.

Code got cheap; proof became the scarce asset. Every AI vendor claims governance. h|ve shows the record: the platform is built with the platform itself, and the status of each piece, what already runs and what is still under construction, stays here, open and checkable.

h|ve inside the h|ve Platform

h|ve Platform Changes screen: every card that changed in the period, who made it, the scope, the controls that ran and the outcome
h|ve Platform Changes, in the project where h|ve builds itself. Real data; card titles stay in the language they were written in.

What the h|ve trail itself records.

Volume of code impresses an intern; discipline impresses an architect. These are the rules h|ve applies to its own development, the same ones the platform sells.

Every spec has its DONE

No delivery is valid without the spec approved before and the completion record after. The spec-and-DONE pair is the merge condition, not a formality.

The engine is tested before the screen

Pure logic is proven against known vectors before any interface exists. The UI comes after the engine is verified, never in its place.

No shortcut in TypeScript

Zero type suppression, zero any. What does not pass the compiler does not ship, and that is a project rule, not a preference.

Conformance verified across pieces

The handoffs between modules are verified by checking, not by trust. What one piece promises is validated against what the other actually does.

Adversarial review before merge

Every delivery goes through a reading that tries to break it. What survives the refutation attempt is what goes into the record.

The merge belongs to the architect

Approving entry into the main base is a person-only transition, with a person credential. The same rule the platform imposes on the agent.

The exact numbers for each discipline, how many paired specs, how many test files, how many verified conformance combinations, are published here as the inventory is checked in the code. This page carries no number you cannot check at the source: a page that sells proof cannot claim what it does not show.

The company is the first operation governed by h|ve.

We build the platform with the platform itself. Specs, gates, adversarial review and versioned decisions form a real record, with successes, blocks and rework visible.

Dogfooding, not a customer case

The numbers below come from h|ve’s own repository. They demonstrate operating discipline; they are not presented as a customer outcome.

605
SPECs

written before the code

659
pull requests

counted in the repository itself

12,150
tests

with a CI gate on every PR

952,320
conformance cases

compared field by field across two independent implementations of the same decision; zero divergences

The same governance decision is produced by two paths that share no implementation, and both verdicts are compared field by field. Both denying is not enough: they have to deny for the same reason. The report is generated by command, never written by hand, is guarded against drift in CI, and publishes coverage axis by axis, including where it does not reach.

Inventory from the h|ve Flow repository, 30 October 2026. Method details and what is still under construction are public on the proof pages.

The ruler we apply to ourselves, applied to your team.

A short conversation to understand what your audit asks for and how the same discipline that records our work starts recording yours.

Talk to h|ve