System Reconstruction Coverage Matrix — Integration / Worker / Provider Wave¶
- Status:
CURRENT PLATFORM COVERAGE COMPANION - Source baseline:
qa/master@a5280b7cdc1c78b809ed6f1996ca31491b522146 - Source authority:
PLATFORM_INTEGRATION_OUTBOX_WORKER_PROVIDER_SOURCE_AUTHORITY.md - Rebuild packet:
PLATFORM_INTEGRATION_OUTBOX_WORKER_PROVIDER_REBUILD_PACKET.md - Phase implementation:
USER HOLD - Important: these labels measure documentation/evidence gaps. They do not activate a generic outbox, worker, provider retry or migration.
1. Coverage Vocabulary¶
COMPLETE INPUT
PARTIAL
MAPPED
MISSING
OPEN POLICY
RUNTIME EVIDENCE REQUIRED
PROVIDER EVIDENCE REQUIRED
DEPLOYMENT EVIDENCE REQUIRED
NOT APPLICABLE
Dimensions:
PDT Product/business outcome
ROL Actors/roles/access
PRC Process/sequence
STA State/lifecycle
DAT Data/identity/fields
INT Query/command/error
EFF provider/callback/file effect
UIX UI/UX
OPS operations/recovery
WIK Wiki projection/publication
MIG migration/rollback/caller-zero
VER verification evidence
2. Coverage Summary¶
| Family | PDT | ROL | PRC | STA | DAT | INT | EFF | UIX | OPS | WIK | MIG | VER | Main remaining work | |---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| | Shared integration concern model | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | provider-scoped owner acceptance and first-family selection | | Generic outbox policy | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | NOT APPLICABLE | NOT APPLICABLE | COMPLETE INPUT | COMPLETE INPUT | NOT APPLICABLE | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | preserve canceled policy; no implicit implementation | | QBO invoice | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | PARTIAL | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PROVIDER EVIDENCE REQUIRED | provider search/matching, stale SYNCING policy, Finance role and unknown-result evidence | | QuickBooks Time | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | PARTIAL | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PROVIDER EVIDENCE REQUIRED | conflict rules, attempt identity, provider result/retry and payroll acceptance | | Gmail outgoing | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | PARTIAL | PARTIAL | PARTIAL | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PROVIDER EVIDENCE REQUIRED | required attachment policy, outgoing intent/result identity and current caller inventory | | Gmail appointment watch/intake | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | current watch/cursor/schema/provider state, scheduler and role review | | Telegram outgoing | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | PARTIAL | PARTIAL | PARTIAL | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PROVIDER EVIDENCE REQUIRED | delivery/suppression UI, attempt/dedup policy and operational criticality | | Telegram webhook/cron | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | PARTIAL | PARTIAL | PARTIAL | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | Update ID/replay, scheduler overlap/run identity and role/tenant evidence | | AI Voice/Twilio | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PROVIDER EVIDENCE REQUIRED | current DB/callback/provider/service evidence and profile/capability policy | | Voice transcript filesystem outbox | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | DEPLOYMENT EVIDENCE REQUIRED | host/storage ownership, restart/backlog/multi-instance and expiry evidence | | Gemini live gateway | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PROVIDER EVIDENCE REQUIRED | live service/config/tool/callback/Office fallback evidence | | File object/metadata/link/cleanup | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | RUNTIME EVIDENCE REQUIRED | current object/link/cleanup residuals, retention/owner and worker policy | | Root CLI cron/mail jobs | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | PARTIAL | PARTIAL | PARTIAL | NOT APPLICABLE | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | DEPLOYMENT EVIDENCE REQUIRED | external schedule, overlapping runs, job-run history and active modes | | Future shared Node worker runtime | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | OPEN POLICY | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | DEPLOYMENT EVIDENCE REQUIRED | first approved provider family, topology, lease store and release/rollback | | Provider callback receipt pattern | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | COMPLETE INPUT | OPEN POLICY | COMPLETE INPUT | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PARTIAL | COMPLETE INPUT | PROVIDER EVIDENCE REQUIRED | provider-by-provider identity/security/order and persistence need |
3. Common Contract Coverage¶
| Contract | Documentation result | Remaining evidence/decision |
|---|---|---|
| Local business versus provider state | COMPLETE INPUT | owner acceptance per process |
| Effect intent | COMPLETE INPUT | provider-specific persistence and first family |
| Immutable provider attempt | COMPLETE INPUT | provider-specific schema/owner |
| Callback receipt | COMPLETE INPUT | provider-specific requirement and identity |
| Reconciliation result | COMPLETE INPUT | provider query APIs and manual-review role |
| Suppressed state | COMPLETE INPUT | current UI/readback adoption |
| Unknown-result recovery | COMPLETE INPUT | target-role/provider scenario execution |
| Worker lease/heartbeat | COMPLETE INPUT | queue technology and deployment topology |
| Retry/backoff/manual review | COMPLETE INPUT | provider-specific values/policies |
| Compensation | COMPLETE INPUT | provider/business owner approval contracts |
| Correlation/evidence chain | COMPLETE INPUT | actual caller propagation and provider refs |
| Secret/redaction | COMPLETE INPUT | current support/log/provider screen review |
| Shared/Dedicated worker parity | COMPLETE INPUT | actual deployment design and rehearsal |
4. QBO Detailed Gaps¶
| Area | Current input | Gap |
|---|---|---|
| Local intent/status | transaction QBO fields and conditional claim documented | claim/error field separation and immutable attempts |
| Provider call | synchronous invoice create documented | provider request identity and search/query client |
| Unknown result | duplicate-invoice risk documented | accepted provider matching/reconciliation process |
| Retry | current manual finance path documented | stale SYNCING, retry approval and attempt limit |
| Role | Billing/Finance conceptual owner | current role/page/API/action matrix |
| UI/Wiki | source-specific warnings drafted | current labels/content and Finance acceptance |
| Migration | one-writer/provider-scoped worker documented | selected cohort/sandbox/rollback evidence |
5. Gmail Detailed Gaps¶
Outgoing¶
- inventory all direct Gmail callers;
- classify required versus optional attachments;
- define recipient/target/part identity;
- identify where Gmail Message/Thread IDs are stored or absent;
- define provider lookup/reconciliation method;
- define resend/correction policy;
- separate cron markers from send attempts;
- verify token/credential ownership in Shared/Dedicated deployments.
Watch/intake¶
- verify current
T_MAILBOX_WATCH_STATE, message and item schema/rows; - verify active watch expiration/history cursor;
- characterize Pub/Sub retries and webhook deployment;
- verify manual replay limits and duplicate-message behavior;
- confirm role/access for approval queue;
- define scheduler/register-watch owner;
- publish current Wiki only after mailbox/role review.
6. Telegram Detailed Gaps¶
- distinguish current provider success, suppression, failure and unknown in UI/state;
- inventory every sender caller and business criticality;
- decide whether any family meets outbox re-evaluation triggers;
- define message/effect identity if durable retry is considered;
- characterize duplicate Telegram message impact;
- verify webhook Update ID/callback replay behavior;
- verify tenant/module/secret and linked-user behavior;
- verify cron scheduler/overlap and current Break effects;
- preserve assignment/break authority outside Telegram.
7. AI Voice / Gateway Detailed Gaps¶
| Area | Current input | Gap |
|---|---|---|
| Call intent | Request Key/Call UUID and states documented | current DB/provider evidence and role acceptance |
| Provider unknown | explicit no-retry behavior documented | support query/reconcile and callback window |
| Callback | signature and transactional apply documented | duplicate/out-of-order receipt evidence and optional receipt store |
| Gateway tool | HMAC/timestamp/nonce documented | deployment/service/tool failure characterization |
| Transcript outbox | filesystem format/drain/retry/expiry documented | multi-instance/shared storage ownership and backlog observation |
| Recording cleanup | delete/retry fields documented | current timer/service/provider cleanup evidence |
| Profile | numeric Client 1 compatibility documented | named profile/capability/config migration |
| Retention | 90-day current source value documented | approved privacy/legal/tenant policy |
8. File/Long-Running Detailed Gaps¶
- current storage distribution between EFS/S3;
- active object/metadata/link/readability divergence count;
- pending cleanup count and age;
- orphan object detection authority;
- shared object/link delete policy;
- archive/restore and cleanup overlap;
- file generation workload inventory;
- selected worker versus synchronous upload/download policy;
- signed upload/finalization target decision;
- retention/legal hold and tenant export requirements.
9. Required Documentation Packet¶
docs/reconstruction/PLATFORM_INTEGRATION_OUTBOX_WORKER_PROVIDER_SOURCE_AUTHORITY.md
docs/reconstruction/PLATFORM_INTEGRATION_OUTBOX_WORKER_PROVIDER_REBUILD_PACKET.md
docs/reconstruction/SYSTEM_RECONSTRUCTION_COVERAGE_MATRIX_INTEGRATION_WORKER_WAVE.md
docs/processes/PLATFORM_INTEGRATION_OUTBOX_WORKER_PROVIDER_POLICY_AND_SEQUENCE.md
docs/runbooks/PLATFORM_INTEGRATION_PROVIDER_RECOVERY_RUNBOOK.md
docs/wiki/internal/PLATFORM_INTEGRATION_PROVIDER_WIKI_PROJECTION_PACKET.md
docs/operations/changes/2026-08-07-platform-integration-outbox-worker-provider-documentation-handover.md
10. Current Readiness Disposition¶
Current provider/source map:
DETAILED INPUT
Common intent/attempt/callback/worker model:
DETAILED INPUT
Generic outbox implementation:
NOT APPROVED / CURRENT POLICY CANCELED
Provider-specific policy acceptance:
PARTIAL / OPEN
Provider credentials/connectivity/current rows:
NOT VERIFIED
Current scheduler/worker deployment:
NOT VERIFIED
Current Wiki content:
NOT READ
Target provider worker implementation:
USER HOLD
Migration readiness:
NOT M4
11. Stop Conditions¶
Do not begin an implementation wave when:
- no provider/effect family is explicitly selected;
- generic outbox cancellation is being bypassed;
- provider idempotency/search/reconciliation is unknown;
- local business owner/effect owner is ambiguous;
- credential owner/tenant/deployment is ambiguous;
- callback signature/dedup/order is undefined;
- retry could duplicate invoice/message/call/physical/file effect;
- no manual fallback exists;
- one-writer/rollback/caller-zero is missing;
- filesystem outbox ownership is unsafe for the target topology;
- retention/redaction policy is unresolved for sensitive evidence;
- current provider/role/deployment evidence is required;
- Phase implementation remains held.
12. Next Documentation Wave¶
Deployment / Environment / Observability / Backup / Restore
That wave must connect:
- Shared versus Dedicated deployment identity;
- source/config release identity;
- PHP/Next.js/web/worker/voice-gateway process topology;
- scheduler/service ownership;
- health/readiness/metrics/logs/traces;
- provider/webhook public endpoints;
- DB/file/config/credential backup and restore;
- rollout/canary/rollback/failover;
- evidence required before declaring a deployment healthy.
It must not deploy, change environments or activate workers.
---¶
Source:
docs/reconstruction/SYSTEM_RECONSTRUCTION_COVERAGE_MATRIX_INTEGRATION_WORKER_WAVE.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.