mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Implement Quality Gate Configuration System #135

New Issue
Closed
opened 2026-01-30 23:42:29 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-30 23:42:29 +00:00
Owner
Copy Link

Create configuration system for quality gates that orchestrator enforces.

Objective: Define quality standards per workspace/project that cannot be negotiated by AI agents.

Configuration Format (YAML):

  • Build gates: compilation, type checking
  • Lint gates: ESLint rules, max errors/warnings
  • Test gates: minimum pass rate, required suites
  • Coverage gates: line/branch/function thresholds
  • Custom gates: project-specific scripts

Storage: Database table (WorkspaceQualityGates) with JSONB config field

Gates are loaded by orchestrator and enforced programmatically.

Related: L-015, #134 (orchestrator design)

Acceptance Criteria:

  • Prisma model for WorkspaceQualityGates
  • CRUD API for gate configuration
  • Default gate templates (strict, standard, relaxed)
  • Frontend UI for gate configuration
  • Gates loaded and cached by orchestrator
Create configuration system for quality gates that orchestrator enforces. Objective: Define quality standards per workspace/project that cannot be negotiated by AI agents. Configuration Format (YAML): - Build gates: compilation, type checking - Lint gates: ESLint rules, max errors/warnings - Test gates: minimum pass rate, required suites - Coverage gates: line/branch/function thresholds - Custom gates: project-specific scripts Storage: Database table (WorkspaceQualityGates) with JSONB config field Gates are loaded by orchestrator and enforced programmatically. Related: L-015, #134 (orchestrator design) Acceptance Criteria: - Prisma model for WorkspaceQualityGates - CRUD API for gate configuration - Default gate templates (strict, standard, relaxed) - Frontend UI for gate configuration - Gates loaded and cached by orchestrator
jason.woltje added the databasep0apiapidatabase labels 2026-01-30 23:42:29 +00:00
jason.woltje added this to the M4-LLM (0.0.4) milestone 2026-01-30 23:45:33 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label api api database database p0
Milestone
No items
No Milestone M4-LLM (0.0.4)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#135
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?