The handoff
What one layer hands the other, and what has to be true first.
You can run Wisdom OS without voice. This page is only the specification for when a coverage system is authorized to act on a scored priority. North Star Intelligence decides. The coverage system executes. Neither guesses what the other meant.
The handoff record
- 01
Scored priority
One decision, not a list. It carries the Index movement that raised it, the window it must be acted in, and the value at stake if nothing happens. If two decisions tie, the record breaks the tie by which one has the shorter reversible window.
- 02
Evidence
The records the score was built from, named and dated. An operator can open the underlying rows. A priority that cannot be traced back to records is not eligible for handoff.
- 03
Single owner
One named human accountable for the outcome, plus the system layer acting on their behalf. Shared ownership is treated as no ownership and blocks the handoff.
- 04
Governed action
What EchoCody AI is authorized to do: which conversations it may handle, what it may say, what it must escalate, and what it may write back into the CRM. Anything outside that boundary returns to the owner.
- 05
Verification criteria
The observable fact that proves the decision worked, agreed before execution starts. Not activity, not sentiment. A booked job, a recovered record, a closed exception.
- 06
Write back
The verified outcome returns to the same record that scored the decision, so the next score is built on what actually happened rather than what was intended.
Where the line sits
North Star Intelligence owns
- Which decision matters most right now
- The evidence and the scoring method
- The owner assignment and the escalation path
- The operating record and its history
- Whether an outcome counts as verified
EchoCody AI owns
- Answering the inbound conversation
- Qualifying and routing the caller
- Booking or owning the next step
- Writing the action into the CRM
- Returning what happened, in full
Three rules that keep it honest
Nothing executes without an owner. A scored priority with no named human stays in the record as an open exception. It is never handed to an attached system to be absorbed quietly.
Execution cannot rewrite the score. The attached system reports what happened. It does not adjust the evidence, the criteria, or the history. That separation is what makes the record worth steering by.
Unverified is not the same as failed. An outcome that cannot be observed is recorded as unverified and stays visible until it resolves. Nothing is closed on the basis of activity alone.
This page describes how the two programs are designed to work together. Examples of scores and outcomes shown elsewhere on this site are illustrative models, not customer results.