feat(outreach): move distribution tracking to Airtable#22
Open
Ducksss wants to merge 1 commit into
Open
Conversation
Replace the hand-edited LAUNCH.md ledger with an Airtable base so multiple outreach agents can run in parallel without racing on a shared file. - Add scripts/outreach-tracker.mjs: zero-dependency Node helper (list/get/claim/release/upsert/set-status/log) with upsert-on-Key dedup, a 15-minute claim protocol, and 429 backoff. Kept out of the npm package. - Redirect agent.md to read and write the tracker instead of LAUNCH.md; add Concurrency and Owned-Listings-On-Release sections; drop the LAUNCH.md commit step from Durable State. - Slim LAUNCH.md to positioning, channel copy, launch order, policy gates, and metrics, with a pointer to the Airtable base. - Freeze archive/launch-ledger-history.md as the pre-Airtable record. - Add token guards to .gitignore and a `make outreach` helper target. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Outreach/distribution tracking lived in
LAUNCH.mdas hand-edited Markdown tables that theagent.mdoutreach agent committed to git. To run several outreach agents in parallel, that model breaks — parallel runs collide on the shared branch and onLAUNCH.md(merge conflicts, lost updates, duplicate submissions to the same target). This moves tracking to an Airtable base with atomic upserts and a claim protocol, and slimsLAUNCH.mdto the parts that are actually doctrine.Changes
scripts/outreach-tracker.mjs(new): zero-dependency Node helper (list/get/claim/release/upsert/set-status/log) with upsert-on-Keydedup, a 15-minute claim protocol, and 429 back-off. Kept out of the npm package via thefileswhitelist (npm packcontains 0scripts/entries).agent.md: reads and writes the tracker instead ofLAUNCH.md; adds Concurrency (claim-before-act) and Owned Listings On Release sections; drops theLAUNCH.mdcommit step from Durable State (a normal run now makes no repo commit).LAUNCH.md: slimmed to positioning, channel copy, launch order, policy gates, and metrics, with a pointer to the Airtable base. No more per-target tables.archive/launch-ledger-history.md: marked frozen (pre-Airtable record)..gitignore: token guards.Makefile:make outreachhelper target.The 80 existing outreach rows were migrated into the base separately; this PR is the code/docs cutover.
Verification
make lintandmake testpass.claimfrom two workers — exactly one succeeds, the other exits non-zero;releaseclears it; an idempotent no-opupsertkeeps exactly one row.Follow-ups (manual, not in this PR)
Merge Queuetable and trim the junk select-field options.🤖 Generated with Claude Code