Skip to content

Complete styled training curriculum and development equipment navigation #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ibloud merged 62 commits into from
Oct 13, 2026
Merged

Complete styled training curriculum and development equipment navigation #39

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
62 commits
Select commit Hold shift + click to select a range
c9de1c5
Add styled guide: Career tracks
ibloud Oct 13, 2026
8d4027c
Add styled guide: Accessibility
ibloud Oct 13, 2026
c33deff
Add styled guide: Technology planning
ibloud Oct 13, 2026
f2573b9
Add styled guide: Funding research
ibloud Oct 13, 2026
77a1287
Add styled guide: AI research prompts
ibloud Oct 13, 2026
cd3bfc4
Add styled guide: Preparation templates
ibloud Oct 13, 2026
d3faa56
Add styled guide: Worked example
ibloud Oct 13, 2026
2015daa
Route training home links to styled guides
ibloud Oct 13, 2026
bb6c32b
Improve guide readability and mobile layout
ibloud Oct 13, 2026
7604fa2
Add accessible development environment and equipment guide
ibloud Oct 13, 2026
f7f2ac4
Surface development equipment guide in curriculum
ibloud Oct 13, 2026
8448230
Surface development equipment guide in curriculum
ibloud Oct 13, 2026
34fb889
Surface development equipment guide in curriculum
ibloud Oct 13, 2026
14b9693
Surface development equipment guide in curriculum
ibloud Oct 13, 2026
4d51300
Surface development equipment guide in curriculum
ibloud Oct 13, 2026
57c6a8d
Render accessible curriculum: Software development track
ibloud Oct 13, 2026
a9c62ef
Render accessible curriculum: Game development track
ibloud Oct 13, 2026
e8aae6b
Render accessible curriculum: Video track
ibloud Oct 13, 2026
0ba2bab
Render accessible curriculum: Audio track
ibloud Oct 13, 2026
db286a6
Render accessible curriculum: Design track
ibloud Oct 13, 2026
ff3e670
Render accessible curriculum: Hybrid creative-technology track
ibloud Oct 13, 2026
6ed4910
Render accessible curriculum: Optional maker pathway: game rules and …
ibloud Oct 13, 2026
875297f
Style curriculum reference Veiled Dominion / Duet development provenance
ibloud Oct 13, 2026
7092070
Style curriculum reference Visual access
ibloud Oct 13, 2026
4f0f56b
Style curriculum reference Screen-reader access
ibloud Oct 13, 2026
a407238
Style curriculum reference Magnification
ibloud Oct 13, 2026
ddfec07
Style curriculum reference Input and motor access
ibloud Oct 13, 2026
92a4e63
Style curriculum reference Cognitive and learning access
ibloud Oct 13, 2026
bb3510b
Style curriculum reference Xbox development workstation: dated purcha…
ibloud Oct 13, 2026
d3e0733
Navigate from guide overview to styled lessons
ibloud Oct 13, 2026
9ef9db8
Navigate from guide overview to styled lessons
ibloud Oct 13, 2026
32c809f
Navigate from guide overview to styled lessons
ibloud Oct 13, 2026
3d4126c
Navigate from guide overview to styled lessons
ibloud Oct 13, 2026
267e03e
Navigate from guide overview to styled lessons
ibloud Oct 13, 2026
ec0dac9
Navigate from guide overview to styled lessons
ibloud Oct 13, 2026
f93009a
Navigate from guide overview to styled lessons
ibloud Oct 13, 2026
73b247d
Style curriculum: Prompt: safe research practices
ibloud Oct 13, 2026
cf9e20e
Style curriculum: Prompt: find programs
ibloud Oct 13, 2026
81989fb
Style curriculum: Prompt: verify eligibility information
ibloud Oct 13, 2026
8294ef8
Style curriculum: Prompt: research technology
ibloud Oct 13, 2026
a04e890
Style curriculum: Prompt: compare costs and alternatives
ibloud Oct 13, 2026
5e87e10
Style curriculum: Prompt: build a request
ibloud Oct 13, 2026
df81bec
Style curriculum: Prompt: audit existing information
ibloud Oct 13, 2026
dbe0db6
Style curriculum: Prompt: adapt research to another jurisdiction
ibloud Oct 13, 2026
f6e4c1b
Style curriculum: Needs statement
ibloud Oct 13, 2026
7d86f42
Style curriculum: Technology plan
ibloud Oct 13, 2026
26866c6
Style curriculum: Equipment justification
ibloud Oct 13, 2026
64566c6
Style curriculum: Training plan
ibloud Oct 13, 2026
20b4755
Style curriculum: Quote comparison
ibloud Oct 13, 2026
9ff1284
Style curriculum: Questions for a counselor or decision-maker
ibloud Oct 13, 2026
8450e12
Style curriculum: Approval packet checklist
ibloud Oct 13, 2026
efe2c7f
Style curriculum: Source-verification record
ibloud Oct 13, 2026
363d749
Style curriculum: 1. Vocational goal
ibloud Oct 13, 2026
13898ed
Style curriculum: 2. Work tasks
ibloud Oct 13, 2026
b54d609
Style curriculum: 3. Accessibility requirements
ibloud Oct 13, 2026
08c14f3
Style curriculum: 4. Technology assessment
ibloud Oct 13, 2026
23a483a
Style curriculum: 5. Funding research
ibloud Oct 13, 2026
6ea5fd4
Style curriculum: 6. Approval packet
ibloud Oct 13, 2026
3981c46
Style curriculum: 7. Lessons learned
ibloud Oct 13, 2026
fd77f77
Style curriculum: United States federal context
ibloud Oct 13, 2026
39c889c
Style curriculum: Minnesota funding research
ibloud Oct 13, 2026
0042472
Style curriculum: Program research record
ibloud Oct 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/accessibility/cognitive-learning.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Cognitive and learning access — Loptr Lab</title><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><p><a class="button" href="../index.html">Guide home</a></p><h1>Cognitive and learning access</h1></header><main id="main"><article class="brief guide"><h2>Cognitive and learning access</h2>
<p>Reduce avoidable memory, sequencing, naming, interruption, and context-switching burdens. Useful capabilities may include clear steps, persistent state, meaningful defaults, templates, checklists, searchable history, undo, reminders, transcription, plain-language explanations, and resumable workflows. The system should support autonomy rather than make decisions or disclose information on the participant's behalf.</p></article><nav class="actions"><a class="button" href="index.html">Section overview</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/accessibility/cognitive-learning.md">Source Markdown</a></nav></main><footer>Verify current evidence and requirements. Protect private records.</footer></body></html>
10 changes: 10 additions & 0 deletions docs/accessibility/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Accessibility — Loptr Lab</title><meta name="description" content="Describe barriers without oversharing"><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><p><a class="button" href="../index.html">← Guide home</a></p><h1>Accessibility</h1><p class="subtitle">Describe barriers without oversharing</p></header><main id="main"><article class="brief guide"><p>Describe the barrier in relation to a task, then identify a capability or accommodation. Share only what is necessary; a diagnosis is not required to explain that text must enlarge without clipping or that an input method causes fatigue.</p>
<div class="table-wrap"><table><tbody>
<tr><td>Area</td><td>Planning questions</td></tr>
<tr><td><a href="./visual.html">Visual access</a></td><td>Can content be perceived through contrast, scale, spacing, and non-color cues?</td></tr>
<tr><td><a href="./screen-reader.html">Screen readers</a></td><td>Are controls named, ordered, and operable without visual position?</td></tr>
<tr><td><a href="./magnification.html">Magnification</a></td><td>Does reflow preserve context and prevent horizontal scanning?</td></tr>
<tr><td><a href="./input-motor.html">Input and motor access</a></td><td>Can tasks be completed with alternate input and reduced precision or repetition?</td></tr>
<tr><td><a href="./cognitive-learning.html">Cognitive and learning access</a></td><td>Can work be resumed, sequenced, checked, and understood without avoidable memory burden?</td></tr>
</tbody></table></div>
<p>Reference this section from a career track. Do not duplicate the guidance inside every track.</p></article><nav class="actions" aria-label="Guide navigation"><a class="button" href="../index.html">Back to guide overview</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/accessibility/index.html">Read source / contribute</a></nav></main><footer><p>Educational planning only. Verify current rules, eligibility and costs.</p><p>Privacy first: do not publish private records.</p></footer></body></html>
2 changes: 2 additions & 0 deletions docs/accessibility/input-motor.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Input and motor access — Loptr Lab</title><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><p><a class="button" href="../index.html">Guide home</a></p><h1>Input and motor access</h1></header><main id="main"><article class="brief guide"><h2>Input and motor access</h2>
<p>Identify precision, reach, repetition, pressure, timing, posture, and fatigue barriers. Consider keyboard-only use, remapping, switch access, voice input, pointing alternatives, adjustable timing, automation, ergonomic positioning, and recovery from accidental activation. Evaluate sustained real tasks, not a brief demonstration.</p></article><nav class="actions"><a class="button" href="index.html">Section overview</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/accessibility/input-motor.md">Source Markdown</a></nav></main><footer>Verify current evidence and requirements. Protect private records.</footer></body></html>
2 changes: 2 additions & 0 deletions docs/accessibility/magnification.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Magnification — Loptr Lab</title><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><p><a class="button" href="../index.html">Guide home</a></p><h1>Magnification</h1></header><main id="main"><article class="brief guide"><h2>Magnification</h2>
<p>Test operating-system and application zoom at the participant's working scale. Check reflow, pointer tracking, focus visibility, context retention, dialogs, timelines, canvases, and multi-pane layouts. A larger display may help some workflows, but it is not a substitute for software that remains operable when magnified.</p></article><nav class="actions"><a class="button" href="index.html">Section overview</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/accessibility/magnification.md">Source Markdown</a></nav></main><footer>Verify current evidence and requirements. Protect private records.</footer></body></html>
2 changes: 2 additions & 0 deletions docs/accessibility/screen-reader.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Screen-reader access — Loptr Lab</title><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><p><a class="button" href="../index.html">Guide home</a></p><h1>Screen-reader access</h1></header><main id="main"><article class="brief guide"><h2>Screen-reader access</h2>
<p>Verify meaningful names, roles, states, reading and focus order, keyboard operation, error announcements, document structure, and accessible output. Test installation, authentication, editor panes, dialogs, collaboration tools, and export—not only the primary screen. Record blockers and available workarounds without assuming that theoretical standards compliance equals usable work.</p></article><nav class="actions"><a class="button" href="index.html">Section overview</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/accessibility/screen-reader.md">Source Markdown</a></nav></main><footer>Verify current evidence and requirements. Protect private records.</footer></body></html>
2 changes: 2 additions & 0 deletions docs/accessibility/visual.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Visual access — Loptr Lab</title><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><p><a class="button" href="../index.html">Guide home</a></p><h1>Visual access</h1></header><main id="main"><article class="brief guide"><h2>Visual access</h2>
<p>Document the task and observable barrier: text size, contrast, glare, focus visibility, dense layout, color dependence, detail inspection, or eye fatigue. Required capabilities may include scalable text, reflow, high contrast, adjustable brightness, non-color cues, zoom that preserves context, and display positioning. Test the actual application; a hardware specification alone does not prove access.</p></article><nav class="actions"><a class="button" href="index.html">Section overview</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/accessibility/visual.md">Source Markdown</a></nav></main><footer>Verify current evidence and requirements. Protect private records.</footer></body></html>
6 changes: 6 additions & 0 deletions docs/case-study/01-vocational-goal.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>1. Vocational goal — Loptr Lab</title><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><a class="button" href="../index.html">Guide home</a><h1>1. Vocational goal</h1></header><main id="main"><article class="brief guide"><h2>1. Vocational goal</h2>

<p>The participant wants to pursue accessible creative-technology work that combines software, interactive media, documentation, and production support. The goal is stated as work to be performed—not as ownership of a particular device, company formation, guaranteed employment, or a claim that a program must fund the plan.</p>

<p><strong>Next:</strong> <a href="./02-work-tasks.html">Identify the work tasks</a>.</p>
</article><nav class="actions"><a class="button" href="README.html">Section overview</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/case-study/01-vocational-goal.md">Source Markdown</a></nav></main><footer>Educational guidance only. Verify decisions and protect private records.</footer></body></html>
8 changes: 8 additions & 0 deletions docs/case-study/02-work-tasks.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>2. Work tasks — Loptr Lab</title><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><a class="button" href="../index.html">Guide home</a><h1>2. Work tasks</h1></header><main id="main"><article class="brief guide"><h2>2. Work tasks</h2>

<p>Representative tasks include editing and testing code, organizing project files, producing and reviewing media, documenting decisions and provenance, collaborating through repositories, conducting source-based research, and preparing accessible demonstrations.</p>

<p>The participant distinguishes occasional tasks from sustained workflows and identifies which tasks must run concurrently. That prevents a technology list from being assembled before the work is understood.</p>

<p><strong>Next:</strong> <a href="./03-accessibility-requirements.html">Identify accessibility requirements</a>.</p>
</article><nav class="actions"><a class="button" href="README.html">Section overview</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/case-study/02-work-tasks.md">Source Markdown</a></nav></main><footer>Educational guidance only. Verify decisions and protect private records.</footer></body></html>
8 changes: 8 additions & 0 deletions docs/case-study/03-accessibility-requirements.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>3. Accessibility requirements — Loptr Lab</title><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><a class="button" href="../index.html">Guide home</a><h1>3. Accessibility requirements</h1></header><main id="main"><article class="brief guide"><h2>3. Accessibility requirements</h2>

<p>The participant describes functional needs without publishing diagnoses or private records. The plan includes readable scaling and contrast, reduced visual strain, resumable task state, low-memory-burden file handling, clear sequencing, alternate input where needed, and reliable ways to recover after interruption.</p>

<p>Each need is tied to a task and linked to the centralized <a href="../accessibility/index.html">accessibility guidance</a>, avoiding repeated or inconsistent accommodation text.</p>

<p><strong>Next:</strong> <a href="./04-technology-assessment.html">Translate requirements into a technology assessment</a>.</p>
</article><nav class="actions"><a class="button" href="README.html">Section overview</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/case-study/03-accessibility-requirements.md">Source Markdown</a></nav></main><footer>Educational guidance only. Verify decisions and protect private records.</footer></body></html>
8 changes: 8 additions & 0 deletions docs/case-study/04-technology-assessment.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>4. Technology assessment — Loptr Lab</title><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><a class="button" href="../index.html">Guide home</a><h1>4. Technology assessment</h1></header><main id="main"><article class="brief guide"><h2>4. Technology assessment</h2>

<p>The assessment converts tasks and barriers into capabilities: accessible display and input, sufficient compute for representative development and media workloads, dependable storage and backup, portable project state, and compatible collaboration tools.</p>

<p>Minimum, preferred, and alternative configurations are evaluated separately. Models and prices are not embedded here because they change; current candidates belong in dated source and quote records.</p>

<p><strong>Next:</strong> <a href="./05-funding-research.html">Research possible funding</a>.</p>
</article><nav class="actions"><a class="button" href="README.html">Section overview</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/case-study/04-technology-assessment.md">Source Markdown</a></nav></main><footer>Educational guidance only. Verify decisions and protect private records.</footer></body></html>
8 changes: 8 additions & 0 deletions docs/case-study/05-funding-research.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>5. Funding research — Loptr Lab</title><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><a class="button" href="../index.html">Guide home</a><h1>5. Funding research</h1></header><main id="main"><article class="brief guide"><h2>5. Funding research</h2>

<p>The participant identifies the relevant jurisdiction and researches programs through current official sources. General program descriptions are separated from an individual eligibility or authorization decision. Conflicts and missing facts are labeled <strong>unverified</strong>, and questions are prepared for the responsible counselor or agency.</p>

<p>Benefits, housing, business activity, and training-provider status are treated as separate authority questions rather than collapsed into one AI-generated conclusion.</p>

<p><strong>Next:</strong> <a href="./06-approval-packet.html">Assemble the approval packet</a>.</p>
</article><nav class="actions"><a class="button" href="README.html">Section overview</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/case-study/05-funding-research.md">Source Markdown</a></nav></main><footer>Educational guidance only. Verify decisions and protect private records.</footer></body></html>
8 changes: 8 additions & 0 deletions docs/case-study/06-approval-packet.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>6. Approval packet — Loptr Lab</title><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><a class="button" href="../index.html">Guide home</a><h1>6. Approval packet</h1></header><main id="main"><article class="brief guide"><h2>6. Approval packet</h2>

<p>The packet contains the vocational goal, work tasks, functional barriers, essential capabilities, minimum and preferred configurations, alternatives, a training plan where relevant, dated quotes, source-verification records, and a concise list of decisions required from the responsible human.</p>

<p>Public copies exclude identifiers and confidential documents. Work that depends on agency payment or approval does not begin until the required written authorization exists.</p>

<p><strong>Next:</strong> <a href="./07-lessons-learned.html">Review lessons learned</a>.</p>
</article><nav class="actions"><a class="button" href="../index.html">Guide home</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/case-study/06-approval-packet.md">Source Markdown</a></nav></main><footer>Educational guidance only. Verify current rules and protect private records.</footer></body></html>
12 changes: 12 additions & 0 deletions docs/case-study/07-lessons-learned.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>7. Lessons learned — Loptr Lab</title><link rel="stylesheet" href="../training.css"></head><body><a class="skip-link" href="#main">Skip to main content</a><header class="masthead"><div class="serial">LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING</div><a class="button" href="../index.html">Guide home</a><h1>7. Lessons learned</h1></header><main id="main"><article class="brief guide"><h2>7. Lessons learned</h2>

<p>• Beginning with work tasks produces a defensible plan; beginning with a desired product produces assumptions.</p>
<p>• Accessibility is a system requirement throughout the workflow, not a final checklist.</p>
<p>• AI can structure research and expose uncertainty, but it cannot make an agency decision or prove that a human completed a review.</p>
<p>• Jurisdiction, authority, source date, and verification date must stay visible.</p>
<p>• Minimum, preferred, and alternative paths make the request more resilient.</p>
<p>• Privacy improves when functional evidence is separated from identifying records.</p>
<p>• Proposed, implemented, tested, and approved are different statuses and must remain distinct.</p>

<p>Return to the <a href="../index.html">guide homepage</a> or copy the <a href="../templates/README.html">preparation templates</a> for a new plan.</p>
</article><nav class="actions"><a class="button" href="../index.html">Guide home</a><a class="button" href="https://github.com/Loptr-Lab/training/blob/main/docs/case-study/07-lessons-learned.md">Source Markdown</a></nav></main><footer>Educational guidance only. Verify current rules and protect private records.</footer></body></html>
Loading
Loading