MeshCommand MeshCommand

Tables

Every table in every attached database, measured on disk. The path is where the shared resolver actually found the file — an app that computed a path from the module name would report "table missing" for a database that had simply moved.

Task registry mc_task.db

tasks, task types, task-to-task edges, document links · — missing

Projects mc_project.db

the SPACE a task lives in; project_and_task is the authority on which · — missing

Clients mc_client.db

authority for client_id; task.client_id is the denormalised fence · — missing

Calendar mc_calendar.db

calendars, events and series; task_and_calendar_event in mc_task.db is the task edge · — missing

Drive files mc_drive.db

what task_and_drive_file points at · — missing

Print tasks mc_task_print.db

print packets, AR invoices, and the files that bill them · — missing

Identities mc_ory_kratos_identity.db

who task_and_identity points at · — missing

Vendors mc_vendor.db

who task_and_vendor points at · — missing

Mesh registry mc_mesh.db

this app's own surfaces and routes · — missing

Realm workflows mc_realm.db

behavior trees the due-diligence button recommends · — missing

Timelines mc_timeline.db

standardized timelines; a task's are subject_kind 'task' (mirrored from mc_task.db#timeline) · — missing