ENGINEERING INDEX / ENTRY 03
CASE 03 / BUSINESS WORKSPACE / WORKING PILOT
The queue is populated. The conflict rule is tested.
James describes starting with law-firm websites that seemed to lack a clear intake path, then widening the research question: what does each site's intake reveal about a possible engineering need? The local outreach workspace gives research, follow-up, and next actions a persistent place to live. It has an imported CRM snapshot, activity history, a due-work view, and a path for recording local decisions.
How can opportunity history become durable, reviewable work without giving an assistant unchecked authority over business records?
Where the handoffs happen.
Repeated imports of the same CSV are detected by digest. The decision path marks an edited record local_dirty; a later import skips that record and counts the conflict for reconciliation. This protection passed a fixture test, but the populated pilot has not yet recorded a local conflict. J-Bot has no approved write path here.
- 01Source snapshot
- 02Import receipt
- 03Opportunity history
- 04Local decision
What the record earns.
601 imported opportunities; 852 activities; one import receipt. Conflict handling is test-proven, not yet observed in the populated pilot.
- Observed receipt
- A read-only SQLite recount on September 25, 2026 found 601 opportunities, 852 activities, and one import receipt dated September 22. One nonprofit's earlier inquiry appears in the imported workspace with eight activity entries; an independent email thread confirms an inbound request and a later reply. That conversation predates the CRM import, so this is evidence of captured history, not CRM-generated outreach. The database has zero local_dirty records and zero recorded import conflicts. Four focused CRM tests passed, including a fixture decision surviving a changed-source re-import.
- Source and scope
- Twilight Outreach's CRM module, SQLite aggregate counts, and four focused endpoint tests. The module and tests are untracked in a dirty checkout; their exact file hashes are pinned in the private case note, not in a release commit.
What this does not prove.
Imported records are real pilot data, but they do not prove an operational local-decision conflict. Drive remains the authority of record. The API-key check is conditional on configuration; access controls, reconciliation, backup/restore, and J-Bot handoff are not qualified by this case.
Where the work goes next.
Create an approved, redacted import-to-review walkthrough; confirm contribution and access controls; then test reconciliation and a human-approved J-Bot handoff before claiming an operated CRM loop.