LaunchRepoThe launch-date floor is one field, one question and one refusal. The field is earliest_launch_date in product.json. The question is asked during onboarding: is there a date before which nothing should go public? The refusal is in scripts/record.py: it will not mark a platform as scheduled for a date earlier than the floor, and it will not accept scheduled without a launch date at all. Everything else in this guide follows from those three facts. The feature shipped with the 15 September 2026 release on the changelog.
What the floor does
When an agent records a scheduled listing, it passes the date the platform confirmed:
On Windows, use py -3 instead of python3 in the commands below (or python if that is your Python 3.10+ command). Keep your workspace in a private local folder outside OneDrive or other sync folders. For multiline shell examples, put the command on one line and remove the trailing \ characters in PowerShell.
python3 scripts/record.py --project ../private-product tinylaunch scheduled \
--launch-date 2026-10-14 \
--note "Weekly slot confirmed; approval still outstanding" \
--next-action "Verify listing on the launch date"If product.json holds "earliest_launch_date": "2026-10-12", that command succeeds. With --launch-date 2026-09-28 it is rejected with a message saying the date is earlier than the owner-authorised floor — and nothing is written. Leaving the field blank means there is no floor. The local dashboard shows the floor next to the scheduled state, so the number is visible without opening the file.
What it cannot do
The floor is a guard on your records, not a lever on the directories. It does not delay a submission, because submitting and publishing are different events and the agent controls only the first. It does not stop a moderated directory from publishing whenever its queue reaches you. And it does not make a confirmed date a publication guarantee: a slot on a launch board can still depend on approval, which is why the runbook tells the agent to keep any outstanding approval in the note. The outcome recording guide covers that convention.
Why weeks, not days
The onboarding script makes the agent warn you up front that many free-tier directories queue submissions for review and that publication can take several weeks. That warning is drawn from what the public field guides on this site observed in September 2026: a SaaSHub page that was reachable but labelled Pending approval, a PitchWall review window stated as more than 30 days, a TinyLaunch weekly slot with approval still outstanding, Uneed allowing one pending launch per account. Free tiers are moderated by people with a queue. A floor lets you submit early to the moderated directories — submission is not publication — while keeping the platforms that let you choose a date from firing before your announcement is ready.
Choosing the date
Two rules of thumb from the kit’s own docs and the launch-date article:
- Pick the floor as the first day of the week you want listings to start appearing, not the day you plan to start submitting. The gap between the two is where the review queues do their work.
- Do not confuse a floor with a target. A target is where you would like things to land; the floor is the earliest anything under your control is allowed to land. Directories make targets unreliable and floors cheap.
If you decide later that the date was wrong, change the field; the tracker re-checks it on the next scheduled record. Existing rows are not rewritten, so review anything already scheduled against the new date yourself. The concept in one paragraph, with related terms, is on the launch-date floor glossary page.