Product

A workbench for deciding what can become evidence.

RegEngine is built around one simple operating rule: supplier data is useful only after it is mapped, checked, fixed, persisted, and explicitly committed.

Verify security

Inflow affects RegEngine before evidence exists

It turns supplier noise into a commit decision.

Raw supplier feed

CSV/XLSX upload or supplier portal, the JSON events API, or EPCIS-shaped records (EPCIS in Preview)

unmapped columns
missing KDEs
broken handoffs
sandbox source mode

Inflow Workbench output

One preflight run containing normalized event candidates, readiness score, fix queue, and commit gate state.

Normalize

Raw rows become CTE/KDE candidates with source, lot, facility, and handoff context.

Score

Readiness exposes whether the feed can support traceability, recall, and export workflows.

Route

Missing KDEs and lineage breaks become owner-ready fix queue items before persistence.

Gate

The commit decision separates sandbox/preflight work from production evidence.

Commit gate says no

Fix before evidence

RegEngine keeps failed preflight work in correction mode until the blockers are cleared.

Commit gate says yes

Persist and prove

RegEngine promotes checked records into tenant-scoped evidence, then uses that evidence for scores and exports.

Blocked or corrected

Bad supplier data is routed back through the fix queue instead of polluting the evidence ledger.

Tenant-scoped evidence

Allowed records persist with tenant context, provenance, run hashes, and audit history.

Export-ready package

Compliance score, recall posture, and FDA/retailer exports use checked records only.

Core loop

Prepare. Prove. Commit. Export.

Inflow handles the messy outside world. The Engine handles rules, persistence, and gate decisions. The result is an audit path your operations team can explain under pressure.

Tenant isolation	Records are scoped to the authenticated tenant via row-level policies; cross-tenant hardening is in active rollout.
Provenance	Evidence commits require traceable source and run context.
Mode separation	Sandbox work cannot silently become production evidence.
Hash verification	Committed evidence carries content hashes so downstream consumers can re-check it independently. Strict downstream verification is rolling out.

Readiness is explicit

Scores, fix counts, sources, and export eligibility stay visible.

Evidence is gated

Production evidence is designed to require identity, provenance, persistence, and clean mode state. Rule enforcement is currently advisory in production and being promoted to blocking.

Exports are explainable

Export packages come from checked records, not a black-box promise. Regulatory acceptance and retention obligations remain with the operator.