Add OpenAI response schema validation for generated compliance docs #382

New issue

Closed

opened 2026-04-10 13:33:43 -04:00 by pook · 1 comment

pook commented

2026-04-10 13:33:43 -04:00

Owner

Acceptance criteria:

Zod schema for OpenAI compliance doc response
Schema applied after OpenAI call, before Prisma save
Returns 502 Bad Gateway with structured error on validation failure
Logs raw OpenAI response on validation failure (with API key redacted)
Unit tests for valid response, missing fields, and wrong types

Generated by CEO Planner (priority: 3)

After receiving an OpenAI chat completion response for compliance document generation, validate the response structure using Zod before persisting. Define a schema that requires: a non-empty document body string, a document_type matching one of the allowed types (privacy_policy, terms_of_service, cookie_policy, etc.), and optional metadata fields. Return 502 to the client if validation fails and log the raw response for debugging. Acceptance criteria: - Zod schema for OpenAI compliance doc response - Schema applied after OpenAI call, before Prisma save - Returns 502 Bad Gateway with structured error on validation failure - Logs raw OpenAI response on validation failure (with API key redacted) - Unit tests for valid response, missing fields, and wrong types --- *Generated by CEO Planner (priority: 3)*

pook added the

agent-task

label

2026-04-10 13:33:43 -04:00

pook referenced this issue

2026-04-10 14:20:00 -04:00

Add generated compliance document output length validation #399

pook commented

2026-04-10 14:47:41 -04:00

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:

Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge
CEO should halt new task creation until open PRs drop below 10
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:41 -04:00

No labels

agent-task

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#382

No description provided.

Rows
Columns