Build Engine · Odoo 20 + React · 2026-11-17

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 حفظ السجلات وإدارة العمليات الأساسية. توضح هذه الصفحة الوظائف المتاحة وما تحقق منها وما تبقى.

Verified acceptance · Checkpoint 469 · 2026-11-17

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.

Full traceability · Portable user manual

164Total user stories
156DONE · 95.1% verified
1PARTIAL · 0.6%
70 missing · 7 blocked

Progress at a glance

156 of 164 stories are fully verified DONE (95.1%).

1 PARTIAL · 0 MISSING · 7 BLOCKED. Totals are generated from the requirements traceability matrix.

Odoo and React footprint

31Build Engine Odoo add-on manifests in source
18Construction add-ons installed in the isolated QA database (live registry check)
71React workspace components in source
1Consolidated Accounting KSA add-on installed in the separate accounting QA database

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

PARTIAL

The 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

PARTIAL

React 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

PARTIAL

React 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

PARTIAL

Odoo/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

PARTIAL

Local-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 / PARTIAL

Official 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

BE-111 / BE-112 · DONE

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 correspondence register showing submittal review history

Checkpoint 405 · Live QA evidence · Full story matrix

React operational exports · Checkpoint 404

BE-147 · PARTIAL

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.

Checkpoint 404 · Live role QA · Full story matrix

Latest verified feature: project charter AI drafts · Checkpoint 402

BE-148 · DONE

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

BE-055 / BE-056 / BE-153 · DONE

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

BE-029 · DONE

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).
Reviewed Arabic CRM account research draft with sources and complete uncertainty

Checkpoint 399 · Isolated live QA evidence · Full story matrix

Latest React feature: material variance and ticket drilldowns · Checkpoint 398

BE-162 · DONE

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.

Checkpoint 398 · BE-162 live QA · Full traceability

Previously verified React feature: persistent CRM scouting chat · Checkpoint 396

BE-027 · DONE

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.

Checkpoint 396 · Isolated live QA · Full traceability

Latest verified feature: auditable Arabic BOQ spreadsheet imports · Checkpoint 327

BE-050 · PARTIAL

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

BE-160 · PARTIAL

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_ksa business records were unchanged. BE-160 remains PARTIAL for statement/internal-transfer React workflows, complete AR/AP, broader roles/currencies and accountant UAT.
React payment history showing an audited posted payment reversal

Checkpoint 317 · Isolated live QA evidence · Full story matrix

Latest feature: company onboarding and first-value sample project · Checkpoint 310

BE-006 · PARTIAL

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_onboarding is not installed there.

Checkpoint 310 · Isolated Odoo QA · Full story matrix

Latest feature: role-based scheduled in-app digests · Checkpoint 309

BE-163 · PARTIAL

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_dashboard is not installed there and its runtime image lacks OCA report_xlsx, so the live bell is not enabled.

Checkpoint 309 · Isolated Odoo QA · Full story matrix

Project expenses now available in React

Supplemental capability · not a BRS story

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

BE-151 / BE-155 / BE-157 · DONE

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

A PM can draft lessons only after the selected project has a certified Odoo closeout. React shows the project/company, author, saved time, source IDs, uncertainty and review state. The Owner review is audit-only; no project action is applied and no message is sent.

React closeout lessons draft

Latest construction acceptance: charter and closeout · Checkpoint 293

BE-046 / BE-048 / BE-148 · PARTIAL

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

BE-081 · PARTIAL

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:3200 also 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.
Local React project cash-flow report with the synthetic draft allocation

Checkpoint 291 · Native report QA · Isolated and local runtime QA · Full story matrix

Latest CRM feature: indexed construction trade/category matching · Checkpoint 337

BE-003 · PARTIAL

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

BE-080 · PARTIAL

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

BE-132 · PARTIAL

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_ksa was 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.
React project archive with export history and ZIP download

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

BE-045 · PARTIAL

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_ksa was unchanged. Broader role/tenant, Arabic/accessibility and full A1–A4 acceptance remain.
React project planning with persisted milestone and stakeholder handover obligation

Checkpoint 280 · Live QA evidence · Full story matrix

Latest feature: live React proposal + BOQ archive · Checkpoint 279

BE-128 · PARTIAL

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_ksa was 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.
Live React project archive with approved proposal and confirmed BOQ PDFs

Checkpoint 279 · Live QA evidence · Checkpoint 278 · Full story matrix

Latest feature: approved technical proposal archive · Checkpoint 261

BE-036 · PARTIAL

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.
Synthetic React CRM opportunity showing privately archived approved proposal PDFSynthetic React project archive with an accessible project selected and archived proposal PDF

Checkpoint 261 · Checkpoint 260 · Archive QA · Full story matrix

Latest feature: CRM proposal approval and revision

BE-035 · PARTIAL

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).
Synthetic React CRM technical proposal after independent internal review

Checkpoint 259 · Review QA · Full story matrix

Latest feature: private proposal PDF preview

BE-034 · PARTIAL

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.
Synthetic React financial proposal with saved approval PDF link

Checkpoint 258 · PDF QA evidence · Full story matrix

Previous feature: financial proposals from approved Odoo pricing

BE-032 · PARTIAL

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.
Synthetic React financial proposal draft showing source order prices

Checkpoint 257 · QA evidence · Full story matrix

Latest feature: customer-template technical proposal drafts

BE-031 · PARTIAL

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.
Live React technical proposal draft pending human review

Checkpoint 256 · Isolated live QA · Native QA

Latest verified feature: project charter AI drafts · Checkpoint 402

BE-148 · DONE

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

BE-078 · PARTIAL

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.
React milestone certificate with linked Saudi draft invoice from isolated QA

Checkpoint 272 · Isolated live QA evidence · Full story matrix

Verified feature: variation creation, review and impact advice · Checkpoint 417

BE-055 / BE-056 / BE-153 · DONE

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

BE-152 · PARTIAL

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

BE-154 · PARTIAL

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 / مسار العرض

0–3React dashboard and navigation
Open React, show design preview, Arabic/English, phone layout, recent-record search and the synthetic-data label.
3–7Business workflows
Walk through CRM, sales, purchasing and accounting. Use preview edits and draft finance records; show the quote/subtotal and milestone billing screens without posting.
7–10AI and review
Show specialist prompts, stored requests and explicit human review. Preview examples do not execute AI; live AI readiness is separate.
10–16Construction Odoo internal QA
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.
16–18Manual and acceptance checklist
Open the portable manual, switch language/device view, enlarge a screenshot and show print/PDF. Record partner acceptance in the checklist.
18–20Scope and next work
Review the verified DONE percentage and story matrix. PARTIAL means implemented but not fully accepted; it is not completion.

Implementation phases

01Finance and connected workflows
Complete Saudi accountant validation, connected CRM/sales/purchase-to-ledger flows and bank/statutory acceptance.
02Project planning and cost control
Finish BOQ revisions/imports, project calendars, supplier award, receipts, committed and actual cost reconciliation.
03Construction and field collaboration
Complete safety, documents, submittals, equipment, closeout and ordinary site-role acceptance.
04Offline and mobile
Reliable queues, conflict resolution, idempotent uploads and field reconnect/soak tests.
05AI agents
Expand agents with source evidence, human approvals, permission boundaries and Arabic/English evaluations.
06Saudi portal integrations
Connect only after each provider contract, scope, official sandbox and owner-authorized access is available.
07Dashboards and closeout
Reconcile portfolio reporting to records; finish project and finance closeout acceptance.
08Security and rollout
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.

StoryWorkstreamRequirementStatus
BE-001Platform, tenancy and onboardingCreate tenant and configure legal company identityP0DONE
BE-002Platform, tenancy and onboardingInvite users and assign project-scoped rolesP0DONE
BE-003Platform, tenancy and onboardingConfigure company trades, regions and tender thresholdsP0DONE
BE-004Platform, tenancy and onboardingConfigure company branding and document templatesP0DONE
BE-005Platform, tenancy and onboardingImport initial master data with validationP1DONE
BE-006Platform, tenancy and onboardingView onboarding checklist and first-value sample projectP1DONE
BE-007Platform, tenancy and onboardingConfigure Arabic/English language and timezoneP1DONE
BE-008Platform, tenancy and onboardingSuspend tenant and export customer dataP2DONE
BE-009CRM, tenders and opportunitiesCreate lead from manual entryP0DONE
BE-010CRM, tenders and opportunitiesClassify government vs private leadP0DONE
BE-011CRM, tenders and opportunitiesDeduplicate organization and leadP0DONE
BE-012CRM, tenders and opportunitiesQualify lead yes/no/maybe with reasonP0DONE
BE-013CRM, tenders and opportunitiesApprove lead-to-opportunity promotionP1DONE
BE-014CRM, tenders and opportunitiesManage pipeline stage and probabilityP1DONE
BE-015CRM, tenders and opportunitiesCreate tender and bid checklistP1DONE
BE-016CRM, tenders and opportunitiesTrack bid deadline and submission evidenceP2DONE
BE-017CRM, tenders and opportunitiesConvert won opportunity to projectP2DONE
BE-018CRM, tenders and opportunitiesView win rate and pipeline valueP2DONE
BE-019Business development AIConfigure scouting mandate and source allowlistP0DONE
BE-020Business development AISchedule periodic tender and public signal discoveryP0BLOCKED
BE-021Business development AIFilter by project size, region and sectorP0DONE
BE-022Business development AIVerify sources and organization legitimacyP0BLOCKED
BE-023Business development AIClassify lead as yes/no/maybeP1DONE
BE-024Business development AIRoute yes/maybe to human review and archive noP1DONE
BE-025Business development AIPrevent duplicate CRM handoffP1DONE
BE-026Business development AIShow source links and fit rationaleP2DONE
BE-027Business development AIChat with scouting agent about findingsP2DONE
BE-028Business development AIReview run logs and disable unreliable sourcesP2DONE
BE-029Sales AI and proposalsGenerate account research and opening message draftP0DONE
BE-030Sales AI and proposalsRequire human first contact and consent to proceedP0DONE
BE-031Sales AI and proposalsDraft technical proposal from customer templateP0DONE
BE-032Sales AI and proposalsDraft financial proposal from approved pricingP0DONE
BE-033Sales AI and proposalsApply tenant logo and letterheadP1DONE
BE-034Sales AI and proposalsProduce final PDF preview for approvalP1DONE
BE-035Sales AI and proposalsApprove/reject/revise outgoing proposalP1DONE
BE-036Sales AI and proposalsSave approved PDF to opportunity/project archiveP2DONE
BE-037Sales AI and proposalsGenerate daily follow-up listP2DONE
BE-038Sales AI and proposalsBlock autonomous sending and stage promotionP2DONE
BE-039Projects and schedulingCreate project from awarded opportunityP0DONE
BE-040Projects and schedulingCreate phases tasks subtasks and dependenciesP0DONE
BE-041Projects and schedulingAssign crew and responsible personsP0DONE
BE-042Projects and schedulingDisplay Gantt and critical deadlinesP0DONE
BE-043Projects and schedulingDetect crew and equipment double-bookingP1DONE
BE-044Projects and schedulingConfigure project lifecycle stage templateP1DONE
BE-045Projects and schedulingTrack project milestones and stakeholder obligationsP1DONE
BE-046Projects and schedulingDraft project charter and obtain approvalP2DONE
BE-047Projects and schedulingRecord schedule baseline and change historyP2DONE
BE-048Projects and schedulingClose project after required reconciliationsP2DONE
BE-049BOQ, BOM and cost controlCreate versioned project BOQP0DONE
BE-050BOQ, BOM and cost controlImport BOQ spreadsheet with mappingP0DONE
BE-051BOQ, BOM and cost controlCapture labor material equipment and work linesP0DONE
BE-052BOQ, BOM and cost controlDraft BOQ from drawings and scope with AIP0DONE
BE-053BOQ, BOM and cost controlValidate units rates and quantity totalsP1DONE
BE-054BOQ, BOM and cost controlApprove BOQ baseline and lock revisionP1DONE
BE-055BOQ, BOM and cost controlCreate variation order with impact analysisP1DONE
BE-056BOQ, BOM and cost controlApprove/reject variation order with audit trailP2DONE
BE-057BOQ, BOM and cost controlCompare estimated vs actual consumption and costsP2DONE
BE-058BOQ, BOM and cost controlLink manufacturing BOM where applicableP2DONE
BE-059Procurement and suppliersMaintain approved supplier directoryP0DONE
BE-060Procurement and suppliersCreate material request linked to BOQP0DONE
BE-061Procurement and suppliersDraft and review RFQ to selected suppliersP0DONE
BE-062Procurement and suppliersRecord supplier quotations and validityP0DONE
BE-063Procurement and suppliersCompare landed prices and delivery datesP1DONE
BE-064Procurement and suppliersFlag quote anomalies for human reviewP1DONE
BE-065Procurement and suppliersApprove purchase before commitmentP1DONE
BE-066Procurement and suppliersReceive materials into correct locationP2DONE
BE-067Procurement and suppliersDetect stock shortage against scheduleP2DONE
BE-068Procurement and suppliersTrack vendor performance and RFQ historyP2DONE
BE-069Inventory and warehousesCreate warehouses and site stock locationsP0DONE
BE-070Inventory and warehousesReceive materials against purchase orderP0DONE
BE-071Inventory and warehousesTransfer material to project siteP0DONE
BE-072Inventory and warehousesIssue material to project and BOQ lineP0DONE
BE-073Inventory and warehousesReturn unused material to yardP1DONE
BE-074Inventory and warehousesPerform stock count and variance approvalP1DONE
BE-075Inventory and warehousesTrack minimum stock and reorder alertsP1DONE
BE-076Inventory and warehousesPrevent negative stock per configurationP2DONE
BE-077Accounting and ZATCAAssign analytic project cost centerP0DONE
BE-078Accounting and ZATCACreate customer invoice from milestoneP0DONE
BE-079Accounting and ZATCARecord vendor bill and match purchase orderP0DONE
BE-080Accounting and ZATCAReconcile bank payments and receiptsP0DONE
BE-081Accounting and ZATCAView project P&L and cash flowP1DONE
BE-082Accounting and ZATCAGenerate compliant Saudi tax invoiceP1BLOCKED
BE-083Accounting and ZATCAClear/report electronic invoice via approved ZATCA adapterP1BLOCKED
BE-084Accounting and ZATCAHandle credit and debit notesP2DONE
BE-085Accounting and ZATCATrack failed compliance submission and retryP2BLOCKED
BE-086Accounting and ZATCAExport finance reports with restricted permissionsP2DONE
BE-087HR and timesheetsManage employee records and assignmentsP0DONE
BE-088HR and timesheetsOnboard and offboard staffP0DONE
BE-089HR and timesheetsRecord project task timesheetsP0DONE
BE-090HR and timesheetsReview and approve attendance entriesP0DONE
BE-091HR and timesheetsAllocate labor cost to projectP1DONE
BE-092HR and timesheetsExport basic payroll inputs with authorizationP1BLOCKED
BE-093Assets and maintenanceRegister equipment and acquisition dataP0DONE
BE-094Assets and maintenanceAssign equipment to projectP0DONE
BE-095Assets and maintenanceCheck out and return toolsP0DONE
BE-096Assets and maintenanceSchedule preventive maintenanceP0DONE
BE-097Assets and maintenanceRecord breakdown and repair costsP1DONE
BE-098Assets and maintenanceTrack utilization and idle timeP1DONE
BE-099Assets and maintenanceRetire or dispose asset with approvalP1DONE
BE-100Quality, inspections and safetyConfigure quality gate checklistP0DONE
BE-101Quality, inspections and safetyAttach inspection evidence and signaturesP0DONE
BE-102Quality, inspections and safetyPrevent advancing past mandatory unsigned gateP0DONE
BE-103Quality, inspections and safetyMap regulatory checkpoint to current referenceP0BLOCKED
BE-104Quality, inspections and safetyLog nonconformance and corrective actionP1DONE
BE-105Quality, inspections and safetyTrack incident and near missP1DONE
BE-106Quality, inspections and safetyComplete daily safety checklistP1DONE
BE-107Quality, inspections and safetyEscalate overdue inspection or safety incidentP2DONE
BE-108Quality, inspections and safetyMaintain punch list until closeoutP2DONE
BE-109RFI, submittals and site reportingCreate RFI and assign respondentP0DONE
BE-110RFI, submittals and site reportingTrack RFI response deadline and statusP0DONE
BE-111RFI, submittals and site reportingCreate submittal with drawing revisionP0DONE
BE-112RFI, submittals and site reportingRecord approval or resubmissionP0DONE
BE-113RFI, submittals and site reportingCapture daily site report offlineP1DONE
BE-114RFI, submittals and site reportingLog manpower deliveries weather and delaysP1DONE
BE-115RFI, submittals and site reportingGenerate consolidated RFI and submittal logsP1DONE
BE-116Contracts and client helpdeskRegister client subcontractor and supplier contractsP0DONE
BE-117Contracts and client helpdeskTrack expiry renewal and milestone datesP0DONE
BE-118Contracts and client helpdeskDraft contract clause checklist for reviewP0DONE
BE-119Contracts and client helpdeskFlag potentially missing contract clausesP0DONE
BE-120Contracts and client helpdeskCreate internal defect or blocked-task ticketP1DONE
BE-121Contracts and client helpdeskCreate client snag ticket after handoverP1DONE
BE-122Contracts and client helpdeskRoute ticket and escalate SLA breachP1DONE
BE-123Contracts and client helpdeskRecord ticket resolution evidenceP2DONE
BE-124Documents, drawings and knowledgeCreate dedicated project document foldersP0DONE
BE-125Documents, drawings and knowledgeUpload and version drawingsP0DONE
BE-126Documents, drawings and knowledgePreview supported drawing formats without CAD editingP0DONE
BE-127Documents, drawings and knowledgeLink drawing revision to task and submittalP0DONE
BE-128Documents, drawings and knowledgeArchive approved proposal and BOQ PDFsP1DONE
BE-129Documents, drawings and knowledgeSearch archived decisions and lessons learnedP1DONE
BE-130Documents, drawings and knowledgeEnforce tenant/project document ACLsP1DONE
BE-131Documents, drawings and knowledgeIsolate archive indexing from live transaction performanceP2DONE
BE-132Documents, drawings and knowledgeExport archived project packP2DONE
BE-133No-code workflow engineCreate workflow from standard templateP0DONE
BE-134No-code workflow engineBuild stages and transitions in visual editorP0DONE
BE-135No-code workflow engineConfigure transition conditions and role permissionsP0DONE
BE-136No-code workflow engineBind mandatory quality gates to transitionsP0DONE
BE-137No-code workflow engineValidate workflow before publishingP1DONE
BE-138No-code workflow engineVersion workflow and migrate active instances safelyP1DONE
BE-139No-code workflow engineAudit configuration changes and rollbackP1DONE
BE-140Offline and ExcelDownload offline-ready assigned project dataP0DONE
BE-141Offline and ExcelCreate queued task updates while disconnectedP0DONE
BE-142Offline and ExcelCapture material usage and daily report offlineP0DONE
BE-143Offline and ExcelSync queued changes on reconnectP0DONE
BE-144Offline and ExcelResolve optimistic-version conflicts visiblyP1DONE
BE-145Offline and ExcelRetry failed uploads without duplicate recordsP1DONE
BE-146Offline and ExcelImport validated Excel template and show row errorsP1DONE
BE-147Offline and ExcelExport BOQ and operational reports to ExcelP2DONE
BE-148Project management AIDraft project charter and baseline planP0DONE
BE-149Project management AISuggest task sequencing and resource allocationP0DONE
BE-150Project management AIGenerate BOQ draft from scope and drawingsP0PARTIAL
BE-151Project management AIIdentify schedule cost and quality risksP0DONE
BE-152Project management AIDraft supplier RFQ for human authorizationP1DONE
BE-153Project management AIPropose change order impactP1DONE
BE-154Project management AIDraft RFI site report and status reportP1DONE
BE-155Project management AINotify role-specific risk ownersP2DONE
BE-156Project management AIRecord approve/edit/reject feedbackP2DONE
BE-157Project management AIDraft closeout and lessons learnedP2DONE
BE-158Owner dashboards and notificationsView portfolio status and marginP0DONE
BE-159Owner dashboards and notificationsView budget vs actual by projectP0DONE
BE-160Owner dashboards and notificationsView receivables payables and cash forecastP0DONE
BE-161Owner dashboards and notificationsView overdue quality gates and risksP0DONE
BE-162Owner dashboards and notificationsDrill into material variance and open ticketsP1DONE
BE-163Owner dashboards and notificationsConfigure role-based alerts and digestP1DONE
BE-164Owner dashboards and notificationsExport dashboard reportsP1DONE
AI LOGIC · نسخة AI Logic، نُسخت في 17 نوفمبر 2026 من namaa-react-ksa.ngrok-free.app/demo.html