Load status for the next action.
Private mission control
One rollup for launch-critical work.
This console calls `/api/operator-status`, `/api/source-monitor`, and `/api/launch-gate` to combine automation status, live source monitor records, lead counts, proof ledger health, outcome metrics, and the hard paid-launch decision into one operational verdict.
Worker and proof state will appear here.
Private ROI proof records loaded from KV.
appeal_watch_launch_gate_v1
Paid launch gate
This is the hard evidence gate. If this says blocked, we do not take paid automation money yet.
Not checked
Load operator status
Paid launch
No
Payment guard not checked.
Private candidate
No
Proof review state not checked.
Worker
Unknown
SOURCE_BROWSER_WORKER plus BROWSER binding.
Proof readiness
0
Launch proof candidate count.
Outcome proof
No
Verified, anonymized win for marketing proof.
Next action
-
Do this before changing payment posture.
0Total leads
0Packet requests
0Proof needed
0Proof ready
0Proof candidates
0Source monitors
0Monitor captures
0Source jobs
0Job blocked
0Draft deliveries
0County validate
0County blocked
0Validation batches
0Promotion queue
0Target seeds
0Lead ready
0Lead blocked
0Launch-ready proofs
0Incomplete proofs
0Customer reports
0Outcome review
$0Tracked savings
Source monitor engine
Run this protected API on known parcel records or paid-case follow-ups. It executes source check, discovery, selector validation, Browser Worker execution when bound, and stores the evidence trail in KV.
Endpoint
/api/source-monitor
Batch schema
appeal_watch_source_monitor_batch_v1
List schema
appeal_watch_source_monitor_list_v1
Launch rule
paymentAllowed: false until proof-ledger review
Deploy package when local npm/npx is missing.
Build the handoff artifact locally, then deploy it from a machine with Node package tooling. Payment remains parked until the Worker is bound and a launch-ready evidence pack exists.
Build handoff
.\scripts\build-browser-worker-handoff.ps1
Handoff zip
dist\appeal-watch-browser-worker-handoff.zip
Deploy command
npm install; npx wrangler deploy
Pages binding
SOURCE_BROWSER_WORKER -> appeal-watch-browser-worker
Worker binding
BROWSER
Proof artifact
appeal_watch_county_automation_evidence_pack_v1
appeal_watch_county_validation_promotion_queue_v1
County proof promotion queue
Captured public proof candidates that still require operator review before any launch/payment claims. This queue promotes only persisted non-sensitive county validation proof, never customer addresses.
| County | Proof | Review status | Guard | Next action |
|---|---|---|---|---|
| Load operator status to inspect the county proof promotion queue. | ||||
appeal_watch_county_validation_queue_v1
Georgia county validation queue
All 159 Georgia counties ranked by browser-flow status, latest monitor result, proof state, next action, and payment guard. This is the expansion board for turning candidate flows into proven county automation.
| Rank | County | Validation | Browser flow | Next action |
|---|---|---|---|---|
| Load operator status to inspect the county validation queue. | ||||
appeal_watch_county_validation_batch_v1
Latest county validation batch
Manual batch runs and Import + Validate actions persist to KV and render here, so the operator can reload the console and still see which public targets actually attempted source proof.
No batch run
Run validation to populate this panel.
| County | Target | Status | Proof | Next action |
|---|---|---|---|---|
| Run County Validation Batch or Import + Validate Targets to inspect the latest proof attempt. | ||||
appeal_watch_county_validation_batch_history_v1
Recent validation batch history
Persisted county validation batches across reloads. This is the audit trail for which public targets were tried, how often, and whether the blocker is missing targets, worker binding, selectors, or source capture.
| Created | Run | Attempted | Skipped | Guard |
|---|---|---|---|---|
| Load operator status to inspect persisted validation batch history. | ||||
appeal_watch_source_monitor_target_seed_v1
Source target seed queue
Counties cannot be validated from private customer data. This queue lists the exact non-sensitive public proof targets needed before county validation batches can run at scale.
The protected registry rejects targets unless `nonSensitivePublicRecord` is true and a parcelId or HTTPS sourceUrl is present.
| Rank | County | Needed target | Safety rule | Tools |
|---|---|---|---|---|
| Load operator status to inspect missing public source targets. | ||||
appeal_watch_packet_source_job_v1 -> appeal_watch_packet_source_draft_v1
Packet source jobs
Each packet request becomes an address-to-source automation job. Run the queue or one job, then use Download Packet Draft and Save Draft Delivery only after source_review_ready. Draft gated until source_review_ready protects the token-gated case room from raw proof.
| Job | Status | Proof | Next action | Tools |
|---|---|---|---|---|
| Load operator status to inspect packet source jobs. | ||||
appeal_watch_packet_draft_delivery_ledger_v1
Packet draft delivery ledger
Ready draft deliveries saved from source-reviewed jobs. These records keep the case-room handoff visible after jobs move to `packet_draft_delivered` and leave the active packet source queue.
| Delivery | Case | Status | Customer ask | Guard |
|---|---|---|---|---|
| Load operator status to inspect delivered packet drafts. | ||||
appeal_watch_operator_lead_readiness_v1
Lead readiness verdicts
Packet leads are automatically checked against prequalification, launch gate, proof ledger, source monitor history, and saved monitor targets. This is the operating surface for deciding what the system does next.
| Lead | Case | Readiness | Proof/monitor match | Next action |
|---|---|---|---|---|
| Load operator status to inspect lead readiness. | ||||
Launch-critical work queue
| Priority | Type | Task | Action | Source |
|---|---|---|---|---|
| Load operator status to build the work queue. | ||||
appeal_watch_county_automation_matrix_v1
County automation matrix
County-by-county source posture, payment policy, and launch readiness. This is the map for expanding automation without selling fake certainty.
| County | Payment policy | Launch readiness | Source capabilities | Proof required |
|---|---|---|---|---|
| Load operator status to inspect county automation posture. | ||||
Status JSON
{}