Partner demo
and implementation progress
React is the end-user application. Linked Odoo databases and native screens are isolated technical QA evidence, not the daily user interface. This page shows what is present, what has passed scoped verification, and what still needs work. Use clearly labelled synthetic demo records.
تطبيق بيلد إنجن هو واجهة الاستخدام للمستخدمين، فيما يتولى أودو 20 حفظ السجلات وإدارة العمليات الأساسية. توضح هذه الصفحة الوظائف المتاحة وما تحقق منها وما تبقى.
156 / 164 stories are fully acceptance-verified DONE (95.1%). Classification: 1 PARTIAL, 0 MISSING and 7 BLOCKED. The active 90% target requires 148 DONE (90.2%). Nine stories beyond the 75% milestone now verify initial master-data imports, reviewed source links and rationale, mandatory exit gates, manual ticket/SLA and quality escalation, weighted quote comparisons, BOQ operational actuals, and posted project financial margin and budget/actual reports. Each has isolated native and authenticated production-build browser evidence. Backend 355/355 and React 120/120 pass. The portable manual embeds 410 screenshots and explains the new workflows in both languages. These are scoped engineering acceptance results; source legitimacy, automatic escalation tiers, inventory/GL valuation policy, model accuracy and regulatory or accountant production sign-off remain separate. Three further stories now verify configured independent CRM/charter approvals and client-only snag reporting after handover. The active target is at least90%. Offline assigned-project downloads, encrypted captures, reconnect/conflict/photo retry and authorized archive search with a separate bounded index worker now pass native and authenticated browser acceptance.
Progress at a glance
1 PARTIAL · 0 MISSING · 7 BLOCKED. Totals are generated from the requirements traceability matrix.
Odoo and React footprint
Construction and Saudi accounting databases are isolated internal QA evidence, not the React end-user interface. Module counts do not represent completed user stories. Accountant UAT, statutory validation and official portal onboarding remain open.
Feature areas
Saudi accounting
PARTIALThe consolidated KSA package is installed in the separate accounting QA database and includes localization, financial reports, assets, budgets, bank imports/reconciliation and read-only local advice. Accountant UAT, statutory validation and official ZATCA/bank onboarding remain.
CRM and sales
PARTIALReact workflows cover customers, leads, qualification, approvals, pipeline updates, tender records and won-opportunity project conversion. Public tender discovery, proposal authoring/approval and fully reconciled funnel acceptance remain.
Purchase and suppliers
PARTIALReact supports supplier register, qualification review, material requests, RFQ alternatives, receipts and quote compliance. Supplier evidence/eligibility policy, complete RFQ/subcontract and invoice reconciliation remain.
Construction execution
PARTIALOdoo/React slices cover projects, BOQ, schedule, site stock, time, equipment, maintenance, quality/safety, drawings, RFI, submittals, contracts and dashboards. Full end-to-end site-role acceptance, closeout and offline field sync remain.
AI specialists
PARTIALLocal-model agents provide bounded advice and human-reviewed drafts for selected CRM, procurement, BOQ and schedule tasks. Arabic/English evaluation, citations, reliable background jobs and complete agent coverage remain.
Saudi portals and offline
BLOCKED / PARTIALOfficial transactional integrations are not active. Etimad, Balady, Ejar/Wafi, ZATCA and bank services need approved products, credentials and sandboxes. Offline sync, conflict recovery and field-soak tests remain incomplete.
Latest verified feature · Drawing-linked submittal revisions · Checkpoint 405
In an isolated React → BFF → Odoo acceptance run, a Site author created and submitted a submittal against a current issued drawing with PDF evidence. A separate PM requested a revision; the Site author resubmitted revision 2 with updated evidence; the PM approved it with rationale. Fresh readback verified project/company scope, drawing linkage, actors, timestamps, immutable revision snapshots and ordered audit events.
- Native Odoo correspondence tests: 29/29; live browser journeys: 2/2.
- Invalid required input returned 422 without a write; a user without the project role received 403 for protected reads/exports.
- BE-147 correspondence Excel export was exercised in the same QA run and remains PARTIAL because broader register and role/company acceptance is open.

React operational exports · Checkpoint 404
Authorized users can export filtered BOQs, daily site reports and the project correspondence register (RFIs/submittals) to Excel. Correspondence includes state, actors/timestamps, deadlines, response or decision, drawing/revision detail and audit history. Arabic workbooks use RTL, and formula-like labels are stored as literal text.
- Correspondence export backend tests: 2/2; React download browser journey: 1/1. Current-source isolated role QA: native Odoo 29/29 and live React→BFF→Odoo journeys 2/2; PM download passed and unauthorized same-company export was denied. Earlier BOQ/site workbook tests: 2/2; download journeys: 2/2.
- Project/type/search/language filters are preserved. Invalid input returns 422 before Odoo; project access errors return 403 without data disclosure. Exports are read-only.
- Other operational registers and live non-admin/foreign-company acceptance remain. Verified story count is 156/164 (95.1%); BE-147 stays PARTIAL.
Latest verified feature: project charter AI drafts · Checkpoint 402
Project Managers can create source-grounded English and Arabic charter/baseline suggestions in React. Both remain pending for human review. Fresh login reopens drafts with task phases, citations, uncertainty, actor, timestamp and company. The AI does not create or approve an official charter.
- Native Odoo acceptance: 5 passed, 0 failures/errors; authenticated live browser: 1 passed.
- Unsupported language returned 422 with no write. Same-company reader saw no AI drafts and could not generate one; foreign-company PM list/create were denied without disclosure. Project and task records stayed unchanged.
- Disposable QA clone dropped and source database unchanged. Totals: 156 DONE, 1 PARTIAL, 0 MISSING, 7 BLOCKED (95.1% fully verified).
Checkpoint 402 · Isolated live QA evidence · Full story matrix
Verified feature: variation creation, review and impact advice · Checkpoint 417
A PM created a variation in React; Odoo persisted its draft, project/company, BOQ line, actor and computed amount. Source-cited English/Arabic and newly created variation advice stayed pending and non-mutating. An independent Build Engine Owner approved one request and rejected another with mandatory rationale. Invalid language and short decision rationale returned 422 without state changes; requester self-approval and same-company reader/foreign-company list access were denied.
- Native AI bridge tests: 4/4; clean variation lifecycle/approval suite: 21/21; authenticated live React → BFF → qwen3.8:27b → Odoo browser journey: 1/1.
- Readback verified React-created draft, company/project, creator and calculated SAR 225 amount; cited advisory remained pending. Approval saved immutable Owner/time/rationale, applied SAR 750 once (BOQ 100→110) and preserved the prior baseline. Rejection saved its separate immutable audit and left the BOQ unchanged.
- Disposable clone dropped; source database unchanged. Story totals: 156 DONE, 1 PARTIAL, 0 MISSING, 7 BLOCKED (95.1% fully verified).
- DEC-06 is provisionally resolved for variations using independent Owner review; other listed workflows remain open. Advisory drafts must be regenerated if their source revision changes.
Checkpoint 417 · Isolated live QA evidence · Full story matrix
Latest feature: CRM account research and opening message
React drafts a CRM account summary, fit hypotheses, research gaps and an unsent opening message using only current, company-scoped Odoo lead and organization facts. Odoo checks Sales/Owner permission, linked-company scope, source revision and exact citation IDs before saving a pending suggestion. False/None/blank Odoo sentinels are removed from model input. Drafts reopen with actor, time, company and project; the live flow validates invalid input and denies unauthorized and foreign-company access without disclosure. No CRM record is modified or outbound message sent.
- Backend generator unit tests: 5/5; native Odoo tests: 4/4; authenticated React → BFF → Qwen → Odoo browser journey: 1/1.
- Source fingerprint unchanged; clone dropped: True; Odoo healthy: True.
- Root reviewed the full Arabic draft and uncertainty as understandable and appropriately cautious; no false/null value leaked. External account verification and actual contact/consent remain separate scopes (BE-020/022 and BE-030).

Checkpoint 399 · Isolated live QA evidence · Full story matrix
Latest React feature: material variance and ticket drilldowns · Checkpoint 398
React opens authoritative Odoo material variance and open-ticket records. Drilldowns show source IDs and available project, company, responsible-user and timestamp metadata.
- Invalid page size returned field-level 422 with no Odoo call or writes.
- Same-company PM was denied without disclosure; a foreign owner saw only their company’s ticket data.
- Native Odoo: 1/1; backend invalid-filter: 1/1; preview plus authenticated live browser: 2/2; React units: 96/96; production build passed.
- Odoo source readback confirmed unchanged records. A3 write audit is N/A because this drilldown is read-only; persisted state and available audit metadata are visible. Clone and worker removed; source unchanged.
Previously verified React feature: persistent CRM scouting chat · Checkpoint 396
Owner chats with the local scouting agent about one current CRM lead. Odoo saves each answer as a read-only draft turn with its exact lead source/revision, uncertainty, company, linked project, actor and timestamp. Close/reopen loads the transcript from Odoo; it is not kept only in browser memory.
- Invalid short input returned HTTP 422 and created no turn. Native checks denied unauthorized and foreign-company readers, stale source revisions and stale conversation versions.
- Focused native tests 2/2; backend/API tests 240/240; authenticated React → BFF → Qwen 3.8 27B → Odoo journey 1/1. QA clone and temporary services removed; source database unchanged.
- AI text is marked as draft, cites the current CRM lead and shows uncertainty. A separate human action remains responsible for qualification.
Latest verified feature: auditable Arabic BOQ spreadsheet imports · Checkpoint 327
React BOQ spreadsheet imports suggest mappings for common Arabic headings, parse Arabic-Indic/Persian digits and Arabic separators, map Arabic item types, and reject duplicate source-column mappings. Odoo retains immutable source filename, exact workbook SHA-256, mapping, row count, importer and timestamp with the BOQ. Raw fields are restricted to the system group; the bridge returns them only after BOQ/project access checks. React shows provenance after reopening; workbook bytes are not stored.
- Isolated native Odoo retry/provenance/security test: 1 passed. Backend business/import suites: 224 passed, 314 subtests. React import/reopen Playwright journey: 1 passed.
- Namaa demo schema upgraded after verified backup; read-only React → BFF → Odoo smoke passed; no shared business rows were created.
- History search/retention policy, broader role/company acceptance, reusable mappings beyond BOQ and full BE-050 acceptance remain open.
Checkpoint 327 · Isolated history QA · Arabic parser QA · Full story matrix
Latest accounting feature: filtered React payment CSV export · Checkpoint 317
React lists native receipts and supplier payments, pages company-authorized results in stable date/ID order, and exports every payment matching current search/status filters across pages. CSV includes linked documents, actor/time, references and reversal details; formula-like values are neutralized and fields quoted. Draft cancellation, reasoned posted-payment reversal and pooled/exact grouped allocations remain available through their audited flows.
- Native Odoo payment tests: 6/6; React units: 89/89; export helper: 4 passed; payment browser journeys: 5/5; production build passed.
- Authenticated isolated React→BFF→Odoo journey downloaded and read a CSV with the QA receipt, grouped payment, linked invoices and reversal reason (3 payment rows). Export stops at 5,000 rows and checks for additional matches before showing a truncation notice.
- Disposable QA resources were removed; shared
namaa_ksabusiness records were unchanged. BE-160 remains PARTIAL for statement/internal-transfer React workflows, complete AR/AP, broader roles/currencies and accountant UAT.

Checkpoint 317 · Isolated live QA evidence · Full story matrix
Latest feature: company onboarding and first-value sample project · Checkpoint 310
An Owner can start a company-scoped Odoo checklist in React, record completion notes, and reopen the state with actor/time audit. Stale revisions are rejected. The first-value action creates one labeled sample project with five linked project tasks; it creates no customer, supplier, purchase order, invoice or posted accounting entry.
- Isolated Odoo QA: 4 tests passed for persistence, validation, role/company boundaries, audit, idempotency and zero accounting moves; backend: 212 passed; React: 85 unit tests, 1 responsive preview browser journey and production build passed.
- The preview is local and clearly labeled. Signed-in React→BFF→Odoo acceptance remains. The shared database was unchanged;
be_onboardingis not installed there.
Latest feature: role-based scheduled in-app digests · Checkpoint 309
React shows assigned activities, pending Odoo approvals and overdue quality actions. Owners configure all 18 role/topic combinations with audit and revision protection. Odoo generates daily/weekly in-app digests at 08:00 in each user's timezone, stores user/company-scoped snapshots, prevents duplicate runs, rechecks access on read, and records who marked a digest read and when.
- Isolated Odoo: 2 tests passed, including daily/weekly scheduling, idempotency, read state and company/user scope; backend: 211 passed; React: 85 unit tests and 1 notification browser flow passed; production build passed.
- Email/SMS/push, live role/company acceptance and rollout remain open. The shared database was unchanged.
be_dashboardis not installed there and its runtime image lacks OCAreport_xlsx, so the live bell is not enabled.
Project expenses now available in React
The optional Build Engine expense add-on is installed with native Odoo Expenses in local demo database namaa_ksa. Admin is linked to the synthetic employee “Demo Expense Employee (Administrator)”; capability checks now pass and the user has 2 eligible company projects and 6 expense categories. No expense claim has been created or posted.
- React creates an idempotent draft linked to the active company, employee and project, and can submit it through Odoo’s native review process.
- Odoo remains responsible for approval, accounting and reimbursement. Receipt capture and broader role/company acceptance remain open.
- The BRS count remains 156 / 164 (95.1%). This feature does not add to verified story completion.
Project expense user guide · Test results · Purchased module review
Verified construction AI: project risks and owner follow-up · Checkpoint 400
React drafts source-cited schedule, cost and quality risks and closeout lessons from authorized Odoo sources. After independent Owner review, an explicit action can assign a current risk finding to a same-company Project Manager, Finance user or Site user. Odoo creates an internal project activity and source-cited audit entry; no risk report is published or sent.
- Focused Odoo native report bridge: 7 passed, 0 failures, 0 errors; authenticated live React → BFF → Qwen 3.8 27B → Odoo journeys: 3 passed.
- Readback verified risk approved reviewed by report.owner; notification assigned to report.pm with Odoo activity #5; lessons approved included closeout/task/RFI citations.
- Invalid inputs returned field-level 422 without partial writes. Same-company reader and foreign Owner/PM access to the target project's report list were denied without disclosure; foreign users' own-company lists remained scoped. Combined QA passed and the disposable clone/services were removed; source database unchanged.
- BE-151, BE-155 and BE-157 passed their supplied acceptance criteria. Broader portfolio-risk forecasting and unsourced risk mitigation are separate remaining product scope.
Checkpoint 400 · Combined isolated live QA · Full story matrix
Closeout lessons workflow
Latest construction acceptance: charter and closeout · Checkpoint 293
Current-source isolated React → BFF → Odoo acceptance now covers the charter approval and closeout journeys. The PM created and submitted a charter; a separate Owner approved it with immutable event history. The source-cited AI charter/baseline suggestion stayed pending. A PM recorded all seven closeout attestations and reopened the saved closed certification; the Odoo project remained active.
- Charter and AI native suite: 7 passed; live two-role browser journey: 1 passed. Closeout suite: 6 passed; live PM browser journey: 1 passed.
- Disposable test clones and the temporary `namaa_ksa` source snapshot were dropped; shared source database unchanged. The earlier Checkpoint 292 upgrade made the three model tables available in local `namaa_ksa`.
- Stories remain PARTIAL: DEC-25/21, automated finance/stock reconciliation, broader roles/companies, Arabic review and full A1–A4 remain open.
Checkpoint 293 · Charter/AI live QA · Closeout live QA · Full story matrix
Latest accounting improvement: project-attributed cash flow · Checkpoint 291
An authenticated finance user ran project-filtered Cash Flow through React, the BFF and Odoo on an isolated clone. The local React workspace is also updated and verified. Its labeled draft-only demo cash move is SAR 100, allocated 50% to the selected project analytic account; React and Odoo both return a SAR 50 outflow. The journal entry stays in draft and does not affect posted totals. Project views omit company-wide opening and closing cash balances.
- Accounting KSA report class: 8 passed; security/API suite: 15 passed; BFF boundaries: 3 passed; React journey: 1 passed.
- Isolated finance-user journey downloaded filtered PDF and XLSX; local admin smoke at
localhost:3200also passed both downloads. - The local demo bridge was upgraded with required Odoo MRP dependencies after a protected DB backup. The QA clone was dropped. A labeled project/account and one draft entry were added to demo
namaa_ksa; no transaction was posted. - Broader role/company acceptance, accountant UAT and full A1–A4 remain open.

Checkpoint 291 · Native report QA · Isolated and local runtime QA · Full story matrix
Latest CRM feature: indexed construction trade/category matching · Checkpoint 337
CRM leads and opportunities retain validated code lists as the source of truth. A synchronized normalized Odoo relation and composite company/kind/code index now keep configured mandate matching in PostgreSQL instead of scanning company leads in Python. Odoo 20 company-scoped access domains protect direct reads of the projection.
- Clean-install Odoo tests: 2/2 passed, including a foreign-company index read denial.
- Live React → BFF → disposable Odoo journey: 1/1 passed; the React-created lead was indexed, matched correctly, and wrong-code/disallowed-source leads were excluded.
- Upgrade/backfill on a disposable clone: passed; existing JSON codes were backfilled. Clone and temporary QA services removed.
- Local demo upgrade to be_tender .6 and bridge .42 followed a validated mode-0600 backup; services are healthy and no shared business records changed. Large-volume performance benchmarking remains open.
Checkpoint 337 · Isolated native QA · Live acceptance evidence · Migration QA · Live React editor screenshot · Full traceability
Latest feature: duplicate-safe Saudi bank CSV imports · Checkpoint 335
Accounting KSA now generates deterministic transaction IDs for mapped CSV/Excel rows when the bank export has no ID column. Stable normalized fields make the same transaction recognizable on retry; an occurrence counter keeps repeated equal rows separate during the initial import.
- Native QA imported three rows, including two identical transactions, and retained all three.
- Re-importing the same file skipped the existing rows; an extended statement imported only the new transaction.
- The 11-case CSV parser class plus the native retry/overlap regression passed 12/12 on a disposable clone, which was dropped. Arabic/Persian digits, localized dates and Saudi separators are also supported.
Bank-specific formats/maps and banking-role UAT remain open; rows with no bank ID cannot be perfectly matched when their mapped transaction details are later amended.
Checkpoint 335 · Isolated QA evidence · Arabic digit normalization
Latest feature: project archive includes ACL-checked DMS files · Checkpoint 289
Project Archive exports approved proposal and confirmed BOQ PDFs, eligible drawings and approved submittal revision files, direct project attachments, and ACL-checked OCA DMS files when DMS is installed. DMS-backed attachments are exported only through their DMS file and cannot bypass directory permissions. Export is refused if the active user cannot read every active DMS file linked to the project. The manifest records source IDs, revision metadata, approval time and SHA-256 checksums. A foreign-project attachment is excluded. Odoo persists an immutable export record; React can reopen history and download the saved package.
- DMS archive native lifecycle/security test: 1/1 on a disposable clone with DMS installed. Existing live React→BFF→Odoo direct-attachment journey passed 1/1 at Checkpoint 284. BFF route 2/2 and React unit 85/85 are inherited from checkpoint 281, not rerun.
- Odoo verified the private linked attachment, `exported` state and whole-ZIP checksum; embedded proposal, BOQ, drawing, approved-submittal and direct project attachment bytes matched their manifest/source checksums; pending submittal and foreign-project attachment were excluded. Reader and foreign-company probes were denied.
- The disposable clone was removed; shared
namaa_ksawas unchanged. DMS is not installed in the shared runtime or its configured addon path, so isolated integration verification does not mean it is deployed. Knowledge items, broader role/company acceptance and full A1–A4 remain.

Checkpoint 289 · DMS archive QA · OCA DMS suite QA · Checkpoint 284 live React QA · Full story matrix
Latest feature: live React project milestones and stakeholder obligations · Checkpoint 280
An ordinary Project Manager enabled project milestones and recorded a stakeholder handover obligation in React. The milestone links a named stakeholder, responsible person and project task; Odoo persists the company/project scope and blocks completion while the linked task remains open.
- Authenticated React→BFF→Odoo browser journey: 1 passed on a disposable clone. Reopening the plan showed the persisted milestone and obligation.
- Invalid blank task input returned HTTP 422; unauthorized and foreign-company write attempts were denied. Native readback confirmed stakeholder, responsible user, task, actor and project/company links.
- QA clone and temporary services were removed; shared
namaa_ksawas unchanged. Broader role/tenant, Arabic/accessibility and full A1–A4 acceptance remain.

Latest feature: live React proposal + BOQ archive · Checkpoint 279
React Project Archive saves an immutable internal pack containing an independently approved proposal PDF and confirmed BOQ baseline PDF. Odoo rechecks company/project access and source approval/state, renders the baseline with a native QWeb report, and stores private checksummed PDFs with actor/time/rationale. The authenticated BFF serves project-scoped PDFs with private no-store headers. Nothing is published or emailed.
- Authenticated Project Manager React→BFF→Odoo browser acceptance passed 1/1 on a disposable clone. Both PDF downloads returned 200 with PDF signatures and private no-store headers. A read-only user and foreign-company project probe were denied with 403.
- Odoo readback verified the saved project/company/source links, PM actor, rationale, private attachment ownership and checksums. QA clone and temporary services were removed; shared
namaa_ksawas unchanged. - Earlier verification: focused Odoo proposal suite 12/12 after final archive refinement; full isolated custom-module suite 382/382 before that refinement; BFF 4/4, React units 85/85 and production build passed. Broader role/company matrix, Arabic visual review and complete A1–A4 remain open.

Checkpoint 279 · Live QA evidence · Checkpoint 278 · Full story matrix
Latest feature: approved technical proposal archive · Checkpoint 261
After independent Sales Manager/Owner approval, React can save a private, immutable PDF to the CRM opportunity archive. The React project archive now loads accessible projects on direct entry and lets users choose a project before opening the same document. Odoo rechecks reviewer event, source revision, company and project access; the BFF validates company, PDF signature, size and filename. Archive is internal only: nothing is emailed or published.
- Full isolated Odoo regression: 373 passed; 0 failures; 0 errors (fresh isolated all-module Odoo 20 run); backend: 238 passed; 2 skipped; 265 subtests passed; React: 80 passed; focused browser: 27 passed; full business.spec.js browser suite, including synthetic CRM approval/archive and direct project selection/archive/PDF link journeys.
- Live role acceptance, QWeb layout in target runtime, Arabic visual review and customer-release authority remain open.


Checkpoint 261 · Checkpoint 260 · Archive QA · Full story matrix
Latest feature: CRM proposal approval and revision
React now lets an independent Sales Manager or Owner approve a technical proposal for internal release, reject with a rationale, or request changes. A revision creates a linked pending version and keeps customer headings and source citations. Odoo records an immutable reviewer event and rejects self-review, stale source data or citations outside the original source set. This does not create a quotation or send/release a customer document.
- Full isolated Odoo suite: 7 focused tests passed; complete isolated Odoo regression 371 passed, 0 failed, 0 errors; backend suite: 236 passed, 2 skipped; 265 subtests; React units: 80 passed; focused browser journeys: 2 focused mocked browser journeys passed.
- Browser screenshot is synthetic. Authenticated two-user acceptance, role/company/project matrix, Arabic review, approved authority policy, live role acceptance and external release remain open; approved PDFs can now be archived internally (BE-036).

Latest feature: private proposal PDF preview
React Sales detail saves and reopens a private approval PDF from a pending BE-032 proposal. Native Odoo rechecks the confirmed order and source-price revision, renders a QWeb one-page A4 document, and stores immutable raw bytes with actor, company, time, revision and checksum. The BFF checks company scope, filename, size and PDF signature before returning the file. It does not approve or send the proposal or change the order.
- Native Odoo lifecycle/QWeb tests: 3 passed; full isolated Odoo regression 367 passed, 0 failed, 0 errors; backend route/security tests: 2 passed; React units: 80 passed; browser journey: 1 passed (mocked browser journey).
- Real synthetic Odoo PDF: Valid one-page A4 PDF, 22,857 bytes; extracted source proposal and SAR 2,875 total. Source order total remained unchanged. The clone lacked referenced CSS filestore assets, so normal-database styling still needs acceptance.
- Live two-role workflow, broad role/company/project matrix, Arabic visual review and full A1–A4 remain open. Screenshot uses synthetic mocked data.

Previous feature: financial proposals from approved Odoo pricing
React Sales detail drafts financial-proposal wording from a confirmed Odoo order. Exact prices, tax and totals are displayed from a source snapshot; AI drafts prose only. Odoo rechecks company access and pricing freshness before saving. A separate Sales Manager/Owner can approve or reject the draft with rationale; this review does not alter, publish or send the order.
- Backend generator tests: 2 passed; BFF route tests: 3 passed; React unit suite: 80 passed; mock browser: 1 passed.
- Isolated Odoo lifecycle/security tests: 2 passed, 0 failures, 0 errors. Price-source freshness, independent decision, rationale audit, self-review denial and unchanged order were verified; clone dropped.
- This browser image uses synthetic mocked data. Live model/browser, broader role/company/project matrix, Arabic quality and business approval-source policy remain open.

Latest feature: customer-template technical proposal drafts
React CRM lets Sales draft a technical proposal from pasted customer template text and current opportunity/customer/project facts. The app preserves the customer's exact heading text and order; Odoo checks Sales/Owner access, company, source revision, template digest and citation membership before saving a pending suggestion. Reopening the opportunity reloads the draft. No quotation is created and no customer message is sent.
- Backend generator and route tests: 5 passed; native Odoo tests: 3 passed, 0 failures/errors; authenticated live React → BFF → Qwen 3.8 27B → Odoo browser: 1 passed.
- Postconditions: one pending suggestion by technical.proposal.sales; exact customer headings persisted; opportunity, messages, activities and sale-order count unchanged.
- QA result: passed; clone dropped and source DB unchanged. Template file/PDF extraction, Arabic quality and wider role/company acceptance remain.

Latest verified feature: project charter AI drafts · Checkpoint 402
Project Managers can create source-grounded English and Arabic charter/baseline suggestions in React. Both remain pending for human review. Fresh login reopens drafts with task phases, citations, uncertainty, actor, timestamp and company. The AI does not create or approve an official charter.
- Native Odoo acceptance: 5 passed, 0 failures/errors; authenticated live browser: 1 passed.
- Unsupported language returned 422 with no write. Same-company reader saw no AI drafts and could not generate one; foreign-company PM list/create were denied without disclosure. Project and task records stayed unchanged.
- Disposable QA clone dropped and source database unchanged. Totals: 156 DONE, 1 PARTIAL, 0 MISSING, 7 BLOCKED (95.1% fully verified).
Checkpoint 402 · Isolated live QA evidence · Full story matrix
Latest feature: Saudi milestone invoice draft in React
On an isolated clone, a Finance reader could review the approved certificate but received HTTP 403 when attempting invoice creation. A separate accountant created the linked draft invoice through React; Odoo kept it unposted and used the active Saudi company's configured 15% sales tax.
- Native progress-billing tests: not run; live React → BFF → Odoo browser: not run.
- Odoo verified SAR — untaxed + SAR — VAT = SAR —, draft `out_invoice`, correct source/customer/company and one-invoice retry idempotency.
- Disposable clone dropped; source QA database unchanged. No posting or ZATCA call. Retention/advance policy, accountant/customer UAT, wider role/company acceptance and full BE-078 A1–A4 remain open.

Checkpoint 272 · Isolated live QA evidence · Full story matrix
Verified feature: variation creation, review and impact advice · Checkpoint 417
A PM created a variation in React; Odoo persisted its draft, project/company, BOQ line, actor and computed amount. Source-cited English/Arabic and newly created variation advice stayed pending and non-mutating. An independent Build Engine Owner approved one request and rejected another with mandatory rationale. Invalid language and short decision rationale returned 422 without state changes; requester self-approval and same-company reader/foreign-company list access were denied.
- Native AI bridge tests: 4/4; clean variation lifecycle/approval suite: 21/21; authenticated live React → BFF → qwen3.8:27b → Odoo browser journey: 1/1.
- Readback verified React-created draft, company/project, creator and calculated SAR 225 amount; cited advisory remained pending. Approval saved immutable Owner/time/rationale, applied SAR 750 once (BOQ 100→110) and preserved the prior baseline. Rejection saved its separate immutable audit and left the BOQ unchanged.
- Disposable clone dropped; source database unchanged. Story totals: 156 DONE, 1 PARTIAL, 0 MISSING, 7 BLOCKED (95.1% fully verified).
- DEC-06 is provisionally resolved for variations using independent Owner review; other listed workflows remain open. Advisory drafts must be regenerated if their source revision changes.
Checkpoint 417 · Isolated live QA evidence · Full story matrix
Latest verified feature: supplier RFQ draft and independent approval
React lets an authorized Project Manager draft supplier wording from approved Odoo request, supplier, BOQ and project records. A separate Procurement reviewer must authorize it with a rationale. The native OCA purchase-request wizard creates a linked draft purchase order; the workflow does not confirm it or email the supplier.
- Native Odoo lifecycle/security tests: 4 passed, 0 failures/errors.
- Live React → BFF → Qwen 3.8 27B → Odoo two-role journey: 1 passed; PM, Procurement and foreign-company Procurement sessions; Arabic draft captured.
- Postconditions: author 185, reviewer 186, purchase order P00049 remains draft; 0 supplier emails.
- QA result: passed; clone and temporary services removed; source DB unchanged. Broader production role/company acceptance, Arabic evaluation and full A1–A4 remain open.
Live React screens
Checkpoint 251 · Isolated live QA evidence · Feature comparison
Previously verified feature: project status and RFI report drafts
React drafts project status and RFI site reports from the signed-in user’s authorized Odoo project records. Local Qwen output is constrained to a strict report schema and exact source IDs before Odoo saves an auditable pending draft. A separate Project Manager or Owner can review with a required rationale. Approval records the review only; it does not apply, publish or send the report.
- Focused backend tests: 9 passed; native Odoo report lifecycle/security tests: 3 passed.
- Live React → BFF → Qwen 3.8 27B → Odoo PM/Owner journey: 1 passed on an isolated disposable clone.
- Saved citations were project:307 and rfi:94; database checks confirmed the RFI remained open and the report was not applied.
- BE-154 remains PARTIAL pending broader role/company acceptance, Arabic evaluation, export policy and full A1–A4. Clone dropped; source database unchanged.
Live React report screens
Checkpoint 250 · Isolated live QA evidence · Feature comparison
20-minute demo walkthrough / مسار العرض
Open React, show design preview, Arabic/English, phone layout, recent-record search and the synthetic-data label.
Walk through CRM, sales, purchasing and accounting. Use preview edits and draft finance records; show the quote/subtotal and milestone billing screens without posting.
Show specialist prompts, stored requests and explicit human review. Preview examples do not execute AI; live AI readiness is separate.
Switch to the isolated construction database. Show the synthetic project, BOQ, RFQ comparison, equipment custody, submittal revision history and owner dashboard. Native Odoo screens are QA evidence, not the end-user workflow.
Open the portable manual, switch language/device view, enlarge a screenshot and show print/PDF. Record partner acceptance in the checklist.
Review the verified DONE percentage and story matrix. PARTIAL means implemented but not fully accepted; it is not completion.
Implementation phases
Complete Saudi accountant validation, connected CRM/sales/purchase-to-ledger flows and bank/statutory acceptance.
Finish BOQ revisions/imports, project calendars, supplier award, receipts, committed and actual cost reconciliation.
Complete safety, documents, submittals, equipment, closeout and ordinary site-role acceptance.
Reliable queues, conflict resolution, idempotent uploads and field reconnect/soak tests.
Expand agents with source evidence, human approvals, permission boundaries and Arabic/English evaluations.
Connect only after each provider contract, scope, official sandbox and owner-authorized access is available.
Reconcile portfolio reporting to records; finish project and finance closeout acceptance.
Complete tenant threat review, restore/load/soak, operational ownership and rollback acceptance.
All 164 user stories
Search by story, feature or area. Filter by the traceability classification.
| Story | Workstream | Requirement | Status |
|---|---|---|---|
BE-001 | Platform, tenancy and onboarding | Create tenant and configure legal company identityP0 | DONE |
BE-002 | Platform, tenancy and onboarding | Invite users and assign project-scoped rolesP0 | DONE |
BE-003 | Platform, tenancy and onboarding | Configure company trades, regions and tender thresholdsP0 | DONE |
BE-004 | Platform, tenancy and onboarding | Configure company branding and document templatesP0 | DONE |
BE-005 | Platform, tenancy and onboarding | Import initial master data with validationP1 | DONE |
BE-006 | Platform, tenancy and onboarding | View onboarding checklist and first-value sample projectP1 | DONE |
BE-007 | Platform, tenancy and onboarding | Configure Arabic/English language and timezoneP1 | DONE |
BE-008 | Platform, tenancy and onboarding | Suspend tenant and export customer dataP2 | DONE |
BE-009 | CRM, tenders and opportunities | Create lead from manual entryP0 | DONE |
BE-010 | CRM, tenders and opportunities | Classify government vs private leadP0 | DONE |
BE-011 | CRM, tenders and opportunities | Deduplicate organization and leadP0 | DONE |
BE-012 | CRM, tenders and opportunities | Qualify lead yes/no/maybe with reasonP0 | DONE |
BE-013 | CRM, tenders and opportunities | Approve lead-to-opportunity promotionP1 | DONE |
BE-014 | CRM, tenders and opportunities | Manage pipeline stage and probabilityP1 | DONE |
BE-015 | CRM, tenders and opportunities | Create tender and bid checklistP1 | DONE |
BE-016 | CRM, tenders and opportunities | Track bid deadline and submission evidenceP2 | DONE |
BE-017 | CRM, tenders and opportunities | Convert won opportunity to projectP2 | DONE |
BE-018 | CRM, tenders and opportunities | View win rate and pipeline valueP2 | DONE |
BE-019 | Business development AI | Configure scouting mandate and source allowlistP0 | DONE |
BE-020 | Business development AI | Schedule periodic tender and public signal discoveryP0 | BLOCKED |
BE-021 | Business development AI | Filter by project size, region and sectorP0 | DONE |
BE-022 | Business development AI | Verify sources and organization legitimacyP0 | BLOCKED |
BE-023 | Business development AI | Classify lead as yes/no/maybeP1 | DONE |
BE-024 | Business development AI | Route yes/maybe to human review and archive noP1 | DONE |
BE-025 | Business development AI | Prevent duplicate CRM handoffP1 | DONE |
BE-026 | Business development AI | Show source links and fit rationaleP2 | DONE |
BE-027 | Business development AI | Chat with scouting agent about findingsP2 | DONE |
BE-028 | Business development AI | Review run logs and disable unreliable sourcesP2 | DONE |
BE-029 | Sales AI and proposals | Generate account research and opening message draftP0 | DONE |
BE-030 | Sales AI and proposals | Require human first contact and consent to proceedP0 | DONE |
BE-031 | Sales AI and proposals | Draft technical proposal from customer templateP0 | DONE |
BE-032 | Sales AI and proposals | Draft financial proposal from approved pricingP0 | DONE |
BE-033 | Sales AI and proposals | Apply tenant logo and letterheadP1 | DONE |
BE-034 | Sales AI and proposals | Produce final PDF preview for approvalP1 | DONE |
BE-035 | Sales AI and proposals | Approve/reject/revise outgoing proposalP1 | DONE |
BE-036 | Sales AI and proposals | Save approved PDF to opportunity/project archiveP2 | DONE |
BE-037 | Sales AI and proposals | Generate daily follow-up listP2 | DONE |
BE-038 | Sales AI and proposals | Block autonomous sending and stage promotionP2 | DONE |
BE-039 | Projects and scheduling | Create project from awarded opportunityP0 | DONE |
BE-040 | Projects and scheduling | Create phases tasks subtasks and dependenciesP0 | DONE |
BE-041 | Projects and scheduling | Assign crew and responsible personsP0 | DONE |
BE-042 | Projects and scheduling | Display Gantt and critical deadlinesP0 | DONE |
BE-043 | Projects and scheduling | Detect crew and equipment double-bookingP1 | DONE |
BE-044 | Projects and scheduling | Configure project lifecycle stage templateP1 | DONE |
BE-045 | Projects and scheduling | Track project milestones and stakeholder obligationsP1 | DONE |
BE-046 | Projects and scheduling | Draft project charter and obtain approvalP2 | DONE |
BE-047 | Projects and scheduling | Record schedule baseline and change historyP2 | DONE |
BE-048 | Projects and scheduling | Close project after required reconciliationsP2 | DONE |
BE-049 | BOQ, BOM and cost control | Create versioned project BOQP0 | DONE |
BE-050 | BOQ, BOM and cost control | Import BOQ spreadsheet with mappingP0 | DONE |
BE-051 | BOQ, BOM and cost control | Capture labor material equipment and work linesP0 | DONE |
BE-052 | BOQ, BOM and cost control | Draft BOQ from drawings and scope with AIP0 | DONE |
BE-053 | BOQ, BOM and cost control | Validate units rates and quantity totalsP1 | DONE |
BE-054 | BOQ, BOM and cost control | Approve BOQ baseline and lock revisionP1 | DONE |
BE-055 | BOQ, BOM and cost control | Create variation order with impact analysisP1 | DONE |
BE-056 | BOQ, BOM and cost control | Approve/reject variation order with audit trailP2 | DONE |
BE-057 | BOQ, BOM and cost control | Compare estimated vs actual consumption and costsP2 | DONE |
BE-058 | BOQ, BOM and cost control | Link manufacturing BOM where applicableP2 | DONE |
BE-059 | Procurement and suppliers | Maintain approved supplier directoryP0 | DONE |
BE-060 | Procurement and suppliers | Create material request linked to BOQP0 | DONE |
BE-061 | Procurement and suppliers | Draft and review RFQ to selected suppliersP0 | DONE |
BE-062 | Procurement and suppliers | Record supplier quotations and validityP0 | DONE |
BE-063 | Procurement and suppliers | Compare landed prices and delivery datesP1 | DONE |
BE-064 | Procurement and suppliers | Flag quote anomalies for human reviewP1 | DONE |
BE-065 | Procurement and suppliers | Approve purchase before commitmentP1 | DONE |
BE-066 | Procurement and suppliers | Receive materials into correct locationP2 | DONE |
BE-067 | Procurement and suppliers | Detect stock shortage against scheduleP2 | DONE |
BE-068 | Procurement and suppliers | Track vendor performance and RFQ historyP2 | DONE |
BE-069 | Inventory and warehouses | Create warehouses and site stock locationsP0 | DONE |
BE-070 | Inventory and warehouses | Receive materials against purchase orderP0 | DONE |
BE-071 | Inventory and warehouses | Transfer material to project siteP0 | DONE |
BE-072 | Inventory and warehouses | Issue material to project and BOQ lineP0 | DONE |
BE-073 | Inventory and warehouses | Return unused material to yardP1 | DONE |
BE-074 | Inventory and warehouses | Perform stock count and variance approvalP1 | DONE |
BE-075 | Inventory and warehouses | Track minimum stock and reorder alertsP1 | DONE |
BE-076 | Inventory and warehouses | Prevent negative stock per configurationP2 | DONE |
BE-077 | Accounting and ZATCA | Assign analytic project cost centerP0 | DONE |
BE-078 | Accounting and ZATCA | Create customer invoice from milestoneP0 | DONE |
BE-079 | Accounting and ZATCA | Record vendor bill and match purchase orderP0 | DONE |
BE-080 | Accounting and ZATCA | Reconcile bank payments and receiptsP0 | DONE |
BE-081 | Accounting and ZATCA | View project P&L and cash flowP1 | DONE |
BE-082 | Accounting and ZATCA | Generate compliant Saudi tax invoiceP1 | BLOCKED |
BE-083 | Accounting and ZATCA | Clear/report electronic invoice via approved ZATCA adapterP1 | BLOCKED |
BE-084 | Accounting and ZATCA | Handle credit and debit notesP2 | DONE |
BE-085 | Accounting and ZATCA | Track failed compliance submission and retryP2 | BLOCKED |
BE-086 | Accounting and ZATCA | Export finance reports with restricted permissionsP2 | DONE |
BE-087 | HR and timesheets | Manage employee records and assignmentsP0 | DONE |
BE-088 | HR and timesheets | Onboard and offboard staffP0 | DONE |
BE-089 | HR and timesheets | Record project task timesheetsP0 | DONE |
BE-090 | HR and timesheets | Review and approve attendance entriesP0 | DONE |
BE-091 | HR and timesheets | Allocate labor cost to projectP1 | DONE |
BE-092 | HR and timesheets | Export basic payroll inputs with authorizationP1 | BLOCKED |
BE-093 | Assets and maintenance | Register equipment and acquisition dataP0 | DONE |
BE-094 | Assets and maintenance | Assign equipment to projectP0 | DONE |
BE-095 | Assets and maintenance | Check out and return toolsP0 | DONE |
BE-096 | Assets and maintenance | Schedule preventive maintenanceP0 | DONE |
BE-097 | Assets and maintenance | Record breakdown and repair costsP1 | DONE |
BE-098 | Assets and maintenance | Track utilization and idle timeP1 | DONE |
BE-099 | Assets and maintenance | Retire or dispose asset with approvalP1 | DONE |
BE-100 | Quality, inspections and safety | Configure quality gate checklistP0 | DONE |
BE-101 | Quality, inspections and safety | Attach inspection evidence and signaturesP0 | DONE |
BE-102 | Quality, inspections and safety | Prevent advancing past mandatory unsigned gateP0 | DONE |
BE-103 | Quality, inspections and safety | Map regulatory checkpoint to current referenceP0 | BLOCKED |
BE-104 | Quality, inspections and safety | Log nonconformance and corrective actionP1 | DONE |
BE-105 | Quality, inspections and safety | Track incident and near missP1 | DONE |
BE-106 | Quality, inspections and safety | Complete daily safety checklistP1 | DONE |
BE-107 | Quality, inspections and safety | Escalate overdue inspection or safety incidentP2 | DONE |
BE-108 | Quality, inspections and safety | Maintain punch list until closeoutP2 | DONE |
BE-109 | RFI, submittals and site reporting | Create RFI and assign respondentP0 | DONE |
BE-110 | RFI, submittals and site reporting | Track RFI response deadline and statusP0 | DONE |
BE-111 | RFI, submittals and site reporting | Create submittal with drawing revisionP0 | DONE |
BE-112 | RFI, submittals and site reporting | Record approval or resubmissionP0 | DONE |
BE-113 | RFI, submittals and site reporting | Capture daily site report offlineP1 | DONE |
BE-114 | RFI, submittals and site reporting | Log manpower deliveries weather and delaysP1 | DONE |
BE-115 | RFI, submittals and site reporting | Generate consolidated RFI and submittal logsP1 | DONE |
BE-116 | Contracts and client helpdesk | Register client subcontractor and supplier contractsP0 | DONE |
BE-117 | Contracts and client helpdesk | Track expiry renewal and milestone datesP0 | DONE |
BE-118 | Contracts and client helpdesk | Draft contract clause checklist for reviewP0 | DONE |
BE-119 | Contracts and client helpdesk | Flag potentially missing contract clausesP0 | DONE |
BE-120 | Contracts and client helpdesk | Create internal defect or blocked-task ticketP1 | DONE |
BE-121 | Contracts and client helpdesk | Create client snag ticket after handoverP1 | DONE |
BE-122 | Contracts and client helpdesk | Route ticket and escalate SLA breachP1 | DONE |
BE-123 | Contracts and client helpdesk | Record ticket resolution evidenceP2 | DONE |
BE-124 | Documents, drawings and knowledge | Create dedicated project document foldersP0 | DONE |
BE-125 | Documents, drawings and knowledge | Upload and version drawingsP0 | DONE |
BE-126 | Documents, drawings and knowledge | Preview supported drawing formats without CAD editingP0 | DONE |
BE-127 | Documents, drawings and knowledge | Link drawing revision to task and submittalP0 | DONE |
BE-128 | Documents, drawings and knowledge | Archive approved proposal and BOQ PDFsP1 | DONE |
BE-129 | Documents, drawings and knowledge | Search archived decisions and lessons learnedP1 | DONE |
BE-130 | Documents, drawings and knowledge | Enforce tenant/project document ACLsP1 | DONE |
BE-131 | Documents, drawings and knowledge | Isolate archive indexing from live transaction performanceP2 | DONE |
BE-132 | Documents, drawings and knowledge | Export archived project packP2 | DONE |
BE-133 | No-code workflow engine | Create workflow from standard templateP0 | DONE |
BE-134 | No-code workflow engine | Build stages and transitions in visual editorP0 | DONE |
BE-135 | No-code workflow engine | Configure transition conditions and role permissionsP0 | DONE |
BE-136 | No-code workflow engine | Bind mandatory quality gates to transitionsP0 | DONE |
BE-137 | No-code workflow engine | Validate workflow before publishingP1 | DONE |
BE-138 | No-code workflow engine | Version workflow and migrate active instances safelyP1 | DONE |
BE-139 | No-code workflow engine | Audit configuration changes and rollbackP1 | DONE |
BE-140 | Offline and Excel | Download offline-ready assigned project dataP0 | DONE |
BE-141 | Offline and Excel | Create queued task updates while disconnectedP0 | DONE |
BE-142 | Offline and Excel | Capture material usage and daily report offlineP0 | DONE |
BE-143 | Offline and Excel | Sync queued changes on reconnectP0 | DONE |
BE-144 | Offline and Excel | Resolve optimistic-version conflicts visiblyP1 | DONE |
BE-145 | Offline and Excel | Retry failed uploads without duplicate recordsP1 | DONE |
BE-146 | Offline and Excel | Import validated Excel template and show row errorsP1 | DONE |
BE-147 | Offline and Excel | Export BOQ and operational reports to ExcelP2 | DONE |
BE-148 | Project management AI | Draft project charter and baseline planP0 | DONE |
BE-149 | Project management AI | Suggest task sequencing and resource allocationP0 | DONE |
BE-150 | Project management AI | Generate BOQ draft from scope and drawingsP0 | PARTIAL |
BE-151 | Project management AI | Identify schedule cost and quality risksP0 | DONE |
BE-152 | Project management AI | Draft supplier RFQ for human authorizationP1 | DONE |
BE-153 | Project management AI | Propose change order impactP1 | DONE |
BE-154 | Project management AI | Draft RFI site report and status reportP1 | DONE |
BE-155 | Project management AI | Notify role-specific risk ownersP2 | DONE |
BE-156 | Project management AI | Record approve/edit/reject feedbackP2 | DONE |
BE-157 | Project management AI | Draft closeout and lessons learnedP2 | DONE |
BE-158 | Owner dashboards and notifications | View portfolio status and marginP0 | DONE |
BE-159 | Owner dashboards and notifications | View budget vs actual by projectP0 | DONE |
BE-160 | Owner dashboards and notifications | View receivables payables and cash forecastP0 | DONE |
BE-161 | Owner dashboards and notifications | View overdue quality gates and risksP0 | DONE |
BE-162 | Owner dashboards and notifications | Drill into material variance and open ticketsP1 | DONE |
BE-163 | Owner dashboards and notifications | Configure role-based alerts and digestP1 | DONE |
BE-164 | Owner dashboards and notifications | Export dashboard reportsP1 | DONE |
English draft
Arabic draft
English draft
Arabic draft
React-created variation
Saved scouting draft
Reopened transcript
English desktop preview
Arabic phone preview
Risk owner assignment
Risk draft
Closeout lessons
PM draft pending review
Independent Procurement review
Authorized unsent draft
Draft with source citations
Independent review
Review approved; nothing applied