Documentation Coverage

The Logidav workflow audit is in progress. Start with the order and carrier journey, the workflow index, or the business-rule coverage backlog. Source review does not establish live configuration or business-owner approval.

Use this matrix to choose where to start and to see what the shared docs do not yet prove. “Unknown” and “Missing” are deliberate evidence states, not invitations to infer a setup command, API, owner, or operational guarantee. A source-verified code path still does not prove deployed configuration, production behavior, or owner acceptance.

The matrix covers all 21 project areas currently listed in the project directory, including Logidav. The project index may contain useful starter notes even where the setup, architecture, or operations cell remains incomplete.

System	Setup	Architecture	Flows	Operations	Evidence	Next gap
Logidav	Local setup	Data flow	Menu interfaces, order, stock, refunds	Runbooks	Reviewed flow refs	Gap details: Validate unresolved menu routes and remaining downstream/provider paths against the intended environment.
Logidav V2	Unknown — project setup gap	Missing	Order, stock, support; V2 participation unknown	Missing	Evidence and gaps	Gap details: Verify V2/legacy ownership, local setup, schedules, and deployment boundary.
Rest Menzzo	Unknown — project setup gap	Missing	Order, stock, support; endpoint participation unknown	Missing	Evidence and gaps	Gap details: Add route-level source refs, consumer map, and API operations guide.
Menzzo Magento	Devbox entry and bootstrap boundary	Custom-module architecture	Product publication, catalog imports, dependency feeds, commerce journeys, workflow map	Source-level failure checkpoints in catalog guides; runtime operations unverified	Pinned source and gaps	Verify configured providers and runtime commerce outcomes; complete physical returns, remaining provider paths, environment setup and worker acceptance.
SAV Menzzo	Unknown — project setup gap	Missing	Support, order context	Missing	Evidence and gaps	Gap details: Verify UI callers, API ownership, auth/session, and case-state transitions.
Logidav ASIR Tickets	Unknown — project setup gap	Missing	Support; wrapper path unknown	Missing	Evidence and gaps	Gap details: Verify device permissions, target routes, build/release, and ticket submission.
Menzzo Chatbot	Unknown — project setup gap	System overview	Chatbot API, support	Missing	Pinned code refs	Gap details: Identify the UI caller and base URL for SAV routes, then verify remaining support failure paths.
Menzzo Chatbot UI	Unknown — project setup gap	Global ownership; UI architecture missing	Chatbot API, support	Missing	Evidence and gaps	Gap details: Verify UI caller branches, uploads, environment config, and deployment runbook.
Menzzo Chatbot Backend	Unknown — project setup gap	Documented connections; full architecture unknown	Chatbot API, support	Missing	Evidence and gaps	Gap details: Verify remaining controller branches, callers, retry behavior, and ops procedures.
Menzzo Chatbot Logs	Unknown — project setup gap	Missing	Chatbot diagnostics context; correlation unknown	Missing	Evidence and gaps	Gap details: Verify schema, ingest path, retention, access, and query semantics.
Catalog Menzzo	Unknown — project setup gap	Missing	Stock and catalog; mobile refresh path unknown	Missing	Evidence and gaps	Gap details: Verify feed authority, refresh/offline behavior, and release steps.
Menzzo Partners	Unknown — project setup gap	Missing	Stock and catalog; partner export path unknown	Missing	Evidence and gaps	Gap details: Verify feed inventory, schedule, payloads, and rejection runbook.
Menzzo EAN	Unknown — project setup gap	Missing	Stock and catalog; EAN rules unknown	Missing	Evidence and gaps	Gap details: Confirm canonical identifier owner, validation rules, and conflict handling.
Ameubleo	Unknown — project setup gap	Missing	Meduse feed producer; WooCommerce consumer and acceptance unknown	Missing	Evidence and gaps	Gap details: Verify WordPress setup, catalog fields, checkout, and theme publishing.
Mosaikasa	Unknown — project setup gap	Missing	Meduse Shopify paths, catalog enrichment; storefront acceptance unknown	Missing	Evidence and gaps	Gap details: Verify backend owner, theme workflow, product/stock fields, and QA.
Miskoh	Unknown — project setup gap	Missing	Missing — content publishing path not mapped	Missing	Evidence and gaps	Gap details: Confirm site owner, plugin/cache boundaries, and deployment.
Tracking Menzzo	Unknown — project setup gap	Missing	Order and shipment context; customer tracking path unknown	Missing	Evidence and gaps	Gap details: Verify URL, invoice, delivery-confirmation, and stale-status behavior.
RDV Menzzo	Unknown — project setup gap	Missing	Adjacent order context; appointment path missing	Missing	Evidence and gaps	Gap details: Verify slot provider, appointment state, notification, and incident guide.
Menzzo Images Resizing Lambda	Unknown — project setup gap	Missing	Missing — ingestion-to-publication path unmapped	Missing	Evidence and gaps	Gap details: Verify storage, supported variants, cache invalidation, and failures.
Menzzo Meduse	Source setup boundary; environment procedure unverified	Vue/API/Artisan architecture	Interfaces, API inventory, editing, catalog structure, media, Logidav enrichment, reference-data sync, connector handoffs	Schedules, queues	Pinned frontend/backend source	Verify live worker configuration, endpoint mismatches, destination processing and environment acceptance.
Menzzo Reviews App	Unknown — project setup gap	Missing	Missing — review collection/moderation unmapped	Missing	Evidence and gaps	Gap details: Verify ingestion, moderation states, retention, setup, and rollback.

Reading the matrix

• A project page may contain useful context while its setup or source evidence is still unknown.
• A shared flow can verify one segment and leave its callers, schedules, retries, or environment configuration open. Read the flow's evidence boundary before relying on it.
• “Missing” means no suitable page is linked here yet. “Unknown” means a page exists but does not establish the requested fact.
• Environment operations, image-resizing ingestion and review paths are intentionally visible as gaps; the current shared flows do not complete those areas.

The Logidav interface map and Meduse interface map now provide screen-to-source entry points. Their route inventories distinguish resolved declarations from missing or incompatible paths.

Remaining expansion work includes identifying the SAV route's UI caller and configured base URL, completing the remaining refund/provider checks, then mapping image-resizing ingestion and review lifecycles, project-local setup, operations, and runtime schedule/worker configuration. Meduse editing, catalog-structure, media and enrichment paths have dedicated source-based guides. The complete product publication loop now connects UI actions to named jobs, file transitions, Magento imports and returned IDs. The older family/attribute guides now include Magento’s intermediate processing. Destination acceptance and runtime configuration remain unverified.

Next workflow gaps after the Meduse audit

Priority	Missing proof	Why it matters
Catalog runtime acceptance	Product publication and Magento dependency consumers now trace the product, family and attribute return bridges. The FTP roots, active launchers, workers and final storefront remain unverified.	A file acknowledgement can precede partial writes or failed indexing.
Meduse runtime and development setup	Confirm the assigned frontend/API pair, tenant, enabled connectors, queue connection and actual scheduler/worker services for a development environment.	Source inventories cannot establish which paths run or give a verified start-to-finish setup procedure.
Commerce and support acceptance	Complete the missing consumer/provider segments described in order to delivery and support and refunds.	Imported orders, local shipment state and refund status checks are intermediate results.
Remaining project journeys	Expand the project-specific setup and flows marked Missing/Unknown in the matrix, especially storefront consumers, partner feeds, tracking, reviews and image resizing.	A project overview or shared-flow link is not a system-specific onboarding guide.

The Meduse reading path now covers five additional source-based journeys. The historical cron notes are preserved and linked; none of these additions claims live runtime or owner acceptance.

Menzzo workflow depth after the publication audit

Journey	Current documentation	Remaining work
New product publication	Interface clicks → flags → JSON → Meduse → JSONL → Magento → acknowledgement → Logidav	Isolated environment proof, matching FTP roots and actual launcher/worker configuration.
Family, attribute, image, file and menu changes	Magento receiver transitions plus the Meduse producer guides	Reconcile physical FTP paths, menu activation, partial failures, media/CDN and rendered results.
Operational stock and price	Logidav producer and Magento route/queue map	Full field-level API/DB/AMQP consumer comparison and a store-view/checkout acceptance trace.
Checkout and payment	Cart and payment journey, including provider-specific browser return/webhook states	Verify enabled providers, checkout configuration and real payment outcomes; complete adapters outside the reviewed paths.
Promotions and recovery	PDP/cart coupons, chatbot links and WhatsApp recovery	Verify the visible trigger, active sender configuration, coupon totals and restored cart in an isolated environment.
Product reservation requests	Product form → OTP → confirmed request → Logidav importer	Establish importer schedule, sent-flag acknowledgement and runtime consent handling; this is not an inventory reservation.
Order, shipment, refund and return	Import, operator item edits and shipment feedback; whole/partial cancellation, pre-refund and reconciliation	Provider/customer-facing acceptance, unresolved shipment-report interface and physical return-to-stock remain open.

These gaps describe documentation depth and missing evidence, not absent application features. The source-flow pass did not execute an application command or inspect production.