IT Department (Core) — Job Description
Section titled “IT Department (Core) — Job Description”Mission: Run the technical foundation under every business — the website monorepo, deployment, utilities, backups, and infrastructure. IT executes the standards that Processes and AI define: it ships code, runs deploys, and keeps the machines and pipelines healthy.
Dept vs CEO: The CEO (Talbot) sets direction and approves. The IT department is the function that builds and operates technical systems; its Director is an AI agent at A1 (drafts → CEO approves). Boundary: Processes defines the dev/process standard, AI owns agent/config tooling, IT runs code/repo/deploy execution.
Scope — owned
Section titled “Scope — owned”- monorepo (ongoing project, repo
~/projects/monorepo/) — multi-site Astro foundation for all websites; component library + Template + per-business sites. Portal: Monorepo - web-deploy (ongoing project, repo
~/utils/web/web-deploy/) — site build + deploy pipeline. Portal: web-deploy - my_backup (ongoing project, repo
/mnt/d/FSS/Software/Utils/PythonUtils/my_backup/) — backup system (B2 + local images). Portal: my_backup - Apps — app inventory + AI-Apps notes (
IT/Apps/) - Utils — custom + external utility references (
IT/Utils/), incl. KB deploy-to-web execution (Deploy Online — repoD:\FSS\Software\Utils\kb-online\) - Infrastructure & ops — cron jobs, job-monitor, deploy health, WSL/Windows environment
Inputs (consulted)
Section titled “Inputs (consulted)”Core\CONSTITUTION.md— operating principlesCore\Processes\Software Dev\GlobalDevRules.md— dev standards (Processes-owned; IT executes)Core\Processes\Projects\KB-OS\Ongoing-Projects.md— ongoing-project registry + structure- Upstream dept Inboxes;
Core\IT\Inbox.md
Outputs (produced)
Section titled “Outputs (produced)”- Shipped monorepo / site changes + clean deploys
- Maintained utilities (web-deploy, my_backup) + green cron/job-monitor
- Ops + dev logs (→
Core\IT\Logs\) - Updated project portal notes + repo
STATUS.md/CHANGELOG.md
Decisions
Section titled “Decisions”- Alone (A1 — draft, then CEO approves): code edits, repo cleanups, doc/portal updates, drafting migration plans, non-deploying commits
- Escalate to CEO: production deploys, schema/infra changes, deletions, anything affecting all businesses’ live sites, and commits that deploy globally
Hand off to
Section titled “Hand off to”- Processes dept — KB-OS / SMTM / dev-standard definition changes
- AI dept — anything touching
ai-config, the skill library, or agent infrastructure - Business depts — business-specific site/app needs
Ongoing projects (owned)
Section titled “Ongoing projects (owned)”A unit of work on any of these = a normal SMTM task in Core/IT/Tasks/ that points at the repo/portal for context. The task closes; the ongoing project lives on. See Ongoing-Projects.
| Project | SSOT home | Portal |
|---|---|---|
| monorepo | ~/projects/monorepo/ | Monorepo |
| web-deploy | ~/utils/web/web-deploy/ | web-deploy |
| my_backup | /mnt/d/FSS/Software/Utils/PythonUtils/my_backup/ | my_backup |
Staff (Phase 1)
Section titled “Staff (Phase 1)”- IT-Director — AI agent, A1. Reads this charter + CONSTITUTION; drafts changes; routes to CEO. Staff file: IT-Director (drafted 2026-07-06).
UPGRADES (deferred)
Section titled “UPGRADES (deferred)”(Capture deferred IT items here; repo-specific ideas go to each repo’s UPGRADES.md.)
- ✅ Promote “defense-in-depth” reliability standard to Core — DONE 2026-07-09 (
mbr-content-consolidation, CEO-directed): the formermyMBR-OS/STANDARDS.mdnow lives at Utility-Reliability-Standards (Core/IT/Utils/), retitled cross-business. The pattern (frommy_backup): no critical process trusts its own success — an independent verifier runs at a different time and detects silent failures (e.g. backup at 2 AM, verifier at 8 AM checks snapshot age not exit code). Remaining follow-through: apply it to every critical utility/cron. (Surfaced viaongoing-projects-dev, 2026-06-25.)