Parties prototypes
Table of Contents
1. Summary
The tenant's own legal entities and the counterparties it trades with: their identifiers, contacts, and the countries, currencies and units they connect to.
3 prototypes answer to this group. Each one is a static page under
doc/prototypes/, opens with no build and no session, and reads mock data
only. The table below opens each one and says what it argues. Where a
prototype carries a Gemini review, the last column opens it: a review is a
generated alternative kept beside the agreed design, never instead of it.
Prototypes is the top page and the only inventory.
2. The prototypes
| Prototype | What it argues | Open it | Review |
|---|---|---|---|
| Onboard a counterparty | A counterparty is a legal entity before it is a trading relationship: the identifiers that name it, the people to call, and the agreements that govern it. It also draws a second person's approval before a counterparty is written: the request waits, the checker decides, and a decline leaves the record alone. | prototype | none |
| Keep a party's details current | A party's record is corrected, not replaced: a name, an identifier, a contact and the countries and currencies it works in, each with a version to fall back to. It also draws a second person's approval for every material correction: the request waits, the checker decides, and a decline leaves the party alone. | prototype | none |
| Keep a counterparty's details current | A counterparty is a record, not a workflow: drawn like the parties screen, with a list, a record on tabs for its details, identifiers, contacts, business centres, the parties that may trade with it and its history, and a dialog for each card. A dialog never writes. The review shows each change with the function that decides it, and the button saves a contact change directly or raises one request for the rest. | prototype | none |
3. Adding a prototype
Create doc/prototypes/parties/<name>/ with an index.html, and a
prototype.css and prototype.js when it needs them. Open the page with
the links table every prototype carries, and leave its review row at
none. Add a row to the table above, with the design note beside the
prototype when there is one. Stop there: the site build finds every
prototype under this tree, so no build file names it.
A review goes at doc/prototypes/parties/<name>/review/, with an
index.html that lists its screens. The row names it, and the
prototype's review row points at it. Prototypes states the
whole method and the rules that hold for every group.
4. See also
- Prototypes — the top page: the groups, and the one way to add a prototype.
- Parties journeys — the journeys these prototypes answer.