The ritual
Specify. Quote. Install.
Three words. They’re the only ones we promise. Specify the slab once in the project. Quote it once when the inquiry lands. Install it once when the fabricator’s job calendar says it’s ready. Honed Earth holds the trail in between.
Step by step
Three nouns. Three verbs.
01
Specify
Designer drops the spec into a project. Stone type, finish, thickness, dimensions, install date. Honed Earth shows every slab on the marketplace that matches — with the lot, the supplier, and when it was last verified.
02
Quote
Fabricator opens the inquiry, pulls real-time inventory, attaches the photos that came off the warehouse floor this morning. Quote arrives in the designer's inbox eleven minutes after the fabricator opens the inquiry.
03
Install
Slab status moves available → on hold → sold. Every step is audit-logged. If something gets disputed, the trail is already written.
The trail
Every change writes a row.
When a slab moves from available to on hold, it writes a row. When the hold expires, it writes a row. When a fabricator releases a slab back, it writes a row. When a supplier corrects a dimension, it writes a row.
Twelve seconds to undo any single action in the UI. Sixty seconds at the server. The trail is append-only. It cannot be edited, only added to. If the trail is wrong, the platform is wrong, and we will fix the platform.
- UI undo
- 12s
- Server undo
- 60s
- Trail mutability
- Append-only
Common questions
What about…
What if a slab gets damaged in shipping?
The dispute protocol kicks in. The fabricator records the damage with photos, the supplier and the platform see the same trail, and the resolution path is documented from the moment the dispute opens. We don't arbitrate — we make the evidence trail unambiguous.
Can I list slabs without committing to publish them publicly?
Yes. Listings are private by default. They show up in your fabricators' inventories and in inquiries from your existing trade designers, but the public /slab/[id] surface only renders when your org flips the marketplace_listed flag.
How do you prevent suppliers from listing the same slab twice?
Listings are scoped to org_id + sku, with a unique constraint. The platform refuses duplicate SKUs at insert. If a slab gets cut and a remnant is created, it gets its own listing with parent_slab_id pointing back to the source.
What happens if a supplier goes offline?
If a supplier is offline for thirty days without a heartbeat (no logins, no listing updates), all their listings auto-private. They re-confirm the inventory on next login and the listings come back. We don't host slabs nobody is watching.
Spend less time on the phone tag.
Create your account — founding-member pricing locked in for the first year.