High-value read-only workflow
Read-only shipment-exception desk: join tracking events, booking state, delivery windows, and proof-of-delivery indexes; surface late or incomplete consignments.
← Back to industry registry
logistics_freight · evidence-backed demand prior · observed 2026-08-27
Logistics & Freight
Logistics demand centers on shipment exceptions, carrier booking, POD filing and customer notices; event ordering and idempotency dominate the data model.
45Observed repo slots
8Distinct repos
3Observed demand cells
9Open matrix cells
Demand atoms and workflow
Demand signal / validated demand
E — Catalogue signal: Flag exceptions, book carriers, file proof of delivery, and notify customers.
U — Not established in this lane; no attributable industry denominator or repeated accepted-outcome receipt.
Atom join
Specification crosswalk: I — monitor_alert, triage_route, schedule_coordinate, sync_handoff, follow_up_chase
Industry model
Entities
States
planned → booked → in_transit → delivered | delayed | damaged → exception_review → resolved
Terminal owner
transport_operations_or_logistics_coordinator
Authority boundary
Read-only tracking/booking/POD views; no carrier booking, route change, customer notice, claim, or dispatch.
Source of truth / exception paths
Source of truth: Transport-management/carrier tracking system; POD repository is authoritative for delivery evidence.
Exception paths: duplicate event; out-of-order status; missing POD; ETA conflict; carrier identity mismatch; location/PII restriction
Discovery preparation
Precomputable context
- shipment/event state machines with out-of-order handling
- TMS/carrier-tracking system model
- archetype fit (exception desk + coordination)
Questions that must be asked
- TMS and tracking-source mix; where POD actually lives
- exception taxonomy that costs money (late, damaged, missing POD)
- customer notification obligations
- carrier mix and EDI/API reality
Contradiction risks
- ETA truth conflicts across sources
- 'real-time visibility' wanted vs data arrives batched/late
Observed repository matrix
These are the non-null rows from repo-matrix-observations.jsonl for this industry. The 1,000-row partition includes reserved cells; only 45 observed repository slots are shown here.
| Repository | Observed slots | Dimensions | Capability families | Observed atoms |
|---|---|---|---|---|
| apifyforge/logistics-freight-intelligence-mcp ↗ | 8 | agent_authority, demand_atom_fit, economics_maintenance, integration_surface, provenance_rights, runtime_deployment, ui_assembly, workflow_behavior | browser | browser_data_entry, monitor_alert, sync_handoff, triage_route |
| okoroaforkingsley30s/obech-flow-logistics ↗ | 7 | data_model, demand_atom_fit, economics_maintenance, integration_surface, runtime_deployment, ui_assembly, workflow_behavior | browser | browser_data_entry, monitor_alert, sync_handoff, triage_route |
| AhmedHassan650/Logistics-Freight-Shipping ↗ | 6 | agent_authority, demand_atom_fit, economics_maintenance, integration_surface, runtime_deployment, workflow_behavior | browser | browser_data_entry, monitor_alert, sync_handoff, triage_route |
| samkomane008/zenit-global-interlink ↗ | 6 | demand_atom_fit, economics_maintenance, integration_surface, runtime_deployment, ui_assembly, workflow_behavior | browser | browser_data_entry, monitor_alert, sync_handoff, triage_route |
| alphaparkinc/genpark-voice-first-logistics-coordinator-skill ↗ | 5 | agent_authority, demand_atom_fit, economics_maintenance, integration_surface, workflow_behavior | browser | browser_data_entry, monitor_alert, sync_handoff, triage_route |
| bhaktofmahakal/Karm-Logistics---Freight-Transport- ↗ | 5 | data_model, demand_atom_fit, economics_maintenance, integration_surface, workflow_behavior | browser | browser_data_entry, monitor_alert, sync_handoff, triage_route |
| Aditya-tiwariMOL/freight-calculator ↗ | 4 | demand_atom_fit, economics_maintenance, integration_surface, workflow_behavior | browser | browser_data_entry, monitor_alert, sync_handoff, triage_route |
| Clearkess/my-awesome-project ↗ | 4 | demand_atom_fit, economics_maintenance, integration_surface, workflow_behavior | browser | browser_data_entry, monitor_alert, sync_handoff, triage_route |
Empty-cell gap matrix
The ten category cells retain both demand and supply state. NO_OBSERVED_DEMAND_SIGNAL means the research denominator is empty; it is not a claim that the workflow does not exist.
| Category / empty-cell key | Observed demand | Candidate coverage | Search wave | Candidate examples |
|---|---|---|---|---|
Intake and normalizationintake_and_normalization | NOT_OBSERVED_IN_750_SLOTS0 slots · 0 repos | NO_OBSERVED_DEMAND_SIGNAL10 candidate repos · 10 source rows | NOT_SEARCHEDno targeted search proposal | LimeSurvey/LimeSurvey, ProcessMaker/processmaker, al1abb/invoify, formbricks/formbricks |
Triage and routingtriage_and_routing | OBSERVED45 slots · 8 repos | SHARED_CANDIDATE_COVERAGE31 candidate repos · 31 source rows | NOT_SEARCHEDno targeted search proposal | Alfresco/alfresco-community-repo, Leantime/leantime, ProcessMaker/processmaker, Worklenz/worklenz |
Records, extraction and auditrecords_and_audit | NOT_OBSERVED_IN_750_SLOTS0 slots · 0 repos | NO_OBSERVED_DEMAND_SIGNAL47 candidate repos · 47 source rows | NOT_SEARCHEDno targeted search proposal | Alfresco/alfresco-community-repo, AppFlowy-IO/AppFlowy, BookStackApp/BookStack, BuilderIO/builder |
Classification and prioritizationclassification_and_prioritization | NOT_OBSERVED_IN_750_SLOTS0 slots · 0 repos | NO_OBSERVED_DEMAND_SIGNAL39 candidate repos · 39 source rows | NOT_SEARCHEDno targeted search proposal | Dolibarr/dolibarr, PostHog/posthog, SuiteCRM/SuiteCRM, apache/superset |
Scheduling and coordinationscheduling_and_coordination | NOT_OBSERVED_IN_750_SLOTS0 slots · 0 repos | NO_OBSERVED_DEMAND_SIGNAL14 candidate repos · 14 source rows | NOT_SEARCHEDno targeted search proposal | calcom/cal.diy, alextselegidis/easyappointments, lukevella/rallly, thunderbird/appointment |
Follow-up and communicationfollow_up_and_communication | NOT_OBSERVED_IN_750_SLOTS0 slots · 0 repos | NO_OBSERVED_DEMAND_SIGNAL23 candidate repos · 23 source rows | NOT_SEARCHEDno targeted search proposal | RocketChat/Rocket.Chat, TryGhost/Ghost, activepieces/activepieces, chatwoot/chatwoot |
Reporting and digestreporting_and_digest | NOT_OBSERVED_IN_750_SLOTS0 slots · 0 repos | NO_OBSERVED_DEMAND_SIGNAL15 candidate repos · 15 source rows | NOT_SEARCHEDno targeted search proposal | PostHog/posthog, apache/superset, bigcapitalhq/bigcapital, cube-js/cube |
Monitoring and alertsmonitoring_and_alerts | OBSERVED45 slots · 8 repos | ZERO_CANDIDATE_COVERAGE0 candidate repos · 0 source rows | SEARCHED_DRYtargeted search eligible | none recorded |
Approval and controlled publishingapproval_and_controlled_publish | NOT_OBSERVED_IN_750_SLOTS0 slots · 0 repos | NO_OBSERVED_DEMAND_SIGNAL21 candidate repos · 21 source rows | NOT_SEARCHEDno targeted search proposal | Budibase/budibase, ProcessMaker/processmaker, activepieces/activepieces, apache/airflow |
Sync and browser operationssync_and_browser_operations | OBSERVED45 slots · 8 repos | THIN_OR_PARTIAL_COVERAGE1 candidate repos · 1 source rows | SEARCHED_DRYtargeted search eligible | activepieces/activepieces |
Shelf candidates joined to this industry
These records come from the permanent source registry's industry-demand join. A joined candidate remains a discovery/research record; qualification and admission are shown explicitly.
| Joined shelf record | Observed slots | Families / atoms | Current verdict | Qualification / admission |
|---|---|---|---|---|
| Aditya-tiwariMOL/freight-calculator ↗ | 4 | browserbrowser_data_entry, monitor_alert, sync_handoff, triage_route | discovery_candidate | NOT_QUALIFIED / NOT_ADMITTED |
| AhmedHassan650/Logistics-Freight-Shipping ↗ | 6 | browserbrowser_data_entry, monitor_alert, sync_handoff, triage_route | discovery_candidate | NOT_QUALIFIED / NOT_ADMITTED |
| alphaparkinc/genpark-voice-first-logistics-coordinator-skill ↗ | 5 | browserbrowser_data_entry, monitor_alert, sync_handoff, triage_route | discovery_candidate | NOT_QUALIFIED / NOT_ADMITTED |
| apifyforge/logistics-freight-intelligence-mcp ↗ | 8 | browserbrowser_data_entry, monitor_alert, sync_handoff, triage_route | discovery_candidate | NOT_QUALIFIED / NOT_ADMITTED |
| bhaktofmahakal/Karm-Logistics---Freight-Transport- ↗ | 5 | browserbrowser_data_entry, monitor_alert, sync_handoff, triage_route | discovery_candidate | NOT_QUALIFIED / NOT_ADMITTED |
| Clearkess/my-awesome-project ↗ | 4 | browserbrowser_data_entry, monitor_alert, sync_handoff, triage_route | discovery_candidate | NOT_QUALIFIED / NOT_ADMITTED |
| okoroaforkingsley30s/obech-flow-logistics ↗ | 7 | browserbrowser_data_entry, monitor_alert, sync_handoff, triage_route | discovery_candidate | NOT_QUALIFIED / NOT_ADMITTED |
| samkomane008/zenit-global-interlink ↗ | 6 | browserbrowser_data_entry, monitor_alert, sync_handoff, triage_route | discovery_candidate | NOT_QUALIFIED / NOT_ADMITTED |
Open gaps
Intake and normalization
NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 10 candidate repositories.
NOT_SEARCHED. Exact P03 source-kind coverage for form/portal intake; generic CRM or Stage 0 tags are not counted as intake coverage.
Records, extraction and audit
NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 47 candidate repositories.
NOT_SEARCHED. Exact P03 document/record kinds; source-specific authority and provenance remain unqualified.
Classification and prioritization
NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 39 candidate repositories.
NOT_SEARCHED. Exact P03 CRM/analytics/search candidates are adjacent supply, not proof of a classifier workflow.
Scheduling and coordination
NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 14 candidate repositories.
NOT_SEARCHED. Exact P03 scheduling kind only; calendar UI alone is not a booking/authority proof.
Follow-up and communication
NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 23 candidate repositories.
NOT_SEARCHED. Exact P03 message/support candidates; consent, approval and idempotency are not inferred.
Reporting and digest
NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 15 candidate repositories.
NOT_SEARCHED. Exact P03 analytics kind; a reporting surface is not a measured client outcome.
Monitoring and alerts
ZERO_CANDIDATE_COVERAGE · 45 observed demand slots · 0 candidate repositories.
SEARCHED_DRY. No dedicated P03 capability kind is mapped; analytics is not silently promoted to monitoring.
Approval and controlled publishing
NO_OBSERVED_DEMAND_SIGNAL · 0 observed demand slots · 21 candidate repositories.
NOT_SEARCHED. Exact P03 approval/signing kinds; an approval-shaped product does not grant host authority.
Sync and browser operations
THIN_OR_PARTIAL_COVERAGE · 45 observed demand slots · 1 candidate repositories.
SEARCHED_DRY. Connector candidates cover a possible sync seam; no direct P03 browser-operation kind is available.
Safe-pilot boundary
Rationale
Synthetic tracking and POD records exercise event ordering and exception ownership without external booking or customer contact.
Falsifier
The read model cannot deterministically handle out-of-order/duplicate events, or value requires carrier/customer side effects.
Sources: research/actionmodel-builder-research-2026-08-26/phase-2/outputs/industry-atom-specifications.md · research/workstreams/p01-client-intelligence/runs/2026-08-27-sprint-1-fable/industry-discovery-priors.jsonl · research/actionmodel-builder-research-2026-08-26/expansion/outputs/repo-matrix-observations.jsonl · research/workstreams/2026-08-28-program-driver/shelf-prebake/industry-gap-matrix.json · knowledge/capability-shelf/source-registry.jsonl