Interactive Wiki Interface
Relevant source files
The following files were used as context for generating this wiki page:
The Interactive Wiki Interface (often referred to as the "Atlas TAMV") serves as the primary cognitive and documentary layer of the TAMV ONLINE ecosystem. It is designed not merely as static documentation but as a dynamic, "living whitepaper" that bridges the gap between technical implementation (code) and civilizational governance. The interface enables users to navigate a complex graph of knowledge, spanning 14 distinct modules including identity (ISNI), architecture (MD-X), and philosophical frameworks (DEKATEOTL).
Sources: src/pages/wiki/modulo-omega/WikiValeMas.tsx, src/components/WikiLayout.tsx:12, src/App.tsx:28-44
Interface Architecture and Layout
The interface is structured around a multi-tier navigation system that facilitates discovery across high-level modules and specific technical articles. The root of this structure is defined by the wikiStructure, which organizes content into thematic sections.
Global Layout and Navigation
The WikiLayout component establishes a persistent sidebar (WikiSidebar) and a sticky header for consistent navigation across the Atlas. It utilizes a lg:ml-72 margin to accommodate the fixed sidebar on larger screens, ensuring the main content area remains focused on readability.
The diagram shows the structural relationship between global navigation components and the content area. Sources: src/components/WikiLayout.tsx:5-30, src/App.tsx:238-250
Module and Article Hierarchies
Content is indexed by modules (e.g., "Módulo 0 · Observabilidad", "Módulo 4 · SSI / DID"). Each module contains a collection of articles that can be viewed either as a grid of summaries or as individual full-text documents.
| Component | Responsibility | Relevant Files |
|---|---|---|
WikiPage | Main entry point for dynamic sections; handles routing between lists and specific articles. | src/pages/wiki/WikiPage.tsx |
ModuleArticleList | Renders a "Knowledge Grid" of 9 articles per page for a specific module. | src/pages/wiki/WikiPage.tsx:45 |
ArticleView | Displays full Markdown content with metadata (read time, tags, access level). | src/pages/wiki/WikiPage.tsx:103 |
PaginationBar | Manages stateful navigation through large article sets. | src/pages/wiki/WikiPage.tsx:94 |
Sources: src/pages/wiki/WikiPage.tsx:45-101, src/App.tsx:28-44
Data Flow and Dynamic Fetching
The interface utilizes a hybrid approach to content delivery, combining static route definitions with dynamic fetching from a Supabase backend.
Article Discovery and Routing
The application uses Vite's import.meta.glob to automatically discover wiki page components located in src/pages/wiki/**/*.tsx. These are then mapped to slugs using a slugifyFileName utility and indexed for the ArticleRouter.
This diagram illustrates the sequence of operations required to resolve a dynamic wiki article from the database. Sources: src/App.tsx:53-76, src/hooks/useWikiArticles.ts:98-124
Hook-based Data Retrieval
The interface relies on custom hooks for data fetching, primarily useWikiArticles and useWikiModules. These hooks manage the lifecycle of Supabase queries, including search filtering and status checks.
- useWikiArticles: Implements pagination (
range(from, to)) and full-text search using thespanishconfiguration for thesearch_tsvcolumn. - useWikiArticle: Retrieves a single article based on its module ID and slug, ensuring it is in a "published" status before rendering.
Sources: src/hooks/useWikiArticles.ts:38-65, src/hooks/useWikiArticles.ts:107-118
Core Visual Components
The wiki interface employs a specialized set of UI components designed for high-density technical information. These components are defined in WikiComponents.tsx and used throughout the dynamic pages.
Design Standards
- WikiCard: Used for highlights or warnings, supporting multiple accent colors (
cyan,orange,green,blue,purple). - WikiTable: A standardized data table for summarizing technical specifications and roadmap milestones.
- AuroraBackground: A visual wrapper providing a cyan/indigo blur effect to create a futuristic "Atlas" aesthetic.
The diagram displays the relationship between the layout wrapper and the specialized typography/container components. Sources: src/components/WikiComponents.tsx:5-102, src/pages/wiki/WikiPage.tsx:24-32
Search and Observability
The WikiHome serves as the central "Civilization Stream" console. It provides a real-time view of the "ISNI Pipeline" and "MD-X5 Kernel" status. It aggregates metrics such as the number of indexed repositories (195) and federated nodes (48).
Search Parameters
The search functionality, managed via useWikiArticles, supports:
- Module Filtering: Restricting results to a specific
module_id. - Tag-based Discovery: Filtering by arrays of tags defined in the
wiki_articlestable. - Semantic Search: Utilizing Postgres
textSearchwithwebsearch_to_tsqueryto allow natural language queries.
Sources: src/pages/WikiHome.tsx:64-90, src/hooks/useWikiArticles.ts:60-65
Metadata and Academic Integration
A critical feature of the interface is the integration of persistent identifiers (PIDs). The footer and article views explicitly link to:
- ORCID: Identifying the system's architect (Edwin O. Castillo Trejo).
- Zenodo/DOI: Providing permanent links to technical reports and the "Canon TAMV".
- MSR/BookPI: A ledger-based narrative system mentioned as the underlying audit layer for wiki decisions.
Sources: src/pages/WikiHome.tsx:110-125, src/pages/wiki/referencias/ReferenciasAcademicas.tsx:10-15, src/pages/wiki/modulo-omega/WikiViva.tsx:15-18
The Interactive Wiki Interface functions as the "prefrontal cortex" of TAMV ONLINE, transforming technical documentation into an executable interface for territorial governance and identity management. By combining a rigid constitutional code (QC-TAMV-01) with a dynamic user interface, it ensures that the project's evolution remains traceable, audit-ready, and human-centric.
Sources: src/pages/wiki/modulo-omega/ManifiestoTamv.tsx:20-22, src/pages/wiki/implementacion/CicdPipelines.tsx:14-20