Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 73 Pull Requests 9 Actions Packages Projects Releases Wiki Activity

Web Console: Notifications and human-attention routing (Phase 3) #648

New Issue
Open
opened 2026-07-10 14:41:52 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-10 14:41:52 -05:00
Owner
Copy Link
Copy Source

Problem statement

Humans are interrupted for routine workflow transitions. The console needs notifications and human-attention routing that only escalate at the defined attention boundary (#628), while recording quieter events for operator pull-based review.

User and operational impact

Alert fatigue or missed true blockers (auth, business decisions, irrecoverable state).

Scope

  • Attention classes: routine (no page), operator (console inbox), human-required (notify channel).
  • Inbox UI of items needing human/controller attention with links to issues.
  • Routing rules documented; default fail closed to inbox not spam.
  • Integrate with workflow blockers and dependency waits.

Explicit non-goals

  • No mandatory Slack/email vendor lock without adapters.
  • No notification for every handoff.

Required implementation investigation

#628 attention boundary, #640 traffic, #637 timeline, #631, incident bridge patterns.

Proposed architecture or implementation direction

Attention event table; poll/API; optional webhook adapters later; console inbox first.

Security and workflow-safety requirements

RBAC on inbox; no secrets in notifications; audit deliveries.

Acceptance criteria

  1. Attention classes defined and implemented.
  2. Inbox lists human/controller items only as configured.
  3. Routine transitions do not create human alerts by default.
  4. Tests for classification rules.
  5. Docs for operators.

Required tests

Classifier unit tests; inbox API tests.

Observability and audit requirements

Delivery attempts logged.

Dependencies and linkage

Canonical issue state

STATE: ready-for-author
WHO_IS_NEXT: author
NEXT_ACTION: Implement attention inbox + classification
NEXT_PROMPT: Author notifications/inbox; PR; stop

Required final evidence

PR with inbox, rules, tests, docs.

Required final response and handoff expectations

Brief PR → reviewer.

## Problem statement Humans are interrupted for routine workflow transitions. The console needs **notifications and human-attention routing** that only escalate at the defined attention boundary (#628), while recording quieter events for operator pull-based review. ## User and operational impact Alert fatigue or missed true blockers (auth, business decisions, irrecoverable state). ## Scope * Attention classes: routine (no page), operator (console inbox), human-required (notify channel). * Inbox UI of items needing human/controller attention with links to issues. * Routing rules documented; default fail closed to inbox not spam. * Integrate with workflow blockers and dependency waits. ## Explicit non-goals * No mandatory Slack/email vendor lock without adapters. * No notification for every handoff. ## Required implementation investigation #628 attention boundary, #640 traffic, #637 timeline, #631, incident bridge patterns. ## Proposed architecture or implementation direction Attention event table; poll/API; optional webhook adapters later; console inbox first. ## Security and workflow-safety requirements RBAC on inbox; no secrets in notifications; audit deliveries. ## Acceptance criteria 1. Attention classes defined and implemented. 2. Inbox lists human/controller items only as configured. 3. Routine transitions do not create human alerts by default. 4. Tests for classification rules. 5. Docs for operators. ## Required tests Classifier unit tests; inbox API tests. ## Observability and audit requirements Delivery attempts logged. ## Dependencies and linkage * Parent: #631 · Soft-depends: #640, #637 · Related: #628 ## Canonical issue state ```text STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Implement attention inbox + classification NEXT_PROMPT: Author notifications/inbox; PR; stop ``` ## Required final evidence PR with inbox, rules, tests, docs. ## Required final response and handoff expectations Brief PR → reviewer.
jcwalker3 added the type:featurestatus:readyworkflow-hardeningdashboard labels 2026-07-10 14:41:52 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
No labels dashboard status:ready type:feature workflow-hardening
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#648