atlas/tickets/backlog/TICKET-045_confirmation-flows.md
ilia 7c633a02ed Initialize project structure with essential files and documentation
- Added .cursorrules for project guidelines and context
- Created README.md for project overview and goals
- Established ARCHITECTURE.md for architectural documentation
- Set up tickets directory with initial ticket management files
- Included .gitignore to manage ignored files and directories

This commit lays the foundation for the Atlas project, ensuring a clear structure for development and collaboration.
2026-01-05 20:09:44 -05:00

1.4 KiB

Ticket: Confirmation Flows

Ticket Information

  • ID: TICKET-045
  • Title: Confirmation Flows
  • Type: Feature
  • Priority: High
  • Status: Backlog
  • Track: Safety/Memory
  • Milestone: Milestone 3 - Memory, Reminders, Safety
  • Created: 2024-01-XX

Description

Implement confirmation flows for high-risk actions:

  • Risk classification (high-impact actions list)
  • Confirmation UX (text and voice prompts)
  • Agent explains action, asks for "Yes/No"
  • Log decisions
  • Enforcement at tool level (signed confirmation token from client)

Acceptance Criteria

  • Risk classification system implemented
  • High-impact actions identified and documented
  • Confirmation UX designed (text + voice)
  • Confirmation flow working
  • Decision logging implemented
  • Tool-level enforcement (confirmation token)

Technical Details

High-impact actions:

  • Send email
  • Calendar changes
  • File edits outside "safe" areas
  • Smart-home actions
  • High-value task changes

Confirmation flow:

  1. Agent proposes action
  2. User confirms (voice or UI)
  3. Signed token generated
  4. Tool validates token before execution
  5. Action logged

Dependencies

  • TICKET-026 (tool-calling policy)
  • TICKET-029 (MCP server)
  • TICKET-039 (phone client) or TICKET-040 (web dashboard)
  • home-voice-agent/safety/confirmations/ (to be created)

Notes

Ties into clients for presenting confirmations. Critical for safety.