Create schedules by name rather than internal ID #54
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#54
Reference in new issue
Block a user
The recording requires inventing an ID before describing a schedule and uses that ID as a default task title. Start with a user-facing schedule name/title; generate stable unique internal identifiers using an existing server convention where possible, and preserve existing schedules and references.
Acceptance criteria
An operator creates, edits and runs a schedule without inventing a machine ID. Schedule names and task titles are understandable. Identifier generation handles collisions and existing references survive edits; required fields and interval errors are clear.
Notes
New schedules start with an editable name and a generated stable identifier. Existing schedule identifiers are retained while editing; names are used as workflow task titles. Browser check creates a named draft without an ID field and reviews/discards it without writing a schedule.
Close reason
Implemented and verified in
57456b3e. Full quality gate passed, seven targeted local browser checks passed, and real audit-name save/readback was verified with the original setting restored. Per-issue acceptance evidence is recorded in notes.Imported from beads
archie-core-3z4fd.5· GitHub #1709 · type task · priority P2 · created 2026-10-16 · closed 2026-10-16