fix(ai): don't write the scheduled posting time into recurring posts #79

Merged

kreativmonkey merged 2 commits from fix/recurring-posting-time into main 2026-06-13 21:53:58 +02:00

Conversation 0 Commits 2 Files changed 2 +53 -13

kreativmonkey commented 2026-06-13 21:51:31 +02:00

Owner

• Copy link
• Copy Markdown

Problem

For recurring / announcement jobs the AI wrote the posting time (when the post is published) into the post body, as if it were the event time. The posting time should only be passed through for scheduling, never appear in the text — the event facts live in the template (source_content).

Root cause

recurringPublicationPlan (in internal/ai/prompts.go) added a line to the prompt's ## Publication plan:

This post publishes: <post_scheduled_at>

For the main recurring post this was the only time-shaped line in the prompt, so the model treated that posting timestamp as the event time and wrote it into the copy.

Fix

• Remove the This post publishes: <time> line — the posting time is a scheduling-only field; the scheduler already uses post_scheduled_at to set the post's ScheduledAt, so it has no business in the text prompt.
• Add an explicit guard: tell the model the publication time is set automatically and must never be mentioned; any time/date wording comes only from the template.
• Announcements still get the real event date (main_event_at) — that is legitimate, referenceable content; only the posting time is suppressed.

Tests (added, TDD)

• Main recurring prompt: the posting time (and This post publishes) is absent; the "set automatically — never mention" guard is present.
• Announcement prompt: the posting time (09:00) is gone, while the event date line is kept.

go test ./..., go vet ./internal/ai/ pass.

🤖 Generated with Claude Code

## Problem For recurring / announcement jobs the AI wrote the **posting time** (when the post is published) into the post body, as if it were the **event** time. The posting time should only be passed through for scheduling, never appear in the text — the event facts live in the template (`source_content`). ## Root cause `recurringPublicationPlan` (in `internal/ai/prompts.go`) added a line to the prompt's `## Publication plan`: ``` This post publishes: <post_scheduled_at> ``` For the main recurring post this was the *only* time-shaped line in the prompt, so the model treated that posting timestamp as the event time and wrote it into the copy. ## Fix - **Remove** the `This post publishes: <time>` line — the posting time is a scheduling-only field; the scheduler already uses `post_scheduled_at` to set the post's `ScheduledAt`, so it has no business in the text prompt. - **Add an explicit guard**: tell the model the publication time is set automatically and must never be mentioned; any time/date wording comes only from the template. - Announcements still get the real **event date** (`main_event_at`) — that is legitimate, referenceable content; only the posting time is suppressed. ## Tests (added, TDD) - Main recurring prompt: the posting time (and `This post publishes`) is absent; the "set automatically — never mention" guard is present. - Announcement prompt: the posting time (09:00) is gone, while the event date line is kept. `go test ./...`, `go vet ./internal/ai/` pass. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

kreativmonkey added 1 commit 2026-06-13 21:51:32 +02:00

fix(ai): stop recurring posts from writing the scheduled posting time ... 1cb89133b7

For recurring/announcement jobs the generation prompt listed "This post
publishes: <time>" (post_scheduled_at). With nothing else time-shaped in the
prompt, the model mistook that *posting* time for the *event* time and wrote
it into the post body.

The posting time is a scheduling-only field — the system already uses it to
set the post's ScheduledAt; it does not belong in the text. Remove that line
from the prompt and instead instruct the model that the publication time is
set automatically and must never appear in the text; event timing comes only
from the template (source_content). The real event date is still provided to
announcements (it is legitimate, referenceable content).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

kreativmonkey added 1 commit 2026-06-13 21:52:58 +02:00

style(ai): gofmt prompts.go (align moodAdjustmentHints) ... a30337af9b

Pre-existing gofmt drift in the moodAdjustmentHints map; no behaviour change.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

kreativmonkey merged commit de0b97f8c1 into main 2026-06-13 21:53:58 +02:00

kreativmonkey referenced this pull request from a commit 2026-06-13 21:54:01 +02:00

fix(ai): don't write the scheduled posting time into recurring posts (#79)

kreativmonkey referenced this pull request from a commit 2026-06-17 09:09:33 +02:00

fix(ai): don't write the scheduled posting time into recurring posts (#79)

kreativmonkey referenced this pull request from a commit 2026-06-27 08:54:30 +02:00

chore(main): release 0.1.1 (#4)

kreativmonkey referenced this pull request from a commit 2026-09-23 11:15:36 +02:00

chore(deps): update frontend non-major dependencies (#79)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

wontfix

This won't be fixed

No labels

bug

duplicate

enhancement

help wanted

invalid

question

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

kreativmonkey/goloom!79

No description provided.