One counterparty, from candidate to completed work.

Scene 1 · Business intent

It starts with what the business is trying to achieve.

Not with a contact list. Everything downstream is judged against what Kestrel offers, where it works and who it serves. No counterparty relationship exists yet, and the product does not pretend one does.

Why this matters. A system that begins at "add a contact" can only record what somebody already decided. Beginning at commercial intent is what lets Orchestrate reason about a market at all.

Scene 2 · Market

A judgment you can argue with.

Market is possibility, before continuity exists. A candidate is a counterparty under evaluation, and it carries both the reason it matters and what argues against it.

The counter-evidence row is the point. A system that only ever tells a business why something is a good idea is one that business will stop believing.

Scene 3 · The decision to pursue

A relationship begins when a person decides it should.

Not when a score crosses a threshold. Kestrel's owner reviews the candidate and chooses to pursue, and that admitted decision is what establishes durable commercial context.

Not every counterparty becomes a relationship. That distinction is the difference between a system holding a company's real commercial world and one holding a list.

Scene 4 · Authority

The moment the governance is real.

Authority is not a permanent panel. It appears when an action approaches consequence, in plain words, and it says what is missing and what resolves it.

One refusal, resolved in a sentence, and the work continues. That is what governed execution looks like in practice. Withdrawal does not unwind what was already done, and the product says so rather than implying otherwise.

Scene 5 · Communication

Drafted by AI, sent under Kestrel's own identity, honest about what happened next.

Sent is not delivered, and delivered is not read. The system records the evidence it actually has, and where it has none it says so rather than showing a green tick.

An operator who has waited on a tender knows the difference between "they said no" and "it never arrived". The product refuses to collapse the two.

Scene 6 · Engagement, agreement and obligations

An undertaking forms inside the relationship.

Agreement, obligations, execution, acceptance, invoice and payment are stages of one undertaking, presented as one experience and kept as distinct commercial facts. The condition becomes IN ENGAGEMENT because there is now open commercial work.

Obligations are real objects with owners and dates, not line items on a document. It is what allows an invoice, later, to cite the work it is for.

Scene 7 · Execution and acceptance

The step fragmented workflows lose.

Work is performed against the obligations. Then Halloway accepts it, as an admitted act by an identified person rather than a status somebody toggled.

An invoice not anchored to accepted work is a dispute waiting to happen. Acceptance is its own commercial event because, in many of the workflows Orchestrate targets, accepted work determines when the next billing step becomes accountable. Deposits, retainers and staged billing are ordinary structures, and the record holds each of them honestly.

Scene 8 · Invoice and payment

The invoice cites the work it is for.

Agreement, obligation, acceptance, invoice and payment are five different commercial facts. Fragmented workflows often flatten or separate them, which makes the causal record hard to reconstruct later. Keeping them distinct is what makes it hold up months afterward, when somebody asks what happened.

Scene 9 · The relationship continues

Payment did not end this.

The undertaking completed and moved into history. The condition returns to ACTIVE, and the next undertaking starts from everything already on the record rather than from nothing.

One counterparty. One continuous record of what was judged, agreed, delivered, accepted and paid, and under whose authority each of those happened. That record is the asset.