Skip to content

Creating Cahier des Charges for PolyPortal

Field Value
Source Obsidian · Claudian plugin
Session ses_f78372a34ffepb5q2bqgQ9mXd2
Started 2026-09-09 20:08
Messages 11
Parts 70 (text+patch+tool) · 10 reasoning · 29 tool calls
Model opencode:big-pickle
Directory /home/sambasene/obsidian/Vault

based on all teh data we have and this file create another file that will be the cahier des charge of the polyportal project

<linked_note path=“Cahier des Charges - PolyPortal.md” />

Let me gather all the PolyPortal data from the vault first.

read — {"filePath": "/home/sambasene/obsidian/Vault/Cahier des Charges - PolyPortal.md"}

<path>/home/sambasene/obsidian/Vault/Cahier des Charges - PolyPortal.md</path>
<type>file</type>
<content>
1:
2: Un **Cahier des Charges (CdC)** structure votre projet pour aligner la maîtrise d'ouvrage (vos besoins) et la maîtrise d'œuvre (les prestataires).
3:
4:
5:
6: **1. Présentation du Projet**
7:
8:
9:
10: - **Contexte :** Histoire, enjeux, raisons du lancement de ce projet.
11:
12:
13:
14: - **Objectifs :** Résultats attendus (ex: augmenter le trafic de 20 %, automatiser la paie).
15:
16:
17:
18: - **Périmètre :** Ce qui est inclus dans le projet... et ce qui en est explicitement exclu.
19:
20:
21:
22: - **Cibles / Utilisateurs :** Profil des utilisateurs finaux (pers
…[truncated]

glob — {"pattern": "**/*[Pp]oly[Pp]ortal*"}

/home/sambasene/obsidian/Vault/Cahier des Charges - PolyPortal.md
/home/sambasene/obsidian/Vault/drafts/polyportal.md
/home/sambasene/obsidian/Vault/Projects/PolyPortal.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Projects/Solo/PolyPortal fr 1.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Projects/Solo/PolyPortal fr.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Projects/Solo/PolyPortal.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Images/PolyPortal figma_light_new.png
/home/sambasene/obsidian/Vault/The Pseudo Line/Images/PolyPortal figma_light_components.png
/home/sambasene/obsidian/Vault/The Pseudo Line/Images/PolyPortal figma_light_brown_mobile.png
/home/sambasene/obsidian
…[truncated]

glob — {"pattern": "The Pseudo Line/**/*"}

/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/Wizard of Oz.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/wireframes.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/Wireframe testing.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/Viability.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/ventures.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/user interviews.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/user flows.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/technical specs.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/strategic alignment.md
/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/Steering Committee.md
/home/sambasene/o
…[truncated]

Now let me read all the key PolyPortal source documents:

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Projects/Solo/PolyPortal.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Projects/Solo/PolyPortal.md</path>
<type>file</type>
<content>
1: ---
2: type: projet
3: statut: en_cours
4: tags:
5: - pseudo-line
6: - projet
7: pm-project: true
8: id: "vy9n0u9t1ieya1k"
9: title: "PolyPortal"
10: taskIds: []
11: customFields: []
12: teamMembers: []
13: savedViews: []
14: createdAt: "2026-08-19T15:23:25.947Z"
15: updatedAt: "2026-08-19T15:23:25.947Z"
16: ---
17:
18:
19: As follow is a prototype of what I wanted to be the Pseudo Polytech Portal (PPP).
20:
21: This prototype was made specially for my classmates : DUT 1 TR, even though I'm at odd with them because they are mfs.
22:
23: The name shown in the following sc
…[truncated]

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Projects/Solo/PolyPortal fr.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Projects/Solo/PolyPortal fr.md</path>
<type>file</type>
<content>
1: ---
2: type: projet
3: statut: en_cours
4: tags:
5: - pseudo-line
6: - projet
7: pm-project: true
8: id: "vy9n0u9t1ieya1k"
9: title: "PolyPortal"
10: taskIds: []
11: customFields: []
12: teamMembers: []
13: savedViews: []
14: createdAt: "2026-08-19T15:23:25.947Z"
15: updatedAt: "2026-08-19T15:23:25.947Z"
16: ---
17:
18:
19: Vous trouverez ci-dessous un prototype de ce que je souhaitais être le Pseudo Polytech Portal (PPP).
20:
21: Le nom affiché dans la capture d'écran suivante, « Polytech Portal », a depuis été remplacé par « PolyPortal », à la suite d'une suggestion
…[truncated]

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Projects/Solo/PolyPortal fr 1.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Projects/Solo/PolyPortal fr 1.md</path>
<type>file</type>
<content>
1: ---
2: type: projet
3: statut: en_cours
4: tags:
5: - pseudo-line
6: - projet
7: pm-project: true
8: id: "vy9n0u9t1ieya1k"
9: title: "PolyPortal"
10: taskIds: []
11: customFields: []
12: teamMembers: []
13: savedViews: []
14: createdAt: "2026-08-19T15:23:25.947Z"
15: updatedAt: "2026-08-19T15:23:25.947Z"
16: ---
17:
18:
19: Vous trouverez ci-dessous un prototype de ce que je souhaitais être le Pseudo Polytech Portal (PPP).
20:
21: Le nom affiché dans la capture d'écran suivante, « Polytech Portal », a depuis été remplacé par « PolyPortal », à la suite d'une suggestio
…[truncated]

read — {"filePath": "/home/sambasene/obsidian/Vault/Projects/PolyPortal.md"}

<path>/home/sambasene/obsidian/Vault/Projects/PolyPortal.md</path>
<type>file</type>
<content>
1: ---
2: pm-project: true
3: id: "xf56h9m5mtrgt5g4"
4: title: "PolyPortal"
5: description: ""
6: color: "#7a9ec4"
7: icon: "📱"
8: taskIds: ["vgzy6zl2mtrgu2tj"]
9: customFields: []
10: teamMembers: ["Awa Diop", "Samba Sene"]
11: savedViews: []
12: createdAt: "2026-09-07T16:38:38.548Z"
13: updatedAt: "2026-09-07T19:36:44.250Z"
14: ---
15:
16: # 📱 PolyPortal
17:
18: ## Tasks
19: - [ ] [[cahier-des-charges|Cahier des charges]]
(End of file - total 19 lines)
</content>

read — {"filePath": "/home/sambasene/obsidian/Vault/drafts/polyportal.md"}

<path>/home/sambasene/obsidian/Vault/drafts/polyportal.md</path>
<type>file</type>
<content>
1: ---
2: title: "PolyPortal — A Google-Inspired Student Dashboard for ESP"
3: published: 2026-08-30
4: description: "How a frustrated DUT 1 TR student built a centralized launcher and dashboard that replaced scattered WhatsApp links, missed announcements, and daily meeting-link hunts."
5: cover: ""
6: tags:
7: - Education
8: - Student Life
9: - ESP
10: - Web App
11: - UI/UX
12: category: "Projects"
13: draft: true
14: ---
15:
16: # PolyPortal — A Google-Inspired Student Dashboard for ESP
17:
18: Every online class day at ESP started the same way: ten students pasting meeting links into WhatsApp, t
…[truncated]

Let me also read the existing project documents and technical specs:

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Documents/PolyPortal/PolyPortal Doc.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Documents/PolyPortal/PolyPortal Doc.md</path>
<type>file</type>
<content>
1: ---
2: type: doc
3: statut: en_cours
4: tags:
5: - polyportal
6: ---
7:
8: # PolyPortal
9:
10: **Pitch :** Une page d'accueil inspiré par la page par défaut Google du navigation Chrome et un tableau de bord avec des fonctionnalités supplémentaires pour les étudiants DUT 1 Telecom Reseaux (TR) de l'ESP, centralisant principalement les liens d'accès rapide.
11:
12: **Vertical :** Campus/Éducation
13:
14: **Statut :** en pause (prototype hors ligne depuis l'arret de mon serveur)
15:
16: ## Problème / Pourquoi
17:
18: - **Problème :** les étudiants perdent du te
…[truncated]

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Documents/PolyPortal/PolyPortal en doc.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Documents/PolyPortal/PolyPortal en doc.md</path>
<type>file</type>
<content>
1: ---
2: type: doc
3: statut: en_cours
4: tags:
5: - polyportal
6: ---
7:
8: # PolyPortal
9:
10: **One-line pitch:** A Google-inspired launcher and dashboard for ESP DUT 1 TR students that centralizes quick-access links, announcements, schedule, notes, subjects, and class-rep broadcast tools in one place.
11:
12: **Vertical:** Campus/Education
13:
14: **Status:** active (live prototype, in use by classmates for a semester and a half)
15:
16: ## Problem / Why
17:
18: - **Problem:** Students waste time hunting for scattered links — meeting links, Google Class
…[truncated]

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Documents/PolyPortal/PolyPortal Doc 1.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Documents/PolyPortal/PolyPortal Doc 1.md</path>
<type>file</type>
<content>
1: ---
2: type: doc
3: statut: en_cours
4: tags:
5: - polyportal
6: ---
7:
8: # PolyPortal
9:
10: **Pitch :** Une page d'accueil inspiré par la page par défaut Google du navigation Chrome et un tableau de bord avec des fonctionnalités supplémentaires pour les étudiants DUT 1 Telecom Reseaux (TR) de l'ESP, centralisant principalement les liens d'accès rapide.
11:
12: **Vertical :** Campus/Éducation
13:
14: **Statut :** en pause (prototype hors ligne depuis l'arret de mon serveur)
15:
16: ## Problème / Pourquoi
17:
18: - **Problème :** les étudiants perdent du
…[truncated]

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Documents/PolyPortal/PolyPortal Doc 1 1.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Documents/PolyPortal/PolyPortal Doc 1 1.md</path>
<type>file</type>
<content>
1: ---
2: type: doc
3: statut: en_cours
4: tags:
5: - polyportal
6: ---
7:
8: # PolyPortal
9:
10: **Pitch :** Une page d'accueil inspiré par la page par défaut Google du navigation Chrome et un tableau de bord avec des fonctionnalités supplémentaires pour les étudiants DUT 1 Telecom Reseaux (TR) de l'ESP, centralisant principalement les liens d'accès rapide.
11:
12: **Vertical :** Campus/Éducation
13:
14: **Statut :** en pause (prototype hors ligne depuis l'arret de mon serveur)
15:
16: ## Problème / Pourquoi
17:
18: - **Problème :** les étudiants perdent d
…[truncated]

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/Stack.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/Stack.md</path>
<type>file</type>
<content>
1: ---
2: type: note
3: statut: actif
4: tags:
5: - pseudo-line
6: - glossaire
7: ---
8:
9:
10: The **Stack** refers to the full set of technologies, programming languages, frameworks, databases, libraries, and infrastructure tools used to build and run an application.
11:
12: - **Typical Components:**
13:
14: - **Frontend/UI:** Flutter, React, Vue, HTML/CSS.
15:
16: - **Backend:** Node.js, Python, Java, Go, PHP.
17:
18: - **Database:** PostgreSQL, Firebase, MongoDB.
19:
20: - **DevOps/Hosting:** Docker, AWS, GitHub Actions.
21:
22: - **Example:** _"Flutter for mobile, Firebase for ba
…[truncated]

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/Scope.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/Scope.md</path>
<type>file</type>
<content>
1: ---
2: type: note
3: statut: actif
4: tags:
5: - pseudo-line
6: - glossaire
7: ---
8:
9:
10: **Scope** defines the boundaries of a project, what **will** be included and, equally importantly, what **will not** be included (out of scope).
11:
12: - **Why it matters:** It prevents "scope creep" (the gradual, uncontrolled expansion of project requirements as work progresses).
13:
14: - **Example:** _"For v1.0, users can sign up, create a profile, and make payments. Subscriptions and dark mode are out of scope."_
15:
(End of file - total 15 lines)
</content>

Let me grab a few more supporting documents:

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/risk assessment.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/risk assessment.md</path>
<type>file</type>
<content>
1: ---
2: type: note
3: statut: actif
4: tags:
5: - pseudo-line
6: - glossaire
7: ---
8:
9:
10: The systemic process of identifying, analyzing, and evaluating potential risks, events or conditions that could negatively impact project timelines, budgets, or deliverables before they occur.
11:
(End of file - total 11 lines)
</content>

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/technical specs.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/technical specs.md</path>
<type>file</type>
<content>
1: ---
2: type: note
3: statut: actif
4: tags:
5: - pseudo-line
6: - glossaire
7: ---
8:
9:
10: Detailed engineering documents written by developers outlining implementation details—such as algorithmic approaches, data flows, third-party library dependencies, security considerations, and edge-case handling.
11:
(End of file - total 11 lines)
</content>

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/Solution Architecture.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/Solution Architecture.md</path>
<type>file</type>
<content>
1: ---
2: type: note
3: statut: actif
4: tags:
5: - pseudo-line
6: - glossaire
7: ---
8:
9:
10: The micro-level blueprint focused on designing a specific software solution or project. It bridges high-level business requirements and technical implementation, defining the specific stack, database structure, and component integrations.
11:
(End of file - total 11 lines)
</content>

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/acceptance criteria.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/acceptance criteria.md</path>
<type>file</type>
<content>
1: ---
2: type: note
3: statut: actif
4: tags:
5: - pseudo-line
6: - glossaire
7: ---
8:
9:
10: **Acceptance Criteria** are a pre-defined set of strict conditions or requirements that a feature/user story **must meet** for it to be considered "Done" and accepted by the product manager, client, or QA team.
11:
12: - **Format:** Often written using **Given-When-Then** (BDD) syntax or as a strict checklist.
13:
14: - **Example (User Login Story):**
15:
16: - $\checkmark$ **Given** the user is on the login page, **When** they enter a valid email and password and click "Login",
…[truncated]

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/SMART deliverables.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/SMART deliverables.md</path>
<type>file</type>
<content>
1: ---
2: type: note
3: statut: actif
4: tags:
5: - pseudo-line
6: - glossaire
7: ---
8:
9:
10: Concrete project outputs designed around the **SMART** framework to ensure clarity and accountability:
11:
12: - **S**pecific: Clearly defined without ambiguity (e.g., _"Build an authentication API endpoint"_ rather than _"Work on backend"_).
13:
14: - **M**easurable: Quantifiable so progress can be verified (e.g., _"Handles 1,000 requests/sec with $<100\text{ms}$ latency"_).
15:
16: - **A**chievable: Realistic given team skills, tech stack, and resources.
17:
18: - **R**elevant:
…[truncated]

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/Stakeholders.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/Stakeholders.md</path>
<type>file</type>
<content>
1: ---
2: type: note
3: statut: actif
4: tags:
5: - pseudo-line
6: - glossaire
7: ---
8:
9: **Parties prenantes**
10:
11: Any individuals, teams, or groups who are impacted by or have an interest in the outcome of the project. This includes end-users, developers, designers, investors, regulators, and marketing teams.
12:
(End of file - total 12 lines)
</content>

read — {"filePath": "/home/sambasene/obsidian/Vault/Artifacts/Projects/Pseudo Line_tasks/polyportal.md"}

<path>/home/sambasene/obsidian/Vault/Artifacts/Projects/Pseudo Line_tasks/polyportal.md</path>
<type>file</type>
<content>
1: ---
2: pm-task: true
3: projectId: "38h6z28ss5euguh"
4: parentId:
5: id: "klixbfdowu0q5v8"
6: title: "PolyPortal"
7: type: "task"
8: status: "in-progress"
9: priority: "medium"
10: start: "2026-08-19"
11: due: ""
12: progress: 0
13: assignees: []
14: tags: []
15: subtaskIds: []
16: dependencies: []
17: createdAt: "2026-08-19T15:23:25.947Z"
18: updatedAt: "2026-08-19T15:23:25.947Z"
19: ---
20:
21: Sub-project: [[Artifacts/Projects/Pseudo Line_tasks/polyportal]]
(End of file - total 21 lines)
</content>

Let me check the architecture and product map artifacts:

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/specs.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/specs.md</path>
<type>file</type>
<content>
1: ---
2: type: note
3: statut: actif
4: tags:
5: - pseudo-line
6: - glossaire
7: ---
8:
9:
10: **Specs** (short for Specifications) are detailed documents or descriptions that explain **how** a system, feature, or component should behave, operate, and be built.
11:
12: - **Types of Specs:**
13:
14: - **Functional Specs (FRs):** Describe features and user flows (e.g., _"When the user taps 'Submit', validate the email format and save to the database"_).
15:
16: - **Non-Functional Specs (NFRs):** Describe system quality, constraints, and performance (e.g., _"API responses must load under $
…[truncated]

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/user flows.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/user flows.md</path>
<type>file</type>
<content>
1: ---
2: type: note
3: statut: actif
4: tags:
5: - pseudo-line
6: - glossaire
7: ---
8:
9:
10: Diagrams or visual maps that illustrate the step-by-step path a user takes through an application to complete a specific goal or task (e.g., from hitting a landing page $\rightarrow$ creating an account $\rightarrow$ checking out).
11:
(End of file - total 11 lines)
</content>

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/DB schemas.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/DB schemas.md</path>
<type>file</type>
<content>
1: ---
2: type: note
3: statut: actif
4: tags:
5: - pseudo-line
6: - glossaire
7: ---
8:
9:
10: Database Schemas
11:
12: The logical and physical structure that defines how data is organized inside a database—including tables, columns, data types, relationships, indexes, and constraints.
13:
(End of file - total 13 lines)
</content>

read — {"filePath": "/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/API specs.md"}

<path>/home/sambasene/obsidian/Vault/The Pseudo Line/Sub/API specs.md</path>
<type>file</type>
<content>
1: ---
2: type: note
3: statut: actif
4: tags:
5: - pseudo-line
6: - glossaire
7: ---
8:
9:
10: Formal documentation specifying how client applications (like Flutter) interact with backend servers. They define available endpoints, request structures, headers, authentication methods, and expected JSON responses (e.g., using OpenAPI/Swagger).
11:
(End of file - total 11 lines)
</content>

Now I have everything. Let me create the comprehensive Cahier des Charges, synthesizing all the data from the vault.

todowrite — `{“todos”: [{“content”: “Read all PolyPortal source documents”, “status”: “completed”, “priority”: “high”}, {“content”: “Read the CdC template structure”, “status”: “completed”, “priority”: “high”}, {”

…[truncated]`

[
{
"content": "Read all PolyPortal source documents",
"status": "completed",
"priority": "high"
},
{
"content": "Read the CdC template structure",
"status": "completed",
"priority": "high"
},
{
"content": "Read supporting sub-documents (specs, scope, risks, etc.)",
"status": "completed",
"priority": "medium"
},
{
"content": "Synthesize and write the Cahier des Charges document",
"status": "in_progress",
"priority": "high"
},
{
"content": "Update the PolyPortal.md task list to link the CdC",
"status": "pending",
"priority": "medium"
}
]

write — `{“filePath”: “/home/sambasene/obsidian/Vault/The Pseudo Line/Documents/PolyPortal/Cahier des Charges - PolyPortal.md”, “content”: “—\ntype: doc\nstatut: en_cours\ntags:\n - polyportal\n - cahier-des

…[truncated]`

Wrote file successfully.

Now let me update the project task file to reflect the CdC completion:

edit — `{“filePath”: “/home/sambasene/obsidian/Vault/Projects/PolyPortal.md”, “oldString”: “## Tasks\n- [ ] [[cahier-des-charges|Cahier des charges]]”, “newString”: “## Tasks\n- [x] [[The Pseudo Line/Document

…[truncated]`

Edit applied successfully.

todowrite — `{“todos”: [{“content”: “Read all PolyPortal source documents”, “priority”: “high”, “status”: “completed”}, {“content”: “Read the CdC template structure”, “priority”: “high”, “status”: “completed”}, {”

…[truncated]`

[
{
"content": "Read all PolyPortal source documents",
"status": "completed",
"priority": "high"
},
{
"content": "Read the CdC template structure",
"status": "completed",
"priority": "high"
},
{
"content": "Read supporting sub-documents (specs, scope, risks, etc.)",
"status": "completed",
"priority": "medium"
},
{
"content": "Synthesize and write the Cahier des Charges document",
"status": "completed",
"priority": "high"
},
{
"content": "Update the PolyPortal.md task list to link the CdC",
"status": "completed",
"priority": "medium"
}
]

Done. Le Cahier des Charges — PolyPortal a été créé à [[The Pseudo Line/Documents/PolyPortal/Cahier des Charges - PolyPortal]].

Voici ce qu’il contient, structuré en 8 sections à partir de toutes les données du vault :

Section Contenu
1. Présentation du projet Contexte (ESP, DUT 1 TR, prototype v1 utilisé 1,5 semestre), objectifs mesurables, périmètre (in/out), personas utilisateurs
2. Spécifications fonctionnelles 4 grands modules détaillés — Launcher, Dashboard (annonces, planning, focus lab, notes, matières, archivage), Panel Admin, Profil — avec parcours utilisateurs en 5 scénarios et arborescence complète
3. Spécifications techniques Stack v1 vs. v2 (3 options candidates), modélisation des données (11 entités principales), intégrations (Google, Cloudinary, écosystème Poly), performances, sécurité
4. Organisation & calendrier 5 phases (Phase 1 terminée → Phase 5 éloignée), livrables SMART, gouvernance avec le point de défaillance unique identifié
5. Modalités de réponse Format, critères de sélection pondérés, applicable si prestataire externe
6. Risques & questions ouvertes 8 risques identifiés avec impact et mitigation
7. Critères de succès 7 critères mesurables
8. Annexes Liens wikilinks vers tous les documents sources du vault

J’ai aussi mis à jour [[Projects/PolyPortal]] pour marquer la tâche CdC comme terminée. ✅

10 internal reasoning block(s) omitted — raw thinking is not exported (see archive index).