Jordan-Hall / Jordan-Hall/browser

[P3][AUTO-02] Notifications and bounded unattended work

Open
#93 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Programme: #1
Epic: #30

## Objective
Deliver useful background work and attention management without giving unattended tasks open-ended authority or overwhelming the user.

## Scope
- Notification policy by workspace/task/source/severity and quiet hours.
- Approval/action queue with expiration and grouped notifications.
- Explicit execution location and online requirements per automation.
- Per-task/tool/financial/time/resource budgets.
- Unattended pre-authorized actions only where scope/limits/verification are enforceable.
- Relevance/deduplication so repeated source noise does not spam the user.
- Failure/escalation states that request human attention when authority or verification is insufficient.

## Safety rules
- Unattended tasks cannot widen their own grants, destinations, spending ceilings or target resources.
- Notification dismissal is not authorization.
- Consequential actions still use TX policy and reconciliation.

## Acceptance criteria
- [ ] Quiet hours and notification grouping work without suppressing critical approval/incident state incorrectly.
- [ ] Automation clearly states whether this device/home worker/remote worker must be online.
- [ ] Unattended task cannot exceed its capability/time/financial/data-destination budget.
- [ ] Expired approval/request cannot be executed from a stale notification.
- [ ] Duplicate source events do not generate duplicate consequential actions/notifications.
- [ ] User can inspect, pause, revoke and audit each unattended workflow.

## Dependencies
- AUTO-01
- TX-01
- WS-03

**First phase:** P3
**Maturity target:** P5
**Owner:** platform

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the AUTO-01, TX-01, and WS-03 dependencies and mapping the existing automation, notification, approval, and audit entry points. Done means the acceptance criteria are met across quiet hours, online requirements, enforced budgets, expiration, deduplication, and user inspection, pause, revocation, and audit controls.

Written by the indexing model from the issue text.

Assessment

Domain
backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.