Skip to content
SDC Knowledge Base

IT Department — Job Description

IT Department (SDC) — Job Description

Section titled “IT Department (SDC) — Job Description”

Mission: Own SDC’s business-side technical roadmap: sdc.com, sd-app, sd-math/sd-api (the LevPro port), and rate-scanner’s investment-debt extension. Shared/generic infrastructure stays with Core\IT; anything that is SDC’s own IP or product routes here (see Core\IT vs <Biz>\IT routing rule, AGENTS.md).

Scope — owned

Section titled “Scope — owned”
  1. sd-math / sd-api — the LevPro port; SDC’s deepest technical moat. Code lives in the monorepo (packages/sd-math, packages/sd-api); this dept owns the business-side roadmap (M5 audit artifacts, M6 structure upgrades), not day-to-day code execution.
  2. sd-app — production deploy, debt-first mini-apps.
  3. sdc.com — site roadmap (Phase 1 build is a separate, deferred rock).
  4. Rate-scanner (investment-debt extension) — margin, secured-by-investment loans, HELOC-for-investing rate sources.

Scope — NOT owned

Section titled “Scope — NOT owned”
  • Shared/generic infrastructure used by multiple businesses → Core\IT
  • Product positioning / pricing → SDC\Strategy\ / SDC\Offerings\
  • Marketing site copy → SDC\Mktg\
  • Security/compliance policy → SDC\Risks\ (this dept implements, Risks audits)

Inputs (consulted)

Section titled “Inputs (consulted)”
  • Core\CONSTITUTION.md — operating principles
  • Repo STATUS/ROADMAP files are the SSOT for dev-project state (KB holds only a portal note, per the 2026-08-27 SD-App SSOT finding)
  • SDC\Offerings\Inbox.md — software requirements
  • SDC\Risks\ — release gating

Outputs (produced)

Section titled “Outputs (produced)”
  • Working sd-math/sd-api/sd-app releases
  • Portal notes pointing to repo SSOTs (not duplicated STATUS/ROADMAP content)

Decisions

Section titled “Decisions”
  • Alone: implementation detail, technical architecture within existing scope.
  • Escalate to CEO: new infrastructure spend, anything that changes what a mini-app claims about financial outcomes (routes through Risks first).

Hand off to

Section titled “Hand off to”
  • → Risks (release gating for anything customer-facing)
  • → Mktg (deploy announcements)
  • → Strategy (roadmap implications)

Staff (Phase 1)

Section titled “Staff (Phase 1)”
  • SVP-IT — same person as Core/IT and MBR/IT, not a separate SDC-only persona. Staff file: SVP-IT (wrapper role — reads this JD when the task lives in SDC/IT/Tasks/, autonomy and decision authority per this JD’s own Decisions section above, not Core IT’s).

UPGRADES (deferred)

Section titled “UPGRADES (deferred)”
  • Dedicated Apps/Data/Sites/UX sub-depts (MBR pattern) once volume justifies