Foundation

Settings

Policy, scope, and validation controls for the Collect → Process → Run system.

Operating Model

Easy to capture. Strict to promote.

Settings defines what the field can capture quickly, what Processing must validate before promotion, and what Run is allowed to consume as trusted operational truth.

Collect accepts imperfect reality. Barcode scans, shelf tags, manual entry, and notes are preserved as structured events even when evidence or confidence is incomplete.

Process determines authority. Normalization, classification, evidence binding, and confidence thresholds decide whether data is promoted to registry truth or routed to unresolved review.

Run consumes verified outputs only. Execution surfaces should never assume unresolved data is true. Ambiguity stays visible until it is resolved intentionally.

Control Surface

What Settings governs

Capture Rules

Collect

Tolerance, evidence prompts, store scope, and incomplete-event posture.

Validation Gates

Process

Classifier policy, confidence thresholds, unresolved routing, and registry promotion rules.

Authority Model

Identity

Who may review, promote, override, export, and act on verified records.

Execution Limits

Run

What the action layer can do once data is trusted enough to drive operations.

Access

Identity & Access

Define who can capture, who can validate, who can promote unresolved data, and who is allowed to operate on verified outputs.

Configure authority across Collect, Process, and Run

Intelligence

Registry Rules

Control normalization, identifier classification, promotion gates, confidence scoring, and the unresolved review path.

Configure truth formation and registry protection

Structure

Retailer Configuration

Register retailers, stores, and permitted collection scope so captured events always retain location and boundary context.

Configure scope and locality

Platform

System

Set platform integrations, retention posture, unresolved handling, evidence policy, and service-level controls for the full pipeline.

Configure infrastructure and operating constraints

Geography

Maps

Control the shared open-source mapping provider used by Boundary, demo, and future location-aware pages from one Foundation-managed settings surface.

Configure tiles, geocoder posture, and shared map runtime defaults

Never lose incomplete data.

Collection may be imperfect, but the system must preserve what happened and surface what is still missing.

Never promote ambiguity as truth.

Registry writes and operational actions should be driven by validated evidence, not optimistic assumptions.

Evidence increases authority.

Settings should raise confidence and permission only when context, validation, and proof support it.

Back to Portal