Rituals and communication

Working hours and languageCopy Anchor Link

• Sunday to Thursday. Normal day 09:00–17:00, core hours 10:00–15:00 when everyone is reachable. Times are Africa/Algiers.
• Friday and Saturday carry no expectation, except the on-call duty of the pilot (on-call).
• Absences are announced at least a week ahead when planned, or by 09:00 the same day otherwise. Anis records them in people[].unavailable in tasks.json and the plan recomputes.
• Language. French with HOCO: e-mails, recaps, release notes, change requests, validation documents. English in code, commits, PRs, issues and these docs. The product's UI copy is French.

Weekly rhythmCopy Anchor Link

Assumption — the client review slot (every second Thursday at 14:00) is confirmed with HOCO at the cadrage workshop (PRJ-03).

Sunday planningCopy Anchor Link

1. Last week against the plan: what slipped and why (5 min).
2. This week per person, from the week-by-week plan (10 min).
3. Dependencies: contract changes coming, designs to hand off, decisions due (register) (10 min).
4. What HOCO must provide this week — data, access, answers (5 min).

Sunday has no stand-up message: the planning replaces it.

Daily stand-up messageCopy Anchor Link

Posted in the team group by 10:00, Monday to Thursday. Task ids are mandatory; a blocker names who or what it waits for.

Stand-up — Imad
Yesterday: MRA-04 cart screen against the mock (PR #31 open)
Today: MRA-04 checkout confirmation; review hoco#52 (contract)
Blockers: cart.checkout example lacks the CREDIT_LIMIT_EXCEEDED error — Anis

Nobody answers a stand-up in the group. A blocker is handled directly with the person named, within the hour.

Mid-week syncCopy Anchor Link

1. Blockers older than half a day.
2. Contract changes and design changes coming before Sunday.
3. Open Critical and Major issues, needs-info issues older than 3 days.
4. Walkthrough of PRs labelled security merged this week (5 min).
5. What each person will show on Thursday.

Thursday internal demoCopy Anchor Link

• Show, do not tell: from staging (or Claude Design for design), never from localhost.
• For each item: task id, what is done, what is left.
• Each done item has its recording of at most 2 minutes attached to the PR (definition of done).
• Akram notes design-QA findings; Anis notes what changes in the plan.

Client reviewCopy Anchor Link

HOCO receives the agenda at least one working day before. Anis chairs.

1. Progress against the milestones — the Progress page (5 min).
2. Demo of what is new (30 min), driven by the team on staging, or by HOCO's testers on pre-production when a candidate is out.
3. Decisions due — the register items whose needed-by task is near (15 min).
4. Change requests: new, analysed, waiting for a decision (5 min).
5. The next two weeks (5 min).

Nobody accepts new scope during the review: the answer is « C'est noté — nous revenons vers vous avec l'impact » and a change request follows. Anis sends the recap e-mail within 24 hours (template).

RetroCopy Anchor Link

Keep / stop / try, 30 minutes. At most three actions, each with an owner and a deadline expressed as a task id or "before the next retro". Actions are reviewed at the next retro. An action that changes a rule becomes a PR to these pages.

ChannelsCopy Anchor Link

Never decide in chat only. A decision reached in WhatsApp or in a call exists only once it is in the register (or, for a technical choice, in an ADR on the architecture page).

Response timesCopy Anchor Link

Working hours, Sunday to Thursday.

Outside working hours nobody is expected to answer; muting notifications is fine. A phone call is reserved for P1 incidents.

Meeting notesCopy Anchor Link

The person who called the meeting writes the notes (Anis for every client meeting) and publishes them within 24 hours.

# <Réunion / Meeting> — YYYY-MM-DD
Participants:
Ordre du jour / Agenda:

## Décisions / Decisions
- D-xx — <decision> (entered in the register)

## Actions
- <who> — <what> — <task or issue id> — <by when: task or next meeting>

## Questions ouvertes / Open questions
- <question> → register D-xx, owner, needed by <task id>

## Notes

For client meetings the same content, in French, goes to HOCO by e-mail, which is the record HOCO can answer.

Progress reportingCopy Anchor Link

1. Thursday by 12:00 each person posts their Thursday report: done (task ids and PRs), in progress (what remains), blocked (on what — a decision, a dependency, a person).
2. Thursday by 16:00 Anis sets status: "done" and doneOn in tasks.json, runs pnpm docs:generate, adds the dated section to the Progress page (what was delivered, with PR links; what changed in the plan and why), and merges a docs(plan): … PR. The docs deploy publishes it.
3. tasks.json records only done work: "in progress" lives in PRs and stand-ups. A slip is never fixed by editing a date — it is a changed effort, dependency or scope (planning method).
4. HOCO follows progress through the Progress page, the client review and the recap e-mail.

EscalationCopy Anchor Link

RamadanCopy Anchor Link

Ramadan is expected from about 8 February to 8 March 2027, Eid al-Fitr around 9–10 March (both confirmed on announcement; the Eid days are holidays in the plan). The plan keeps the working days; the schedule changes:

The pilot may overlap Ramadan: its KPIs are read in that context, or HOCO chooses to start it after Eid — see the timeline.