Skip to content

docs(architecture): mapa hexagonal del monorepo (18 componentes)#51

Merged
montfort merged 1 commit into
mainfrom
docs/architecture-map
Jun 18, 2026
Merged

docs(architecture): mapa hexagonal del monorepo (18 componentes)#51
montfort merged 1 commit into
mainfrom
docs/architecture-map

Conversation

@montfort

Copy link
Copy Markdown
Contributor

Resumen

Añade un mapa de arquitectura versionado del monorepo bajo .straymark/architecture/, clasificando los crates del workspace lnxdrive-engine, la integración GNOME y las UIs experimentales en las capas hexagonales del proyecto (presentation / application / domain / outbound-adapters / infrastructure), según lnxdrive-guide/03-Arquitectura/01-arquitectura-hexagonal.md.

  • model.yml — 18 componentes × 5 capas, con enlaces entre componentes.
  • plan.drawio — diagrama de cajas por capa (se abre en cualquier editor DrawIO).

Contexto: por qué el mapa sí, el dashboard no

El formato es StrayMark Loom Spec 002 (straymark architecture validate → 18 componentes, exit 0), pero lo que se conserva es el mapa autónomo, no el dashboard de Loom.

Tras evaluar Loom decidimos no adoptarlo como herramienta de trabajo:

  • Su knowledge graph reportó ~169 "broken links", pero el análisis mostró que no son deuda documental: 146 son task-IDs de SpecKit (related: [T0xx], trazabilidad intencional), 18 son refs cross-artefacto (US2, FR-019, rutas a lnxdrive-guide/), y los 8 "doc-ref rotos" resuelven a archivos existentes (desajuste id-corto vs nombre-con-slug). Loom interpreta related: como enlaces doc→doc; lnxdrive lo usa para trazabilidad multi-artefacto.
  • El overlay "you are here" no se engancha (0/13, todo uncharted).
  • Para un proyecto single-operator y una extensión EXPERIMENTAL, el costo/beneficio no lo justifica.

packaging/guide/testing quedan fuera de alcance a propósito (sin código fuente; Loom solo cuenta archivos de código).

Notas

🤖 Generated with Claude Code

Versioned architecture map of the monorepo under .straymark/architecture/:
the lnxdrive-engine workspace crates, the GNOME integration and the
experimental UIs, classified into the project's hexagonal layers
(presentation / application / domain / outbound-adapters / infrastructure)
per lnxdrive-guide/03-Arquitectura/01-arquitectura-hexagonal.md.

- model.yml   — 18 components × 5 layers, with inter-component links
- plan.drawio — layered box diagram (opens in any DrawIO editor)

The format is StrayMark Loom Spec 002 (`straymark architecture validate`
passes: 18 components, exit 0), but the value kept here is the standalone
map. We are NOT adopting the Loom dashboard: its knowledge graph treats
SpecKit task refs (related: [T0xx]) as broken links, and the "you are here"
status overlay does not wire up — not worth the cost for a single-operator
project. See analysis in conversation.

packaging/guide/testing are intentionally out of scope (no source code).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@montfort montfort merged commit 92288fb into main Jun 18, 2026
5 checks passed
@montfort montfort deleted the docs/architecture-map branch June 18, 2026 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant