// trackingtogether · automation agency · 2026-05-23

Track everything.
Automate everything.

TrackingTogether is Anthony's automation-agency brand. Every operation — owned ventures, client work, agent routing, deliverables — lives under a single pane of glass. Eli executes against the whole scope.
brand TrackingTogether stake qi sole-prop · 50/50 Anthony venture-revenue agent Eli canon single pane of glass
// scope split · owned vs clients

Two operational lanes, one umbrella

Every project under TrackingTogether is either an Anthony-owned venture (equity + IP retained) or a client engagement (TT runs automations FOR the client, IP belongs to the client). The folder tree enforces the boundary.

owned_/ · equity + IP

Anthony-owned ventures

  • net_meter_/
  • pfc_farms_/
  • _holdings_-private_/
  • ixl_/ (paired with Net Meter)
Internal R&D, equity, brand assets retained.
clients_/ · service + deliverables

Client engagements

  • acme_/ + auto-vendor list
  • culligan_/ list
  • (continued as intake completes)
TT runs automations FOR them. IP belongs to client. Different access controls + revenue model.
// 50/50 split memo · 2026-05-23

Venture-revenue at the brand layer

TrackingTogether is held as a sole-proprietorship under qi's portfolio. At the venture-revenue layer the split is 50/50 with Anthony Vasquez. Eli persona operates as the execution agent against both owned + client lanes.

Full memo at /trackingtogether/internal/docs/ (pending publish). Source: /Volumes/tech_/sync_/profiles_/anthony_/ventures_/trackingtogether_/TT_5050_TRANSFER_2026-05-23.md

// eli · agent operational role

Eli executes against the whole scope

persona: ELI org: L7S P1 routing function: automation execution scope: owned + clients
  1. Owned-side — runs automation on Anthony's ventures (Net Meter monitoring, PFC Farms agricultural automation, IXL integration, _holdings_-private ops).
  2. Client-side — opt-out scrubs, contact-list maintenance, campaign management, scheduled reporting against client deliverables.
  3. RingCentral integration — scans for STOP/opt-out responses across client message threads, red-marks Google Sheet on 3-day schedule, surfaces clean call-lists to qi.
  4. Single-pane-of-glass — every task across both lanes lives on one master sheet under TT scope. No fragmentation.
// active p0 · this week

Three blockers before outbound calling resumes

1) Opt-out scrub — Eli scans RingCentral for every contact who replied STOP/opt-out, marks them RED on the Google Sheet, 3-day re-scan schedule. Blocker on calling green-list.

2) Sheet consolidation — 3 chronological sheets → 1 master under TT scope. qi sends the 3 sheet links, Eli merges. Groups (Culligan, etc.) stay on same sheet, not split.

3) Agriculture / patent pivot — fertilizer patent filed, white-girl ally (7 certs + degree, food-system collapse thesis) brings wineries + agricultural manufacturing equipment scope. Eli replicates site-building pattern for equipment marketplace research.

// universal-intake pipeline

Every contact → master notebook

Inbound across SMS / Beeper / Beside / mail → load contact notebook ~/.xen/notebooks/<slug>.md + recent thread + persona-relevant canon → Nitro Qwen/Llama-70B drafts reply → sends via inbound channel → appends interaction back to notebook. One context spine across all channels.

Anthony V is the first intake target for this pipeline — the TrackingTogether scope serves as the canonical proving ground before extending to MB, Stal'lyon, and broader client roster.