Where Precise lands in Prisma

SURFACE 01The buy: price the decision before the IO goes out

Prisma Media · Buy tab · the placement grid inside a campaign

• 1
  The decision-value column. One number per placement line: predicted contribution to the campaign objective per dollar, with its uncertainty band, computed before authorization. Reads like a rate, sits beside the rate, respects the line's Cost Method and Unit Type.route 02 · building
• 2
  The pre‑order panel. Prisma already gates the way out twice: financials before the order send ("Financial update pending. Update financials before sending this order") and client authorization before the ad‑server push ("Campaign must be authorized by client to send to ad server"). We add the third gate question: what is this order worth, and what one move improves it? The rebalance is priced, not suggested.shipped as the incremental‑reach optimizer · running in the Omnicom engagement
• 3
  The release gate. Nothing auto‑executes. The buyer releases the move; the Order‑view send (which already stamps order number, version, and Send date) seals the first three fields of the decision record: what was known, what was chosen, what we predicted. Surfaces 02 and 03 write the last two.governed release · shipped pattern

Native vocabulary on this board: Buyer workflow · Campaign ID (CP…) · C/P/E · placement / package (cube) / roadblock (road icon, created by starring a primary child placement) · Placement ID (P10…) · Cost Method (CPM/CPA/CPMV/Flat/Free) · Unit Type · Planned Unit Amount · Served by · order versions R0.01 / Rev 0.01 · buyer order states Not sent / Sent / Agency Accepted / Accepted / Revision requested · changed cells highlight purple, mandatory cells blue

SURFACE 02Actualization: the calibration track writes itself

Buyer workflow · Actualize Performance view inside Buy · planned and actual side by side, payable delivery by source, then "Update financials"

• 1
  Predicted / Realized / Band, per line. Actualization is the one place in adtech where committed spend and realized delivery already sit side by side, monthly, under variance rules, with the payable source chosen line by line. We add the third pair: what we said the decision was worth, and what it proved to be worth. No new plumbing; the daily delivery feed and the source picker already exist.route 01 · ready as read‑only value report
• 2
  The calibration track. Every month of actualization appends to a recorded track: predictions against outcomes, bands honored or broken. Ninety days in, this is a track record nobody can argue with; it is the agreed success test from the July 24 call.write path designed · the skunkworks build
• 3
  Variance priced in contribution, not face dollars. Prisma flags a −7.2% delivery miss and lays the sources side by side; the teal pair adds what the miss meant, priced. This is deliberately not plan‑vs‑actual reconciliation, which Guideline's exclusive API owns; it is decision‑level calibration, which nobody owns.boundary honored

Native vocabulary: Actualize Performance (view in Buy) · billable and payable lines · Actual > Payable · payable source: Planned / Invoice (weighted) / Invoice / Supplier / 3rd party · Redistribute all variances for <month> · Update financials · variance rules (agency / user level) · MOS · delivery data pulled daily

SURFACE 03Reconcile mode: History logs edits; this logs decisions

Buyer workflow · Invoices module · Reconcile mode, where OK to pay lives, with statuses and the tolerance gate verbatim from the Invoice Management quick card

• 1
  A record chip per placement line. Prisma already auto‑matches booked to invoiced and gates payment on tolerance. The chip answers the next question: did the flagged variance matter, and what did it teach the system?route 01 · ready
• 2
  The dispute gets a number. Today the tolerance gate says that sources disagree, never why or which deserves to win, and the investigation moves to email ("Review the Planner's workflow after a financial adjustment" is literally a training module). With the record, finance disputes on value.the reconciliation wedge · first workload
• 3
  The five fields, on their settlement rail. Every decision written down completely: what was known, chosen, predicted, what happened, what it taught. Signed so anyone can re‑check it, appended beside the History audit trail (Event / On / Modified by) that today records edits, riding the same close into Ignitia payables and the IPS rails.the product

Native vocabulary: Reconcile mode · OK to pay · Incomplete / Pending / Reconciled / Pending credit / Pending adjustment / Revision requested / Reversed · Actualized? · Approved source: Planned / Invoice (weighted) / Invoice / Supplier / 3rd party · allowable variance · Itemize invoice · credit memos and cash receipts always negative, adjustments always positive · Reverse reconciled · History (Event / On / Modified by) · Recommended for payment (Ignitia)

SURFACE 04The substrate: where the whole program is headed

This board is the goal. The estate running as governed capabilities on Boombox, every action carrying the record. Shown here through a NIVO run view because that is the world it serves; the position itself sits underneath, and NIVO's orchestration stays NIVO's.

• 1
  Agents optimize a calibrated objective. Today an optimization agent chases a dashboard. Under the record, it chases the same calibrated contribution track Surfaces 01–03 write, so "90% faster" means "90% faster at the right thing."lands Prisma‑side; shown to NIVO engineering in the session Zvika offered
• 2
  Numbers reach reports through the registry only. The measurement agent can only speak numbers that exist in the record; it structurally cannot write a number into prose. We run this pattern in production today.trace‑talk pattern · runnable now
• 3
  The POV shift. The likely house view runs new agents on the new stack, with legacy as the install base. The bet runs the other way: Boombox wraps the legacy products as agents and capabilities, NIVO registers them, and the twelve agents get the deepest toolset in media on day one. Governance (autonomy policies, release gates, the exportable trail) arrives with it, by construction. Their roadmap stays good; this is the flyer on top of it.the session Zvika offered · lands with Bill

Native vocabulary: NIVO thinks, Orchestrator connects, Agents act · twelve agents · Create / Deliver / Measure / Optimize · Taxonomy agent, Campaign Trafficking agent, Campaign QA agent, Decisioning agent · "notify a human" workflow steps · Bring your own agents (BYOA) · Hypermode / Standard Mode

SURFACE 05The workload they asked for: predict Prisma retention

The skunkworks console · run on Mediaocean's data about Mediaocean

• 1
  Renewals priced as decisions. Same math as Surface 01, different asset: predicted outcome, band, the single driver, the single move. Calibration on churn signals is the fastest possible proof loop because renewals actualize on a known calendar.skunkworks candidate · zero client‑data exposure
• 2
  The trust ladder. Prove calibration on their own book first; earn the reconciled‑spend slice second; govern NIVO third. Each rung writes records the next rung stands on.sequencing per the Jul 24 agreements

SURFACE 06The connection map: how we physically get in

Six ways in, from zero‑permission to joint build. What makes sense, where, and why.

The sequence that makes sense: the Boombox skunkworks trial runs from day one on the portfolio seat we already hold, the fastest full‑fidelity proof of the whole stack. Beside it: the value report starts the calibration track this quarter, the invited overlay makes it visible in their workspace during the pilot, the certified API is the deal, BYOA is the NIVO lane entered through its own door, and the settlement rail is the compounding end state.

And the template travels. The method ships whole (backstory file, screen‑level walkthrough, connection map) and is the repeatable play for every platform partner. iHeart is next: same record, same wedge logic, pointed at their ad platform, shows, and attribution surfaces instead of Prisma's grids.

SURFACE 07The network: what the whole thing becomes

Boards 01–06 are the seed. This is the plant: Prisma's relationship graph made programmable, Mediaocean as custodian, every company keeping its own authority.

• Why everyone in the room wins. Agencies keep their authority and their client relationships. Sellers keep decisioning on their side (their own stated boundary). NIVO keeps its agents and gains distribution. Mediaocean keeps neutrality; the network is neutrality, made enforceable.the room‑safe version of the biggest idea
• Why it starts at Prisma, not Innovid. The ask already on the table (calibrate creative) is well‑formed and small; say yes and treat it as the demo. The network needs the place where every counterparty already meets and where our access is strongest. That is Prisma.sequencing per the File's Four ways in table
• What Boards 01–06 have to do with it. Every teal element earlier in this document is a network primitive in disguise: the priced decision is the edge's offer, the calibration track is the edge's trust, the signed record is the edge's settlement, the release gate is the mandate. Build the boards, and the network is what they compound into.compounding