0.1.0.45: the broker commission leaves the charter funds

---

The short version

The broker commission stops being a number Trident calculates and starts being work Trident finishes. The deduction is a credit memo against the charter fee, raised by one action, checked by one set of rules that report every failure at once, recorded in the commercial log, linked to the charter, and announced to other extensions. Once it exists the commission is settled, and settled is final. Until it exists, a completed charter with a commission cannot be closed.

---

Why the deduction is a credit memo

The MYBA agreement states the commission as a percentage of the charter fee deducted from the funds. The broker does not invoice the owner and wait to be paid. The broker already holds the client's money, keeps the commission out of it, and forwards the rest. In the owner's books the client is billed the whole fee and the commission part is never collected, so the honest document is a credit against the charter fee for exactly that amount, on the same product the fee was billed on. The two net to what the owner actually keeps.

The other arrangement, where the owner really does pay the broker out as a supplier, is a purchase document and a whole class of machinery Trident does not touch. It is not built, and this build does not pretend otherwise. The place it would arrive is marked on the documents this build creates, so adding it later moves nothing that exists today.

---

What the build does

• One action creates the deduction. It sits on the charter card next to the commission it settles, and it is enabled exactly while the commission is outstanding.
• Every blocker is reported in one message. A charter that is not completed, has no customer, no broker or no commission, is already settled, already has its deduction, or is missing its billing setup gets told all of it at once, not one complaint per attempt.
• The commission status is derived, never typed. No commission reads Not Applicable. A commission on a completed charter reads Outstanding. Only the deduction being created moves it to Settled, and Settled cannot be reopened, by anyone, deliberately.
• The money lock now covers the commission. Once a charter is financially committed, the rate and the amount freeze with the rest of the charter's money, and the only thing that can still move is the settlement itself.
• The closeout refuses to happen over an outstanding commission. It is the last gate before the door, checked only where the charter would otherwise read ready to close, with its own reason, guidance and error like every gate before it.
• The checklist shows it as the thirteenth row. Blocked when outstanding, not a warning. A deposit return can lag the paperwork by days and still be honest; an undeducted commission means the books are wrong, not late.
• Commission documents are recognisable as themselves. Everywhere Trident lists a charter's documents, the deduction is distinguishable from the charter fee, the advance and the settlement paperwork.
• The moment is announced. Creating a deduction is the 37th moment Trident announces to other extensions, for broker statements and approval flows, and it ships with its subscriber proof, so the surface stays fully proven. One telemetry event was added with it, carrying the same anonymous shape as the other eight.

---

The tests

Fifteen of the 657 methods are new in this build. Eight drive the document itself: the credit memo raised against the charter fee, the refusals and the single message that carries them, the settled state that cannot be settled twice, and the document being findable again afterwards. Five hold the derived status through the charter's life and the money lock now covering the commission fields. One proves the closeout refuses to happen while the commission is outstanding, and one is the subscriber proof for the announcement. Every method that existed before them passed unchanged.

---

What this deliberately does not do

The credit memo is created, linked and logged, and never posted. Posting stays with the finance user, on purpose, because the deduction document is evidence to review before it moves money.

A commission the owner pays out as a purchase, with the broker as a supplier, is not built at all. The field it would hang off exists and nothing is behind it. And the pricing moment named in the 0.1.0.44 note is still missing: nothing announces a scheme's defaults being applied.

---

Upgrade notes

Going from 0.1.0.26 to 0.1.0.45 runs everything the 0.1.0.26 note describes, the six builds in the 0.1.0.31 to 0.1.0.36 note, the charter agreement terms in the 0.1.0.37 note, the invoice language in the 0.1.0.38 note, the status history in the 0.1.0.39 note, the pricing scheme check in the 0.1.0.41 note, the charter state changes in the 0.1.0.42 note and the two proof builds in the 0.1.0.43 and 0.1.0.44 notes.

Take the backup you would take for any extension upgrade. After upgrading, confirm the four assignable permission sets are still assigned as intended: Trident Admin, Trident Ops, Trident Read and Trident API. The procedure is in the install runbook.

---

What still ships broken

The full register is on the known limitations page. What matters most alongside this particular change:

• The deduction is never posted by Trident. A finance user reviews and posts it. If you wanted the whole path automated, this build stops one step short on purpose.
• Retained and invoiced commissions are not built. If your brokers are paid as suppliers, this is not that.
• There is still no pricing announcement. A partner who wants to attach to a scheme's defaults being applied has nowhere to stand.
• The cruising area does nothing. It is stored and displayed and no rule anywhere consults it.
• The security deposit has no posting path. Trident records that money is held and that it went back. Moving it is a bank transaction you do outside Trident.
• Neither API page has a runtime test that repeats. Two HTTP runs have proved the platform agrees with the source, the second of them as a restricted user and driven by a script, and nothing re-fires either when a page changes.
• No live non-SUPER sign-off exists for all three UI personas in a controlled tenant on this build.
• The licence terms and the pilot agreement are unreviewed. Nothing gets signed until both come back from a lawyer.
• No telemetry reaches Marvera. If something is wrong on your install, tell me, because I will not find out on my own.
• Still not submittable to AppSource, for one remaining reason that has never affected a per-tenant pilot install. Debugging is enabled as a deliberate pilot-time setting.

---

This build has its package hashes written down, so whoever is eventually sent the file can check they were sent that one. They are on the install page. Writing the hashes down is not the same as shipping, and the sentence at the top of this page still stands. If something here is wrong or unclear, say so: [email protected].