Roadmap: Knowledge Base Migration

1. Overview

This roadmap defines the strategic migration of existing knowledge bases to the Domus Digitalis Antora documentation ecosystem:

  • Principia/02_Assets/ARS-*: 78 domains, 434 curated files - canonical command reference

  • Aethelred-Codex: 2,679 markdown files - archived reference (ported to ARS-*)

  • Doctrina: 3,153 files - Zettelkasten methodology

  • Sapientia: Reference and wisdom archive

  • PRJ-ANTORA-PRINCIPALIS: Template and standards reference

The canonical source is Principia/02_Assets/ARS-* - the curated, categorized command arsenal ported from Aethelred-Codex. This is not a bulk conversion but strategic extraction of high-value content into purpose-built Antora components.

2. Migration Philosophy

direction: right

source: "Principia/02_Assets/ARS-*" {
  shape: rectangle
  style.fill: "#313244"
  style.stroke: "#cba6f7"

  domains: "78 Domains\n434 Files" {
    shape: rectangle
    style.fill: "#45475a"
  }

  traits: |md
    - Curated command refs
    - Categorized taxonomy
    - Ported from Codex
  | {
    shape: text
    style.font-size: 12
  }
}

target: "domus-command-arsenal" {
  shape: rectangle
  style.fill: "#313244"
  style.stroke: "#a6e3a1"

  output: "Antora Component" {
    shape: rectangle
    style.fill: "#45475a"
  }

  traits: |md
    - Polished AsciiDoc
    - Versioned & searchable
    - Cross-linked xrefs
  | {
    shape: text
    style.font-size: 12
  }
}

source -> target: "pandoc + polish" {
  style.stroke: "#f9e2af"
  style.stroke-width: 2
}

workflow: "Migration Workflow" {
  shape: rectangle
  style.fill: "#1e1e2e"
  style.stroke: "#89b4fa"

  s1: "1. Author in Obsidian"
  s2: "2. Identify ready content"
  s3: "3. Convert to AsciiDoc"
  s4: "4. Publish to Antora"
  s5: "5. Archive source"

  s1 -> s2 -> s3 -> s4 -> s5
}

Key Principle: Obsidian remains the authoring environment; Antora becomes the publishing environment.

3. Current Source Systems

System Files Format High-Value Content

Principia/02_Assets/ARS-*

434

Markdown + YAML

CANONICAL SOURCE - 78 domains: Network, Security, DevTools, Containers, Cloud, Database, SIEM

Aethelred-Codex

2,679

Markdown + YAML

Archived reference (content ported to ARS-*)

Principia (other)

~2,600

Markdown + YAML

OPS-* runbooks, PRJ-* project docs

Doctrina

3,153

Markdown + YAML

Zettelkasten notes, learning materials, technical disciplines

Sapientia

~2,000

Markdown

Reference materials, wisdom collection

PRJ-ANTORA-PRINCIPALIS

40 pages

AsciiDoc

Antora standards, templates, theme examples

4. Target Antora Components

4.1. Existing (Expand)

Component Current Pages Migration Target

domus-infra-ops

68

+20 runbooks from Codex OPS-*

domus-linux-ops

128

+50 commands from Codex ARS-DEVTOOLS-*

domus-python

21

+30 patterns from Codex automation scripts

domus-ise-ops

62

+15 ISE procedures from Codex

4.2. New Components (Create)

Component Purpose Source Content

domus-command-arsenal

78-domain command reference (434 files)

Principia/02_Assets/ARS-* (canonical source)

domus-automation-ops

Network automation, Nornir, Ansible

ARS-AUTOMATION-*, ARS-NETWORK-AUTOMATION

domus-container-ops

Kubernetes, Docker, security

ARS-CONTAINERS-, ARS-INFRASTRUCTURE-

domus-captures

Work chronicles, meeting notes

Already Antora-ready, added to playbook ✓

5. Phase 1: Quick Wins - Ready Components

5.1. Objectives

  • Add domus-captures to aggregator (already Antora-ready)

  • Verify domus-gabriel-docs integration (if desired)

  • Extract PRJ-ANTORA-PRINCIPALIS standards

5.2. Tasks

# Task Priority

1.1

Add domus-captures to antora-playbook.yml

HIGH

1.2

Add domus-captures to antora-playbook-local.yml

HIGH

1.3

Add domus-captures to antora-playbook-ci.yml

HIGH

1.4

Review PRJ-ANTORA-PRINCIPALIS for reusable patterns

MEDIUM

1.5

Decision: Include domus-gabriel-docs in public aggregator?

MEDIUM

1.6

Update CLAUDE.md with new component

HIGH

5.3. Success Criteria

  • domus-captures visible at docs.domusdigitalis.dev

  • Work chronicles searchable via Lunr

  • Navigation includes captures component

6. Phase 2: Command Arsenal Migration

6.1. Objectives

  • Create domus-command-arsenal repository

  • Migrate highest-value command domains

  • Establish AsciiDoc conversion workflow

6.2. ARS Domain Taxonomy (78 Total)

Domain Category Sub-domains Priority

ARS-NETWORK (12)

Automation, Cloud, Core, Load Balancers, Routing, Security, SSH, Switching, Troubleshooting, VPN, Wireless

HIGH

ARS-SECURITY (5)

Code Security, Encryption, Identity, Scanning + base

HIGH

ARS-DEVTOOLS (12)

Algorithms, Android, API, Bash, C++, JavaScript, LaTeX, Lua, Neovim, Python, Text Processing + base

HIGH

ARS-DATABASE (6)

Kafka, MongoDB, MySQL, PostgreSQL, Redis + base

MEDIUM

ARS-CONTAINERS (3)

Docker, Kubernetes + base

MEDIUM

ARS-CLOUD (3)

AWS, Azure + base

MEDIUM

ARS-AUTOMATION (4)

ArgoCD, GitHub Actions, Jenkins + base

MEDIUM

ARS-INFRASTRUCTURE (4)

Ansible, CloudFormation, Terraform + base

MEDIUM

ARS-OBSERVABILITY (4)

ELK Stack, Grafana, Prometheus + base

MEDIUM

ARS-AIML (3)

LLM, MLOps + base

LOW

ARS-SIEM (2)

QRadar, Sentinel

MEDIUM

ARS-DAILY (5)

Critical Incidents, File Management, Health Checks, Quick Fixes + base

HIGH

Other (15)

GIT, ISE, LINUX, MEDIA, NETAPI, HARDWARE, FIREWALLS, SYSADMIN, WINDOWS, ASCIIDOC, IMAGE-ANALYSIS, MULTIPLATFORM

VARIES

6.3. Conversion Workflow

# 1. Convert markdown to AsciiDoc
pandoc -f markdown -t asciidoc -o output.adoc input.md

# 2. Fix common conversion issues
# - Code blocks: ```bash → [source,bash]
# - Links: [text](url) → link:url[text]
# - Headers: # → =
# - YAML frontmatter → AsciiDoc attributes

# 3. Add Antora structure
# - :navtitle:, :description:, :keywords:
# - Cross-references (xref:)
# - Includes for code examples

# 4. Review and polish
# - Verify code blocks render correctly
# - Add callouts for important notes
# - Cross-link related content

6.4. Tasks

# Task Priority

2.1

Create domus-command-arsenal repository structure

HIGH

2.2

Convert ARS-NETWORK-* (12 sub-domains, ~50 files)

HIGH

2.3

Convert ARS-SECURITY-* (5 sub-domains, ~30 files)

HIGH

2.4

Convert ARS-DEVTOOLS-* (12 sub-domains, ~80 files)

HIGH

2.5

Convert ARS-DAILY-* (5 sub-domains, ~25 files)

MEDIUM

2.6

Add to Antora playbooks (all three)

HIGH

6.5. Success Criteria

  • domus-command-arsenal with 200+ pages

  • Searchable command reference online

  • Cross-links to related domus-* components

7. Phase 3: Runbook Expansion

7.1. Objectives

  • Extract ARS-* runbooks to appropriate domus-* components

  • Standardize runbook format

  • Ensure copy-paste ready commands

7.2. Runbooks to Migrate (from ARS-*)

Source Content Target

ARS-FIREWALLS

VyOS HA deployment (migrated from pfSense 2026-03-07), zone policies

domus-infra-ops

ARS-LINUX

Arch Linux deployment, system admin

domus-linux-ops

ARS-SYSADMIN

Backup procedures, maintenance tasks

domus-infra-ops

ARS-NETWORK-SSH

SSH hardening, key management

domus-secrets-ops

ARS-ISE

ISE daily checks, deployment procedures

domus-ise-ops

7.3. Tasks

# Task Priority

3.1

Audit ARS-SYSADMIN for runbook candidates

MEDIUM

3.2

Convert ARS-FIREWALLS content to runbooks

MEDIUM

3.3

Convert ARS-LINUX to domus-linux-ops

MEDIUM

3.4

Merge ARS-ISE content into domus-ise-ops

LOW

8. Phase 4: Learning Content Curation

8.1. Objectives

  • Identify Lyceum content worth publishing

  • Create learning path documentation

  • Link to external certification resources

8.2. Lyceum Content Areas

Discipline Content Action

Programming Languages

Python, Go, Rust patterns

Extract to domus-python

Networking

CCNA/CCNP study materials

Reference, don’t migrate

Cybersecurity

ISE Zero Trust framework

Migrate to domus-ise-ops

Cloud Computing

AWS/Azure patterns

Extract to domus-automation-ops

8.3. Tasks

# Task Priority

4.1

Review Lyceum for publication-ready content

LOW

4.2

Extract security frameworks to domus-ise-ops

MEDIUM

4.3

Create certification study path guides

LOW

9. Phase 5: Template Adoption

9.1. PRJ-TEMPLATE-MULTI Features to Adopt

The Principia-Labor PRJ-TEMPLATE-MULTI offers:

  • 4 rendering engines (Antora, Asciidoctor, Quarto, Typst)

  • 5 output formats (HTML, PDF, EPUB, DOCX, standalone)

  • Dark/Light/Catppuccin themes

  • Diagram-as-code (D2, Mermaid, PlantUML)

  • CI/CD ready (GitHub Actions, GitLab CI)

9.2. Tasks

# Task Priority

5.1

Review PRJ-TEMPLATE-MULTI CI/CD patterns

LOW

5.2

Adopt PDF generation for domus-docs

LOW

5.3

Standardize diagram tooling (D2 + Mermaid)

LOW

10. Migration Metrics

Metric Current Target

Total Antora pages

490 (11 components)

900+ (14+ components)

ARS-* source files

434 (78 domains)

Convert 80% to AsciiDoc

Command reference pages

~50 (scattered)

350+ (centralized in domus-command-arsenal)

Runbook coverage

22 (infra-ops)

75+ (across components)

Searchable content

490 pages

900+ pages

11. Work Applicability

This migration enables:

  • Knowledge Capture: Move from personal vaults to shared documentation

  • Onboarding: New team members can search and learn

  • Standardization: Consistent format across all documentation

  • Publishing: Professional web presence at docs.domusdigitalis.dev

  • Scale: Foundation for enterprise documentation practices

Migration patterns apply directly to work knowledge management.

12. Related Documentation

13. Revision History

Date Author Changes

2026-02-11

EvanusModestus

Updated canonical source to Principia/02_Assets/ARS-* (78 domains, 434 files); clarified Aethelred-Codex as archived reference

2026-02-11

EvanusModestus

Initial roadmap from source system analysis