Wikantik is an agent-grade technical knowledge platform — engineered simultaneously for human deep reading and native AI agent retrieval, graph traversal, and software engineering coordination. Every page is stored as structured Markdown with validated YAML frontmatter, rename-safe ULIDs (canonical_id), and explicit cluster declarations.

Core Platform Capabilities

Software Engineering & Multi-Agent Development Workflows

Beyond serving as a reference library, Wikantik acts as the active architectural control plane for ongoing software development across multiple repositories (Simple Agility Stack Hub):

  1. Tiered Session-Start Briefings (get_briefing / SA-13): Rather than relying on static repo-local prompt files that silently drift out of date, coding agents start every session by calling get_briefing(clusters=["<project>"], prompt="<task>") (Project Context Separation Design). The wiki dynamically assembles three tiers of context: the project's core architecture pages (ranked by intra-cluster in-degree), the cross-project contracts that project cites (Architectural Decision Log, Telemetry Contract, Agent Coordination), and task-matched sections — while isolating operational incident runbooks from standing coding context.
  2. Design-First RFCs & Cross-Repository Contract Propagation: System designs (type: design), RFCs, and cross-repo API/telemetry contracts live in the wiki as versioned, link-verified specifications (Context Engineering for Coding Agents). When a shared contract is updated, every downstream repository whose Hub cites that contract automatically receives the updated specification on its next session briefing.
  3. Scenario-Keyed Engineering & Incident Runbooks (type: runbook): Recurring engineering playbooks — exploring module API surfaces, running parallel integration test reactors, planning schema migrations, or triaging production alerts — are encoded as structured runbooks (when_to_use, steps, pitfalls) in the Agent Cookbook and infrastructure hubs (Home Lab Infrastructure Hub), ready for on-demand agent execution.
  4. Living Documentation & Verification Loops: As code changes land or incidents are resolved, coding agents update the corresponding architecture pages and runbooks in the same workflow (update_page → verify_pages → mark_page_verified), keeping design documentation, Knowledge Graph entities, and production implementation continuously aligned (Agentic Coding Hub).

New here? Start with About for the platform manifesto, the Wikantik Platform Hub for system internals, the Agent Cookbook for operational agent runbooks, or the Simple Agility Stack Hub for cross-project engineering workflows. You can also read the site blog.

Article Clusters

Wikantik Platform, Agent Workflows & Architecture

Agentic AI, Foundation Models & Machine Learning

Software Architecture, Distributed Systems & Computer Science

Cloud, DevOps, Security, Data Engineering & Infrastructure

Mathematics, Operations Research & Applied Engineering

Personal Finance, Investing & Geopolitics