Add generated compliance document output length validation #399

Closed
opened 2026-04-10 14:20:00 -04:00 by pook · 1 comment
Owner

After OpenAI response schema validation (#382), add output length validation before returning the generated compliance document to the user. Reject outputs shorter than 500 characters (indicates truncation or error) and longer than 50000 characters (indicates hallucination or runaway generation). Return a structured 422 error with message asking user to retry if validation fails. Log the length of each generated document for monitoring. Add unit tests for: a 200-char output (reject), a 2000-char output (accept), and a 60000-char output (reject).


Generated by CEO Planner (priority: 3)

After OpenAI response schema validation (#382), add output length validation before returning the generated compliance document to the user. Reject outputs shorter than 500 characters (indicates truncation or error) and longer than 50000 characters (indicates hallucination or runaway generation). Return a structured 422 error with message asking user to retry if validation fails. Log the length of each generated document for monitoring. Add unit tests for: a 200-char output (reject), a 2000-char output (accept), and a 60000-char output (reject). --- *Generated by CEO Planner (priority: 3)*
Author
Owner

Bulk-closed 2026-04-10 during pipeline triage.

Context: CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch agent/dispatch/* because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key.

What to do next:

  1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge
  2. CEO should halt new task creation until open PRs drop below 10
  3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks)

This issue was superseded, not abandoned. Reopen if still relevant after PR triage.

Bulk-closed 2026-04-10 during pipeline triage. **Context:** CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch `agent/dispatch/*` because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key. **What to do next:** 1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge 2. CEO should halt new task creation until open PRs drop below 10 3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks) This issue was superseded, not abandoned. Reopen if still relevant after PR triage.
pook closed this issue 2026-04-10 14:47:39 -04:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pook/compliancebot#399
No description provided.