🔧 Reference

Project Registry — Active Projects, Tools, Automations

1 source Updated Sun Apr 19 2026 19:00:00 GMT-0500 (Central Daylight Time) Internal
business-statereferenceproject-registryregistryprojectsautomations

Summary

Project Registry — Active Projects, Tools, Automations — regenerated from canonical/business-state/project-registry.md. Do not hand-edit this page — update the canonical file and re-project.

Living registry of every active Artemis project, proprietary tool, scheduled automation, and bot. What's running, what's being built, what's queued.

Content

All active projects, proprietary tools, scheduled automations, and bots

Last Updated: April 2026

This document indexes every active workstream in the Artemis ecosystem — Claude projects, proprietary tools, scheduled tasks, automated bots, and recurring processes. Lives in canonical/business-state/project-registry.md in the Venterminator OS vault and is auto-loaded into every Claude session. Updated when workstreams change status or new ones are created.

Source-of-truth relationship to other canonical files:

  • tool-stack-inventory.md — detailed tool status + costs + replacement plan
  • canonical/guides/tools/*.md — per-tool deep briefings (one per proprietary tool)
  • team-mls-ids.md — team roster (29 agents, single source of truth)
  • business-bible.md — strategic narrative; defers to this file for project details
  • roadmap.md — phase structure and sequencing

ACTIVE PROJECTS

Master context — the vault

Venterminator OS (this vault)

  • Status: ACTIVE
  • Purpose: Unified source of truth for business + personal context. Auto-loaded into every Claude session (Web, Code, Desktop). Replaces the old "Master Project in Claude with knowledge files" architecture.
  • Key infrastructure: Obsidian MCP self-hosted at mcp.stoicagents-ops.com (live 2026-04-19), two-tier canonical/working structure, Claude scheduled-tasks for automated maintenance.
  • Owner: Fred
  • Roadmap Lever: ALL

Spoke projects (business)

ARTEMIS — Attraction & HR

  • Status: ACTIVE (reframed 2026-04-20)
  • Purpose: Full agent lifecycle — recruiting, conversion, split package design, onboarding, agent performance reviews, prompt library. Strategy shifted 2026-04-20 from named-target hunts to distributed passive attraction via Prometheus dashboard (Chad Klein leading the pilot).
  • Current state: Jen Schneider onboarded (splits still pending); $20M agent deal killed; Sam VandenBrink passed. No active named-target recruiting conversations.
  • Owner: Fred
  • Roadmap Lever: 1 (Recruit & Retain), 2 (SOP & IP)
  • Notes: Primary output is SOP documentation + agent prompt library + passive-recruit data surface.

Zillow Preferred Coaching Program

  • Status: ACTIVE — Mature
  • Purpose: Agent performance reviews, ZHL conversion metrics, pickup rate coaching, lead distribution management. Weekly zillow-weekly-coaching skill handles the template + sending.
  • Key context: ZHL performance framework, agent roster with ZHL ratings, data updates weekly in canonical/guides/zillow/zillow-flex-health.md.
  • Owner: Fred
  • Roadmap Lever: 1, 3 (Concentration Risk mitigation)
  • Related: upgrade to RealPro Select launching end of April 2026 for expanded connections.

Team Valuation

  • Status: ACTIVE — Quarterly refresh cadence
  • Purpose: Enterprise valuation for estate planning. Tracks EBITDA, multiple, agent roster, financial performance.
  • Key context: Final edition completed Feb 2026 at Financial/Stoic_Agents_Final_Valuation_February_2026.docx. Target: $2.8M–$3.2M at $800K EBITDA x 3.5-4.0x.
  • Owner: Fred
  • Roadmap Lever: ALL (valuation is the output of all 7 levers)
  • Notes: Proprietary tool portfolio (12 tools) is now a material valuation asset — transfers with the team in a sale. Re-score quarterly or on material change.

ARTEMIS — Marketing — Website & SEO

  • Status: IN PROGRESS (promoted from "NOT STARTED" 2026-04-20)
  • Purpose: Build and launch the residential division website (getrealstl.com). Replaces Curaytor + Lofty.
  • Current state: Custom WordPress on SiteGround. Showcase IDX $100/mo install pending, MARIS IDX feed approval received. MVP files scaffolded 2026-03-24 (homepage, 4 listing pages, 10 neighborhood pages). Tier 1 priority, 30-60 day cutover target.
  • Full context: Artemis Website Build/WEBSITE_PROJECT_CONTEXT.md
  • Owner: Fred
  • Roadmap Lever: 1, 3, 5, 7 (Phase 1)

ARTEMIS — Marketing — Content & Paid (Listing Marketing System)

  • Status: IN PROGRESS (promoted from "NOT STARTED" 2026-04-20)
  • Purpose: The automated listing marketing pipeline: Spark → Hermes → Mail → Email → Seller Report → Facebook Ads. Replaces Curaytor end-to-end.
  • Current state: Spark ✅ live. Hermes ~50-60% built, top priority. Mail/Email/Seller Report/Facebook Ads still to build (Phase 2 of roadmap). Meta Ads MCP install pending.
  • Owner: Fred
  • Roadmap Lever: 3, 5, 7 (Phase 1-2)
  • Notes: Top current priority per the 2026-04-20 roadmap rewrite. Hermes production is the blocker for full Curaytor + Lofty sunset.

ARTEMIS — Operations — SOP & Systems

  • Status: NOT STARTED (deferred to Phase 3)
  • Purpose: Document top 10 core processes, build agent training curriculum, DotLoop Business+ unification.
  • Priority: Still a Lever 2 driver — remaining gap for hitting 3.5x valuation multiple.
  • Top 10 SOPs to document first:
    1. New agent onboarding (3-tier structure)
    2. Zillow Flex lead routing and assignment
    3. Listing launch workflow (photos → MLS → marketing cascade)
    4. Buyer lead follow-up sequence (first 48 hours)
    5. Transaction coordination checklist (contract to close)
    6. Agent performance review process (monthly/quarterly)
    7. Recruiting interview and evaluation process
    8. Marketing campaign launch (listing blast + social + paid)
    9. CMA preparation and delivery
    10. Team meeting agenda and accountability tracking
  • Owner: Fred
  • Roadmap Lever: 2, 4, 6 (Phase 3)

Real Legacy Land & Auction

  • Status: ACTIVE
  • Purpose: Land/ag division. Mitch Cain anchor + John Barnak Chicago satellite pod (launches early May 2026).
  • Current state: GAIA land valuation tool live. Orion prospect intelligence live for land. Land domination website planned Phase 3. USDA SSURGO + Regrid integrated via Claude Code skills.
  • Owner: Fred
  • Roadmap Lever: 5 (scale), 6 (non-GCI revenue via title)

Spoke projects (personal)

Volleyball Coaching — Noelle

  • Status: ACTIVE
  • Purpose: Youth volleyball coaching for Noelle (outside hitter, turning 14). Film analysis, serve mechanics, hitting approach.
  • Owner: Fred
  • Roadmap Lever: N/A (personal)

PROPRIETARY TOOLS (12)

These are the tools that make up the Artemis IP moat. Each has its own deep briefing at canonical/guides/tools/<name>.md. For the compact summary of status and costs, see tool-stack-inventory.md.

Tool Role Status Briefing
Spark Listing showcase landing page builder Live spark.md
Lyra Link intelligence — short URLs + pixel + click tracking Live lyra.md
Hermes Social command center — organic distribution ~50-60% built, TOP PRIORITY hermes.md
Athena Buyer portal + offer intelligence Pre-prod beta athena.md
Iris Residential CMA + LENS + ARGUS risk Agent beta iris.md
GAIA Land valuation Live gaia.md
Orion Seller/buyer intelligence + direct mail Live for land, residential pending orion.md
Delphi Closing cost calculator Live delphi.md
Titan Agent income calculator Live titan.md
Olympus Operations wiki (Quartz from this vault) Live olympus.md
Seneca Negotiation coaching bot Live (auto-reads Olympus) seneca.md
Prometheus RMLS/MARIS agent-intelligence dashboard + Courted AI replacement Live prometheus.md

NOTES ON OUT-OF-SCOPE ITEMS

Land Division Website — scoped inside the Real Legacy Land & Auction project. Separate brand, separate audience, separate platform decision from getrealstl.com residential.

DotLoop Business+ unification — scoped inside Operations — SOP & Systems project. Enables centralized transaction reporting + title routing for Lever 6.

RECURRING AUTOMATED TASKS

All automations reflect actual 2026-04-20 reality. "Cowork" recurring tasks are retired — the automation layer is Claude scheduled-tasks + Mac LaunchAgents + cron jobs.

Claude scheduled-tasks (server-side)

Task Cron Purpose Output
rezen-mwf-report Mon/Wed/Fri 7AM CT Pipeline + closed transaction reports Fred's Slack DM
weekly-hybrid-rankings Tuesday 7AM CT MARIS closed + ReZen pending + lead sources agent rankings Fred's Slack DM
milestone-100m-alert Daily 7:15AM CT Fires exactly once when rolling-12 closed volume crosses $100M Fred's Slack DM (Super Team threshold)
infra-health-check Every 30 min Health checks on Prometheus, IRIS, MARIS Fred's Slack DM on any failure
prometheus-nightly-monitor Daily 6:30AM CT Verify Prometheus nightly cron ran Fred's Slack DM on failure
rmls-residential-daily Daily 5AM CT RMLS residential data refresh to MARIS DB (IRIS CMA tool) MARIS PostgreSQL
daily-wiki-ingest-briefing Daily 6AM CT Ingest substantive Slack threads into wiki, regenerate Operations Briefing Wiki + Apple Notes
monthly-listing-title-report 1st of month, 8AM Previous month's listing-side closes by agent + title company Fred's Slack DM

Mac LaunchAgents (local daemons)

Agent Schedule Purpose
com.fred.obsidian Always-on Obsidian REST API daemon (MCP backend)
com.fred.mcp-obsidian-proxy Always-on MCP proxy for Obsidian tunnel
com.fred.tunnel-health Every 15 min Cloudflare tunnel healthcheck
com.fred.morning-briefing 6:30AM daily Regenerates working/briefings/morning-YYYY-MM-DD.md
com.fred.evening-summary 9PM daily Regenerates working/briefings/evening-YYYY-MM-DD.md
com.fred.graduation-brief Friday 7AM Weekly graduation brief to working/briefings/graduation-*.md
com.fred.weekly-stats-draft Sunday 8PM Draft weekly stats
com.fred.vault-autocommit Hourly 9am-11pm Git autocommit of vault changes (if using git)
com.fred.vault-backup Daily Backup the vault
com.fred.conflict-check Hourly Check for Dropbox conflict copies
com.fred.system-health Daily System-level health checks
com.fred.dropbox-absorb 2:30AM daily Scan Dropbox for recently modified files, summarize
com.rezen.daily-reports 7AM daily ~/reports/daily_reports.py — pulls ReZen data, writes snapshots
com.fred.team-roster-watcher On file change Fires when team-mls-ids.md is edited; runs sync in dry-run mode + Slack alerts on drift (new 2026-04-20)

Mac cron jobs

Job Schedule Purpose
rezen_export.py Weekdays 6AM ReZen full data export to JSON
rezen_to_sheets.py Weekdays 6:10AM Sync closed transactions to Google Sheets

Droplet cron jobs

Droplet 192.241.142.56 (MARIS database):

Job Schedule Purpose
MARIS sync (full) 5x daily: 04/10/15/19/23 UTC Pulls from MLS Grid API into PostgreSQL
RMLS sync 3x daily: 10:30/15:30/23:30 UTC Pulls RMLS residential data

Droplet 104.248.13.51 (Prometheus):

Job Schedule Purpose
nightly.py 5AM UTC Snapshot + movement detection + stats recompute + 90-day purge

NEW PROJECT TEMPLATE

When creating any new Artemis workstream, follow this checklist:

Before Creation:

  1. State the project's purpose in one sentence.
  2. Confirm it doesn't overlap with an existing project (check this registry).
  3. Identify which Roadmap Lever(s) it serves and which Phase it belongs to.
  4. Identify dependencies and blockers.
  5. Estimate timeline and owner.
  6. Log the decision to create it in canonical/decisions/decision-log.md.

Project Setup:

  1. Name format: "ARTEMIS — [Domain] — [Specific Focus]" for business work, or follow existing patterns for internal tools.
  2. If it's a proprietary tool: create a briefing at canonical/guides/tools/<name>.md + add row to the Proprietary Tools table above.
  3. If it's a code project: create a folder in Tools/<Name>/ with a deploy.sh, config.py (if applicable), and README.
  4. If it's a content workstream: create a working folder at working/<domain>/<project>/.
  5. Add a detailed row to "Active Projects" in this registry with status, purpose, key context, owner, roadmap lever.

Custom instructions for any Claude context (chat, code, subagent) that operates within the project scope:

You are a specialized assistant for the Artemis team at Real Broker LLC, focused specifically on [DOMAIN AND SCOPE].

The authoritative context lives in the Venterminator OS vault (auto-loaded at session start). Refer to:
- `canonical/business-state/business-bible.md` for strategic framing
- `canonical/business-state/project-registry.md` (this file) for project context
- `canonical/business-state/tool-stack-inventory.md` for tool status and costs
- `canonical/guides/tools/<tool>.md` for per-tool deep briefings
- `canonical/decisions/decision-log.md` for prior decisions

Your specific role: [DESCRIBE WHAT THIS PROJECT DOES AND DOESN'T DO]

Context you should know: [KEY BUSINESS CONTEXT SPECIFIC TO THIS PROJECT]

Communication style: Direct, no fluff, plain English. Lead with the answer, then explain if asked. Follow Write Like Fred v4 (`canonical/brand/write-like-fred-v4.md`).

When producing deliverables, save them to the appropriate `working/` path per `_system/routing-rules.md`. For branded materials, always follow Real Broker brand standards (Cobalt #050E3D, Coral #FF557E, Seaglass #BFDDDB, Telegraf headings, Inter body).

After Creation:

  1. Add a one-line entry to canonical/decisions/decision-log.md: **YYYY-MM-DD** — Created [project] to [purpose] — [rationale].
  2. If the project produces recurring outputs, register as a Claude scheduled-task via the scheduled-tasks MCP (or create a LaunchAgent for Mac-local automations).
  3. Update this registry's Active Projects section.

PROJECT HEALTH EVALUATION FRAMEWORK

Run this evaluation quarterly for each active workstream:

  1. RELEVANCE: Does this project still serve an active need? Is it aligned with the current Roadmap phase?
  2. CONTEXT: Does it have enough vault-referenced context to make good decisions? Is that context current?
  3. SCOPE: Is the scope clear? Does it overlap with another project? Has scope crept?
  4. INSTRUCTIONS: Are per-context custom instructions specific enough? Do they reference the current vault architecture?
  5. OUTPUTS: Are deliverables flowing to the correct working/ paths? Can other Claude sessions access what they need?
  6. MAINTENANCE: When was the associated vault content last updated? Is it stale?

Score each 1-5. Any project scoring below 3 on two or more dimensions needs immediate attention.

RETIRED / SUPERSEDED WORKSTREAMS

Historical — kept for context when working with older docs or running historical queries.

Retired When Why Superseded by
Curaytor Blast Workflow In progress 2026-04-20 Being sunset Spark + Hermes + new website + (forthcoming) Mail/Email/Seller Report tools
Google Drive "Artemis Command Center" folder 2026-04-19 Vault replaced it as source of truth Venterminator OS vault
"Master Project in Claude with 3 knowledge files" 2026-04-19 Vault auto-loads into every session Venterminator OS vault canonical/ tree
Cowork recurring tasks 2026-04-19 Cowork paused Claude scheduled-tasks MCP + Mac LaunchAgents + droplet cron
Weekly-VA-updates-to-Master-Project model 2026-04-19 VA redeployed; vault canonical structure + automated absorb + graduation brief now handles the cadence Daily/weekly LaunchAgents
$15M solo agent recruiting (Jen Schneider) 2026-04-20 Onboarded (not via original sequence); treated as regular team member n/a
$20M agent recruiting 2026-04-20 Deal killed Distributed passive recruiting via Prometheus (Chad Klein pilot)
Sam VandenBrink recruiting target 2026-04-20 Passed on opportunity Now a competitive target
today.md priority file 2026-04-20 Never auto-refreshed — became permanently stale Morning briefing (working/briefings/morning-YYYY-MM-DD.md, auto-generated daily at 06:30)
rezen_bridge.py (Cowork-era) 2026-04-20 Not in production ~/reports/daily_reports.py (Mac) + ~/Claude Programs/rezen/rezen_export.py
Dead Slack webhook B0AKHV9G43H 2026-04-20 Silently failing for 38 days Seneca bot token (OAuth, stable) for all automated Slack delivery