Protocol 077 · SOON Stream Activation · MD-1020

Protocol Body · Build #151

CLAUSE 1.0 · PURPOSE

🟡 Why SOON Streams Need a Protocol

A SOON-temperature stream is not a dead stream — it is a stream with a condition. The condition is real, specific, and external: a property phase completing, an AI licensing event triggering, an international milestone landing, a regulatory window opening. When the condition is met, the stream moves. Until then, it waits — but it must be watched.

Without Protocol 077, SOON streams rot. The condition happens and no one notices. The stream stays at SOON when it should be HOT. The job is never created. The revenue is never activated. Protocol 077 ensures every SOON stream has a watcher, every trigger is caught, and every activation creates a job within 48 hours.

CLAUSE 2.0 · THE FOUR ACTIVATION CONDITIONS

🔑 What Makes a SOON Stream Move

Condition Type A — Property Phase: Stream activation is linked to a property acquisition, planning permission, or site development reaching a specific stage. Monitor: planning portal, Land Registry, Companies House filings of the linked entity.

Condition Type B — Regulatory Event: Stream activation is linked to a regulatory change — EPR obligation expansion, PRN pricing shift, Environment Agency announcement, or DEFRA policy update. Monitor: gov.uk, Environment Agency alerts, EPR industry publications.

Condition Type C — International Milestone: Stream activation is linked to an international expansion event — country entry, partner agreement, licensing deal, regulatory approval in a new territory. Monitor: sovereign briefings, entity-level international dashboards.

Condition Type D — Technology/AI Trigger: Stream activation is linked to an AI licensing event, platform capability milestone, or technology deployment threshold. Monitor: sovereign intelligence feed, H.BLUE agent alerts.

CLAUSE 3.0 · ACTIVATION SEQUENCE

⚡ What Happens When a SOON Stream Triggers

Step 1 · Detection

Trigger Identified

SOON Stream Trigger Monitor (MJ-SOON-002) identifies a condition change. Logs source URL, timestamp, and condition type. Flags immediately to Revenue Intelligence team — no waiting for weekly report if condition is met.

Step 2 · Validation

Condition Confirmed

Revenue Intelligence team validates the trigger is genuine (not a false positive). Checks against the stream's stated activation condition. If confirmed: stream is flagged for reclassification. If disputed: escalate to Sovereign for ruling.

Step 3 · Job Generation

First Job Created Within 48 Hours

Upon confirmed activation, the entity responsible for that stream must generate at least one live job within 48 hours. Job must be logged in the Staff Board with correct entity attribution and PROTOCOL_OPS or stream-appropriate job group.

Step 4 · Reclassification

Stream Moves to HOT or WARM

Stream temperature is updated in the master register. HOT: condition met, revenue immediately actionable. WARM: condition met, revenue actionable within 30 days. The reclassification triggers a Truth Ledger seal: stream ID, old temp, new temp, trigger date, activating entity, first job ID.

Step 5 · Truth Ledger Seal

Activation Sealed and Immutable

Protocol 077 activation is sealed permanently: stream name · condition type · trigger date · first job created · new temperature · activating entity. This seal is the proof that the stream moved correctly — not by guess, not by convenience, but by Protocol 077.

CLAUSE 4.0 · MONITORING DOCTRINE

👁️ How SOON Streams Are Watched

Every SOON stream is assigned to a SOON Stream Trigger Monitor (micro-job MJ-SOON-002). Each monitor watches a batch of 10 streams per week. The monitor checks assigned streams against their condition type using public signals only.

A SOON Stream Readiness Scan (micro-job MJ-SOON-001) is run quarterly across all 75 SOON streams to identify any streams within 30 days of their activation condition. Scan outputs feed directly into monitoring prioritisation.

Doctrine: A SOON stream that triggers without being caught is a system failure, not a market failure. Protocol 077 makes that impossible.

Protocol 077 · Micro Jobs

MJ-SOON-001 · 24 MAY 2026

SOON Stream Readiness Scan

MICRO JOB

Scan all 75 SOON-temperature revenue streams. For each, check its stated activation condition. Flag any stream within 30 days of condition being met. Submit structured report: stream name · condition · estimated activation date · recommended action.

£25 per scan · HOW: /command/staff-board

MJ-SOON-002 · 24 MAY 2026

SOON Stream Trigger Monitor

MICRO JOB

Monitor 10 assigned SOON streams for condition changes. Check public signals: Companies House filings, planning portal updates, regulatory announcements. If a trigger condition changes, log immediately with source URL and timestamp. Weekly report.

£20/week · HOW: /command/staff-board

MJ-MATCH-001 · 24 MAY 2026

Job-to-Stream Matching

HYBRID

Match 5 assigned SOON-temperature streams to their most natural job activation conditions. For each: activation trigger · best entity · first job to create when stream goes live. Feeds Protocol 077 activation pipeline directly.

£30 per 5 streams · HOW: /command/staff-board