The substrate
What we run.
Rarefied Earth runs on the same operating substrate it deploys for clients: the modules, the automated roles, and the skills layer underneath. This page is the current state of that system, module by module and role by role.
Every list below is rendered from the machine-readable registries the substrate itself reads, and a daily health run flags this page when it drifts from them. No hand-written marketing copy. Advertised modules are available through Groundwork; dogfood and designed modules are shown honestly as not-yet-ready.
28
Canonical modules
15
Shipping as packaged bundles
12
Automated operating roles
22
Company-authored skills
13
Wired integrations
4
Skills drafted by the factory
Build the Company · module by module
The canonical modules.
Each module is labeled by how it ships today. Packaged means a deployable bundle exists. Deployment playbook means the module installs through a verified per-client procedure until its packaged bundle lands at first deployment.
Foundation
5 modules
Establishes the workspace shape, the agent context cascade, brand, and operator identity a new company runs on.
01
packaged
Cross-Agent Context
Every AI session loads who you are and what the company does in the first few KB of context.
02
packaged
Folder Taxonomy
A numbered folder structure so every artifact has an obvious home from day one.
12
packaged
Brand Starter Kit
A brand starter (palette, type, founder profile) that locks visual and verbal identity.
13
packaged
Operator Protocol
Operator directives that turn the substrate into a running operating protocol.
14
packaged
Agent Charter
An agent charter so the deployed AI behaves like a member of the company.
Voice + Capture
4 modules
Locks outbound tone and turns inbound email into routed, AI-readable engagement records.
03
packaged
Voice Guide
Drafts pass a voice check before they ship, so outbound writing stays on-brand.
04
deployment playbook
Mail Capture
Every inbound email becomes a routed, relationship-tagged, AI-readable record.
11
packaged
Cursor Session-Start Hooks
Session-start hooks that open every workspace with a current briefing.
15
packaged
Freshness Layer
A bounded freshness layer that tells any session what is true right now.
Time + Money
5 modules
Connects work done to money earned, with a data policy and a brand-coherent document pipeline.
05
deployment playbook
Cursor Session Attribution
Cursor work is attributed to the right client by workspace, without manual timers.
06
deployment playbook
Time + Billing Pipeline
Time entries flow to invoices and Stripe through one weekly close command.
09
packaged
Data Management Policy
A seven-tier data policy that bounds the blast radius of any single failure.
16
packaged
Pattern Log
A pattern log that prevents both re-solving problems and premature abstraction.
17
packaged
PDF Pipeline
A pipeline that renders brand-coherent PDFs for invoices, timesheets, and proposals.
Amplifier
5 modules
Adds the high-leverage tooling, skills, and provisioning that make everything underneath faster.
07
packaged
Agent Skills Layer
A user-level agent-skills layer that makes every workspace more productive.
08
packaged
Client Onboarding Runbook + Script
One command provisions a new client workspace, routing, billing, and hooks.
10
deployment playbook
MCP State Server
An MCP server that serves canonical brand, voice, and freshness facts to agents.
18
packaged
Cursor Cloud Agents
Forward-looking cloud-agent wiring, shipped default-off until a deployment needs it.
19
packaged
Shell Conventions
Slug-prefixed shell conventions for the daily-ops command surface.
Growth
5 modules
Turns real work into a synced article, internal tool, and sellable module on a weekly loop, adds invocable reasoning-discipline modes, and verifies each built artifact before it goes live.
32
operational
Product flywheel (research once, harvest three ways)
A weekly loop that turns real work into articles, tools, and sellable modules.
33
dogfood
Reasoning Discipline Pack
An invocable pack of sixteen reasoning and decision-discipline modes (ultrathink, godmode, l99, uda, ooda, skeptic, premortem, tree, falsify, steelman, redteam, persona, eli5, inversion, firstprinciples, pitch) installed as user-level agent skills so any session can tap into deliberate, composable thinking on top of the agent-skills layer.
34
dogfood
Content Publish Pipeline
A one-click publish pipeline that runs an article draft through voice and confidentiality gates, refuses on any unverified claim, and ships it only after a human approves.
35
dogfood
Build Verification
A build-verification layer that proves a freshly built artifact actually works before the system trusts it as live, catching what a structural check can't.
37
dogfood
BD Standing Track (Standing Track)
A reusable business-development learning loop: capture and digest opportunities, accumulate requirement patterns across pursuits, and emit weekly propose-only standing recommendations (certifications, department portals, partner PE gaps).
Maturity
4 modules
Substrate optimization plus the self-awareness layer for deployments 6+ months in: token-burn reduction and context routing, a private thinking vault, meeting-voice capture, and a propose-only weekly reflection loop.
29
operational
Thinking Substrate
A private thinking vault beside the operating workspace: capture half-formed ideas anywhere, promote the keepers into canonical state on a weekly ritual.
30
dogfood
Reflection Loop
The scheduled self-awareness layer: a weekly organizational reflection that reads a fresh self-model snapshot (what the company runs, what changed, what drifted) and emits proposed adaptations as a dated digest plus review tickets.
31
operational
Voice Capture
Call transcripts land beside captured mail in the engagement record, so agents know what was said, not just what was typed.
36
operational
Context Efficiency Layer
Cuts the static context every agent session loads before it does any work. On Rarefied Earth's own substrate the compressed-context rule saves about 14,400 tokens per project session, a 33 percent reduction, while every dollar amount, email address, ticket number, and date is held verbatim in a separate facts layer and verified zero-loss on every distillation.
The automated roles
Who does the running.
The substrate is operated by a roster of automated roles: scheduled jobs, always-on pipelines, a self-awareness layer, and an in-session skills layer. Every role runs behind human gates; drafts and proposals are automated, decisions are not.
01 · Scheduled automation
5 roles
Unattended jobs on a fixed cadence. Each one proposes; none of them publishes, sends, or sells.
mailsweep
scheduled
Sweep every mailbox for inbound the realtime rule missed (Mail closed, push failed, mail moved to Junk).
btc-candidate-scan
scheduled
Weekly scan for Build the Company package candidates, appending to the candidate queue.
flywheel-cycle
scheduled
Run one product-flywheel cycle per week: research a real work item once and harvest it three ways, an article, an internal tool, and a sellable module. Every publish-and-sell gate is held by a human.
substrate-health
scheduled
Run the daily propose-only health battery and catch drift between the module registry, the deployable package, and this page.
bd-digest
scheduled
Daily business-development digest over a trailing lookback window.
02 · Operating pipelines
4 roles
Always-available pipeline roles invoked by the work itself: mail arriving, drafts shipping, weeks closing.
mail capture worker
running
Classify each inbound sender by relationship type and file a relationship-tagged record to the right engagement inbox, with attachments handled and outbound self-copies detected.
Cursor activity scanner
running
Read live Cursor agent-transcripts and attribute compute and AI-tool spend to the right client by workspace path, without sessions needing to end.
voice guard
running
Programmatic, non-bypassable enforcement of the voice rules on every outbound draft (em-dashes, exclamation points, validation lines, softeners, flourish phrases).
PDF / document render pipeline
running
Render markdown sources to brand-locked PDFs (and DOCX/XLSX/PPTX where needed) via pandoc and Chrome-headless for invoices, timesheets, and proposals.
03 · Self-awareness layer
2 roles
The substrate reads its own moving parts and proposes adaptations. Propose-only by design; every structural change routes through a human.
org self-model assembler
running
Read-only assembler of the org's live self-model from existing sources (modules, health, patterns, engagements, system changes, priorities, recent work, candidate queue).
org reflection
shadow
Read the self-model and apply five fixed, falsifiable rules (pattern-ready-no-module, module-unhealthy, convention-violated, priority-drift, flywheel-stall), capped per run, writing a proposed-adaptations digest.
04 · Agent skills
22 company-authored
22 company-authored skill roles run in-session: inbox processing, the weekly billing close, brand and voice compliance, outreach drafting, lead triage, deployment orchestration, ticket filing, productization detection, system-change logging, and verification of work built outside the shell. 4 third-party skill packs add engineering, design, and document-handling methodologies. 4 of the company-authored roles were drafted by the factory below.
05 · The factory
scheduled
The substrate extends itself, behind a human gate.
The factory watches the firm's recurring work for agent-shaped patterns and drafts new skill definitions into a staging area when a pattern proves itself. A human gate approves every activation. The loop runs detect, draft, gate, adapt: candidates accumulate from observed work, one draft per run lands in staging, a human review activates it, and usage telemetry feeds adaptation proposals back into review.
4 of the 22 live company-authored skills arrived this way. Fully autonomous self-extension is a codified anti-pattern here; the factory observes, drafts, and proposes, and a human promotes.
6 further governance roles are specified in the role library but not yet built; they appear here when they ship. The roles above act through 13 wired integrations (work tracking, billing, error tracking, mail and calendar, web research, meeting context), each with its own authority profile and human gates.
The same substrate, deployed into your company.
Build the Company installs this system into a client workspace over a five-phase engagement. Every module ships debugged, because Rarefied Earth is always the first installation.