All Projects

PRODUCT · UP

With 467 drafts already queued against 98 waiting emails, there is a high risk of multiple drafts being generated per inbox message. Adding a check (e.g., index on message-id or thread-id) before inserting a new draft prevents duplicates and keeps the inbox-to-draft ratio meaningful. [reliability · needs approval]

The project has no Git repo, meaning there is zero version history, rollback capability, or audit trail — a critical gap before any further changes are made. Running `git init && git add -A && git commit -m 'initial snapshot'` establishes a safety net and unblocks collaborative development. [reliability · auto-eligible]

DASHBOARD · UP

An authorization queue of 23 pending items is a growing bottleneck and security surface — unreviewed authorizations can stall workflows or expose the system to unauthorized access. Conducting a focused batch review session to approve legitimate requests and reject/flag suspicious ones will immediately reduce the queue and harden the authorization boundary. [security · needs approval]

The git repository is missing, meaning there is no version control, no audit trail, and no ability to roll back changes — this is the highest risk gap for an operational system. Run `git init`, add a .gitignore, make an initial commit, and push to a remote (GitHub/GitLab) to establish a baseline. [reliability · needs approval]

AGENT · UP

The approval loop is completely disconnected: board writes ./queue/*.md but pickup.sh and the dashboard only read jarvis_cards in Supabase, so every 'approve N' is a silent no-op. Adding a sync-cards.sh called at the end of run-headless.sh to upsert each staged Tier-2 card as a jarvis_cards row closes this gap and is the single fix that makes the headline feature actually work end-to-end. [archite

The 6 AM board silently fails with no visible error trail; piping the n8n execution error log into the existing status output will immediately surface the root cause (likely the dirty-state or Capture-Sent-Feedback matcher regression) without touching workflow logic. Th · ✓ built·tested·reviewed · 🔬 ready to merge

ENGINE · —

The engine's core value is scoring businesses by sell likelihood, but without documented criteria (e.g. years in business, owner age, revenue trends, listing signals), scores are opaque and untunable. A scored_criteria.yaml or config.py with named signals and weights makes the model transparent, testable, and improvable without touching scraping logic. [accuracy · needs approval]

The project has no version control, making every change irreversible and collaboration impossible. Running `git init`, adding a sensible .gitignore (Python/Node artifacts, .env files, secrets), and making an initial commit is the foundational prerequisite before any other improvement can be safely made. [architecture · auto-eligible]

PRODUCT · UP

With the git repo being initialized, laying down the foundational directory structure and dependency manifest immediately gives the project a reproducible, deployable scaffold — preventing ad-hoc file sprawl and enabling CI/CD from day one. [architecture · needs approval]

The project has no git repo (git.missing=true), meaning there is zero version control, history, or rollback capability — a critical gap for any production service. Initializing git with a proper .gitignore (excluding secrets/node_modules) and a README describing the weekly AI investment advisory purpose establishes the foundation for all future safe iteration. [architecture · auto-eligible]

SITE · UP

A live lead-gen site needs search engines to index it properly; adding robots.txt (allowing all crawlers) and a basic sitemap.xml pointing to the homepage ensures Google and Bing can discover and rank the site, directly driving organic leads for Dan. [feature · auto-eligible]

The site is live with no Git repository, meaning there's no version history, no rollback capability, and no safe path for future changes. Running `git init`, committing all current files, and pushing to a remote (GitHub/GitLab) immediately establishes a safety net and enables CI/CD, collaboration, and auditability. [reliability · needs approval]

PIPELINE · UP

With only 1 metric row and a single eval date, the pipeline is fragile — unhandled exceptions or malformed Gmail data could silently corrupt results or halt execution. Adding try/catch blocks, null checks on email payloads, and logging failed rows to a dedicated error sheet ensures failures surface and don't corrupt sales metrics. [reliability · needs approval]

The project has no Git repository, meaning all Apps Script code is one accidental deletion or bad edit away from permanent loss. Creating a repo (e.g. on GitHub), exporting the script files via clasp, and committing them establishes a recoverable baseline and enables future CI/diff tracking. [reliability · needs approval]