70 lines
4 KiB
Markdown
70 lines
4 KiB
Markdown
|
# CLAUDE.md
|
|||
|
|
|
|||
|
|
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
|
|||
|
|
|
|||
|
|
## What this repo is
|
|||
|
|
|
|||
|
|
This is the **project management and documentation repository** for Talas Group — an audio hardware company building professional, repairable, modular microphones and the **Veza** community web platform. It is **not a code repository**. The Veza source code lives at `/home/senke/git/talas/veza`.
|
|||
|
|
|
|||
|
|
This repo is a structured knowledge base of ~80+ markdown files organized into 14 numbered domains (00–13). It is also a Logseq graph (journals disabled, markdown format, `[[wikilinks]]` used for cross-references).
|
|||
|
|
|
|||
|
|
## Repo structure (numbered domains)
|
|||
|
|
|
|||
|
|
| # | Domain | What it covers |
|
|||
|
|
|---|--------|---------------|
|
|||
|
|
| 00 | META | Identity doc (single source of truth), manifesto, glossary, system map |
|
|||
|
|
| 01 | PILOTAGE | Strategy, roadmaps (hardware / software+business), calendar, task tracking |
|
|||
|
|
| 02 | PRODUITS_PHYSIQUES | Microphone (KiCAD, BOM, datasheets), future products (sound card, amp, monitors) |
|
|||
|
|
| 03 | APPS_&_SERVICES | Veza architecture specs, API routes, feature specs (shop, community, personal) |
|
|||
|
|
| 04 | INFRA_DEPLOIEMENT | Ansible roles, Docker, HAProxy, Coraza WAF, CI/CD, security, ops notes |
|
|||
|
|
| 05 | EXPERIENCE_UTILISATEUR | UX/UI direction, design system (Sumi V3), visual identity, innovative concepts |
|
|||
|
|
| 06 | COMMUNAUTE_ECOSYSTEME | Community strategy, artist ambassadors, sample sharing, events |
|
|||
|
|
| 07 | CONTENUS_MARKETING | Branding, content strategy, product page copy, storytelling, social media |
|
|||
|
|
| 08 | CONFORMITE_JURIDIQUE | GDPR, terms of service, trademark filing guide, legal checklists |
|
|||
|
|
| 09 | MODELE_ECONOMIQUE | Business plan, market analysis, fiscal strategy, grants (NLNet), subsidies |
|
|||
|
|
| 10 | QUALITE_TESTS | QA, security audits, competitive benchmarks, hardware test plans |
|
|||
|
|
| 11 | RECHERCHE_&_LAB | AI audio, Rust streaming experiments, UX explorations |
|
|||
|
|
| 12 | DOCUMENTATION | Master index, session reports, references, dev guides |
|
|||
|
|
| 13 | ARCHIVES | Archived Veza code snapshots and old infra configs (excluded from Logseq graph) |
|
|||
|
|
|
|||
|
|
## Key entry points
|
|||
|
|
|
|||
|
|
- **Project identity (the reference doc):** `00_META/TALAS_IDENTITE_PROJET.md`
|
|||
|
|
- **What to do next:** `01_PILOTAGE/CALENDRIER_GENERAL.md`
|
|||
|
|
- **Find any doc:** `12_DOCUMENTATION/INDEX_DOCUMENTATION.md`
|
|||
|
|
- **Software/business tasks (mobile):** `01_PILOTAGE/ROADMAP_SOFTWARE_BUSINESS.md`
|
|||
|
|
- **Hardware tasks (workshop):** `01_PILOTAGE/ROADMAP_HARDWARE.md`
|
|||
|
|
- **Launch checklist:** `01_PILOTAGE/PLAN_ACTION_LANCEMENT.md`
|
|||
|
|
|
|||
|
|
## Tech stack context (for the products this repo documents)
|
|||
|
|
|
|||
|
|
- **Backend API:** Go (Gin, GORM) — 102 handlers, 138 services
|
|||
|
|
- **Streaming/WebSocket:** Rust (Axum)
|
|||
|
|
- **Frontend:** React 18, TypeScript, Tailwind CSS — 661 UI components, 52+ routes, i18n (EN/FR/ES)
|
|||
|
|
- **Database:** PostgreSQL, Redis
|
|||
|
|
- **Hardware design:** KiCAD
|
|||
|
|
- **Infra:** Self-hosted on 2× Dell R720, Ansible, Docker, HAProxy, Coraza WAF, WireGuard
|
|||
|
|
|
|||
|
|
## Working in this repo
|
|||
|
|
|
|||
|
|
### Language
|
|||
|
|
All documentation is written in **French**. Write and edit in French unless asked otherwise.
|
|||
|
|
|
|||
|
|
### Logseq compatibility
|
|||
|
|
This repo doubles as a Logseq graph. When editing markdown files:
|
|||
|
|
- Use `[[wikilinks]]` for cross-references between documents (Logseq resolves them)
|
|||
|
|
- Hidden folders (not indexed by Logseq): `.claude`, `13_ARCHIVES`, `99_SYMLINKS`, `_BROUILLON`
|
|||
|
|
- No daily journals — this is documentation-only mode
|
|||
|
|
|
|||
|
|
### File conventions
|
|||
|
|
- Each numbered domain has its own `README.md` explaining its scope
|
|||
|
|
- Top-level docs in each domain are UPPERCASE (e.g., `CALENDRIER_GENERAL.md`, `TALAS_IDENTITE_PROJET.md`)
|
|||
|
|
- Subdirectories group related detailed files
|
|||
|
|
- `_BROUILLON/` is for drafts
|
|||
|
|
|
|||
|
|
### What NOT to do
|
|||
|
|
- Do not modify files in `13_ARCHIVES/` — these are historical snapshots
|
|||
|
|
- Do not create code files here — code belongs in `/home/senke/git/talas/veza`
|
|||
|
|
- Do not add cloud service recommendations — infrastructure is 100% self-hosted (no AWS, no Cloudflare, no SaaS)
|
|||
|
|
- Do not suggest launching products without visual identity and branding being complete first — art direction is a hard prerequisite
|