Domus Captures Comprehensive Audit

Executive Summary

This audit evaluates domus-captures as a lifelong knowledge management system designed for Harvard/Aristotle/Plato-level scholarship and sharing with others.

Metric Score Assessment

Overall Health

72%

Strong foundation, critical gaps in navigation scalability

Education Section

68%

Rich content, missing 11 index files for discoverability

Codex Section

85%

Excellent CLI patterns, 2 missing page directories

Case Studies

75%

Good coverage, deployment tracking sparse

Trackers System

90%

Well-architected single source of truth

Navigation

60%

Unsustainable at current growth rate

Target after remediation: 93%

Overall Statistics

Component Count

Total AsciiDoc pages

1,068

Worklogs (2026)

88

Case studies

47

Tracker partials

79

Codex examples

194

Codex pages

77

Navigation xrefs

909

Education categories

16

reMarkable scripts

8

Critical Gaps by Priority

Tier 1: Structure (Foundation)

These gaps affect discoverability and navigation.

# Gap Impact Effort

1

11 education categories missing index.adoc

Users cannot discover content in systems/, training/, programming/, languages/, etc.

2h

2

nav.adoc unsustainable (909 xrefs → 2,500+ by 2028)

Manual maintenance impossible, error-prone

4h

3

2025 historical worklogs missing

Chronicle has gap in history

N/A (may not exist)

4

pages/codex/assembly/ directory missing

6 example files exist but no navigable pages

1h

5

pages/codex/languages/ directory missing

lua.adoc example exists but no page

30m

Tier 2: Content Depth

These gaps affect completeness for a "share with others" system.

# Gap Impact Effort

6

Incident template too minimal (28 lines)

vs 244-line RCA template; incidents need more structure

1h

7

Only 2 deployments documented (vs 30 CRs)

Deployment knowledge not captured

Ongoing

8

Meta trackers defined but unpopulated

strategic-alignment, velocity, skill-synergies empty

2h

9

Infrastructure inventory missing

No hardware/VM tracking in captures

1h

Tier 3: Senior Engineer Coverage

These gaps affect advanced CLI mastery curriculum.

# Gap Impact Effort

10

Kubernetes codex missing

kubectl patterns not documented

3h

11

Terraform/IaC codex missing

Infrastructure as code patterns absent

2h

12

tcpdump/packet analysis missing

Network troubleshooting gaps

2h

13

Package manager patterns sparse

pacman, apt, dnf patterns minimal

1h

Structure Improvements Needed

Missing Education Index Files (11)

The following directories contain content but lack index.adoc landing pages:

# These need index.adoc files:
education/systems/           # terminal-mastery, vim-mastery, regex-mastery
education/training/          # nvim/, jq/, python/, lua/, regex/, tmux/
education/programming/       # python/, go/, rust/
education/languages/         # spanish/, linguistics
education/humanities/        # minimal content
education/sciences/          # minimal content
education/ruby/              # single file
education/music/             # minimal content
education/certifications/    # has 4 cert tracks but no overview
education/infrastructure/    # empty
education/rhcsa/             # has content, needs better index

Missing Codex Page Directories (2)

Directory Examples Exist Action Needed

pages/codex/assembly/

6 files (fundamentals, stack-functions, syscalls-linux, arithmetic-logic, reverse-engineering, x86-64-registers)

Create directory + index.adoc + 6 pages

pages/codex/languages/

1 file (lua.adoc)

Create directory + index.adoc + lua.adoc page

Incomplete Templates

Template Lines Issue

incident-template.adoc

28

Too minimal compared to 244-line RCA template

deployment-template.adoc

N/A

Does not exist

troubleshooting-template.adoc

N/A

Does not exist

Navigation Sustainability Fix

Current Problem

nav.adoc growth projection:
- 2026: 909 xrefs (current)
- 2027: ~1,700 xrefs
- 2028: ~2,500 xrefs
- Maintenance: Manual, error-prone, unsustainable

Proposed Solution: Modular Navigation

// nav.adoc becomes lightweight orchestrator
.Chronicle
include::partial$nav/chronicle-2026.adoc[]
include::partial$nav/chronicle-2025.adoc[]

.Education
include::partial$nav/education.adoc[]

.Codex
include::partial$nav/codex.adoc[]

.Case Studies
include::partial$nav/case-studies.adoc[]

Benefits:

  • Each year’s worklogs in separate partial

  • Sections maintained independently

  • Automated sync scripts become simpler

  • Cognitive load reduced

Recommended Action Plan

Phase 1: Foundation (Week 1)

# Task Time Priority

1.1

Create 5 critical education index files (systems, training, programming, languages, certifications)

2h

P0

1.2

Create pages/codex/assembly/ with index + 6 pages

1.5h

P0

1.3

Create pages/codex/languages/ with index + lua page

30m

P0

1.4

Enhance incident-template.adoc to match RCA quality

1h

P1

1.5

Create deployment-template.adoc

1h

P1

Phase 2: Sustainability (Week 2)

# Task Time Priority

2.1

Implement modular nav.adoc with partials

4h

P0

2.2

Create sync-nav.sh automation script

2h

P1

2.3

Populate meta trackers (strategic-alignment, velocity)

2h

P1

2.4

Create remaining 6 education index files

1.5h

P2

Phase 3: Depth (Weeks 3-4)

# Task Time Priority

3.1

Add Kubernetes codex section

3h

P1

3.2

Add Terraform/IaC codex section

2h

P2

3.3

Add tcpdump/packet analysis to networking codex

2h

P2

3.4

Expand package manager patterns

1h

P3

3.5

Document 10+ historical deployments

5h

P2

Quality Score by Section

Section Current Target Notes

Codex (text processing)

95%

98%

awk, sed, jq, grep excellent; add advanced patterns

Codex (vim)

92%

95%

16 examples, strong; add :global patterns

Codex (PowerShell)

90%

95%

60+ examples across AD, remoting, network

Trackers System

90%

95%

79 partials, well-architected

Case Studies

75%

90%

Good RCA/TAC; sparse deployments

Education (navigation)

70%

90%

Strong curriculum, missing indexes

Education (content)

65%

85%

50+ tracks defined, some empty

Navigation

60%

90%

Unsustainable scaling; needs modular rewrite

Overall

72%

93%

What’s Working Excellently

These sections require no structural changes:

Partials Architecture

The single-source-of-truth tracker system is exemplary:

partials/trackers/
├── work/          # 7 files (adhoc, priorities, itsm-tickets, projects, peoplesoft-codes)
├── personal/      # 6 files (life-admin, infrastructure)
├── education/     # 55 files (certifications, skills, languages)
├── meta/          # 5 files (strategic-alignment, velocity, etc.)
└── operations/    # 1 file

partials/worklog/  # 8 include fragments for daily assembly

Worklog Sustainability

The make new-day template system ensures consistent structure:

= WRKLOG-YYYY-MM-DD
include::partial$worklog/urgent.adoc[]
include::partial$worklog/morning.adoc[]
include::partial$worklog/work-chla.adoc[]
== Session Accomplishments
include::partial$worklog/personal.adoc[]
include::partial$worklog/education.adoc[]
include::partial$worklog/infrastructure.adoc[]

Text Processing Codex

27 example files covering:

  • awk (field extraction, patterns, BEGIN/END, arrays)

  • sed (substitution, addressing, hold buffer)

  • jq (JSON parsing, filtering, k8s patterns)

  • grep (BRE, ERE, PCRE, context)

  • xargs (parallel, batching, null-delimited)

  • regex (BRE/ERE/PCRE comparison, drills)

reMarkable Workbook System

8 generator scripts producing study materials:

scripts/remarkable/
├── generate-regex-mastery-workbook.py     # 110+ pages
├── generate-asciidoc-complete-reference.py # 126+ pages
├── generate-idea-capture-enhanced.py       # 332 pages
├── generate-sed-mastery-workbook.py
├── generate-vim-mastery-workbook.py
├── generate-jq-mastery-workbook.py
├── generate-etl-sessions-workbook.py
└── pdf-template-linked.py

Literature Study (Don Quijote)

126 chapters migrated with proper structure:

education/literature/quijote/
├── index.adoc
├── primera-parte/
│   ├── index.adoc
│   └── capitulo-001.adoc through capitulo-052.adoc
└── segunda-parte/
    ├── index.adoc
    └── capitulo-001.adoc through capitulo-074.adoc

Appendix: File Counts by Category

Education Subdirectories

Directory Files Status

certifications/

4+

cissp, devnet, lpic-1, lpic-2; needs index

humanities/

minimal

Sparse content

infrastructure/

0

Empty

kernel/

3

Strong: mastery, modules, building

languages/

2+

spanish, linguistics; needs index

literature/

130+

Excellent: Don Quijote complete

mathematics/

4+

college-algebra complete

music/

minimal

Sparse content

navigation/

4+

Strong learning aids

programming/

3+

python, go, rust; needs index

rhcsa/

5+

Active study track

ruby/

1

Minimal

sciences/

minimal

Sparse content

systems/

3+

terminal/vim/regex mastery; needs index

training/

40+

nvim, jq, python, lua, regex, tmux; needs index

Codex Coverage

Category Examples Pages Gap

assembly

6

0

Missing pages directory

bash

19+

19

Complete

containers

3

3

Complete

git

6

6

Complete

gopass

5

5

Complete

languages

1

0

Missing pages directory

linux

12

12

Complete

networking

5

5

Add tcpdump

powershell

60+

60+

Complete

python

3

3

Complete

quickref

2

2

Complete

security

4

4

Complete

text

27

27

Complete

vim

16

16

Complete

Decision Points

After reviewing this audit, decide:

  1. Phase 1 Priority: Should we start with the 5 critical education index files?

  2. Navigation Rewrite: Approve modular nav.adoc architecture?

  3. 2025 Gap: Investigate if 2025 worklogs exist elsewhere, or accept gap?

  4. Content Depth: Which Tier 3 items (k8s, terraform, tcpdump) are highest priority?

  5. Timeline: Aggressive (2 weeks) or sustainable (4 weeks)?

Audit conducted: 2026-03-26

Next review: 2026-04-26 (monthly)