Prompt-Based Constraint is the dominant enforcement mechanism in LLM-based programming support systems¶

Claim · All claims
Evidence · 1 study · review r2 · q2
Currency · newest study 2026 · not yet checked against its sources · not reviewed by a person

Subclaims¶

q2 i? Prompt-Based Constraint (E1) appeared in 82 of 90 studies (91.1%), while mechanisms involving stronger runtime monitoring or pedagogical intervention were far less common (e.g., Learner Response Quality Control in 4 studies, 4.4%). → Minsun Kim 2026

Evidence¶

Minsun Kim 2026¶

Minsun Kim, S. Moonwara A. Monisha, Zihan Wu, David H. Smith IV. (2026). Exploring the Design Space of LLM-Based Programming Support in CS Education: A Scoping Review through the Lens of Assistance Governance. https://arxiv.org/abs/2607.21257 doi:10.48550/arxiv.2607.21257

q2 · i? · review · r2

Qualitative synthesis coding Enforcement across the 90-system corpus into 11 categories spanning system-level control, backend, frontend, and intervention structures. Studies averaged 2.98 enforcement labels, with 82 studies (91.1%) using two or more mechanisms.

"Prompt-Based Constraint ( E1 ) appeared in 82 studies (91.1%), making it the dominant enforcement mechanism."

Discussion¶

Related Claims¶

• Authority over assistance boundaries is highly centralized in system logic in LLM-based programming support systems — related
• Policy–enforcement pairings are dominated by prompt-based constraints, and policy themes differ in enforcement breadth — a broader claim this one bears on
• Monolithic single-prompt LLM architectures hinder responsible educational deployment by collapsing distinct pedagogical functions — related
• Policy in reviewed systems is commonly expressed as a set of assistance boundaries, concentrated on response constraints, scaffolding, and personalization — related