Meeting yuri × Miguel: fix the architecture of the universe — folders and languages — and decide how the three Miguel projects fit into the larger universe. Today is about form and organization (we’ll see functionality later), thinking about when co takes over. Everything approved. ✅
Objectives
- Understand the current organization (folders + languages)
- Separate what is content from what is scaffolding
- Decide how the 3 projects fit into the Miguel universe
- Define how the universe presents itself when co is downloaded
1. The central idea: content × form
The same idea from method organizes everything:
- Content = what is written (the texts). This is what matters — and it’s only this that co will use.
- Form = translation, visual, widgets, publishing. This is scaffolding: builds the site today, but co takes over later.
Agreed: keep content clean and separate from scaffolding, so the switch to co is seamless. ✅
2. The 3 projects inside the Miguel universe (MG)
Miguel is the umbrella universe (the person, the hub). Each project is a mission = a group of people with a clear and measurable objective:
the three missions
- MSE (
MGMSE) — MS&E degree; it’s the foundation of the others.- App Agro (
MGAGRO) — WhatsApp bot for agricultural management.- Alpha Scholars (
MGALPHA) — study universe (the 22h per week).
How they fit:
Miguel (MG) — hub pessoal
├── MSE (MGMSE) — já é universo próprio
├── App Agro (MGAGRO) — seção hoje → vira universo
└── Alpha Scholars (MGALPHA) — seção hoje → vira universo
- Each project is a child sub-universe of Miguel. MSE is already a separate universe; App Agro and Alpha Scholars today live as sections within Miguel and become their own universe when they grow (same promotion we’ve done before).
- The MG code binds the whole tree:
MG-at the hub,MGMSE·MGAGRO·MGALPHAin each mission — one identity only. - When co loads Miguel, the projects appear alongside it, as children; public ones can be subscribed to.
Agreed: hub + missions; each mission promotes to universe when it matures. ✅
3. Folders — fix
how it looks
- At the top: what matters (content + universe record + translation memory)
- Together: the scaffolding, marked as disposable
- Separate: the references (drafts, comparisons)
Clean content → the switch to co is just “point to the content”. ✅
4. Languages (PT / EN)
- PT is the original; EN is an automatic translated copy, page by page.
- The translation has memory stored — doesn’t retranslate needlessly, and co uses it later without cost.
- Switching language is form (a button), doesn’t go in the menu.
- Translation model chosen: Sonnet (see comparison). ✅
5. Board and widgets
- Tasks live in the text tables (single source of truth). The kanban is just a view of them — co has its own board that reads the same tables.
- The calendar is a real widget; co needs a space to fit widgets like this.
Agreed: table is the source; kanban is disposable. ✅
6. When co is downloaded (first time)
The universe should introduce itself: what is the home page, which languages, who is parent and who is child, what is public.
- Then the user opens co and lands on Miguel’s hub with the projects alongside ready to subscribe — without configuring anything.
- To decide: is Miguel a public showcase or a more private hub? The path for the new user points to private hub + public projects. ⬅️ only open question
What was decided ✅
- Content separated from scaffolding
- 3 projects = child missions of the hub; promote to universe when they grow
- Translation memory stored; default model = Sonnet
- Markdown table = single source of truth for the board
- Miguel public (showcase) × private (hub) — close today