KB-OS — Portal
Section titled “KB-OS — Portal”KB-native ongoing project — the vault itself is the artifact, so this folder note is both the project’s home and its portal. Owner dept: Processes (Processes Job Description). Registry: Ongoing-Projects.
DASHBOARD.mdis reserved for elevated hubs (vault/business roots, Ongoing-Project homes, dept indexes) — this file serves double duty as both. See Folder Notes for when an ordinary Folder Note is the right call instead.
What it is
Section titled “What it is”The vault’s own operating system: folder-note conventions, the SMTM task/project/log system, templates, dept structure, and vault health/audits. The deploy-to-web pipeline itself is owned by IT — see Deploy Online.
Core docs (this folder)
Section titled “Core docs (this folder)”| Doc | Purpose |
|---|---|
STATUS.md | Live state |
ROADMAP.md | Long-term plan |
UPGRADES.md | Deferred ideas backlog |
LESSONS.md | Gotchas / history |
KB-OS-Context.md | How KB-OS supplies context to agents & humans — the tool/structure map (SMTM · qmd · graphify · CodeGraph · auto-capture); memory is its core subsystem |
KB-OS-Usage.md | Reference: vault layout, conventions, Bases syntax gotchas |
Folder Notes.md | Folder-note conventions |
Ongoing-Projects.md | Registry of all ongoing projects (KB-OS is one of them) |
Agent-Team.md | AI agent team roster — dept charters, staff files, autonomy levels |
Tasks/ | KB-OS’s own SMTM tasks (self-contained — see below) |
Templates/ | SMTM task/project templates |
Working on it
Section titled “Working on it”A unit of work = an SMTM task in this folder’s own Tasks/ subfolder (Core/Processes/Projects/KB-OS/Tasks/) — self-contained, since KB-native means the folder is the project. (Repo-backed Ongoing Projects, e.g. monorepo, still file tasks in their dept’s flat Core/<Dept>/Tasks/ — see Ongoing-Projects for the split.)
Related
Section titled “Related”- Ongoing-Projects — full registry of ongoing projects
- Processes Job Description