Salesforce integration: briefing for the CTO, Monday 2 November 2026
Prepared 31 October 2026 from Linear (project "Salesforce", P-OCS-56), the collections and salesforce repositories, and the 30 October team meeting notes.
TL;DR
- The integration is real and running on staging: a Sales Order turned Sold in the Omniyat AI sandbox invites the Owner by email, the Owner logs in with a mobile code, and construction updates and documents are read live from Salesforce. Monday's demo does exactly this on a phone.
- Since 25 October the team shipped 17 API releases, the connector up to v0.7.0, six TestFlight builds and 310 merged pull requests across collections, salesforce and cloud.
- In the Linear project 68 of 131 issues are Done, 6 are In progress, 46 are Todo, 7 are Blocked. All 14 decisions agreed with the Salesforce owner are closed; the catch-up plan (30 issues, phases 1 to 7) is the open work.
- Friday 6 November: the Omniyat AI owner journey, seven items, all unblocked today, one owner each. Friday 13 November: payments, pre-handover and Living, nine items. Five items wait on Salesforce answers and carry no date until the answer lands.
- From Monday every Salesforce question is a Linear decision issue with a two-working-day answer. One Blocked state, one link to the decision, status read from Linear, journey report on every Salesforce pull request before merge.
- Four asks of the CTO: back the two-day SLA, reserve the Salesforce owner's time this week, accept the 6 and 13 November milestones as the plan of record, approve production sharing for pre-handover data.
1. What this meeting is for
- Show that the Salesforce integration is wired and working, with a live journey, not a mock.
- Commit to a scope for Friday 6 November that the team controls, and name what it does not include.
- Show how Salesforce requests and questions flow through Linear from now on, and who does what.
2. Where we are
What has shipped since 25 October (all on staging):
- API releases api-v0.3.107 through api-v0.3.123; the latest went live on 30 October.
- Connector releases up to connector-v0.7.0 and the QA bundle qa-v0.2.3.
- Mobile TestFlight builds RC 38 through RC 43 (UI revamp), 27 to 30 October.
- Merged pull requests since 25 October: 155 in collections, 72 in salesforce, 83 in cloud.
- The 28 October demo chain (Omniyat AI Sales Order Sold, connector, Owner invitation, Owner first login by mobile OTP) was built and released; the demo itself slipped because the stakeholder was unavailable.
- A demo data set exists in the Omniyat AI sandbox since 30 October: one project, four towers (one per journey stage), 36 units and eight demo owners, each with a unit in every tower.
What is live from Salesforce today in the Owner app, and what is not:
| Area | Source today | Org |
|---|---|---|
| --- | --- | --- |
| Owner invitation on Sales Order Sold | Live, connector event | Omniyat AI |
| Owner first login, OTP to the mobile held on the Salesforce Account | Live read; company buyers not yet supported (A2) | Omniyat AI |
| Unit stage and pre-handover readiness | Live read | Omniyat AI |
| Construction updates and milestones | Live read; photos, percentages and stage are local editorial content | Omniyat AI |
| Owner documents | Live read of Document__c and files, cached locally on first open | Omniyat AI |
| Payments, instalments, invoices | Local seeded rows; no Salesforce read yet | none |
| First Visit booking | Live read and write of appointments | Corven AI |
| Household invitation | Live write to Resident__c, feature-flagged on | Corven AI |
| Move-in application | Local draft; submit writes a Move-in Case with pets, vehicle and files | Corven AI |
| Services, maintenance, amenities | Partly mapped; about 30 of 50+ service forms compared field by field | Corven AI |
QA, per the 30 October meeting: cycles 1 to 7 are about 75% executed, 26 tests left, 18 blocked; cycle 8 has started; 19 Salesforce end-to-end scenarios are prepared for cycle 9, covering family access, construction updates, payment updates, visits, amenities, rescheduling and cancellation.
3. Why we are late, and what changed
| Cause | Change |
|---|---|
| --- | --- |
| No single Salesforce decision owner with reserved time; questions waited in chat | Every question is a Linear decision issue owned by the Salesforce owner; the project lead chases a two-working-day answer. The CTO is asked to back the SLA. |
| Field mapping started late; about 30 of 50+ service forms mapped | Mapping is a tracked phase (F1) with a date, and missing Salesforce fields are added before mapping continues. |
| Staging unstable on QA weekends | Release freeze from Sunday midday before any demo or QA weekend; releases run through the gated cycle, 12 minutes per API release. |
| Features merged with the UI done and Salesforce not connected | From 3 November, collections and salesforce pull requests that touch Salesforce behaviour link a journey report before merge. |
| The 28 October demo slipped on availability | Demo owner named; the dry run is recorded on Sunday so the demo never depends on one person or one environment. |
4. Commitment
Friday 6 November, the Omniyat AI owner journey, all unblocked:
| Item | Issue | Owner |
|---|---|---|
| --- | --- | --- |
| A1 Sold-trigger Owner invitations proven on staging | OMN-1017 | Owner API owner |
| A2 Owner mobile OTP, including company buyers | OMN-1018 | Owner API owner |
| B2 Construction progress and files as the integration user | OMN-1020 | Connector owner |
| B4 Owner document downloads through Salesforce Files | OMN-1022 | Connector owner |
| D1 Handover booking, rescheduling and cancellation | OMN-1027 | Tickets owner |
| D2 Handover Completed event path | OMN-1028 | Tickets owner |
| E1 Move-in ticket, pet and vehicle writes in Corven | OMN-1029 | Tickets owner |
Friday 13 November, payments, pre-handover and Living:
| Item | Issue | Owner |
|---|---|---|
| --- | --- | --- |
| B3 Payment plan, instalments, invoices and receipts | OMN-1021 | Connector owner |
| C1 Pre-handover entry signal | OMN-1023 | Connector owner |
| C2 Completion notice, BCC and final area | OMN-1024 | Connector owner |
| E2 Household relationship writes and readback | OMN-1030 | Identity owner |
| F1 Service receiving and status mappings | OMN-1031 | Connector owner |
| F3 Maintenance Case access and lifecycle | OMN-1033 | Connector owner |
| G1 Existing-event notification paths | OMN-1035 | Owner API owner |
| G2 Per-scenario notification contracts | OMN-1036 | Gus |
| G3 Sandbox workflow states for end-to-end QA | OMN-1037 | Gus |
Blocked until a Salesforce answer lands (not committed to a date):
| Item | Issue | Waits on |
|---|---|---|
| --- | --- | --- |
| C3 First Visit | OMN-1025 | Q2 org, appointment type and duration |
| C4 Snag records | OMN-1026 | Q4 Onsite API date and snag records |
| F2 Service confirmation | OMN-1032 | Q6 booking confirmation and proof of payment |
| F4 Amenity reservations | OMN-1034 | Q5 availability, capacity and booking authority |
| G4 Production sharing approval | OMN-1038 | CTO approval |
Each blocked item starts the day its answer lands and carries its own build lead time, stated on the issue.
5. How requests flow from now on
- A Salesforce question or request becomes a decision issue under "Carl: Salesforce questions" (OMN-1016) or the Decisions stream, assigned to the Salesforce owner.
- The build issue it holds up moves to Blocked with a
blockedBylink to the decision. There is one Blocked state; "Blocked by Salesforce" is retired. - The project lead chases every open decision daily; the answer-by is two working days.
- When the decision is Done, the build issue moves to Todo in the current cycle and the phase owner schedules it.
- The project's Insights views (pending inputs queue, owner board) are the status page; no separate report.
- A pull request in collections or salesforce that touches Salesforce behaviour links its
oc qajourney report under "Verification and testing" before merge. A CI gate that runs journeys on every pull request is a Phase 7 follow-up.
6. What each person does this week
| Role | This week |
|---|---|
| --- | --- |
| Gus | Presents; owns Phase 7 and the two decision items G2, G3; signs off releases; applies the Linear changes. |
| Project lead (connector owner) | Chases the eight Salesforce questions to a 4 November answer; owns Phases 2, 3 and 6; delivers B2 and B4 by 6 November. |
| Salesforce owner | Answers Q1 to Q8 by 4 November; deploys any field or sharing change the answers need. |
| Owner API owner | Delivers A1 and A2 by 6 November; G1 by 13 November. |
| Tickets owner | Drives the Monday demo; delivers D1, D2 and E1 by 6 November. |
| Identity owner | Delivers E2 by 13 November; supports the first-login path during the demo. |
| QA lead | Runs the 19 Salesforce scenarios in cycle 9; starts the Figma visual pass in parallel. |
| Mobile | Keeps the demo phone on the build that passed the first-login journey; ships the revamp build to TestFlight after the backend merge. |
7. Asks of the CTO
- Back the two-working-day answer SLA on Salesforce decisions.
- Reserve the Salesforce owner's time this week for the eight open questions.
- Accept the 6 November scope and the 13 November milestone as the plan of record.
- Approve production sharing for new-customer pre-handover data (G4).