Three parties. One counterparty.
A client never has to work out who they are really dealing with. Whoever does the work, Trinity signs for it, answers for it and stands behind it.
ClientSigns with Trinity
One contract, one counterparty, one price for the whole Blueprint.
- A data processing agreement is signed before any of your data is touched. (Running)
- Your engagement opens a Chronik you can read, entry by entry. (Running)
- You see who works on your project: their name, their role and their job. (Running)
TrinityCarries the contract
When Trinity brings in a subcontractor, it does so in its own name and remains the client's counterparty.
- Scope, price and every conversation with the client run through Trinity. (Running)
- The founding entry of every engagement is written by the database, not by a person. (Running)
- Clients are measured by the same doctrine as the people who work for them. (Being built)
Engineer · FreelancerWorks for Trinity
Subcontracted by Trinity, never by the client on the side.
- Assignments come from a work pool, each with a deadline the engineer agreed to. (Running)
- Hours are recorded from the working sessions themselves, not typed in afterwards. (Running)
- Work happens in a sandbox with synthetic data: no client data and no production secrets on the engineer's machine. (Being built)
The board is the only door. Not as a toll: a connection made around it would be a hole in the record, and the record is what everyone on the board relies on.