← Development · Systems

System orbit

Everything in the Systems inventory on rings around the TIIS core: outside systems, pages, edge functions, cron jobs and Zaps, scheduled tasks and skills, then files. The lines are the data flows. When a cron job runs, its node ripples and a pulse travels to what it touches. Click anything for the detail.

Glossarythe words on this page, in plain terms

TIIS, the Hub: The firm's internal app at leads.tituscpa.com: Lead Tracker, Relationship Management, Time & Billing and the modules around them. It is the system of record for time, WIP and relationship detail. The gold sun in the middle of the map is its database.
TaxDome: The client portal, workflow, invoicing and payments system: the firm's cash register. The Hub reads it through the TaxDome API and writes back only after a person approves the change.
UltraTax: The firm's tax software, where returns are prepared. It stays separate from the Hub.
WIP: Work in progress: time that has been logged but not yet billed. The Hub tracks it; the invoice itself is raised in TaxDome.
Supabase: The service that hosts the Hub's database, sign-in, file storage, edge functions and cron jobs.
RLS (row-level security): Rules inside the database that decide which rows each signed-in person may read or change. It is the real lock: the key in the page source is public by design.
Edge function: A small program that runs on Supabase's servers when something calls it: a page, a cron job, Zapier or an incoming email. It can hold secrets a web page must never see.
Cron job: A timer inside the database (pg_cron) that starts a task on a schedule, such as every minute or Mondays at 7am. Schedules are kept in UTC, so after 11/1 a job set for 7am Central runs at 6am Central.
Claude scheduled task: A Claude session that starts on a schedule to do one job, such as processing Hub notes. The weekday Systems inventory refresh records its last run in the register.
Skill: Saved instructions Claude follows for one kind of work, such as the build queue or the review board. Small moons around a skill or task are the helper agents it launches.
Zap: An automation in Zapier. Zaps pass TaxDome events to the Hub (new accounts and contacts) and Hub actions to TaxDome (a won lead, an approved account update).
Data flow (F-number): A route data takes between systems, numbered F01, F02 and so on; a number is never reused. The lines on the map are data flows; dashed ones are not live yet.
Poll: A scheduled read of another system that brings its changes into the Hub, for example taxdome-poll reading TaxDome accounts and contacts.
Heartbeat: A sign that something is still running. Edge functions write one small row per call (name, status and time, no content, kept 14 days; D-275). On this page an every-minute cron job, such as the CAS runner tick, is counted as a heartbeat: if its count drops, something stopped.
Restore point: A copy of a table saved in the restore_points part of the database before a bulk change, so the change can be reversed.
TD snapshot: td-snapshot: a read-only backup of every TaxDome account (name, type, tags, custom fields) into a restore point. It is taken before a batch push to TaxDome. Admins only.
CAS runner tick: The every-minute timer (cas-runner-tick) that starts the Bookkeeping runner, so waiting Bookkeeping steps keep moving.
MMM, MMM apply: The Monday Morning Meeting. Its Plaud recording becomes cards the partners approve; MMM apply (mmm-apply) then sends the approved changes to TaxDome and the Hub. With its live switch off, Send is a dry run.
Plaud: Sam's voice recorder. A code on the first line of each emailed summary routes it: MMM-TIIS to the Monday meeting, HUB-TIIS to Hub notes, CLIENT-TIIS to the Context inbox.
§7216 consent: Section 7216 of the tax code: a client's tax-return information, even their name, goes to an AI provider only with that client's signed consent. The Hub's consent list is the master (D-288). Until a client has signed, using its data with AI is open risk R24, and no new AI use of client data starts without a partner's OK (D-287).
G0 check: The Bookkeeping runner's check, on every write, that the client has an active AI consent.
SB Test accounts: TaxDome accounts kept for testing. When a switch is set to test, changes reach only these.
The register: The Development register (dev_docs): one table holding every item, decision, rule, risk and change-log line. This map is drawn from it, and Claude reads it before every session.
Retired: Things the register marks done, retired, superseded or historical. They are hidden from the map until you press Show retired.