January Os Architecture Planner

Workflow

1. Collect authoritative context.

• Read: AGENTS.md, README.md, Makefile, os_cfg.toml.
• Read: kernel/src/main.rs, kernel/src/init.rs, boot/x86_64/src/main.rs.
• Read progress docs: docs/progress/overview.md, docs/progress/v0.2-plan.md.

2. Build current-state map.

• Confirm implemented subsystems from code and init order:
  • Boot handoff
  • Memory
  • Interrupt/APIC
  • ACPI/IOMMU
  • SMP
  • Task/Scheduler/Syscall
  • Drivers
• Mark empty placeholders explicitly (fs, net, security).
• Mark per-architecture readiness explicitly (x86_64, aarch64, riscv64).

3. Produce diagram and staged plan.

• Draw at least one architecture diagram in ASCII.
• Tie plan stages to existing version plan (v0.2, v0.3, ...).
• Keep plan executable with concrete acceptance criteria.
• If any stage uses a minimum-scope implementation, add a matching debt item in docs/progress/tech-debt.md with full-target repayment version and closure criteria.

4. If changes are written to docs/skills, sync site navigation.

• Update docs/.vitepress/config.ts if new docs page added.
• Update docs/guide/skills-info-flow.md if skill inventory changes.

5. Validate minimum signal.

• For docs-only output: run cd docs && pnpm build.
• If build cannot run, report why and what remains unverified.

Constraints

• Prefer repository facts over assumptions.
• Include exact file paths in conclusions.
• Distinguish "already implemented" vs "planned".
• Use the fixed architecture baseline: modular monolithic kernel + componentized OS.
• Keep target architecture baseline explicit: x86_64 + aarch64 + riscv64.
• Include virtualization split: Host/VMM control plane first, guest detection and observability retained.
• Treat every minimum-scope implementation as mandatory technical debt and plan a later-version repayment to full functionality.
• Keep architecture-specific placement rules:
  • boot/<arch>/
  • kernel/src/**/arch/<arch>/
  • kernel/src/virt/platform/<isa>/ (virt subsystem exception)