pascalandy/cim 30

.abstract.md

@@ -0,0 +1,31 @@
+---
+type: atlas
+layer: l0
+corpus: code-repo
+scope: top
+root: pascalandy-blog-paper
+parent:
+date_updated: 2026-03-13
+---
+# Abstract
+
+This repo is an Astro 5 blog codebase with Bun/Just tooling and a large Markdown post corpus. Use it to locate canonical site config, route behavior, content schema, workflow commands, or published posts. Treat the atlas as a routing layer only; read source files for exact behavior, rendering, and frontmatter rules.
+
+## Use this when
+- you need the fastest entry point for setup, local QA, or build commands
+- you need canonical site config, theme settings, or content schema
+- you need the implementation behind blog routes, tags, or post visibility
+- you need to edit published posts or public workflow docs
+- you need to separate maintained project docs from scratch notes
+
+## Main areas
+- `README.md` — setup and high-level repo entry point
+- `src/` — Astro app code, routes, layouts, utilities, and config
+- `src/data/blog/` — published posts and public development workflow docs
+- `scripts/` — maintenance helpers for tags, imports, and frontmatter cleanup
+- `./.overview.md#reference-map` — Detailed map
+
+## Out of scope
+- generated output in `dist/`, `.astro/`, `cache/`, and `public/pagefind/`
+- secrets or environment files such as `.env`
+- treating `dev_notes/` as canonical project documentation

.overview.md

@@ -0,0 +1,51 @@
+---
+type: atlas
+layer: l1
+corpus: code-repo
+scope: top
+root: pascalandy-blog-paper
+parent:
+date_updated: 2026-03-13
+---
+# Overview
+
+## Corpus Type
+
+`code-repo`. The entry points that shape navigation are `README.md`, `AGENTS.md`, `package.json`, `astro.config.ts`, and the executable files under `src/`. `src/data/blog/` is large, but it is governed by code and schema files rather than standing alone as a separate docs corpus.
+
+## Navigation Strategy
+
+Start with `README.md` for setup, then use `AGENTS.md` for repo-specific workflow and architectural conventions. For behavior questions, go straight to `src/pages/` and follow imports into `src/layouts/`, `src/components/`, and `src/utils/`. For content questions, trust `src/content.config.ts` plus the files in `src/data/blog/`; use `dev_notes/` only as working context.
+
+## Reference Map
+
+| Path | Role | Use When | Trust Level | Notes |
+| --- | --- | --- | --- | --- |
+| README.md | entry-point | You need setup, stack, or the primary repo starting point | high | Shortest path to local commands and project framing |
+| AGENTS.md | authoritative | You need repo-specific agent workflow, architecture, or coding rules | high | Stronger than ad hoc notes when workflow guidance conflicts |
+| src/config.ts | authoritative | You need site metadata, theme selection, or publish timing rules | high | Defines `SITE`, theme catalog, and active theme |
+| src/content.config.ts | authoritative | You need blog schema, loader rules, or ignored-file behavior | high | Canonical frontmatter schema for `src/data/blog/` |
+| src/data/blog/ | authoritative | You need published posts or the public workflow-doc corpus | high | Markdown source of truth; `_`-prefixed files are excluded by loader rule |
+| scripts/ | implementation | You need cleanup or migration helpers for content maintenance | medium | Useful for tag, import, and filename hygiene; not the main runtime path |
+| src/pages/ | implementation | You need route behavior, static path generation, or page-level rendering | high | Start here for `/`, `/blog/`, `/tags/`, `/search/`, and RSS routes |
+| justfile | reference | You need the supported dev, QA, CI, build, or cleanup commands | high | Prefer this over memory or stale notes for command names |
+| src/data/blog/dev_workflows/ | tutorial | You need published workflow guidance for contributors or agents | medium | Public-facing how-to material; useful, but not executable truth |
+| dev_notes/ | archive | You need scratch context, plans, or abandoned ideas | low | User scratchpad; may lag behind current implementation |
+
+## Retrieval Routes
+
+- If you need local commands or quality gates, read `README.md` -> `justfile` -> `.github/workflows/ci.yml` when CI behavior matters.
+- If you need theme, metadata, or publish-window behavior, read `src/config.ts` -> `astro.config.ts` -> `src/utils/postFilter.ts`.
+- If you need content schema or why a post is missing, read `src/content.config.ts` -> the target file in `src/data/blog/`.
+- If you need page behavior or URL generation, read `src/pages/blog/[...page].astro` or `src/pages/blog/[...slug]/index.astro` -> imported layouts/components/utils.
+- If you need contributor workflow docs, read `src/data/blog/dev_workflows/` first; only consult `dev_notes/` for non-canonical working context.
+- If you need tag or frontmatter maintenance, read `justfile` -> `scripts/check-tags.sh` -> the relevant helper in `scripts/`.
+
+## Gaps and Cautions
+
+- `dev_notes/` looks important at a glance, but `AGENTS.md`, `justfile`, and executable source files are the safer defaults.
+- Command guidance is split between `justfile` and public workflow posts under `src/data/blog/dev_workflows/`; when wording differs, prefer executable files.
+
+## Child Maps
+
+- No child maps currently needed.

src/data/blog/cim-30.md

@@ -32,7 +32,7 @@ La présentation sera donnée par **Maciej Cepnik** , cofondateur de Veriphi, do
 
 ### 2) Proof-of-stake
 
-Zakaria parlera du proof-of-stake dans le contexte de la blockchain Tezos (par exemple, il expliquera le fonctionnement du baking). Il comparera l'implémentation du proof-of-stake de Tezos (liquid proof-of-stake) à une autre variante populaire (delegated proof-of-stake). Il abordera également d'autres aspects de Tezos (histoire, philosophie, gouvernance et amendements potentiels).
+L'invité parlera du proof-of-stake dans le contexte de la blockchain Tezos (par exemple, il expliquera le fonctionnement du baking). Il comparera l'implémentation du proof-of-stake de Tezos (liquid proof-of-stake) à une autre variante populaire (delegated proof-of-stake). Il abordera également d'autres aspects de Tezos (histoire, philosophie, gouvernance et amendements potentiels).
 
 **Agenda**
 
@@ -44,7 +44,7 @@ Zakaria parlera du proof-of-stake dans le contexte de la blockchain Tezos (par e
 - La différence entre le liquid proof of stake de Tezos et le delegated proof of stake de EOS
 - Le mécanisme de gouvernance initial de Tezos
 
-**Zakaria Boukhcheb** est un des organisateurs du Meetup Tezos Montréal depuis septembre 2018 et un adepte des cryptomonnaies depuis plusieurs années. Il s'intéresse à l'économie, à la finance, à la technologie, aux sciences et aux arts.
+L'invité est un des organisateurs du Meetup Tezos Montréal depuis septembre 2018 et un adepte des cryptomonnaies depuis plusieurs années. Il s'intéresse à l'économie, à la finance, à la technologie, aux sciences et aux arts.
 
 Dans tous les cas, je vais m'assurer qu'on passe tous une belle soirée! Notre Meetup favorise les triades, les échanges authentiques et l’apprentissage. C'est pas ta classe boring. C'est du réseautage comme le réseautage devrait être fait. See ya 👩‍⚕️ 👨‍⚕️ 👩‍🌾 👨‍🌾 👩‍🍳 👨‍🍳 👩‍🎓 👨‍🎓 👩‍🎤 👨.