87bdef64bd
Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
2.1 KiB
2.1 KiB
DOCS — ARCHITECTURE & INTEGRATION DOCUMENTATION
The public docs/ tree now contains only the canonical repository-level docs:
docs/README.md— canonical documentation index and current-state pointerdocs/07-RED-BEAR-OS-IMPLEMENTATION-PLAN.md— canonical public implementation plan
For subsystem deep-dive plans, see local/docs/. The single source of truth for current
desktop/session execution order, claim language, and roadmap is
local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md.
STRUCTURE
docs/
├── README.md # Documentation index
├── AGENTS.md # This file
└── 07-RED-BEAR-OS-IMPLEMENTATION-PLAN.md # Canonical public implementation plan
WHERE TO LOOK
| Question | Document | Key Section |
|---|---|---|
| What is the canonical current implementation plan? | docs/07-RED-BEAR-OS-IMPLEMENTATION-PLAN.md |
Entire document |
| What is the canonical desktop path plan? | local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md |
Entire document |
| What is the current Wayland plan? | local/docs/WAYLAND-IMPLEMENTATION-PLAN.md |
Entire document |
| What is the current DRM/AMD+Intel plan? | local/docs/DRM-MODERNIZATION-EXECUTION-PLAN.md |
Entire document |
| What is the current Wi-Fi architecture and validation path? | local/docs/WIFI-IMPLEMENTATION-PLAN.md |
Entire document |
| What's missing for Wayland? | local/docs/WAYLAND-IMPLEMENTATION-PLAN.md |
Entire document |
| How to fix POSIX gaps in relibc? | local/docs/KERNEL-IPC-CREDENTIAL-PLAN.md |
Implemented credential syscalls |
| What do the main sync/fetch/apply/build scripts actually guarantee? | local/docs/SCRIPT-BEHAVIOR-MATRIX.md |
Entire document |
READING RULE
When a current-state local document conflicts with an older reference, prefer the
console-to-KDE plan and the canonical subsystem plan for that area. Older assessments and
roadmap drafts that refer to historical P0–P6 numbering, "0.1.0" status, or AMD-first platform
priority are obsolete; the project is now on 0.2.3 with AMD and Intel as equal-priority targets.