Logidav V2

Purpose

logidav-v2 is the newer back-office and operations platform. It complements the legacy Logidav system while introducing newer Laravel, Livewire, and admin tooling for operational workflows.

Stack

• Laravel 10 application.
• Livewire, Filament, Jetstream, Vite, Bootstrap, and DataTables.
• PHP backend with queue, auth, and admin workflows.

Connected Projects

• Logidav remains the current detailed operational reference.
• Menzzo Magento, catalog services, order workflows, SAV, chatbot, delivery, and tracking all connect to the same operational domain.
• Sneat/admin UI planning belongs here when it affects the V2 back office.

Local Docs Submodule

When this repo consumes global docs, use:

cd docs
npm ci
npm start
npm run build

To Expand

• Sneat Integration Plan
• Migration boundary between Logidav and Logidav V2.
• Admin module map.
• Queue and scheduled command inventory.
• Deployment and environment notes.

Dependencies

The page documents Logidav V2 as a newer operations platform connected to legacy Logidav and shared order, stock, SAV, delivery, and tracking domains. Migration and runtime ownership are not established here.

Setup

Application setup is not established by this page. Follow the owning repository's README and setup instructions, and request the approved local access or environment you need. The shared documentation submodule and docs-site commands are described in the repository map and local development guide; they do not start this application.

Flows

See Order to delivery, Stock and catalog, and Support and refunds for shared boundaries; the V2 participation in each is still unverified.

Diagnosis

For an operational screen discrepancy, identify whether the affected action belongs to V2 or legacy Logidav before following either system's runbook. A V2-specific module map and incident guide are missing.

Evidence and gaps

The framework summary is documented, while the migration boundary, exact integrations, V2 queues/schedules, setup, and deployment evidence are missing.

Next evidence to add: source commit and file references for the owned boundary, then repository-specific setup and the relevant operations procedure. See the documentation coverage matrix for the system-wide gap record.