Skip to content
FSS Knowledge Base

Processes Department (Core) — Job Description

Section titled “Processes Department (Core) — Job Description”

Mission: Own cross-business processes: KB-OS (the knowledge-base operating system), the SMTM task/project/log system, software-dev standards, naming conventions, and the capture-routing protocol. Keep the system Talbot uses to run every business simple, robust, and tool-independent.

Dept vs CEO: The CEO (Talbot) sets direction and holds decision authority across all businesses. The Processes department is a function — the machinery that keeps KB-OS and the dev/process standards coherent. Its Director is an AI agent operating at A1 (drafts → CEO approves). The CEO oversees this dept exactly as every other dept; it is not the CEO role itself.

Scope — owned

Section titled “Scope — owned”
  • KB-OS — vault structure, folder-note system, templates, vault health/audits (deploy-online process execution moved to IT — see IT scope below)
  • SMTM — the task/project/log system (SMTM_System.md is the SSOT); versioning and skill alignment
  • Ongoing-project workflow — the standard for evergreen/maintained projects (model defined in Core/AI/Logs/2026-06-15_Ongoing-Projects-Structure.md, formalized in Core/Processes/Projects/KB-OS/Ongoing-Projects.md and Core/Processes/Projects/KB-OS/ROADMAP.md)
  • Software-dev standards — GlobalDevRules.md, Tech Stack.md, web-dev standards (SSOT in Software Dev/ + Website Dev/)
  • Naming conventions — Naming System.md
  • Capture-routing protocol — Core/Processes/Capture-Routing.md (authored 2026-07-09; consolidates the former Core/Ideas-Workflow.md)
  • Process governance — when a process is documented, reviewed, or retired

Inputs (consulted)

Section titled “Inputs (consulted)”
  • Core\CONSTITUTION.md — operating principles (simplification-first, SSOT, borrow > build)
  • Upstream dept Inboxes — process pain surfaced by other depts
  • Core\Processes\Inbox.md — own capture queue

Outputs (produced)

Section titled “Outputs (produced)”
  • Process docs + templates (SSOT under Core\Processes\)
  • SMTM version updates + aligned skills
  • KB-OS structural decisions, migration plans, and audit logs (→ Core\Processes\Logs\ or Core\Logs\System\)
  • Routing rules and naming standards

Decisions

Section titled “Decisions”
  • Alone (A1 — draft, then CEO approves): process-doc edits, template updates, folder-note conventions, non-structural cleanups, drafting migration plans
  • Escalate to CEO: vault restructures, SMTM version bumps, deletions, anything spanning multiple businesses’ folders, and any commit during a restructure (CONSTITUTION hard rule #2)

Hand off to

Section titled “Hand off to”
  • AI dept — anything touching ai-config, the skill library, or agent infrastructure
  • IT dept — code/repo/deploy execution (Processes defines the standard; IT runs it)
  • Business depts — business-specific process needs surfaced back to the owning dept

Staff (Phase 1)

Section titled “Staff (Phase 1)”
  • Processes-Director — AI agent, A1. Reads this charter + CONSTITUTION + the relevant SSOT doc; drafts changes; routes to CEO for approval. Staff file: Processes-Director (drafted 2026-07-06).

UPGRADES (deferred)

Section titled “UPGRADES (deferred)”

(Capture deferred items here; promote to Core\Processes\Projects\KB-OS\UPGRADES.md when concrete.)