Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -221,12 +221,6 @@ DATABASE_URL="postgresql://regengine:${POSTGRES_PASSWORD}@localhost:5432/regengi
--output-dir /tmp/regengine-inflow-e2e
```

For the fast golden contract without Postgres persistence, use:

```bash
./venv/bin/python scripts/run_full_fsma_simulation.py --json
```

Run the consolidated backend:

```bash
Expand Down
21 changes: 0 additions & 21 deletions docs/GOLDEN_PATH.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,27 +6,6 @@ The RegEngine golden path is the narrow story we expect demos, tests, and produc
simulate data -> ingest -> validate -> show failures -> export evidence
```

## Fast Verification

Run the deterministic local simulation:

```bash
python3 scripts/run_full_fsma_simulation.py
```

The runner writes artifacts to `/tmp/regengine-golden-path` by default:

- `summary.json` records the simulated lifecycle, detected failure point, remediation replay, evidence hashes, and export metadata.
- `fda_export.csv` is generated through the ingestion service's FDA CSV formatter.

This check is intentionally database-free. It proves that the production spine primitives still line up:

- deterministic Inflow-style source events
- canonical `TraceabilityEvent` normalization
- stateless FSMA rule evaluation
- SHA-256 record hashes and ordered chain hashes
- FDA export columns, including `System Entry Timestamp`

For the heavier live-service scenario, export the service secret first, then use:

```bash
Expand Down
4 changes: 2 additions & 2 deletions docs/audits/RECALL_FIXTURE_AUDIT_2026-09-16.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ This is a historical audit. The invented recall scenario and its runner were rem
| Requirement | Working | Missing (before this change) | Now covered by the fixture engine |
|---|---|---|---|
| 1. Worksheet with tri-state labels | tri-state precedent (`EvaluationSummary.compliant`) | any `linked / no_link_established / unresolved` vocabulary; pallet column; last-location and destination derivation | yes (DB-free) |
| 2. Controlled scenario + answer key | DB-free runner pattern (`scripts/run_full_fsma_simulation.py`) | answer key; multi-case runs; `sample_data` wired to anything | yes |
| 2. Controlled scenario + answer key | DB-free runner pattern (`scripts/run_full_fsma_simulation.py` (removed in #3559, golden-path sim deleted)) | answer key; multi-case runs; `sample_data` wired to anything | yes |
| 3. lot → pallet contents → shipment → receipt → movement | lot-keyed events with raw payload + hash chain; transformation links; SSCC/GLN validators | pallet/container entity; shipment line items; receipt↔shipment link; evidence pointer on every link | yes (in-memory) |
| 4. Splits, mixed pallets, repack, identifier change | split expressible as N transformation rows | mixed pallet; identifier succession; quantity reconciliation across a transformation | yes |
| 5. Expose uncertainty | mass balance per TLC; KDE coverage 409 gate; identity ambiguity blocker | missing-handoff detection; conflicting contents; unmatched identifiers; per-shipment quantity delta | yes |
Expand All @@ -24,7 +24,7 @@ This is a historical audit. The invented recall scenario and its runner were rem

- Tri-state "no verdict ≠ negative verdict" — `services/shared/rules/types.py:96-114`.
- Package manifest with hash, scope, gap analysis — `services/shared/request_workflow/assembly.py:211-261`.
- DB-free deterministic runner with pass/fail summary — `scripts/run_full_fsma_simulation.py:326-401`; test `tests/scripts/test_run_full_fsma_simulation.py`.
- DB-free deterministic runner with pass/fail summary — `scripts/run_full_fsma_simulation.py:326-401`; test `tests/scripts/test_run_full_fsma_simulation.py`. (removed in #3559, golden-path sim deleted)
- Canonical event with verbatim `raw_payload`, provenance, hash chain — `services/shared/canonical_event.py:293-389`; `alembic/sql/V043__canonical_traceability_events.sql:110`.
- Lot → lot lineage table — `fsma.transformation_links`; writer `services/shared/canonical_persistence/writer.py:701-762`.
- SSCC-18 / GLN-13 / GTIN-14 validators — `services/shared/fsma_validation.py`.
Expand Down
6 changes: 0 additions & 6 deletions docs/runbooks/inflow_workbench_design_partner_demo.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,12 +57,6 @@ Inflow prepares the data. The Engine proves it.

## Local Persisted Evidence Proof

Use the fast simulator for quick golden-contract checks; it is DB-free and does not prove persisted evidence:

```bash
./venv/bin/python scripts/run_full_fsma_simulation.py --json
```

Use the full verifier when you need real local Postgres-backed evidence:

```bash
Expand Down
Loading
Loading