# A3-IM08 Contextual AI and Settings automation

3 November2026. Owner explicitly approved **"Approve calendar/documents/mail and A3-IM08"**. Isolated codex/a3-ui-08 starts at accepted UI07 fba80ef346bc021e675024638dacf9ccef7243db. Acceptance receipt e5a979386d6377138e7ea7fd44958adb22838886 is published and independently remotely verified. No live model activation; application automation controls are distinct from the paused, untouched backlog orchestrator.

- [x] Inspect SettingsView, rules/notification owners, AI privacy/usage and contextual section-assistant callers.
- [x] Initial selected baseline:58 cases/5 suites passed, not blanket AI quality or full roadmap acceptance.
- [ ] Contextual assistance: preserve manual editing, source/document-language separation, explicit review/apply, stale-input discard, quota/consent/failure/retry/close. Investigate context and section-name changes while a proposal is pending or under review.
- [ ] Settings automation: expose current supported controls and explain effects/timing/disable behavior under Settings; preserve existing rules drafts and notification/AI preference writers. Inspect actual worker/data contracts before promising independent per-rule switches not represented in current six numeric thresholds. No fake controls, worker activation or policy/infrastructure change.
- [ ] Scoped EN/NB, responsive/focus/accessibility presentation; types/lint/build, controlled browser and applicable local backend tests; independent review.
- [ ] Publish validated checkpoints and exact evidence; update durable handoff. Next Gate F before IM09 account/session/connections/admin/processing views.

Current source findings:rules expose only six integer day thresholds1–365, not independent enable flags; email-follow-up notifications and AI/privacy preferences have actual existing boolean controls. Do not represent thresholds as disable switches or imply a general worker-control API. Contextual assistant invalidation currently covers source text, target ID, language and entitlement; generation also consumes context and sectionName, which need compatibility review.

No schema/dependency/migration planned for presentation and bounded stale-proposal fix. Existing canonical Career Profile, CV/letter history/settings, RD21, per-owner data, quota/consent and server review/apply stay authoritative. Rollback reverts this UI increment; no database rollback. Full integrated AI/security/native/provider/release qualifications remain separate.