Home: All V2 Specs

Goals Overview

Every feature’s goals at a glance. Click through for detail.

💬 A2P (13 goals)

Cross-Mode Architecture

• Provide one texting system serving two recipient sources while applying the correct mode-specific compliance ruleset at send time.

Dashboard

• Give the user an at-a-glance overview of all campaigns, engagement stats, and active conversations with quick access to start new work.

Compose

• Let the user build a compliant, merge-aware, cost-transparent SMS/MMS message with sender selection and mandatory STOP language.

Recipients

• Resolve a precise, mode-compliant audience from Tribes, ad-hoc filters, or lists with a transparent eligibility audit before commit.

Tech Check

• Serve as the pre-flight compliance and cost commit boundary that validates every aspect of the campaign before send.

Status

• Provide real-time visibility and control over an in-progress send with health monitoring and pause/throttle controls.

Conversations

• Turn inbound replies into a first-class phone-app-style conversation inbox with keyword handling and team assignment.

Automations

• Run durable triggered, drip, opt-in, event, and recurring sends with built-in frequency, quiet-hours, and loop guardrails.

Numbers Management

• Acquire, register, and monitor long codes, toll-free, and short codes with health monitoring and 10DLC compliance.

Compliance

• Enforce TCPA, 10DLC/TCR, and state SMS rules structurally with opt-in provenance and suppression handling.

UVP Provenance

• Write every messaging event to the recipient’s UVP engagement history as a defensible record.

Permissions

• Gate send, automate, and number-management capabilities to appropriate roles while allowing safety pausing broadly.

Performance & Scale

• Ensure the queue, webhook, and conversation architecture scales while respecting throughput limits.

🎯 CTAs (12 goals)

Core Architectural Idea

• Deliver a lightweight, conflict-free behavioral runtime that renders VRM-configured CTAs on customer sites.

Five Formats

• Offer a constrained set of formats and ratios that keep the builder fast and analytics comparable.

Component System

• Provide a drag-and-drop, auto-arranged component set for building CTA content without pixel-pushing.

Politogy Visitor ID

• Maintain a privacy-respecting first-party visitor identifier that merges into the UVP on conversion.

Triggers and Targeting

• Fire CTAs only when both behavioral trigger and contextual targeting conditions are satisfied, with anti-annoyance defaults.

Stranger Conversion

• Convert anonymous visitors in-place via constrained inline capture without leaving the page.

Animations

• Provide a constrained, accessible animation set that respects motion and contrast standards.

Paginated Survey

• Deploy existing Live Surveys as behaviorally-triggered, paginated, partial-capturing CTAs.

A/B Testing

• Run statistically honest two-variant CTA tests that only declare winners on sufficient data.

Lifecycle

• Manage CTA states with version-bucketed analytics and attribution-preserving edit constraints.

Web Engagement Profile

• Write rich pre-conversion behavioral profiles to the UVP under standard exposure controls.

Permissions

• Apply role-based access with live deployment gated to Admin and Manager.

📇 Contacts (13 goals)

Core Architectural Idea

• Render Contacts as a curated, non-duplicating view over the UVP rather than a parallel data store.

VRM Verified

• Surface a system-computed data-quality tier that distinguishes high-confidence contacts as the account’s actionable inventory.

Dashboard

• Give the user a politically-tailored intelligence brief on the size, growth, and composition of their list.

All Contacts

• Provide a fast, customizable, searchable contact table with subscription-aware quick and bulk actions.

Contact Card

• Present a universal UVP detail surface with layer-appropriate edit modes and a unified activity history.

Tribes

• Provide manual static and dynamic list grouping over UVPs that is reusable across modes.

Import

• Ingest CSV/Excel with AI-assisted mapping, identity-match configuration, adjudication, and reversible auditing.

Fields

• Let the account manage its custom field namespace and reference the locked global schema safely.

Activity

• Provide a filterable chronological audit feed of all contact-related events for team oversight.

Duplicates

• Surface and adjudicate likely-duplicate UVPs with a non-destructive, reversible merge workflow.

Permissions

• Apply role-based access with destructive operations gated to Admin.

UVP Provenance

• Provenance every contact change non-destructively to keep Contacts a defensible record system.

Integrations Roadmap

• Provide native and later integrated call/text/email actions that enforce channel compliance.

🗄️ Data System (UVP) (13 goals)

Unified Voter Profile

• Make the Politogy-owned UVP the single canonical voter record with layered sources, strict priority, and full provenance.

Data Ingestion

• Govern how voter-file, user-generated, and enrichment data enter VRM with correct precedence and isolation.

Two-Tier Data Architecture

• Separate omniscient Politogy-tier access from scoped curated customer-tier access.

Exposure Controls

• Give Politogy real-time, field-level, seamless control over which data each customer can see.

Data Monetization

• Enable lawful sale of aggregate intelligence while never exposing identifiable single-account data.

Field System

• Balance a locked global schema with free custom fields and a promotion pipeline that keeps data governable and sellable.

Cross-Mode Data Flow

• Ensure all modes are views of one UVP with no duplicated voter data.

Search Filter and Segmentation

• Provide instant, scope-respecting search and dynamic living segments.

Data Quality and Hygiene

• Proactively surface staleness, duplicates, and conflicts to keep voter data accurate.

Data Lifecycle and Retention

• Preserve all voter and user-generated data indefinitely through archival rather than deletion.

Import and Export

• Allow scoped, matched, fully-audited customer import/export and Politogy-tier extraction.

AI Readiness

• Build the data plumbing (clean schema, provenance, computed layer, event stream) so AI can plug in cleanly.

Permissions

• Define the role/tier permission matrix governing view, edit, and import/export.

📧 Email Engine (14 goals)

Six-Tab Architecture

• Provide a sequential-but-navigable six-tab flow with validation gates and persistent credit visibility.

Dashboard

• Drive repeat sending with an email list, performance snapshot, and fuel/action bar.

Creative Canvas

• Provide a responsive drag-and-drop email builder with AI assist and accessibility-aware blocks.

Sender Information

• Provide a light trust/deliverability layer over SES with verified domains and authenticated sending.

Recipients

• Select audiences strictly from opt-in contacts with segmentation while enforcing the voter-roll wall.

Send & Automate

• Launch broadcasts, sequences, and triggers with mandatory cost transparency and credit guardrails.

Statistics

• Report per-email and aggregate performance including reply tracking and write engagement back to the UVP.

Deliverability Dashboard

• Monitor sustained sender reputation, per-domain health, and compliance exports with actionable alerts.

Block System & Media Library

• Provide a typed block contract and sanitized, optimized, CDN-delivered media asset management.

AI Architecture

• Give every customer ungated AI assistance across the email workflow under fair-use limits.

Fuel System Integration

• Make Broadcast Credit consumption transparent and guardrailed across all surfaces.

Data Model & UVP Writeback

• Define email entities and write all engagement events back to the UVP with defined retention.

Compliance & Security

• Enforce CAN-SPAM, CASL, GDPR, and 2024 sender requirements with sanitization and audit logging.

Relationship/Campaign Wall

• Preserve the strategic wall by blocking live roll querying and Campaign Mode IP in Relationship Mode.

🚪 Field Canvassing (14 goals)

Product Philosophy and User Model

• Serve distinct Manager, Canvasser, and Politogy roles with surfaces tuned to strategy, field speed, and oversight respectively.

Mode Architecture and Product Positioning

• Position Field Canvassing as the highest-value Campaign Mode intelligence channel integrated with the Polling Engine and peer to Phone Banking.

Foundational Architecture

• Establish the two-tier IP boundary, portable Canvasser entity, first-class walk lists, and immutable Door Visit Events as the data backbone.

Walk List Creation and Optimization

• Produce methodologically defensible, optimized, fielding-ready walk lists with consultative AI and auditable overrides.

The Mobile Canvasser Experience

• Give canvassers a fast, offline-first field assistant that handles routing, capture, safety, and polling at the door.

Polling Engine Integration

• Make canvassing a full fielding mode of the Polling Engine with door-administered, scored, provenance-stamped poll responses.

Heavy-Prescription Walk List Next Moves

• Autonomously generate fully-specified follow-up canvass campaigns from poll or canvas findings.

The Canvasser Performance Profile

• Score every canvasser continuously and portably across accounts as a calibrated, sellable data asset.

Capture Mode and Intelligence Routing

• Distinguish what the voter said from what the canvasser inferred so Aggregate Intelligence is honestly weighted.

Reporting, Analytics, and Strategic Memo

• Turn captured canvass data into operational reports, strategic memos, and longitudinal voter trajectories.

Compliance, Safety, and Consent Architecture

• Make canvasser physical safety, consent, and per-state compliance foundational architecture rather than features.

Offline Architecture

• Guarantee end-to-end offline field operation with mandatory pre-shift sync, opportunistic post-shift sync, and lossless conflict resolution.

Donor and Volunteer Canvassing Variants

• Support Donor and Volunteer canvassing on the shared substrate while routing intelligence to their respective pipelines.

Service Boundaries and Integration Points

• Organize the implementation into clear services and integration contracts with the UVP, Polling Engine, and peer features.

📝 Forms (13 goals)

What This Product Is

• Provide the public-facing UVP acquisition surface that turns strangers into resolved contacts in Relationship Mode.

Mode Architecture

• Keep Forms as the sole public-web UVP-creation mechanism, exclusive to Relationship Mode with the strictest consent controls.

The Core Architectural Idea

• Make a form a published UVP write configuration so every input maps cleanly to a single UVP field.

The Field Library

• Expose a curated, mode-appropriate set of locked global fields and reusable account custom fields as the form-building palette.

Creating a Custom Field From Inside the Builder

• Let users create clean, deduplicated custom fields inline that feed the field-promotion pipeline.

The Three-Tab UI

• Provide Forms/Canvas/Submissions navigation that makes building, branding, distributing, and reviewing forms intuitive.

The Submission Pipeline

• Reliably validate, identity-match, and write every submission to the UVP with full provenance.

Form States & Lifecycle

• Govern form Draft/Live/Paused/Archived transitions to protect data integrity for ongoing submitters.

Versioning

• Preserve form version snapshots so historical submissions remain interpretable and precisely provenanced.

The Field Deletion Rules

• Protect in-use and promoted fields from deletion to preserve data integrity and platform asset value.

Distribution & Embedding

• Distribute forms via hosted links, iframe/JS embeds, QR codes, and branded social previews.

Analytics & Stats

• Surface lightweight per-form analytics including submissions over time, conversion, and match rate.

Permissions

• Apply role-based access so only trusted roles author forms and manage custom fields.

✍️ Petition Mode (14 goals)

The Signature Record

• Make every signature a structured, provenance-rich data event owned by Politogy and tied to a UVP.

Sheet Types and Structural Recognition

• Recognize and correctly structure every jurisdiction-specific sheet type with permanent immutable scans.

Signature Ingestion Pipeline

• Move every sheet through capture, OCR, verification, duplicate detection, and routing with full logging and replay.

The Adjudication Workspace

• Let trained reviewers resolve flagged signatures fast with coded reasons feeding AI training and circulator scoring.

The Circulator System

• Track, score, and reputation-rank circulators as first-class field actors with fraud monitoring.

Petition Records

• Maintain petitions as top-level containers with live threshold, distribution, and pace tracking.

Submission Packet Generator

• Assemble legally-defensible SOS filings only after all pre-submission validations pass.

Cross-Mode Data Flow

• Write signatures instantly to the single shared UVP so all modes see them without duplication.

The Petition Drafting & Filing Workspace

• Support the full pre-circulation lifecycle from drafting to filing milestones in one platform.

The Public Transparency Portal

• Offer an optional public dashboard that builds movement momentum while exposing zero PII.

Sub-Modes Within Petition Mode

• Support Initiative, Recall, and Candidate petition use cases on shared data structures via ruleset overlays.

Permissions Summary

• Scope petition capabilities by role from Politogy admins down to limited circulators.

AI Capabilities Specific to Petition Mode

• Apply petition-specific AI models for OCR, matching, forgery, risk, and SOS prediction with full provenance.

Data Lifecycle in Petition Mode

• Retain all core petition records permanently and govern customer-churn data handling.

📞 Phone Banking (13 goals)

Product Philosophy and User Model

• Compress professional phone-bank workflows into compliant self-serve software serving Manager, Caller, and Politogy roles.

Mode Architecture and Product Positioning

• Position Phone Banking as a Campaign Mode voice channel of the Voter Contact substrate, distinct from Relationship Mode click-to-call.

Foundational Architecture

• Inherit substrate entities and define phone-specific Caller, Session, Call Attempt, and VWPP extensions.

The Continuous Lifecycle

• Run phone banking through plan-to-activate phases with compliance and cross-channel checks at each step.

Campaign and Session Creation

• Give Managers a strategic console to build compliant lists, scripts, and sessions and monitor them live.

The Caller Experience

• Provide a distraction-free, mobile-first call surface with auto-advance and silent compliance guards.

The Script System

• Render voice-optimized, compliance-pre-checked, versioned scripts via the Methodology Agent and ScriptBuilder.

Telnyx Integration

• Deliver browser and mobile voice over Telnyx with campaign caller ID, voicemail capture, and constrained drops.

Compliance Architecture

• Enforce TCPA, DNC, calling hours, recording consent, and disclosures at five blocking checkpoints.

Disposition Taxonomy

• Capture structured, Posture-constrained connection and contact outcomes with Capture Mode tagging.

Reporting

• Provide real-time and final session, campaign, and cross-campaign reporting with cross-channel saturation.

Field Volunteer Permissions

• Scope Callers tightly to their active session and own data, tightening but never loosening substrate permissions.

Substrate Compliance Summary

• Demonstrate that Phone Banking honors every substrate contract without redefinition.

📊 Polling Engine (21 goals)

Executive Summary

• Deliver campaign-grade, methodologically defensible polling as software that turns voter intelligence directly into campaign action.

Product Philosophy and User Model

• Make non-pollster users capable of producing defensible polls by acting as an embedded senior polling strategist that explains, pushes back, and protects.

Mode Architecture and Product Positioning

• Position polling exclusively within Campaign Mode and govern customer visibility through a tiered two-tier IP boundary.

Architectural Foundations

• Establish the Polling Engine as a continuous, stateful system writing to the correct UVP layers with longitudinal records from day one.

Lifecycle Overview

• Define an auditable poll lifecycle with strictly allowed state transitions.

Poll Command Center

• Give users a disciplined home base to create, monitor, and open analysis for all polling activity.

Poll Creation Workflow — Intake Phase

• Capture user intent and produce a pollster-formal objective, classification, and recommended structure before drafting.

The Methodology Agent — Drafting and Review/Negotiation

• Generate and negotiate a defensible questionnaire through a consultant-style interaction that protects methodological integrity.

Methodology Generator

• Produce a structured methodology framework and a public-facing abstract for each finalized poll.

Fielding System

• Field polls via tokenized, duplicate-safe links across SMS, email, and web while monitoring sample quality.

Response Collection and Storage

• Persist responses with full version and provenance references, routing them to the correct UVP layers.

Sample Quality Architecture and the Fielding Scorecard

• Continuously assess sample quality and assign honest finding-strength tiers that gate strategic claims.

Scoring, Classification, and Latent State Detection

• Score respondents on four dimensions, classify them, and detect latent states as Politogy’s core polling IP.

The Data-to-Messaging Pipeline

• Convert analysis into segments, message lanes, and human-approved generated content for deployment into VRM.

Strategic Analysis and Closed-Loop Architecture

• Provide an honest interpretive layer with heavy-prescription Next Moves and capture closed-loop signals for future learning.

Longitudinal Tracking

• Track each voter’s response timeline, score evolution, and classification migrations as a living record.

Strategic Memo and Report Generation

• Produce the headline poll deliverable with honest tiering and credibility flags that travel across all export formats.

VRM Integration Outputs

• Integrate poll outputs into VRM segments, tags, messaging workflows, and exports.

Technical Stack and Implementation Posture

• Organize the engine into modular services with a shared, versioned, guardrailed AI orchestration layer.

UX Principles

• Make the product feel like a strategist that guides, trains, and protects users while keeping action one step away.

V1 MVP Scope Summary

• Ship the full integrity-preserving polling capability and moat in V1 without cutting corners.

📋 Relationship Dashboard (15 goals)

Purpose & Strategic Frame

• Serve as the daily-driver insight surface that tells users what is changing, what to do, and how prepared they are.

Core Architectural Principles

• Govern the dashboard as an insight-driven, action-oriented, mode-aware control surface with persistent AI and visible data flywheel.

The Five-Tab Architecture

• Organize the dashboard into five tabs that form a complete observe-understand-act-analyze-plan loop.

Tab 1: Pulse

• Show daily momentum, what is moving, and what to act on today, reorienting to voter contact in Campaign Mode.

Tab 2: Network

• Present the network as an owned asset with size, verification, completeness, sources, and growth, overlaid on the universe in Campaign Mode.

Tab 3: Relationships

• Surface named individuals to act on today through AI-curated ranked queues with one-click actions.

Tab 4: Demographics

• Reveal network composition and gaps, summarizing demographic intelligence and handing off deep analysis to Battleground.

Tab 5: Opportunities

• Turn data into ranked, actionable AI recommendations and a readiness/activation score that drives Next Moves.

The AI Layer

• Weave a persistent, attributed, confidence-aware AI presence through every tab via the Insight Bar, annotations, and Strategic Analyst.

The Mode Shift

• Reorient the same five tabs between Relationship and Campaign Mode while preserving data continuity across modes.

Influencer vs. Campaign Adaptation

• Flex labels, emphasis, and AI tone by account type over an identical data model.

Integration with Other VRM Systems

• Act as the surface layer over UVPs, Next Moves, polling, field activity, petitions, donations, and future social data.

Data Sources and Refresh Logic

• Feed the dashboard from defined sources on a predictable, mostly-daily refresh cadence with on-demand recompute.

UI Surface Conventions

• Establish consistent, accessible, action-oriented presentation conventions across the dashboard.

Tier Gating, Permissions, and Monetization

• Keep the dashboard uniform in MVP while honoring role permissions and deferring tier gating to the account layer.

🪧 Sign Mapping (15 goals)

Executive Summary

• Track campaign sign assets geospatially while capturing supporter signal to the UVP from the same pin drop.

Product Thesis

• Replace spreadsheets and memory with a shared visual database that also preserves supporter intelligence across cycles.

Mode Architecture

• Confine Sign Mapping to Campaign Mode where district geofence and voter-roll matching exist.

The Two-Tier IP Boundary

• Tier sign asset data and supporter event data distinctly while anonymizing cross-account host history.

The Continuous Lifecycle (SignPlacement)

• Model each sign as a stateful, auditable entity whose lifecycle never invalidates the supporter signal.

The SignPlacement Entity

• Define the canonical asset-tracking entity that links to but stays separate from any supporter event.

The Three Sign Types

• Treat Yard, Field, and Billboard signs as operationally, analytically, and supporter-relationally distinct.

Pin Drop Workflow (Mobile)

• Provide a fast, forgiving, offline-safe pin drop that captures supporter signal invisibly server-side.

Map Visualization (Manager & Mobile Views)

• Render placements on a filterable district map with role-appropriate supporter and UVP detail.

Analytics & Reporting

• Produce operational, supporter-signal, strategic, and aggregate-intelligence outputs with tiered exposure.

Recovery Workflow

• Make post-election sign recovery a first-class routed workflow that preserves supporter events.

Permissions

• Scope placement, editing, deletion, export, and match-confirmation rights appropriately by role.

Integration Points

• Integrate with VRM geographic, supporter-layer, geocoding, voter-file, and aggregate-intelligence systems.

AI & Aggregate Intelligence Hooks

• Emit full event telemetry from V1 to feed supporter scoring and future AI capabilities.

Critical Architectural Principles

• Keep sign assets and supporter signals distinct, offline-first, frictionless, and anonymized at the write layer.

🗳️ Surveys (15 goals)

What This Product Is

• Provide a lightweight, campaign-deployed form for group-level intelligence that funnels users toward the Polling Engine.

Mode Architecture

• Confine Surveys to Relationship Mode alongside Forms, distinct from Campaign Mode Polls.

The Defining Distinction: Forms vs. Surveys vs. Polls

• Clearly differentiate Forms, Surveys, and Polls by purpose, audience, rigor, and output.

The Core Architectural Idea: A Survey Is a Deployed Form

• Build Surveys as a Form plus deployment plan, aggregate results, and identity modes on shared infrastructure.

What Surveys Deliberately Are NOT

• Exclude all Polling Engine rigor capabilities from Surveys to preserve the upgrade funnel.

The Deployment Plan — What Makes a Survey a Survey

• Define audience, channel, schedule, close conditions, reminders, and anti-abuse that turn a Form into a bounded Survey.

The Identity Model — Three Modes

• Offer Identified, Anonymous, and Pseudonymous identity behaviors locked at go-live.

The Three-Tab UI

• Provide Surveys, Canvas, and an aggregate-first Results tab using the shared Forms pattern.

The Upgrade Funnel — Surveys to Polls

• Surface contextual upsells that route users to the Polling Engine when rigor is needed.

Question Types & Builder

• Reuse Forms field types plus aggregate-friendly Survey-specific additions.

UVP Provenance & Survey-Specific Metadata

• Write Survey responses to UVPs with full provenance plus invitation and send/response history.

Lifecycle & State Machine

• Govern Surveys through a Draft-Scheduled-Live-Closed-Archived state machine that locks the instrument once live.

Anonymous Mode & The Data Trust Boundary

• Deliver architecturally-enforced honest anonymity for sensitive Surveys.

Branding, Templates, Distribution

• Provide branded, templated, tokenized, and public distribution mechanics for Surveys.

Permissions, V1/V2 Scope

• Gate Survey authoring and deployment to Admin/Manager and define phased V1/V1.5/V2 scope.

👥 Tribes (14 goals)

Cross-Mode Architecture

• Establish Tribes as a horizontal, mode-agnostic segmentation primitive that all three modes can create and consume from a single Tribe object.

Membership Types

• Provide five membership types spanning manual, dynamic, petition-sourced, issue-stance, and AI-suggested so any audience can be defined.

Issue Stance Architecture

• Make issue stances first-class consolidated UVP data with confidence and provenance so audiences query a clean canonical layer.

Tribe Builder

• Let users build precise audiences in plain English backed by a transparent, editable, auditable structured criteria layer.

Criteria Expression Language

• Provide an evaluable, composable filter DSL with operators, logic, set operations, and pre-computed fields.

Tribe Library

• Give accounts a managed surface to browse, organize, and operate on their full Tribe inventory including curated system Tribes.

Petition-to-Tribe Pipeline

• Turn petition signatures into automatic Tribe membership and issue-stance signal without manual tagging.

Performance Architecture

• Deliver sub-second Tribe evaluation via hot/cold caching, indexing, and async recomputation within defined limits.

Privacy IP and Two-Tier Boundary

• Isolate customer Tribe data while mining only anonymized aggregate patterns as Politogy IP.

AI-Suggested Tribes

• Proactively surface clustering-derived candidate Tribes for user adoption in V2.

Cross-Mode Audience Resolution

• Automatically intersect cross-mode Tribe consumption against authorization and opt-in scope.

Permissions

• Enforce role-based access to viewing, building, using, deleting, and bulk-operating Tribes.

Provenance and Audit

• Provenance-track every Tribe operation to verify segmentation decisions and consent compliance.

Mobile

• Provide read-and-consume Tribe access on mobile in V1 with the Builder reserved for desktop.

🎙️ Voter Contact (14 goals)

Substrate Philosophy and Scope

• Define one channel-agnostic contact architecture where Posture locks behavior and captured signal is honestly tagged.

Mode Architecture and Product Positioning

• Confine governed Voter Contact to Campaign Mode and enforce correct UVP layer routing and data priority.

Foundational Entities

• Define the six channel-agnostic substrate entities that channel specs reference but cannot redefine.

Continuous Lifecycle

• Standardize a shared Plan-to-Activate-Next session lifecycle with auditable state transitions across channels.

Two-Tier Boundary

• Enforce the customer/Politogy tier boundary at the data layer to protect IP and gate exposure by tier.

Shared Campaign Type Taxonomy

• Maintain a stable substrate-defined campaign type enum that all channels honor.

Volunteer Worker Performance Profile

• Score every worker on four shared dimensions plus channel-specific dimensions in one portable cross-account profile.

Cross-Channel Contact Ledger

• Maintain one append-only source of truth for all contact attempts to prevent double-contact and power saturation analytics.

Polling Engine Integration

• Define the fielding, script, and versioning contracts that let channels deliver Polling Engine instruments.

Heavy-Prescription Next Moves

• Provide a substrate-owned strategic Next Moves queue surfacing fully-specified follow-up actions across channels.

Capture Mode Taxonomy

• Tag every datum as Self-Report, Observation, or Verified so Aggregate Intelligence weights signal honestly.

Compliance Scaffolding

• Define abstract cross-channel compliance primitives (DNC propagation, audit, disclosure, pre-check) every channel honors.

Field Volunteer Permissions

• Constrain field volunteers to minimum data access scoped to their active assignment.

Future Channel Extension

• Allow new channels to extend the substrate without modifying it, via a governed amendment process.