HNK Institute publishes this page on hnk.org because explanation-before-tools track is easy to fake with fluent tools and hard to own as human knowledge. This track trains students to produce a human explanation before they are allowed to operate a new system. The institute's tagline — human knowledge for new technology — is a working rule here, not a decoration beside the pink mark. Students, families, and schools should read the page as a description of practice: what the student will explain, what artifact will hold that explanation, and what the work will refuse.
This page on explanation-before-tools track is written for students and the adults who review their work. It is not written for tool theater. If a visitor came to hnk.org looking for a shortcut around thinking, explanation-before-tools track will feel slow on purpose. AI literacy for students is treated as STEM knowledge practice: repeated, reviewable, and independent of whichever interface is fashionable this term.
What explanation-before-tools track demands of a student
What explanation-before-tools track demands of a student sits at the center of this HNK page because speed is not the scarce resource. The student must be able to speak the idea without borrowing a fluent machine voice. Students practicing explanation-before-tools track should write a human-language account of explanation-before-tools track with the interface closed. They should also circle every term in explanation-before-tools track the student cannot define without a slogan. Those two moves keep responsible AI education attached to a real student mind rather than to a transcript.
A reviewer looking at an explanation card for explanation-before-tools track can ask the closed-interface question: can the student still talk? Common failure looks like opening a tool first and writing the explanation of explanation-before-tools track afterward. HNK treats that failure as a literacy gap. The next assignment is not a more impressive tool. It is a clearer human sentence.
- Write a human-language account of explanation-before-tools track with the interface closed.
- Circle every term in explanation-before-tools track the student cannot define without a slogan.
- Name the human decision hidden inside explanation-before-tools track and who is responsible for it.
- List one thing explanation-before-tools track cannot do, even when the output looks fluent.
- Can the student explain the idea without looking at the interface?
Explanation before operation
Under the heading Explanation before operation, HNK asks adults to listen differently. If the interface is required for the student to sound knowledgeable, the knowledge is still on loan. Families do not need to become engineers to review explanation-before-tools track. They need to hear a limitation note and a teach-back. If the student can only perform while a model is completing sentences, the knowledge is still on loan.
Keep a source note that separates a claim from a guess about explanation-before-tools track in the folder. Refuse treating a fluent answer as proof that explanation-before-tools track is understood. Responsible AI education is rehearsed in small refusals: not pasting other people's work, not sending private records, not claiming certainty the map does not support.
- Can the student explain the idea without looking at the interface?
- Which human decision is the student still responsible for?
- What would make this explanation false?
- Which words are decorative rather than known?
- What should not be sent to a model or a public form?
Human artifacts worth keeping
Human artifacts worth keeping is where STEM knowledge practice becomes visible on paper. Reviewers want maps, limitation notes, and teach-backs more than they want exports. The student should produce a source note that separates a claim from a guess about explanation-before-tools track and a revision log showing how the explanation of explanation-before-tools track changed before anyone talks about publishing, showcasing, or applying the work to a larger story.
Mentors are held to a negative duty as much as a positive one. They may not complete the explanation of explanation-before-tools track. They may not replace a weak student sentence with a better generated one. They may ask: What should not be sent to a model or a public form? That question protects the student from fluent machines and from helpful adults.
- Opening a tool first and writing the explanation of explanation-before-tools track afterward.
- Pasting generated text about explanation-before-tools track as if it were student knowledge.
- Treating a fluent answer as proof that explanation-before-tools track is understood.
- Hiding uncertainty so explanation-before-tools track looks finished.
- Collecting screenshots of explanation-before-tools track without a human account of what they show.
Responsible boundaries
Responsible boundaries sits at the center of this HNK page because speed is not the scarce resource. Literacy includes practiced refusal: privacy, honesty about sources, and not using other people's data. Students practicing explanation-before-tools track should list one thing explanation-before-tools track cannot do, even when the output looks fluent. They should also keep a limitation note beside any example of explanation-before-tools track. Those two moves keep responsible AI education attached to a real student mind rather than to a transcript.
A reviewer looking at a source note that separates a claim from a guess about explanation-before-tools track can ask the closed-interface question: can the student still talk? Common failure looks like hiding uncertainty so explanation-before-tools track looks finished. HNK treats that failure as a literacy gap. The next assignment is not a more impressive tool. It is a clearer human sentence.
- List one thing explanation-before-tools track cannot do, even when the output looks fluent.
- Keep a limitation note beside any example of explanation-before-tools track.
- Compare two explanations of explanation-before-tools track and keep the one a classmate could mark.
- Record a question about explanation-before-tools track that still has no honest answer.
- Which words are decorative rather than known?
How reviewers will push back
Under the heading How reviewers will push back, HNK asks adults to listen differently. A reviewer will ask which sentence would be false and which words are still decorative. Families do not need to become engineers to review explanation-before-tools track. They need to hear a limitation note and a teach-back. If the student can only perform while a model is completing sentences, the knowledge is still on loan.
Keep an explanation card for explanation-before-tools track in the folder. Refuse opening a tool first and writing the explanation of explanation-before-tools track afterward. Responsible AI education is rehearsed in small refusals: not pasting other people's work, not sending private records, not claiming certainty the map does not support.
- Can the student explain the idea without looking at the interface?
- Which human decision is the student still responsible for?
- What would make this explanation false?
- Which words are decorative rather than known?
- What should not be sent to a model or a public form?
What this page refuses
What this page refuses is where STEM knowledge practice becomes visible on paper. HNK will not treat a generated paragraph as a student's mind. The student should produce an explanation card for explanation-before-tools track and a responsible-use boundary list for explanation-before-tools track before anyone talks about publishing, showcasing, or applying the work to a larger story.
Mentors are held to a negative duty as much as a positive one. They may not complete the explanation of explanation-before-tools track. They may not replace a weak student sentence with a better generated one. They may ask: What would make this explanation false? That question protects the student from fluent machines and from helpful adults.
- Opening a tool first and writing the explanation of explanation-before-tools track afterward.
- Pasting generated text about explanation-before-tools track as if it were student knowledge.
- Treating a fluent answer as proof that explanation-before-tools track is understood.
- Hiding uncertainty so explanation-before-tools track looks finished.
- Collecting screenshots of explanation-before-tools track without a human account of what they show.
A practical next step
A practical next step sits at the center of this HNK page because speed is not the scarce resource. Write the human account first, then decide whether any tool is even needed. Students practicing explanation-before-tools track should record a question about explanation-before-tools track that still has no honest answer. They should also translate a technical claim about explanation-before-tools track into ordinary speech, then back again. Those two moves keep responsible AI education attached to a real student mind rather than to a transcript.
A reviewer looking at an explanation card for explanation-before-tools track can ask the closed-interface question: can the student still talk? Common failure looks like pasting generated text about explanation-before-tools track as if it were student knowledge. HNK treats that failure as a literacy gap. The next assignment is not a more impressive tool. It is a clearer human sentence.
- Record a question about explanation-before-tools track that still has no honest answer.
- Translate a technical claim about explanation-before-tools track into ordinary speech, then back again.
- Write a human-language account of explanation-before-tools track with the interface closed.
- Circle every term in explanation-before-tools track the student cannot define without a slogan.
- Which human decision is the student still responsible for?