Skip to content

Clarify hourly conversation naming mechanism and schedule reconciliation - #653

Merged
witbrock merged 2 commits into
mainfrom
codex/von-fa2a7d9557cbee20
Sep 12, 2026
Merged

Clarify hourly conversation naming mechanism and schedule reconciliation#653
witbrock merged 2 commits into
mainfrom
codex/von-fa2a7d9557cbee20

Conversation

@witbrock

Copy link
Copy Markdown
Member

Merge decision: ready — operators can choose the existing naming consumer and reconcile its hourly schedule without mistaking a task assignment or a create retry for activation.

User outcome

For the bounded job of inspecting an actor's owned unnamed conversations and assigning concise titles hourly, reuse the naming workflow delivered in #645. Recurring task continuation uses the same scheduler plus a Tasks/chat launch; it is useful for evolving responsibilities but adds task, conversation and execution dependencies to this existing consumer.

Material changes

Document that mechanism comparison in the VWL schedule guide. Explain how to reuse an existing schedule, explicitly resume it, and reconcile an older naming consumer before creating a replacement. The schedule creation hash includes the definition identity and inputs, so a stable caller key alone does not prevent duplicate schedules across configuration changes.

Evidence

Inspected the current naming bundle, recurring-task submission path, actor-owned schedule service and durable scheduler. pdm run pytest -q tests/backend/test_conversation_naming_workflow.py tests/backend/test_workflow_schedule_service.py tests/backend/test_task_execution_actions.py tests/backend/test_conversation_search_service.py: 38 passed using a mock database and scripted model responses. This includes due-occurrence creation, deduplication, checkpoint recovery, canonical rename read-back and existing/concurrent-title preservation. Diff whitespace and the new local link/anchor were checked.

Ship boundary

This documentation change records the current implementation and operational reconciliation behaviour. Live actor-scope definition, schedule and occurrence read-back remain outstanding: this worker has no Von control tools and is prohibited from live mutations through shell. No schedule, assignment, conversation name, represented prompt, running service or deployment is changed by this PR. Actual live title quality and hourly execution remain unverified.

@witbrock
witbrock merged commit ad873c6 into main Sep 12, 2026
2 checks passed
@witbrock
witbrock deleted the codex/von-fa2a7d9557cbee20 branch September 12, 2026 22:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant