Artifact Output Atlas
See which customer-facing pages generate Deucalion’s PDFs, exports, credentials, assignments, sync artifacts, and follow-up records.
Before you start
- You are trying to understand where a file, generated record, or downstream artifact came from.
Expected outcome
Teams can trace each artifact to the page that produces it and the pages that consume it later.
Files, PDFs, and exports
| Artifact | Primary tables | Origin surface | Review or access surfaces | Typical downstream use |
|---|---|---|---|---|
| Inspection certificate PDF | Inspection certificate fields on inspections, plus template and branding tables | Inspection completion pipeline, Reports inspection scope | Certificate Viewer, Inspections, Site Details, Inspection History | Customer delivery, quote initiation, compliance evidence |
| Fire damper certificate | Inspection certificate fields on inspections, plus template tables | Fire damper inspection flow and report generation path | Certificate Viewer, Inspection History | Specialist compliance evidence and client delivery |
| Site compliance report PDF | generated_reports, template and branding tables | Reports | Reports preview dialogs, Report Writer, customer delivery | Client reporting, audit packs, office review |
| Defect summary PDF | generated_reports, defects, template tables | Reports | Reports preview dialogs | Client reporting, remediation review |
| Batch certificate pack | inspections plus template tables | Reports | Download workflow from reports desk | Customer pack or archive bundle |
| Asset register export CSV | sites, systems, assets | Reports, Assets, site/system asset workflows | Office spreadsheet workflows | External registers, customer data sharing |
| Import template CSV | N/A generated helper artifact, used by integration_import_runs and integration_import_rows later | CRM, Sites, Assets, Work Orders, Connected Systems imports | Download before staged import runs | Preparing source files for bulk import |
| Issue CSV from imports | integration_import_runs, integration_import_rows | Connected Systems staged import review | Import rerun and source-data correction | Fixing source systems before apply |
Generated records and operational artifacts
| Artifact | Primary tables | Origin surface | Consumers |
|---|---|---|---|
| Draft invoice | crm_invoices | Finance receivables composition flows | Finance detail dialogs, customer receivables follow-up |
| Payment record | crm_invoice_payments | Finance | Receivables summaries, account health |
| Quote | quotes, quote_line_items | Quotes desk, CRM opportunity actions, Certificate Viewer, mobile Quote Create | Work Orders, Finance, commercial follow-up |
| Work order | work_orders, work_order_items, work_order_assignments | Work Orders desk, quote acceptance, imports | Scheduling, mobile Work Order List and Detail, Finance |
| Activity event | page_history_events, page_comments, mention_notifications | Any mutating customer-facing admin or field workflow | Activity Feed, notifications, office triage |
| AI conversation thread | ai_conversations, ai_messages, ai_pending_confirmations, ai_usage_log | AI Assistant or AI Chat | Human follow-up in live routes and screens |
Assignment and sync artifacts
| Artifact | Primary tables | Origin surface | Where users see it |
|---|---|---|---|
| Draft scheduled job | scheduler_tasks, plus draft deployment fields on inspections and work_orders | Scheduling | Scheduler draft lanes and related planning views |
| Deployed assignment | scheduler_deployment_batches, scheduler_deployment_items, scheduler_notification_deliveries, plus deployed work rows | Scheduling | Engineer Dashboard, Inspections list, Calendar, work-order execution context |
| Local draft inspection work | Local-first until synced into inspections, inspection_visit_notes, inspection_items, defects | Mobile inspection workspace | Draft Manager, Sync Status, later office review after sync |
| Pending photo upload | Local-first, then persisted onto owner rows like inspection_items.photo_urls or defects.photo_urls | Mobile evidence flows | Sync Status, later inspection/report output once uploaded |
Credentials and integration artifacts
| Artifact | Origin surface | Consumer |
|---|---|---|
| API key | API Keys, Connected Systems | External client or automation |
| Webhook secret and endpoint config | Webhooks, Connected Systems | External receiving system |
| Connection record and sync log | Integrations, Connected Systems | Import and source-of-truth administration |
Evidence storage rule
Evidence is usually attached to the owning records rather than a global media table. That means:
- inspection evidence is usually on
inspection_items - defect evidence is usually on
defects - asset-condition evidence is usually on
asset_inspection_status - asset photos are usually on
assets
When an artifact looks incomplete, check the owner rows first.
Why outputs sometimes look wrong
Artifacts often look wrong because the source record upstream was incomplete rather than because the output page itself was wrong.
| Artifact problem | Upstream source to check first |
|---|---|
| Certificate looks incomplete | Inspection data, signatures, site/system binding, evidence completion |
| Report pack reads badly | Site branding, inspection notes, defect data, template version |
| Assignment never appeared in the app | Scheduler deployment state, assignee eligibility, workspace access |
| Imported rows created duplicates | Source identifiers, candidate-match review, import warnings |
Best diagnostic rule
When an artifact looks wrong:
- Identify the generating surface.
- Check the source records that feed it.
- Confirm whether the problem is still local/draft or already synced/deployed.
- Only then treat the artifact generation surface itself as the likely fault.