{"database": "rubrics", "table": "rubric_gradations", "rows": [[20, "L-CONVENTIONS", "autonomy", 4, "Self-Directed", "Student treats punctuation as a tool for controlling meaning, rhythm, and emphasis across all writing contexts without prompting. Semicolons, colons, dashes, and other internal punctuation are deployed strategically \u2014 not just correctly \u2014 to shape how a reader processes the argument or narrative. The student recognizes that a semicolon creates a different effect than a period or a conjunction, that a colon can build anticipation, and that conventional accuracy is the baseline for stylistic control. Spelling is consistently accurate. During peer review, the student identifies conventions issues in others' work and can explain not just what's wrong but why it matters for the reader's experience. In independent and collaborative work, conventions decisions are deliberate and reflective.", "The novel's opening line does something structurally interesting that most readers process without noticing: it withholds the subject. We get the setting, the weather, the mood \u2014 everything except who we're following. That delay is a convention choice as much as a narrative one; the author uses the semicolon-heavy syntax of the first paragraph to slow the reader down, forcing them to sit in uncertainty before the protagonist appears. It's worth comparing this to the opening of 1984, where Orwell gives us Winston immediately but buries the horror in a subordinate clause \u2014 'the clocks were striking thirteen.' Both authors understand that punctuation controls pacing. Orwell's comma after 'bright cold day in April' creates a pause that makes 'the clocks were striking thirteen' land harder; without that comma, the sentence rushes past the detail that's supposed to unsettle you. In my own writing, I've been experimenting with this \u2014 using colons before key claims to create a half-second of anticipation, and reserving semicolons for moments where I want two ideas held in tension rather than sequenced. It doesn't always work; sometimes the construction feels forced and I revise it back to simpler punctuation. But the awareness that punctuation is doing rhetorical work, not just following rules, has changed how I draft.", "2026-05-24 00:17:32", "2026-05-26 01:43:59", 1]], "columns": ["id", "skill_code", "dimension", "level", "level_label", "behavioral_description", "sample_response", "created_at", "updated_at", "active_version"], "primary_keys": ["id"], "primary_key_values": ["20"], "units": {}, "query_ms": 2.211655955761671}