Trust architecture
Evidence
over theatre.
Trust comes from explicit provenance, private boundaries, structured state and clear operational limits—not from a decorative shield icon.
Image integrity
Every visual source has a meaning.
Seller photos remain the highest-priority representation. Development catalogue decoration is tagged synthetic_placeholder internally with is_synthetic=true, replacement_required=true and is_official=false. The customer UI does not present synthetic work as official or seller supplied.
Value language
A declaration is not a valuation.
Seller asks, cash components and development reference estimates remain semantically distinct. Sparse market context is withheld when the evidence threshold is not met.
Identity & privacy
Public social identity is separated from sensitive data.
Profiles, handles, follows and broad region support discovery. Precise fulfillment context, private identity evidence, account controls and message safety belong behind scoped authorization and row-level policies.
Negotiation
The agreement stays legible.
Offers and counters carry explicit items and amounts. Domain transitions reject invalid state changes. Message rooms, deal states and activity refresh through the same backend events.
Release gates
Before public launch, the production API, authentication, object storage, realtime transport, edge controls, identity, payment, shipping, inspection, moderation operations, legal/privacy review, push delivery, physical-device QA and store release must each be configured and verified. This site does not claim those external provider gates are already complete.