hint: clause-concept hints (deferred extension of ADR-0053) #37
Reference in New Issue
Block a user
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?
Summary
A deferred extension of the contextual
hintfeature (H2 / ADR-0053):clause-concept hints — deeper teaching surfaced when the cursor sits
in a recognized clause within a command, distinct from the per-form
tier-3 block.
Background
ADR-0053 delivers tier-3 hints at per-form granularity (one
what/example/conceptblock per command form, e.g.hint.cmd.add_relationship), plus a liveNext:line. Position-awarenesswithin a form is otherwise owned by tier-2 (the ambient candidate list /
slot prose).
During Phase B we identified a third "point" the per-form model doesn't
serve: concepts that live inside a clause, where a learner may want
teaching deeper than tier-2's candidate list but narrower than the whole
form. Examples:
… on delete ⟨cascade | set null | restrict⟩— referential actionscreate table … ( …, ⟨primary key | unique | check | foreign key⟩ … )— the constraint slots
with pkclause1:n/m:ncardinalityProposed direction (not yet designed)
hint.concept.<topic>catalogue namespace, surfaced when the cursoris detected to be in a recognized clause, layered on top of the
per-form block (does not replace it).
grammar position. This is the main new mechanism.
additive layer.
Why deferred, not empirical
We do not expect to accumulate usage statistics that would tell us which
clauses learners pause at, so this won't be "data-driven later" — it is a
deliberate follow-up job to be designed and scoped on its own once the
per-form tier-3 layer (ADR-0053 Phases A–D) is in real use. Pedagogy-led,
not metrics-led.
Scope to decide (when picked up)
constraint slots — the highest-value relational concepts).
hint.concept.<topic>+ the samewhat/example/conceptshape?) andkeys.rscoverage.