Skip to main content

DSAI guardrails-array dependency blocks AI Refinements

Context​

The AI Guardrails work needs a dedicated guardrails array from DSAI (AI service). Until that lands, AI Refinements (autonomous-ai-agent phase 2, AI-assisted refinement) is blocked — this makes the dependency recorded in the Jul 21 DSAI thread an explicit blocker on refinement delivery, not just an open design question.

Notes​

  • Refine cannot split a single merged guidance.context_clarification Markdown string back into separate guidance and guardrails arrays, so the guardrails field cannot be refined.
  • DSAI agreed (Grasia, Jul 21) to pick up the guardrails array in their new sprint; target date still TBD, so the unblock date for AI Refinements is unknown.

Decisions / changes​

  • AI Refinements is treated as blocked on the DSAI guardrails-array dependency until DSAI ships the field and publishes its contract — owner TBD, date TBD (Unconfirmed as a formally communicated decision).

Follow-ups​

  • Track the DSAI guardrails-array dependency as a cross-squad blocker in the roadmap and in autonomous-ai-agent/delivery/timeline.md gates — TBD.
  • Record the blocked state and its schedule impact in the next dated delivery status for autonomous-ai-agent — TBD.
  • Confirm DSAI's target date for the guardrails array and update the blocker when known — TBD.