What is built and what is not yet.
In development. You cannot use pro2door yet.
Write to hello@pro2door.com0 of 17
- modules built
- All 17 are designed, with 618 features
0 of 17 modules are built. All 17 are designed.
Eight rules and where they stand
The first product will be small: one real request gets offers and ends in a reviewed booking. These eight rules will hold from the start; none of it is built yet.
What the three marks mean
- Built
- It exists today, and a test or a record shows it.
- Designed
- The design holds it. Nothing of it is built.
- Planned
- Decided or foreseen, not yet designed.
-
One way to write
DesignedEvery change will be a command: bounded, authorized, repeatable without a second effect.
It leaves a receipt, a link in the audit chain and its events. All of it comes about in one transaction: together or not at all.
-
Binding acts only on an exact preview
DesignedPublishing, sending, accepting: a person will see exactly what will happen and until when the preview holds.
Only what matches the approved state is carried out. A refusal and a failure are recorded like a success.
-
Four scopes
DesignedWorkspace, unit, role, person: they will hold for every object and every route.
Access across tenants is tested as a failure of its own.
-
Offline
DesignedThe phone will create records with its own ids and send what was done in its order.
Attachments are not lost. A conflict is shown to a person and never overwritten silently.
-
Money and time are exact
DesignedWhole cents, VAT in basis points, whole minutes.
Dates, holidays and tax rules come from versioned country packs. What a pack does not cover answers “not covered”.
-
Issued papers do not change
DesignedAn invoice, a signed proof and a closed period will not change.
A correction is a new, linked record.
-
Limits for Lot
DesignedLot will prepare typed fields; calculating, permissions and states belong to fixed code.
Every model call has a registered purpose and leaves a receipt. What a model returns counts as unchecked input.
Meet Lot -
Two apps, separate data
Designedpro2door and pro2desk will have separate accounts, databases, keys and hosts.
They share code only. Nothing is matched or copied between them.
A conflict stays visible.
When a request is changed in two places at once, the screen will say what holds. Nothing is overwritten silently.
Designed
What it will be built with
The choices are made, nothing is built yet. Three decisions are open.
-
Web
DecidedOne web app with two sides, on a shared kit
-
Phone
DecidedShells around the same web app
-
API and worker
DecidedOne module; the contract comes before the code
-
Database
DecidedRelational, with forced row-level security
-
Offline
DecidedIts own sync on the command path; uploads that resume
-
Documents
DecidedOne engine for every paper
-
Lot
DecidedIts own gateway in front of every model, on hosts in German hands
Three open decisions
-
Hosting
ProposedA data centre in Germany
-
Payments
ProposedA payment service; each firm is its own merchant
-
Sign-in
OpenWhich service is open; until then an issuer for development only
Questions?
Write to hello@pro2door.com.