Skip to content

ERP & Intranet — program plan

Guide

ERP & Intranet — program plan

Plan-phase (build deferred, per the Principal). The ERP is the integrated backbone of the company; the intranet is its portal. We are at Plan in the Standard Flow (docs/methodology.md).

What the ERP is (for us)

An integration layer that unifies the company’s resources. It does not rip-and-replace what exists — the sources of truth stay where they are; the ERP indexes and integrates them. MVP modules (per the scoping decision):

Module Integrates Existing basis
Finance & AI-economy money + AI-usage ledgers new — docs/financial-system.md
HR / Workforce agents, units, hiring/onboarding, roster ORG.md, hr/
Records / Archive versioned documents + manifest archive/
Operations hooks, daily cadence, monitoring, runbooks .claude/hooks/, reports/

(Knowledge/Docs and CRM/Stakeholders are later increments.)

Sequence (per decisions)

  1. ERP backbone first — a shared integration model: common entities (agent, unit, venture, document, transaction, event) with stable IDs and provenance, and a definition of where each lives and how they link.
  2. Finance & AI-economy ledger design — docs/financial-system.md.
  3. Intranet portal — a read-only window over the modules.

Backbone design (sketch)

  • Sources of truth stay put (ORG.md, archive/, the ledgers, Notion); the backbone is an index/event layer over them.
  • Events flow to the Archivist (records) and Finance (cost/usage).
  • Stable IDs let modules cross-reference (e.g. a transaction → agent → unit → venture).

Intranet (portal)

  • Surfaces: org chart & roster, daily briefing/report, archive & manifest, budgets & AI-usage, reviews.
  • Lean first: a docs/static portal over the repo + Notion; a real app later.

Built (slice 1, 2026-05-30): a lean static portal under intranet/ (Astro + Tailwind) with four surfaces — Dashboard, Documents, Chatter, People — reading the repo as the source of truth (docs/adr/ADR-0006). Deploying to Vercel behind single-user Vercel Authentication (docs/adr/ADR-0008; runbook docs/sop/SOP-003-deploy-intranet.md) — tag the first-product-slice milestone once the URL is live. Still deferred: a live chatter store, and Knowledge + Access-Requests surfaces.

Build approach

Plan only now. When we build: lean in-repo first (per “tool agents later”); the tech stack / hosting / data store is an open decision for the build gate.

Build-gate checklist (exit Plan → Build)

  • [ ] Backbone integration model (entities, IDs, links) agreed.
  • [ ] Finance ledger schema + cross-rate agreed (docs/financial-system.md).
  • [ ] Intranet wireframe (what it surfaces, read-only).
  • [ ] Tech-stack / hosting decision (or confirmed lean in-repo).
  • [ ] Finance unit stood up (HR hiring) to own the Finance module.