New Human Workflow Comparison

Revised Human Workflow Comparison

This manual uses the revised human input workflow as the left-side source of truth and overlays the implemented build with explicit DB references and status markers on the right side.

Authoritative source file: /Users/robertwilhelm/Documents/New project/New_human_input.drawio

Revised human workflow vs implemented build

How To Read The Diagram

Left lane: the revised human-authored workflow, kept in its own non-linear shape.
Right lane: the current build mapped onto that workflow with actual DB and storage references.
MATCHED: implemented strongly enough to claim structural alignment.
PARTIAL: implemented in pieces or with a different table shape.
ADDED: the build goes beyond the raw-ingest workflow.
MISSING: the exact lane or contract is not yet implemented.

Strong Matches

MinIO raw-vault usage for retained raw bytes.
PostgreSQL object registry in raw.source_bundles and raw.source_objects.
Immutable audit in audit.event_ledger.
Deterministic metadata extraction and searchable PostgreSQL metadata storage.
Tenant-aware execution and project scoping.

Partial Or Missing Relative To The Revised Human Workflow

No exact flow_a.object_state_log table.
No exact flow_a.input_snapshot, flow_a.lineage_link, flow_a.ontology_join_preset, or flow_a.outbox tables.
No exact PG-A to PG-B outbox/event-bus contract as drawn.
Typed LAS and WITSML extracts exist functionally, but not in the exact flow_a.object_extract_las and flow_a.object_extract_witsml table form.
Quarantine behavior exists, but not as one exact cross-domain state machine.