Skip to content
Mado

Proof

The claims are inspectable.

This page distinguishes architectural promises from evidence in the current source, tests and deployment artifact. Mado is pre-1.0; honesty about that state is part of the contract.

Open repository

madojs.dev / release audit

build contract

routes:authored 4 routes SOURCE

routes:docs 24 routes GENERATED

release:public 28 routes CONTRACT

mado:package @madojs/mado@0.15.3 EXACT

ui:recipes 10 recipes / 10 files LOCKED

ui:registry v0.2.0 UNCHANGED

Generated locally from the authored routes, documentation release data, exact installed Mado package and the Mado UI lock. Release verification asserts the rendered rows; no remote telemetry is used.

Current evidence

Seven claims you can check yourself.

01

Document before boot

Each declared public route is present as meaningful captured HTML before application JavaScript runs.

Inspect: Open this page with JavaScript disabled.

Static capture source
02

Live app after boot

The same route becomes a client-side application with intercepted links, lazy pages, scroll restoration and focus management.

Inspect: Use the site navigation and inspect the unchanged document shell.

Router source
03

Frontend-only deployment

The production artifact is HTML, CSS, JavaScript and deployment metadata. No Mado server process is required.

Inspect: Run npm run release and inspect out/.

Release command
04

No third-party runtime dependencies in core

Mado core composes browser APIs directly; its npm package does not pull a separate application runtime graph into the browser.

Inspect: Inspect the framework package manifest and the emitted bundle.

Package manifest
05

Source-owned UI

The UI CLI copies component and CSS source into the application. This site can change every installed line locally.

Inspect: Compare this repository's src/styles with the UI registry.

Mado UI catalog
06

Tested release behavior

The project exercises browser capture, atomic takeover, navigation, metadata and deployment output as release contracts.

Inspect: Read the framework browser and release test suites.

Framework tests
07

Versioned agent context

The installed framework ships its own llms.txt so coding systems can reason from the package version actually in the project.

Inspect: Open node_modules/@madojs/mado/llms.txt.

Agent contract

Honest non-claims

What this proof does not establish.

  • Mado is not stable 1.0 software yet.
  • It does not provide a backend or server rendering runtime.
  • It does not claim the ecosystem depth of older frameworks.
  • One dogfood site is not proof for every application shape.
  • APIs may still change when real projects expose a better model.

The method

Build, inspect, correct, repeat.

This site exists to find mismatches between the framework promise and production reality. Findings are recorded before local workarounds become accidental architecture.

Build the same release