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

Web Console: Workflow policy and guardrail configuration visibility (Phase 3) #646

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

Problem statement

Policy and guardrails live in code, profiles, docs, and skills. Operators cannot see active workflow policy/guardrail configuration from the console without reading the repo tree.

User and operational impact

Misconfigured sessions; unclear why a gate failed; slow controller triage.

Scope

  • Read-only projection of active policies: role separation, lease rules, worktree rules, merge confirmation, redaction, contamination, allocator policy summaries.
  • Source attribution (file/module/doc) without exposing secrets.
  • Diff vs documented defaults where feasible.

Explicit non-goals

  • No policy editing in this issue (see dedicated edit/rollback issue).
  • No weakening of gates via UI toggles.

Required implementation investigation

docs/safety-model.md, profiles config shape, task_capability_map.py, gates, #633, #631, skills workflows.

Proposed architecture or implementation direction

Policy inventory builder scanning known modules/docs into redacted JSON; HTML tables with source links.

Security and workflow-safety requirements

Never display token values; RBAC for config visibility if sensitive.

Acceptance criteria

  1. Console lists major guardrails with source pointers.
  2. Secrets redacted.
  3. Tests ensure sample secrets never appear.
  4. Docs explain read-only nature.

Required tests

Redaction tests; inventory completeness smoke tests.

Observability and audit requirements

Optional access audit for config views.

Dependencies and linkage

Canonical issue state

STATE: ready-for-author
WHO_IS_NEXT: author
NEXT_ACTION: Implement read-only policy visibility
NEXT_PROMPT: Author policy inventory view; PR; stop

Required final evidence

PR with inventory, tests, docs.

Required final response and handoff expectations

Brief PR → reviewer.

## Problem statement Policy and guardrails live in code, profiles, docs, and skills. Operators cannot **see** active workflow policy/guardrail configuration from the console without reading the repo tree. ## User and operational impact Misconfigured sessions; unclear why a gate failed; slow controller triage. ## Scope * Read-only projection of active policies: role separation, lease rules, worktree rules, merge confirmation, redaction, contamination, allocator policy summaries. * Source attribution (file/module/doc) without exposing secrets. * Diff vs documented defaults where feasible. ## Explicit non-goals * No policy editing in this issue (see dedicated edit/rollback issue). * No weakening of gates via UI toggles. ## Required implementation investigation `docs/safety-model.md`, profiles config shape, `task_capability_map.py`, gates, #633, #631, skills workflows. ## Proposed architecture or implementation direction Policy inventory builder scanning known modules/docs into redacted JSON; HTML tables with source links. ## Security and workflow-safety requirements Never display token values; RBAC for config visibility if sensitive. ## Acceptance criteria 1. Console lists major guardrails with source pointers. 2. Secrets redacted. 3. Tests ensure sample secrets never appear. 4. Docs explain read-only nature. ## Required tests Redaction tests; inventory completeness smoke tests. ## Observability and audit requirements Optional access audit for config views. ## Dependencies and linkage * Parent: #631 · Soft-depends: #632, #633 · Related: #630 ## Canonical issue state ```text STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Implement read-only policy visibility NEXT_PROMPT: Author policy inventory view; PR; stop ``` ## Required final evidence PR with inventory, tests, docs. ## Required final response and handoff expectations Brief PR → reviewer.
jcwalker3 added the type:featurestatus:readyworkflow-hardeningdashboardsafety labels 2026-07-10 14:41:24 -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 safety 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#646