PRJ-03 — Cadrage workshop with HOCO — rules, V1/V2 split, open decisions
Walk HOCO through the PRD and the decision register; close pricing, stock, payment, credit, GPS and language decisions; get the cahier's validation sheet signed.
| Field | Details |
|---|---|
| Task code | PRJ-03 |
| Phase | P0 — Foundations (cadrage, UX/UI, architecture & contract) |
| Product scope | V1 |
| Status | Planned |
| Start | Sun 18 Oct 2026 |
| Due | Sun 18 Oct 2026 |
| Responsible | Anis — Full-stack developer |
| Co-responsible | Akram, Imad |
| Effort | 0.5 person-day(s) planned · 2 from scratch · size XS |
| Area · app | Project · shared |
| Depends on | PRJ-02 |
| Unblocks | SRV-02 |
| Milestones | Cadrage validated — validation sheet signed |
Summary
Walk HOCO through the PRD and the decision register; close pricing, stock, payment, credit, GPS and language decisions; get the cahier's validation sheet signed.
Description
Phase 1 of the cahier (§14) requires a cadrage with HOCO before the build: the PRD and the decision register (srs/open-decisions) are walked through and the cahier's validation sheet is signed. This task closes the decisions that change data and code: the three customer-type prices and whether reseller prices are displayed TTC, whether a newly signed-up reseller sees prices right away or only after validation (default right away), stock reservation and deduction statuses (default VALIDATED / SHIPPED), payment methods and the basic credit policy, the return window, GPS tolerance and location retention (150 m, 90 days), languages, the final domain, iOS, SMS and carrier providers and their costs (INT-07), the support regions and their WhatsApp numbers, and privacy/retention under Law 18-07 (SEC-08). Out of scope: designing screens (DES tasks) and changing the V1/V2 split beyond §14.1/§14.2 and the 17 Oct decisions. Every open item leaves the workshop with an owner and a due date; SRV-02 seeds settings from the closed values.
Note
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | Prepare the decision register extract and the workshop deck from the PRD (one slide per open decision with the proposed default) | Anis |
| 2 | Walk HOCO through the 17 Oct decisions: three prices per variant, availability-only stock, guest mode, manual confirmation of every order, returns and SAV in V1 | Anis |
| 3 | Close pricing and finance points: TTC display, price visibility before validation, payment methods, credit ceiling policy (BLOCK vs approval), delivery-fee policy | Anis |
| 4 | Close operational parameters: stock.reserveOn / stock.deductOn, orders.minAmount, return window, assisted-order expiry (72 h), GPS tolerance and sampling, retention | Anis |
| 5 | Collect support regions (wilaya groups, WhatsApp numbers, hours) and the reference lists (business types, refusal/cancel reasons, visit not-done reasons) | Anis |
| 6 | Collect brand assets, existing visual material and constraints for the design system kickoff | Akram |
| 7 | Confirm mobile scope: Android first, iOS decision, Google Play developer account ownership, test devices for the pilot | Imad |
| 8 | Identify external providers (SMS gateway, FCM, email, storage, carriers) with costs, quotas and approval delays (INT-07) | Anis |
| 9 | Privacy and retention points under Law 18-07 (SEC-08): data ownership, location consent wording, retention durations | Anis |
| 10 | Minutes, updated decision register and signed validation sheet | Anis |
Deliverables
- Signed validation sheet (cahier §14 phase 1) stored with the project records
- Updated decision register at /docs/srs/open-decisions with owner and date for every open item
- Workshop minutes listing every closed decision and the resulting setting values
- Seed inputs for SRV-02: settings defaults, reference lists, support regions, roles
Acceptance criteria
- Every decision in the register is either closed with a value or open with an owner and a due date
- The values of stock.reserveOn, stock.deductOn, orders.minAmount, orders.assistedConfirmationHours, return window and GPS tolerance are recorded
- HOCO has confirmed the customer type of each reseller category and the TTC/HT display rule (PRC-01, PRC-02)
- Support regions with their wilayas and WhatsApp numbers are provided or assigned an owner (ADM-08, SUP-05)
- Provider costs and approval delays are listed and accepted by HOCO (INT-07)
- The cahier validation sheet is signed by HOCO
Requirements covered
| Requirement | Title | Release |
|---|---|---|
| INT-07 | External costs, quotas and approval delays of every provider identified and validated by the client | V1 |
| SEC-08 | Privacy policy, data ownership and retention durations validated with the client (Law 18-07) | V1 |
Test measures
- Review of the minutes by Akram and Imad within one working day
- Cross-check: every closed decision is reflected in the SRS pages and in the settings seed list
Risks
- HOCO cannot decide on price visibility or TTC display during the workshop — ship the documented defaults behind settings so the decision does not block SRV-02/SRV-12
- Support WhatsApp numbers per region not available — seed one default region and number, regions editable later in BO-70
KPI
- Delivered by Sun 18 Oct 2026 within 0.5 person-day(s).
- Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
- Zero open critical defects, permission gaps or data-integrity regressions at sign-off.
Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.
PRJ-02 — Docs site, PRD/SRS baseline & delivery plan
This site: PRD, SRS, service catalogue, data model, API catalogue, screen inventory, ways of working and the scheduled plan.
SRV-01 — Service catalogue — module boundaries, events & ownership (freeze)
Review and freeze the 24 server modules: responsibilities, data each owns, events each emits, jobs, and which apps consume them.