WikantikDevelopment

---\ncanonical_id: 01KQ0P44YWV8Q0JMN1H2H5EGDX\ncluster: wikantik-development\ntags:\n- development\n- architecture\n- engineering\n- platform\ntype: hub\nstatus: deployed\nsummary: Hub page for Wikantik platform development — architecture decisions, feature implementations, and engineering history\nrelated:\n- ADR-001\n- TestStubConversion\n- ContinuousIntegration\n- HexagonalArchitecture\n- TestDrivenDevelopment\n- UserProfileBio\n- CryptographyFundamentals\n- McpServerCritique2026\n- ObservabilityDesign\n- ConstructorInjection\n- McpIntegration\n- KnowledgeGraphCore\n- JspToReactMigration\n---\n\n# Wikantik Development\n\nThis cluster documents the development history of the Wikantik platform itself — the architecture decisions, feature implementations, and engineering patterns that have shaped the system over time.\n\n## Core Engineering Pillars\n\n- **[Test Driven Development (TDD)](TestDrivenDevelopment):** The mandatory "TDD First" mandate that governs all changes.\n- **[Hexagonal Architecture](HexagonalArchitecture):** How we decouple core wiki logic from infrastructure (Postgres, React).\n- **[Continuous Integration (CI)](ContinuousIntegration):** Automated builds, integration tests, and retrieval-quality benchmarks.\n- **[Cryptography Fundamentals](CryptographyFundamentals):** Standards for password hashing (SHA-256) and API key management.\n\n## Architecture Evolution\n\nWikantik began as a fork of Apache JSPWiki. Through a sustained modernization effort in March–April 2026, the platform was transformed into a modern full-stack application:\n\n- **Frontend**: JSP templates replaced with a React SPA (Vite + React Router)\n- **Storage**: File-based providers augmented with PostgreSQL for users, groups, permissions, and the knowledge graph\n- **Security**: XML policy files migrated to database-backed `policy_grants` table with admin UI\n- **AI Integration**: Two dedicated [MCP Servers](McpIntegration) providing tool surfaces for agents.\n- **Observability**: A full [Observability Stack](ObservabilityDesign) using Prometheus, Loki, and Grafana.\n\n## Key Design Decisions\n\n1. **[ADR-001: Extract Manager Interfaces to API](ADR-001)** — The pivotal decision to decouple MCP modules from the core engine.\n\n2. **Frontmatter as Source of Truth** — Wiki page YAML frontmatter is the canonical source for knowledge graph relationships. See **[Frontmatter Conventions](FrontmatterConventions)**.\n\n3. **[Provenance Model](ProvenanceModel)** — Tracking knowledge origin: `human-authored`, `ai-inferred`, or `ai-reviewed`.\n\n## Feature Timeline\n\n| Date | Feature |\n|------|---------|\n| 2026-03-23 | **[Test Stub Conversion](TestStubConversion)** for decoupled testing |\n| 2026-03-28 | JSP → React SPA migration |\n| 2026-04-03 | **[User Profile Bios](UserProfileBio)** and Attachment management |\n| 2026-04-04 | Knowledge graph core |\n| 2026-05-04 | **[MCP Server Critique](McpServerCritique2026)** and Platform documentation cluster |\n\n## See Also\n- [Wikantik Architecture](WikantikArchitecture) — Detailed module breakdown.\n- [Search and Retrieval](WikantikSearchAndRetrieval) — The hybrid retrieval pipeline.\n- [The Knowledge Graph](WikantikKnowledgeGraph) — Semantic network documentation.\n\n[{Relationships}]\n