An invoice is three computations. A habit tracker is a list with a boolean per row. A budget is a spreadsheet with a dashboard view. We built all of these as web apps — with servers, databases, auth flows, and cloud infrastructure — because the file formats we had didn't support reactivity.
Mere is a file format that does. A .mp.html file declares its own screens, state, computed values, and behavior. Open it — it runs. Send it — the recipient has the same app. The file is complete. Nothing else is required.
Mere Store is where you find them.
Every Mere Package is a single .mp.html file. It contains everything — screens, state, logic, theme, data. Open it and it runs. Send it and the recipient has the same app. No server required. No account. No expiry.
Mere Store holds metadata — names, descriptions, MP- identifiers, links. The files live where authors put them. If this store disappeared tomorrow, every package would still work and the index could be reconstructed.
Mere's element vocabulary and sigil grammar are designed as a generation target. Describe what you want in plain English, point your AI at the spec, and it produces a valid workbook. You open the file. That's the whole workflow.
There is no review board, no approval process, no fee. A workbook that passes mere check — structurally valid, semantically correct — can be submitted. The quality bar is technical, not editorial.
Mere Packages store their data locally — in your browser's OPFS storage or localStorage. Nothing leaves your device. The store has no access to anything you enter into a workbook. This is not a privacy policy — it is an architectural property.
The file was always the app.
We just built the store.