From c9de1c5a7c9c3d779b83e20d9946afeccaaeecae Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:20:28 -0500 Subject: [PATCH 01/62] Add styled guide: Career tracks --- docs/tracks/index.html | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 docs/tracks/index.html diff --git a/docs/tracks/index.html b/docs/tracks/index.html new file mode 100644 index 0000000..c115b3e --- /dev/null +++ b/docs/tracks/index.html @@ -0,0 +1,13 @@ +Career tracks — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

Career tracks

Choose the work before the equipment

Choose the work you want to do before comparing equipment. For every track, document: work tasks, software and workflow requirements, compute requirements, accessibility considerations, minimum and preferred capabilities, and questions requiring individual assessment.

+
+ + + + + + + +
TrackBegin with these tasks
Software developmentEdit code, run tests, manage versions, collaborate.
Game developmentBuild and test interactive systems, assets, and levels.
VideoCapture, edit, review, caption, render, and deliver.
AudioRecord, edit, mix, monitor, export, and archive.
DesignResearch, compose, prototype, review, and export.
Hybrid creative technologyCombine code, media, interactive tools, and production workflows.
+

Optional project exercise: maker game systems compares a proposed digital pinball pilot with an unbuilt Duet LED chessboard design study. Their project repositories retain their own rules and approval boundaries.

+

After choosing a track, use the accessibility guidance, then build a technology plan.

+

Do not begin with a brand or device model. A product is justified only after the work and required capabilities are documented.

\ No newline at end of file From 8d4027cbb5a6afaada6a7c96bc4ac483b714a639 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:20:32 -0500 Subject: [PATCH 02/62] Add styled guide: Accessibility --- docs/accessibility/index.html | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 docs/accessibility/index.html diff --git a/docs/accessibility/index.html b/docs/accessibility/index.html new file mode 100644 index 0000000..dce73d8 --- /dev/null +++ b/docs/accessibility/index.html @@ -0,0 +1,10 @@ +Accessibility — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

Accessibility

Describe barriers without oversharing

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.

+
+ + + + + + +
AreaPlanning questions
Visual accessCan content be perceived through contrast, scale, spacing, and non-color cues?
Screen readersAre controls named, ordered, and operable without visual position?
MagnificationDoes reflow preserve context and prevent horizontal scanning?
Input and motor accessCan tasks be completed with alternate input and reduced precision or repetition?
Cognitive and learning accessCan work be resumed, sequenced, checked, and understood without avoidable memory burden?
+

Reference this section from a career track. Do not duplicate the guidance inside every track.

\ No newline at end of file From c33deff448da4b02169fbd24a8eeb0d50c5b9959 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:20:35 -0500 Subject: [PATCH 03/62] Add styled guide: Technology planning --- docs/technology-planning/index.html | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 docs/technology-planning/index.html diff --git a/docs/technology-planning/index.html b/docs/technology-planning/index.html new file mode 100644 index 0000000..3b1c4b0 --- /dev/null +++ b/docs/technology-planning/index.html @@ -0,0 +1,12 @@ +Technology planning — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

Technology planning

Turn tasks into requirements

Use this chain for every recommendation:

+
    +
  1. Vocational goal — the work outcome.
    2. +
  2. Work tasks — observable activities required by that goal.
    3. +
  3. Functional barriers — conditions that make a task inaccessible or unreliable.
    4. +
  4. Required capabilities — what the solution must do.
    5. +
  5. Minimum configuration — the least configuration that can perform the work safely and reliably.
    6. +
  6. Preferred configuration — capabilities that materially improve access, durability, or workflow.
    7. +
  7. Alternatives — lower-cost, borrowed, public-access, or differently configured paths.
    8. +
  8. Current costs and quotes — dated evidence kept outside the architecture.
    9. +
+

Classify each requested capability as essential, preferred, or optional. Never make price or brand the reason for a requirement. Use the technology-plan template and verify current products and prices with the technology-research prompt.

\ No newline at end of file From f2573b93dd569736e6e172178c96fb753dbd2dc8 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:20:37 -0500 Subject: [PATCH 04/62] Add styled guide: Funding research --- docs/funding/README.html | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 docs/funding/README.html diff --git a/docs/funding/README.html b/docs/funding/README.html new file mode 100644 index 0000000..3288c1d --- /dev/null +++ b/docs/funding/README.html @@ -0,0 +1,7 @@ +Funding research — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

Funding research

Check rules before requesting support

Funding is jurisdiction- and program-specific. Start with the jurisdiction tree, verify the responsible agency, and record the source and verification date. Listing a program never guarantees eligibility, authorization, or payment.

+ +

For another country, territory, state, province, or locality, copy the research method—not Minnesota's rules. Volatile facts such as deadlines, dollar limits, models, and program rules belong in dated, source-attributed research notes.

\ No newline at end of file From 77a12872ec24343500aec16df9b5e60219b003ce Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:20:39 -0500 Subject: [PATCH 05/62] Add styled guide: AI research prompts --- docs/prompts/README.html | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 docs/prompts/README.html diff --git a/docs/prompts/README.html b/docs/prompts/README.html new file mode 100644 index 0000000..1866fbd --- /dev/null +++ b/docs/prompts/README.html @@ -0,0 +1,12 @@ +AI research prompts — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

AI research prompts

Use AI research with human oversight

These prompts are designed to make AI research more reliable, not to replace the agency or person who makes the decision. Each prompt requires current authoritative sources, direct links, verification dates, separation of confirmed facts from uncertainty, and the word unverified instead of a guess.

+ +

Never paste credentials, government identifiers, case numbers, private correspondence, medical records, benefit letters, or confidential documents into a research prompt.

\ No newline at end of file From cd3bfc4af1be0631155d7e55af4687aa730d0cb0 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:20:42 -0500 Subject: [PATCH 06/62] Add styled guide: Preparation templates --- docs/templates/README.html | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 docs/templates/README.html diff --git a/docs/templates/README.html b/docs/templates/README.html new file mode 100644 index 0000000..136a4b6 --- /dev/null +++ b/docs/templates/README.html @@ -0,0 +1,11 @@ +Preparation templates — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

Preparation templates

Collect only the evidence you need

Use only the templates needed for your request. Keep private records outside public repositories.

+
\ No newline at end of file From d3faa56246fa7c5120d10af3697bebb86f553eec Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:20:44 -0500 Subject: [PATCH 07/62] Add styled guide: Worked example --- docs/case-study/README.html | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 docs/case-study/README.html diff --git a/docs/case-study/README.html b/docs/case-study/README.html new file mode 100644 index 0000000..8835739 --- /dev/null +++ b/docs/case-study/README.html @@ -0,0 +1,11 @@ +Worked example — Loptr Lab
LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

← Guide home

Worked example

See planning in practice

This anonymized real-world example demonstrates a process, not a guarantee of eligibility, authorization, funding, employment, or benefits treatment. Identifying details are removed. Inspect the work one stage at a time:

+
    +
  1. Vocational goal
    2. +
  2. Work tasks
    3. +
  3. Accessibility requirements
    4. +
  4. Technology assessment
    5. +
  5. Funding research
    6. +
  6. Approval packet
    7. +
  7. Lessons learned
    8. +
+

The example deliberately separates confirmed facts, proposals, implementation evidence, and decisions that only a responsible human or agency can make.

\ No newline at end of file From 2015daa3ffb59e6db620eb03ad5646434f070d74 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:21:03 -0500 Subject: [PATCH 08/62] Route training home links to styled guides --- docs/index.html | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/index.html b/docs/index.html index 001d0aa..cf92809 100644 --- a/docs/index.html +++ b/docs/index.html @@ -27,9 +27,9 @@

Start with your work,
not a computer.

A practical, accessibility-first guide to identifying the technology, training, and documentation you need for a technology or creative career.

@@ -55,20 +55,20 @@

Learn to use AI without outsourcing your judgment

  • Verify agency rules
  • Compare alternatives
  • Identify uncertainty
  • Prepare questions for the human decision-maker
    • - Open the MCP prompt library + Open the MCP prompt library

    Choose what you need next

    - - - - - - - + + + + + + +
    SectionWhat it helps you do
    Career tracksDefine work tasks before choosing products.
    AccessibilityDescribe functional barriers and reusable accommodations.
    Technology planningBuild minimum, preferred, and alternative configurations.
    Funding researchResearch jurisdiction-specific programs using current sources.
    MCP promptsMake AI research more reliable and auditable.
    TemplatesPrepare evidence, questions, quotes, and requests.
    Worked exampleInspect an anonymized process one stage at a time.
    Career tracksDefine work tasks before choosing products.
    AccessibilityDescribe functional barriers and reusable accommodations.
    Technology planningBuild minimum, preferred, and alternative configurations.
    Funding researchResearch jurisdiction-specific programs using current sources.
    MCP promptsMake AI research more reliable and auditable.
    TemplatesPrepare evidence, questions, quotes, and requests.
    Worked exampleInspect an anonymized process one stage at a time.
    From bb6c32b12746091caa1cef3029feb1f66a91f2b5 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:21:05 -0500 Subject: [PATCH 09/62] Improve guide readability and mobile layout --- docs/training.css | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/docs/training.css b/docs/training.css index d531869..115af69 100644 --- a/docs/training.css +++ b/docs/training.css @@ -38,3 +38,24 @@ footer{padding:1.5rem 1.25rem;border-top:3px solid var(--ink);display:flex;justi .checks{display:grid;grid-template-columns:repeat(auto-fit,minmax(14rem,1fr));gap:.5rem 1.5rem} .table-wrap{overflow-x:auto}table{width:100%;border-collapse:collapse}th,td{padding:.8rem;border:1px solid currentColor;text-align:left;vertical-align:top} a:focus-visible,button:focus-visible{outline:3px solid var(--orange);outline-offset:3px} + +/* Readable, consistent guide pages */ +.guide{max-width:900px;margin:0 auto;font-size:1.075rem;line-height:1.65;overflow-wrap:anywhere} +.guide h2{font-size:clamp(1.65rem,4vw,2.5rem);margin:2rem 0 .75rem;line-height:1.15} +.guide p{max-width:75ch} +.guide li{margin-bottom:.65rem;padding-left:.2rem} +.guide ul,.guide ol{padding-left:1.6rem} +.guide a{color:var(--blue);text-underline-offset:.17em;text-decoration-thickness:2px} +.guide a:hover{color:#954213} +.guide table{background:#fff;line-height:1.5} +.guide tr:first-child{font-weight:700;background:#e4eaf0} +.guide td{min-width:10rem} +.guide a:focus-visible{outline-offset:4px} +@media(max-width:700px){ + .masthead h1{font-size:clamp(2.4rem,11vw,4rem);line-height:1;overflow-wrap:break-word} + .subtitle{font-size:clamp(1.05rem,4.5vw,1.4rem);line-height:1.35;letter-spacing:.035em} + .actions{display:grid;grid-template-columns:1fr} + .button{display:block;max-width:100%;font-size:.95rem;line-height:1.35;padding:.85rem 1rem;overflow-wrap:anywhere} + .guide{font-size:1rem;padding:1.1rem;box-shadow:4px 4px 0 var(--blue)} + .guide td{min-width:8.5rem} +} \ No newline at end of file From 7604fa24362217c3f3a5363bcc5541796cad4b88 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:24:44 -0500 Subject: [PATCH 10/62] Add accessible development environment and equipment guide --- .../development-environment.html | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 docs/technology-planning/development-environment.html diff --git a/docs/technology-planning/development-environment.html b/docs/technology-planning/development-environment.html new file mode 100644 index 0000000..b784733 --- /dev/null +++ b/docs/technology-planning/development-environment.html @@ -0,0 +1,22 @@ +Development environment & equipment — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    ← Guide home

    Development environment & equipment

    Plan the work first. Then choose the hardware, software and access tools.

    +

    1. Choose your development path

    Match equipment to the real tasks you must perform, not a brand or a presumed diagnosis. You can start with an iPad or other accessible device and still document why a separate workstation is required for certain development work.

    +
    + + + + +
    PathWhat you need to demonstrateEquipment approach
    Learning and web codingEdit code, use source control, preview accessible pages and run basic testsBrowser-based editor or accessible local editor, dependable internet access, keyboard or alternate input, backup and authentication
    General software developmentRun a selected language/toolchain, debugging, automated tests, local services and possibly containersChoose a compatible local computer, remote workspace, or hybrid setup; measure memory, CPU, storage and access requirements against a representative project
    Game and media developmentRun the chosen engine, edit assets, test performance and input, export buildsDocument engine-specific CPU/GPU, RAM, SSD, display, audio/input, backup and testing hardware requirements
    Xbox console developmentUse Microsoft's supported desktop tools and approved console build/test pathWindows x64 workstation and applicable SDK/tools; approved program and development-kit access where required — not merely a retail console
    +

    2. Equipment checklist

      +
    • Compute: processor architecture, RAM, GPU and cooling appropriate to the actual language, engine and workload.
      • +
    • Storage: working SSD space for project files, packages, builds and media; separate backup or versioned recovery strategy.
      • +
    • Access: readable or magnified display, alternative input, screen reader/keyboard compatibility, usable editor and debugging interfaces.
      • +
    • Software: operating system, editor/IDE, terminal, Git, SDK, dependencies, test runner, licenses and recurring services.
      • +
    • Network: reliable internet, secure sign-in, remote access as needed, and wired connectivity only where required by testing or deployment.
      • +
    • Continuity: power, updates, support, repair, warranty, project restore and recovery if a device becomes unavailable.
      • +
    +

    3. Compare minimum, preferred and optional

    Minimum: the least accessible configuration that can complete and verify real learning or work tasks. Preferred: added capability tied to a specific workflow, accessibility or reliability gain. Optional: conveniences without a demonstrated requirement. Do not equate a faster machine with an eligibility or funding justification.

    +

    4. Existing Xbox workstation example

    The source curriculum already documents a planning target for comfortable Windows/Xbox-related development: 8-core-class CPU, 32 GB RAM, 1–2 TB NVMe SSD and an engine-appropriate discrete GPU. These are not Microsoft minimum requirements, a universal developer specification or a purchase recommendation. Its September 26, 2026 budget example must be rechecked against current offers.

    +

    Read the technical game-development source · View the dated price research

    +

    5. Make an evidence-based equipment request

    1. Identify the career goal and representative project.
    2. Record software/engine, supported operating system and required tests.
    3. Document access barriers in terms of tasks, without disclosing unnecessary medical details.
    4. Test local, cloud and hybrid alternatives against the actual workload.
    5. Make a minimum, preferred and alternative specification list.
    6. Collect comparable, dated itemized quotes, including accessible peripherals and recurring costs.
    7. Ask the responsible counselor, employer or funder to decide; do not presume approval.
    +

    Use the technology plan, equipment justification and quote comparison. Keep private records outside public repositories.

    +
    \ No newline at end of file From f7f2ac4219e0772191cdcb9d21710f0482cc682b Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:24:55 -0500 Subject: [PATCH 11/62] Surface development equipment guide in curriculum --- docs/index.html | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/index.html b/docs/index.html index cf92809..104660e 100644 --- a/docs/index.html +++ b/docs/index.html @@ -29,6 +29,7 @@

    Start with your work,
    not a computer.

    @@ -64,6 +65,7 @@

    Choose what you need next

    Career tracksDefine work tasks before choosing products. AccessibilityDescribe functional barriers and reusable accommodations. + Development equipmentCompare hardware, software, access tools and workstation requirements. Technology planningBuild minimum, preferred, and alternative configurations. Funding researchResearch jurisdiction-specific programs using current sources. MCP promptsMake AI research more reliable and auditable. From 84482306c1b4ab8a8d1ba2e631a4ed99eb6a96a2 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:24:58 -0500 Subject: [PATCH 12/62] Surface development equipment guide in curriculum --- docs/technology-planning/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/technology-planning/index.html b/docs/technology-planning/index.html index 3b1c4b0..82c5578 100644 --- a/docs/technology-planning/index.html +++ b/docs/technology-planning/index.html @@ -1,4 +1,4 @@ -Technology planning — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    ← Guide home

    Technology planning

    Turn tasks into requirements

    Use this chain for every recommendation:

    +Technology planning — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    ← Guide home

    Technology planning

    Turn tasks into requirements

    Explore development environment & equipment →

    Use this chain for every recommendation:

    1. Vocational goal — the work outcome.
    2. Work tasks — observable activities required by that goal.
      3. From 34fb8891717d673cae5e4977c81bbeb4e0165d17 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:25:01 -0500 Subject: [PATCH 13/62] Surface development equipment guide in curriculum --- docs/tracks/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tracks/index.html b/docs/tracks/index.html index c115b3e..505e459 100644 --- a/docs/tracks/index.html +++ b/docs/tracks/index.html @@ -1,4 +1,4 @@ -Career tracks — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      ← Guide home

      Career tracks

      Choose the work before the equipment

      Choose the work you want to do before comparing equipment. For every track, document: work tasks, software and workflow requirements, compute requirements, accessibility considerations, minimum and preferred capabilities, and questions requiring individual assessment.

      +Career tracks — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      ← Guide home

      Career tracks

      Choose the work before the equipment

      See development equipment requirements →

      Choose the work you want to do before comparing equipment. For every track, document: work tasks, software and workflow requirements, compute requirements, accessibility considerations, minimum and preferred capabilities, and questions requiring individual assessment.

      From 14b9693418bb9e419481f56ed76d1a56d3edcb6c Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:25:03 -0500 Subject: [PATCH 14/62] Surface development equipment guide in curriculum --- docs/tracks/software-development.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/tracks/software-development.md b/docs/tracks/software-development.md index e8015ae..15b083b 100644 --- a/docs/tracks/software-development.md +++ b/docs/tracks/software-development.md @@ -14,3 +14,7 @@ Read and edit code, navigate repositories, run builds and tests, debug, review c ## Plan Document minimum and preferred capability levels; do not name a product until the actual language, framework, test workload, collaboration method, and [accessibility needs](../accessibility/index.md) are known. Individually assess whether local builds, cloud development, or a hybrid workflow is appropriate. + +## Development equipment + +Use the [development environment and equipment guide](../technology-planning/development-environment.html) to compare local, cloud, and hybrid workflows, accessible peripherals, backup, and minimum versus preferred requirements. Do not assume that one device suits every language, toolchain, or test workload. From 4d51300c7cc56e848247312480e7d1b47b41cc93 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:25:06 -0500 Subject: [PATCH 15/62] Surface development equipment guide in curriculum --- docs/technology-planning/index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/technology-planning/index.md b/docs/technology-planning/index.md index ff76708..562fdea 100644 --- a/docs/technology-planning/index.md +++ b/docs/technology-planning/index.md @@ -12,3 +12,7 @@ Use this chain for every recommendation: 8. **Current costs and quotes** — dated evidence kept outside the architecture. Classify each requested capability as **essential**, **preferred**, or **optional**. Never make price or brand the reason for a requirement. Use the [technology-plan template](../templates/technology-plan.md) and verify current products and prices with the [technology-research prompt](../prompts/research-technology.md). + +## Development environment and equipment + +See the [development environment and equipment guide](./development-environment.html) for hardware, software, accessible input, backups, remote workspaces, and specialized game/console development requirements. From 57c6a8d4300918b0797dccb1176e30f0acef049f Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:08 -0500 Subject: [PATCH 16/62] Render accessible curriculum: Software development track --- docs/tracks/software-development.html | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 docs/tracks/software-development.html diff --git a/docs/tracks/software-development.html b/docs/tracks/software-development.html new file mode 100644 index 0000000..ff1904f --- /dev/null +++ b/docs/tracks/software-development.html @@ -0,0 +1,14 @@ +Software development track — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Software development track

      Software development track

      +

      Work tasks

      +

      Read and edit code, navigate repositories, run builds and tests, debug, review changes, manage versions, communicate decisions, and use documentation.

      +

      Required capabilities

      +
        +
      • Editor and terminal access compatible with the participant's input and reading methods
        • +
      • Enough memory and compute for the selected toolchain, tests, containers, and local services
        • +
      • Reliable version control, backups, and authentication that do not depend on inaccessible prompts
        • +
      • Multiple-window or context-switching support without losing task state
        • +
      +

      Plan

      +

      Document minimum and preferred capability levels; do not name a product until the actual language, framework, test workload, collaboration method, and accessibility needs are known. Individually assess whether local builds, cloud development, or a hybrid workflow is appropriate.

      +

      Development equipment

      +

      Use the development environment and equipment guide to compare local, cloud, and hybrid workflows, accessible peripherals, backup, and minimum versus preferred requirements. Do not assume that one device suits every language, toolchain, or test workload.

      Educational information. Check current rules and requirements. Do not publish private records.

      \ No newline at end of file From a9c62efaaaf76026e00debaf127cc9557ff78039 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:11 -0500 Subject: [PATCH 17/62] Render accessible curriculum: Game development track --- docs/tracks/game-development.html | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 docs/tracks/game-development.html diff --git a/docs/tracks/game-development.html b/docs/tracks/game-development.html new file mode 100644 index 0000000..5622020 --- /dev/null +++ b/docs/tracks/game-development.html @@ -0,0 +1,25 @@ +Game development track — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Game development track

      Game development track

      +

      Work tasks

      +

      Implement and test game systems, use an engine and source control, create or integrate assets, profile performance, run playtests, and document production handoffs.

      +

      Required capabilities

      +
        +
      • Compute and graphics appropriate to the chosen engine and target platform
        • +
      • Storage for engine versions, source assets, builds, and backups
        • +
      • Accessible editor, viewport, debugging, and collaboration workflows
        • +
      • Input and output options that support testing without making one physical interaction method mandatory
        • +
      +

      Plan

      +

      Separate requirements for programming, art, audio, design, testing, and target-platform builds. A minimum configuration must run the real learning tasks reliably; preferred capabilities must be tied to a documented barrier or workflow gain. Review accessibility needs before comparing systems.

      +

      Duet architecture provenance

      +

      For the Veiled Dominion / Duet development path, use the Duet development provenance guide. The current Duet Hackathon is the production/playtest build. The architecture lab is the extraction/validation layer, and the permanent Loptr Lab engine receives only validated reusable systems.

      +

      Do not model this as a direct production-to-engine fork. Preserve provenance and test the boundary between presentation-specific Duet code and reusable engine architecture.

      +

      Xbox development workstation path

      +

      For a Windows and Xbox game track, use a Windows x64 PC for editing, builds, debugging, and local PC playtests. An iPad can remain the planning and remote-access device, but the GDK Visual Studio extensions require x64 Windows; ARM Windows devices are unsupported for those extensions. Microsoft lists Windows 10/11 64-bit for Xbox builds, at least 30 GB free for the GDK installation, the Windows SDK, Visual Studio, and the GDK. Microsoft PC requirements · Microsoft tool requirements

      +
      TrackBegin with these tasks
      Software developmentEdit code, run tests, manage versions, collaborate.
      + + + + +
      PhaseCapability and equipmentDecision point
      PC prototypeWindows x64 desktop, suitable CPU/GPU for the chosen engine, accessible display/input, NVMe storage, backups, and wired networkingTest representative Duet or other game builds before committing to a model.
      Comfortable local developmentPlanning target: 8-core-class CPU, 32 GB RAM, 1–2 TB NVMe SSD, and a discrete GPU appropriate to the engine. These are planning targets, not Microsoft minimums.Compare the real engine workload, warranty, upgrade path, and accessibility setup.
      Xbox console buildGDK with Xbox Extensions, approved program access, and an Xbox development kit; connect workstation and kit by Ethernet on the same switch/subnet.Pursue ID@Xbox registration and concept review before budgeting for restricted console hardware.
      +

      Microsoft recommends an NVMe SSD, Cat 6a cabling and a shared Ethernet switch for console deployments; 10 GbE is an optimization for supported dev kits, not a baseline purchase. A retail Xbox in Developer Mode serves a narrower UWP test path and does not substitute for the full GDK console workflow. Microsoft workstation guidance · GDK setup · UWP FAQ

      +

      See the dated Xbox workstation purchasing example for an indicative price range, reputable purchasing channels, and quote checks. Keep the final funding request tied to documented work tasks and current quotes.

      Educational information. Check current rules and requirements. Do not publish private records.

      \ No newline at end of file From e8aae6b00f09a557cecdb2358eba84c3229e56d0 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:13 -0500 Subject: [PATCH 18/62] Render accessible curriculum: Video track --- docs/tracks/video.html | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 docs/tracks/video.html diff --git a/docs/tracks/video.html b/docs/tracks/video.html new file mode 100644 index 0000000..439a5cb --- /dev/null +++ b/docs/tracks/video.html @@ -0,0 +1,12 @@ +Video track — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Video track

      Video track

      +

      Work tasks

      +

      Plan and capture footage, ingest media, edit picture and sound, review detail, create captions, render, deliver, and archive projects.

      +

      Required capabilities

      +
        +
      • Storage capacity, sustained transfer speed, and backup appropriate to actual media formats
        • +
      • Display and scaling that support timeline, text, focus, and color-dependent work
        • +
      • Compute for the selected codecs, effects, resolution, and delivery schedule
        • +
      • Accessible shortcuts, alternate input, transcription, and caption-review tools
        • +
      +

      Plan

      +

      Test with a representative project rather than marketing claims. Document minimum delivery requirements separately from preferred turnaround time. Consider proxies, external storage, shared facilities, or remote rendering as alternatives.

      Educational information. Check current rules and requirements. Do not publish private records.

      \ No newline at end of file From 0ba2babb5ea672984dd01603ba610a4ceb4cc6f8 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:17 -0500 Subject: [PATCH 19/62] Render accessible curriculum: Audio track --- docs/tracks/audio.html | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 docs/tracks/audio.html diff --git a/docs/tracks/audio.html b/docs/tracks/audio.html new file mode 100644 index 0000000..c41e132 --- /dev/null +++ b/docs/tracks/audio.html @@ -0,0 +1,12 @@ +Audio track — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Audio track

      Audio track

      +

      Work tasks

      +

      Record, edit, arrange, mix, monitor, collaborate, export, document rights and versions, and archive sessions.

      +

      Required capabilities

      +
        +
      • Stable low-latency recording and playback for the actual track and plugin load
        • +
      • Accessible controls, meters, labeling, navigation, and keyboard or alternate-input operation
        • +
      • Suitable input/output interfaces and monitoring for the work environment
        • +
      • Storage, naming, versioning, and backup that preserve creative continuity
        • +
      +

      Plan

      +

      Separate recording, editing, mixing, live, and mobile requirements. Minimum specifications must be demonstrated against a representative session. Preferred items require a task or accessibility justification, not an assumption that more expensive equipment is automatically vocationally necessary.

      Educational information. Check current rules and requirements. Do not publish private records.

      \ No newline at end of file From db286a6e2716141d05bd7096f08224b90bde479c Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:19 -0500 Subject: [PATCH 20/62] Render accessible curriculum: Design track --- docs/tracks/design.html | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 docs/tracks/design.html diff --git a/docs/tracks/design.html b/docs/tracks/design.html new file mode 100644 index 0000000..0d2f4cd --- /dev/null +++ b/docs/tracks/design.html @@ -0,0 +1,12 @@ +Design track — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Design track

      Design track

      +

      Work tasks

      +

      Research, sketch, compose, prototype, review, revise, export, and prepare assets for production or handoff.

      +

      Required capabilities

      +
        +
      • Perceivable, scalable interfaces and non-color-only review methods
        • +
      • Input options suited to precision, repetition, fatigue, and mobility needs
        • +
      • Enough memory, graphics, display area, and storage for the actual asset sizes and tools
        • +
      • Export, collaboration, font, and color workflows compatible with intended recipients
        • +
      +

      Plan

      +

      Test common documents and prototypes at the participant's required scale and input method. Document which requirements are essential for access, which improve efficiency, and which are optional preferences.

      Educational information. Check current rules and requirements. Do not publish private records.

      \ No newline at end of file From ff3e6705e1077a715811fbc35e7ea58385a98c0e Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:22 -0500 Subject: [PATCH 21/62] Render accessible curriculum: Hybrid creative-technology track --- docs/tracks/hybrid-creative-technology.html | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 docs/tracks/hybrid-creative-technology.html diff --git a/docs/tracks/hybrid-creative-technology.html b/docs/tracks/hybrid-creative-technology.html new file mode 100644 index 0000000..cff29cf --- /dev/null +++ b/docs/tracks/hybrid-creative-technology.html @@ -0,0 +1,12 @@ +Hybrid creative-technology track — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Hybrid creative-technology track

      Hybrid creative-technology track

      +

      Work tasks

      +

      Combine code, interactive media, audio, video, design, automation, documentation, and production coordination into an integrated workflow.

      +

      Required capabilities

      +
        +
      • Interoperability across the selected tools and file formats
        • +
      • Enough compute, memory, storage, and ports for the most demanding concurrent workflow
        • +
      • A consistent accessibility layer across capture, creation, review, and delivery
        • +
      • Versioning and provenance that distinguish source, generated, edited, approved, and published material
        • +
      +

      Plan

      +

      Map the workflow stage by stage. Do not simply combine the preferred specifications from every other track. Identify the real concurrency, bottlenecks, handoffs, and accessible fallback paths, then test a representative end-to-end project.

      Educational information. Check current rules and requirements. Do not publish private records.

      \ No newline at end of file From 6ed491060fc7f58bfd438d97129a45aaf84ed895 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:25 -0500 Subject: [PATCH 22/62] Render accessible curriculum: Optional maker pathway: game rules and physical interaction --- docs/tracks/maker-game-systems.html | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 docs/tracks/maker-game-systems.html diff --git a/docs/tracks/maker-game-systems.html b/docs/tracks/maker-game-systems.html new file mode 100644 index 0000000..d5181ec --- /dev/null +++ b/docs/tracks/maker-game-systems.html @@ -0,0 +1,17 @@ +Optional maker pathway: game rules and physical interaction — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Optional maker pathway: game rules and physical interaction

      Optional maker pathway: game rules and physical interaction

      +

      Status: proposed, source-based learning pathway. The case studies are at different stages; neither is a verified hardware build or a demonstrated learner outcome.

      +

      Study two directions of translation: a pinball machine simulated in software, and turn-based Duet software considered for a physical LED chessboard. They differ in feedback tempo and access needs. Pinball demands real-time motor input and immediate state feedback; chess allows deliberate turns but must replace browser screen-reader feedback when moved to a standalone board.

      +
      + + + +
      Case studyRoleExercise and evidenceCurrent status
      Break the Grid PinballProposed hands-on digital exerciseSketch a table, implement and test one original digital mode, log motor and sensory access findingsCorridors pilot scoped; no verified playable table, learner test, or physical hardware commitment
      Duet LED chessboardDesign-analysis exerciseMap one rules transition to square selection, LED state, spoken feedback, and a parity test against the Duet multiplayer appUnbuilt concept from founder-supplied text of a Loptr Lab Patreon post; post not publicly retrievable and video unaudited
      +

      Suggested sequence

      +
        +
      1. Read each project's provenance and boundaries. Observe an existing table or review the digital reference with permission where needed.
        2. +
      2. For pinball, draft a shot/state/feedback map and test one accessible software interaction. Record what players actually understand; do not assert learning outcomes before playtests.
        3. +
      3. For Duet, draw the software-to-board boundary and an audio-first state/announcement table. Compare a sample move against the duet-solo-hackathon multiplayer app's server-authoritative state and its M1 test plan before selecting hardware.
        4. +
      4. Document an access check for both: controls, recovery from errors, non-color cues, and nonvisual state. Contrast real-time versus turn-based demands.
        5. +
      5. Scope physical components, budget, maintenance, and maker supervision only after the relevant software and accessibility questions are answered.
        6. +
      +

      This index is a pointer, not approval to build, a partnership with a venue or artist, a funding promise, or a transfer of project ownership. Corridors and Duet keep their own rules and release decisions. Generalized lessons can inform the game development and hybrid creative technology tracks; Veiled Dominion changes require its own engine review.

      Educational information. Check current rules and requirements. Do not publish private records.

      \ No newline at end of file From 875297feb19beb35f5bfeb79d72d399380fb0a0d Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:43 -0500 Subject: [PATCH 23/62] Style curriculum reference Veiled Dominion / Duet development provenance --- docs/tracks/duet-development-provenance.html | 77 ++++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 docs/tracks/duet-development-provenance.html diff --git a/docs/tracks/duet-development-provenance.html b/docs/tracks/duet-development-provenance.html new file mode 100644 index 0000000..dec56b8 --- /dev/null +++ b/docs/tracks/duet-development-provenance.html @@ -0,0 +1,77 @@ +Veiled Dominion / Duet development provenance — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Veiled Dominion / Duet development provenance

      Veiled Dominion / Duet development provenance

      +

      This is the development-training reference for the current Duet architecture. It teaches the actual lineage from the original Pulsr work through the current production/playtest build, the architecture laboratory, and the permanent Loptr Lab engine.

      +

      The source-of-truth flow

      +

      ```text

      +

      ORIGINAL DUET

      +

      Pulsr

      +

      │

      +

      ▼

      +

      MORTIS

      +

      Pulsr

      +

      │

      +

      ▼

      +

      DUET HACKATHON

      +

      CURRENT PRODUCTION / PLAYTEST BUILD

      +

      │

      +

      │ extract + validate architecture

      +

      ▼

      +

      DUET ARCHITECTURE LAB

      +

      ibloud/duet_engine_architecture

      +

      │

      +

      │ graduate reusable systems

      +

      ▼

      +

      LOPTR LAB PERMANENT ENGINE

      +

      Loptr-Lab/veiled-dominion-engine

      +

      │

      +

      ▼

      +

      FUTURE DUET / OTHER BUILDS

      +

      ```

      +

      The important boundary is that Duet Hackathon is the current production/playtest build. It is not a separate historical layer beneath production.

      +

      Development rule

      +

      Do not fork the current Duet Hackathon playtest directly into the permanent Loptr Lab engine.

      +

      The current Duet Hackathon remains the working production/playtest source. The architecture repository is the extraction and validation laboratory: mechanics, accessibility patterns, content contracts, tests, and build/distribution practices are isolated there so they can be proven independently. Only validated reusable systems graduate into the permanent engine.

      +

      Repository roles

      +

      | Layer | Repository / artifact | Development role |

      +

      | --- | --- | --- |

      +

      | Original Duet | Pulsr: `pulsr.social/ibloud` | Original Duet lineage/reference |

      +

      | Mortis | Pulsr: `pulsr.social/mortis` | Related earlier Pulsr lineage/reference |

      +

      | Duet Hackathon | Current production/playtest build | Working source for extraction and validation |

      +

      | Architecture Lab | ibloud/duet_engine_architecture | Extract, isolate, test, document, and validate reusable architecture |

      +

      | Permanent Engine | Loptr-Lab/veiled-dominion-engine | Long-lived reusable engine; receive validated systems |

      +

      | Playable distribution | Veiled Dominion: Duet on itch.io | A later playable distribution artifact, not the original Duet source |

      +

      The Pulsr references above preserve provenance supplied for this project; they are not a claim that their current pages have been independently archived or verified here.

      +

      What belongs in the architecture lab

      +

      The lab may contain:

      +

      • Rebirth / Death mechanics and extracted rule contracts

      +

      • Radius of Ruin and Sanctuary state behavior

      +

      • Veiled-state behavior

      +

      • screen-reader-first command paths

      +

      • keyboard and visual-board parity

      +

      • audio cues

      +

      • content and actor contracts

      +

      • runtime smoke tests

      +

      • reproducible browser and itch builds

      +

      • GitHub Pages distribution

      +

      • architecture notes explaining what was learned from the current playtest

      +

      The lab should make the boundary visible: the production/playtest build proves the game experience; the lab proves which pieces can become reusable architecture.

      +

      What graduates to the permanent engine

      +

      A piece is ready to move toward the permanent engine when it has:

      +

      1. a documented contract;

      +

      2. tests that describe its behavior;

      +

      3. an explicit accessibility requirement where applicable;

      +

      4. clear ownership/provenance;

      +

      5. no accidental dependency on the demo page, fixture, or presentation layer;

      +

      6. a reason to be reusable beyond one Duet build.

      +

      Graduation is therefore extraction and validation, not a blind fork.

      +

      Training exercise

      +

      When extending Duet, record each proposed change as one of:

      +

      • reference — observed in the current production/playtest build or earlier documented lineage;

      +

      • experiment — implemented in the architecture lab to test an idea;

      +

      • validated — supported by tests and suitable for extraction;

      +

      • engine — accepted into the permanent engine;

      +

      • future build — consumes the permanent engine rather than recreating the prototype.

      +

      This classification prevents the development history from collapsing into a false single code lineage.

      +

      Related source

      +

      • Duet architecture lab

      +

      • Permanent Veiled Dominion engine

      +

      • Veiled Dominion: Duet playable distribution

      Verify current evidence and requirements. Protect private records.
      \ No newline at end of file From 709207017fc6065b39d51ddbed899bb554da06e4 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:47 -0500 Subject: [PATCH 24/62] Style curriculum reference Visual access --- docs/accessibility/visual.html | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 docs/accessibility/visual.html diff --git a/docs/accessibility/visual.html b/docs/accessibility/visual.html new file mode 100644 index 0000000..26682dc --- /dev/null +++ b/docs/accessibility/visual.html @@ -0,0 +1,2 @@ +Visual access — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Visual access

      Visual access

      +

      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.

      Verify current evidence and requirements. Protect private records.
      \ No newline at end of file From 4f0f56b1c9e4247dfd6945ffce9575c2e434eccb Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:49 -0500 Subject: [PATCH 25/62] Style curriculum reference Screen-reader access --- docs/accessibility/screen-reader.html | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 docs/accessibility/screen-reader.html diff --git a/docs/accessibility/screen-reader.html b/docs/accessibility/screen-reader.html new file mode 100644 index 0000000..a435057 --- /dev/null +++ b/docs/accessibility/screen-reader.html @@ -0,0 +1,2 @@ +Screen-reader access — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Screen-reader access

      Screen-reader access

      +

      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.

      Verify current evidence and requirements. Protect private records.
      \ No newline at end of file From a4072386a3e421bc2305cbbabddd3e84fe5efc93 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:53 -0500 Subject: [PATCH 26/62] Style curriculum reference Magnification --- docs/accessibility/magnification.html | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 docs/accessibility/magnification.html diff --git a/docs/accessibility/magnification.html b/docs/accessibility/magnification.html new file mode 100644 index 0000000..f908404 --- /dev/null +++ b/docs/accessibility/magnification.html @@ -0,0 +1,2 @@ +Magnification — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Magnification

      Magnification

      +

      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.

      Verify current evidence and requirements. Protect private records.
      \ No newline at end of file From ddfec078a7b89018b4bd310f3f94f728f0077868 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:56 -0500 Subject: [PATCH 27/62] Style curriculum reference Input and motor access --- docs/accessibility/input-motor.html | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 docs/accessibility/input-motor.html diff --git a/docs/accessibility/input-motor.html b/docs/accessibility/input-motor.html new file mode 100644 index 0000000..091c559 --- /dev/null +++ b/docs/accessibility/input-motor.html @@ -0,0 +1,2 @@ +Input and motor access — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Input and motor access

      Input and motor access

      +

      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.

      Verify current evidence and requirements. Protect private records.
      \ No newline at end of file From 92a4e636c968ccf3b859f4c80fdf927fa3f310dd Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:28:58 -0500 Subject: [PATCH 28/62] Style curriculum reference Cognitive and learning access --- docs/accessibility/cognitive-learning.html | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 docs/accessibility/cognitive-learning.html diff --git a/docs/accessibility/cognitive-learning.html b/docs/accessibility/cognitive-learning.html new file mode 100644 index 0000000..2bd393c --- /dev/null +++ b/docs/accessibility/cognitive-learning.html @@ -0,0 +1,2 @@ +Cognitive and learning access — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Cognitive and learning access

      Cognitive and learning access

      +

      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.

      Verify current evidence and requirements. Protect private records.
      \ No newline at end of file From bb3510b084c65574a25d59b27fe35d4e68ff8fc2 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:29:01 -0500 Subject: [PATCH 29/62] Style curriculum reference Xbox development workstation: dated purchasing example --- .../xbox-workstation-example.html | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 docs/technology-planning/xbox-workstation-example.html diff --git a/docs/technology-planning/xbox-workstation-example.html b/docs/technology-planning/xbox-workstation-example.html new file mode 100644 index 0000000..b9c0e6b --- /dev/null +++ b/docs/technology-planning/xbox-workstation-example.html @@ -0,0 +1,15 @@ +Xbox development workstation: dated purchasing example — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      Guide home

      Xbox development workstation: dated purchasing example

      Xbox development workstation: dated purchasing example

      +

      Checked September 26, 2026 (US market). These are planning ranges, not quotes or guaranteed prices. Recheck stock, seller, configuration, taxes, shipping, and return terms before any purchase or funding request. Use the game development track to establish requirements first, and record actual offers in the quote comparison.

      +

      Fair planning range

      +

      | Item | Indicative US price | Basis and purchase channel |

      +

      | --- | ---: | --- |

      +

      | New Windows x64 desktop with 32 GB RAM, 1–2 TB SSD and midrange discrete GPU | $1,500–$2,200 | On September 26, Best Buy's RTX 5060 desktop listings showed an MSI i5-14400F/32 GB/2 TB/RTX 5060 offer around $1,543; RTX 5060 Ti listings included a 32 GB/1 TB MSI desktop around $1,740. Listing prices change and may include marketplace offers. |

      +

      | Display, accessible keyboard/mouse or controller, headset, backup storage, and Ethernet supplies | $250–$700 allowance | Budget placeholder, not a verified bundle quote. Reuse existing accessible equipment where suitable; obtain itemized offers for missing pieces. |

      +

      | Planning total for PC stage | $1,750–$2,900 before tax | Sum of the desktop range and peripheral allowance, not a seller quote. |

      +

      | Dedicated Xbox development kit and console tooling | Quote/access required | Do not assign a retail Xbox price to a dev kit. Console builds use GDK with Xbox Extensions; ID@Xbox registration, concept review, and agreements govern access. |

      +

      For a trustworthy purchase, compare direct manufacturer stores such as Dell or Lenovo, and Best Buy items sold by Best Buy. Verify the seller line, exact CPU/GPU, installed RAM, SSD capacity, Windows x64, warranty, returns, and whether monitor/peripherals are included. A marketplace listing on a reputable site is not necessarily sold or warranted by that retailer. Seek two itemized, dated quotes for the same capability set.

      +

      Stage the decision

      +

      1. Validate the chosen game engine and representative project on a Windows x64 PC. An iPad may connect remotely, but confirm that editor, debugger, sound, controller, and accessible input remain usable over that connection.

      +

      2. Choose 32 GB RAM and 1–2 TB NVMe as a comfortable planning target, then adjust based on measured workloads. Microsoft's hard GDK installation space figure is 30 GB, not a complete project storage requirement. Microsoft development PC requirements.

      +

      3. Defer dedicated kit, 10 GbE switch, 4K HDR display, and console-specific purchases until a console build and test plan justifies them. Microsoft recommends NVMe and wired networking for console deployment; its 10 GbE configuration is for faster supported dev-kit transfers.

      +

      4. Record quote date, seller of record, warranty, taxes, shipping, accessible peripherals, recurring software costs, and alternative configurations in the quote comparison. Explain each cost through the work tasks and access needs, not the brand.

      Verify current evidence and requirements. Protect private records.
      \ No newline at end of file From d3e0733e00bf771cfd934ebdc42cd01dcb41abd8 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:29:10 -0500 Subject: [PATCH 30/62] Navigate from guide overview to styled lessons --- docs/tracks/index.html | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/tracks/index.html b/docs/tracks/index.html index 505e459..17b5e41 100644 --- a/docs/tracks/index.html +++ b/docs/tracks/index.html @@ -1,13 +1,13 @@ Career tracks — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      ← Guide home

      Career tracks

      Choose the work before the equipment

      See development equipment requirements →

      Choose the work you want to do before comparing equipment. For every track, document: work tasks, software and workflow requirements, compute requirements, accessibility considerations, minimum and preferred capabilities, and questions requiring individual assessment.

      - - - - - - + + + + + +
      TrackBegin with these tasks
      Software developmentEdit code, run tests, manage versions, collaborate.
      Game developmentBuild and test interactive systems, assets, and levels.
      VideoCapture, edit, review, caption, render, and deliver.
      AudioRecord, edit, mix, monitor, export, and archive.
      DesignResearch, compose, prototype, review, and export.
      Hybrid creative technologyCombine code, media, interactive tools, and production workflows.
      Software developmentEdit code, run tests, manage versions, collaborate.
      Game developmentBuild and test interactive systems, assets, and levels.
      VideoCapture, edit, review, caption, render, and deliver.
      AudioRecord, edit, mix, monitor, export, and archive.
      DesignResearch, compose, prototype, review, and export.
      Hybrid creative technologyCombine code, media, interactive tools, and production workflows.
      -

      Optional project exercise: maker game systems compares a proposed digital pinball pilot with an unbuilt Duet LED chessboard design study. Their project repositories retain their own rules and approval boundaries.

      +

      Optional project exercise: maker game systems compares a proposed digital pinball pilot with an unbuilt Duet LED chessboard design study. Their project repositories retain their own rules and approval boundaries.

      After choosing a track, use the accessibility guidance, then build a technology plan.

      -

      Do not begin with a brand or device model. A product is justified only after the work and required capabilities are documented.

      Educational planning only. Verify current rules, eligibility and costs.

      Privacy first: do not publish private records.

      \ No newline at end of file +

      Do not begin with a brand or device model. A product is justified only after the work and required capabilities are documented.

      Educational planning only. Verify current rules, eligibility and costs.

      Privacy first: do not publish private records.

      \ No newline at end of file From 9ef9db8b1e3b3531d0490beb8e68ad312862e857 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:29:14 -0500 Subject: [PATCH 31/62] Navigate from guide overview to styled lessons --- docs/accessibility/index.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/accessibility/index.html b/docs/accessibility/index.html index dce73d8..f43860b 100644 --- a/docs/accessibility/index.html +++ b/docs/accessibility/index.html @@ -1,10 +1,10 @@ Accessibility — Loptr Lab
      LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

      ← Guide home

      Accessibility

      Describe barriers without oversharing

      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.

      - - - - - + + + + +
      AreaPlanning questions
      Visual accessCan content be perceived through contrast, scale, spacing, and non-color cues?
      Screen readersAre controls named, ordered, and operable without visual position?
      MagnificationDoes reflow preserve context and prevent horizontal scanning?
      Input and motor accessCan tasks be completed with alternate input and reduced precision or repetition?
      Cognitive and learning accessCan work be resumed, sequenced, checked, and understood without avoidable memory burden?
      Visual accessCan content be perceived through contrast, scale, spacing, and non-color cues?
      Screen readersAre controls named, ordered, and operable without visual position?
      MagnificationDoes reflow preserve context and prevent horizontal scanning?
      Input and motor accessCan tasks be completed with alternate input and reduced precision or repetition?
      Cognitive and learning accessCan work be resumed, sequenced, checked, and understood without avoidable memory burden?
      -

      Reference this section from a career track. Do not duplicate the guidance inside every track.

      Educational planning only. Verify current rules, eligibility and costs.

      Privacy first: do not publish private records.

      \ No newline at end of file +

      Reference this section from a career track. Do not duplicate the guidance inside every track.

    Educational planning only. Verify current rules, eligibility and costs.

    Privacy first: do not publish private records.

    \ No newline at end of file From 32c809f796026f344abcf53a2ce7c78b52df963b Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:29:17 -0500 Subject: [PATCH 32/62] Navigate from guide overview to styled lessons --- docs/technology-planning/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/technology-planning/index.html b/docs/technology-planning/index.html index 82c5578..10bc115 100644 --- a/docs/technology-planning/index.html +++ b/docs/technology-planning/index.html @@ -9,4 +9,4 @@
  • Alternatives — lower-cost, borrowed, public-access, or differently configured paths.
  • Current costs and quotes — dated evidence kept outside the architecture.
    • -

    Classify each requested capability as essential, preferred, or optional. Never make price or brand the reason for a requirement. Use the technology-plan template and verify current products and prices with the technology-research prompt.

    \ No newline at end of file +

    Classify each requested capability as essential, preferred, or optional. Never make price or brand the reason for a requirement. Use the technology-plan template and verify current products and prices with the technology-research prompt.

    \ No newline at end of file From 3d4126cee938c580fdef7f8da85241ce0b28888e Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:29:19 -0500 Subject: [PATCH 33/62] Navigate from guide overview to styled lessons --- docs/funding/README.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/funding/README.html b/docs/funding/README.html index 3288c1d..6272d4d 100644 --- a/docs/funding/README.html +++ b/docs/funding/README.html @@ -1,7 +1,7 @@ Funding research — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    ← Guide home

    Funding research

    Check rules before requesting support

    Funding is jurisdiction- and program-specific. Start with the jurisdiction tree, verify the responsible agency, and record the source and verification date. Listing a program never guarantees eligibility, authorization, or payment.

    -

    For another country, territory, state, province, or locality, copy the research method—not Minnesota's rules. Volatile facts such as deadlines, dollar limits, models, and program rules belong in dated, source-attributed research notes.

    \ No newline at end of file +

    For another country, territory, state, province, or locality, copy the research method—not Minnesota's rules. Volatile facts such as deadlines, dollar limits, models, and program rules belong in dated, source-attributed research notes.

    \ No newline at end of file From 267e03ecc332eda3185ca27c45acac34e836a637 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:29:22 -0500 Subject: [PATCH 34/62] Navigate from guide overview to styled lessons --- docs/prompts/README.html | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/prompts/README.html b/docs/prompts/README.html index 1866fbd..cee71ce 100644 --- a/docs/prompts/README.html +++ b/docs/prompts/README.html @@ -1,12 +1,12 @@ AI research prompts — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    ← Guide home

    AI research prompts

    Use AI research with human oversight

    These prompts are designed to make AI research more reliable, not to replace the agency or person who makes the decision. Each prompt requires current authoritative sources, direct links, verification dates, separation of confirmed facts from uncertainty, and the word unverified instead of a guess.

    -

    Never paste credentials, government identifiers, case numbers, private correspondence, medical records, benefit letters, or confidential documents into a research prompt.

    \ No newline at end of file +

    Never paste credentials, government identifiers, case numbers, private correspondence, medical records, benefit letters, or confidential documents into a research prompt.

    \ No newline at end of file From ec0dac97d334b5d5d620e07ec009f4cc0da861fd Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:29:26 -0500 Subject: [PATCH 35/62] Navigate from guide overview to styled lessons --- docs/templates/README.html | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/templates/README.html b/docs/templates/README.html index 136a4b6..6f1b14f 100644 --- a/docs/templates/README.html +++ b/docs/templates/README.html @@ -1,11 +1,11 @@ Preparation templates — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    ← Guide home

    Preparation templates

    Collect only the evidence you need

    Use only the templates needed for your request. Keep private records outside public repositories.

    \ No newline at end of file +
  • Needs statement
    • +
  • Technology plan
    • +
  • Equipment justification
    • +
  • Training plan
    • +
  • Quote comparison
    • +
  • Counselor or decision-maker questions
    • +
  • Approval packet checklist
    • +
  • Source-verification record
    • + \ No newline at end of file From f93009ae9d959e0283174ff201b7140a76976af8 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:29:28 -0500 Subject: [PATCH 36/62] Navigate from guide overview to styled lessons --- docs/case-study/README.html | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/case-study/README.html b/docs/case-study/README.html index 8835739..8070b59 100644 --- a/docs/case-study/README.html +++ b/docs/case-study/README.html @@ -1,11 +1,11 @@ Worked example — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    ← Guide home

    Worked example

    See planning in practice

    This anonymized real-world example demonstrates a process, not a guarantee of eligibility, authorization, funding, employment, or benefits treatment. Identifying details are removed. Inspect the work one stage at a time:

      -
    1. Vocational goal
      2. -
    2. Work tasks
      3. -
    3. Accessibility requirements
      4. -
    4. Technology assessment
      5. -
    5. Funding research
      6. -
    6. Approval packet
      7. -
    7. Lessons learned
      8. +
    8. Vocational goal
      9. +
    9. Work tasks
      10. +
    10. Accessibility requirements
      11. +
    11. Technology assessment
      12. +
    12. Funding research
      13. +
    13. Approval packet
      14. +
    14. Lessons learned
    -

    The example deliberately separates confirmed facts, proposals, implementation evidence, and decisions that only a responsible human or agency can make.

    \ No newline at end of file +

    The example deliberately separates confirmed facts, proposals, implementation evidence, and decisions that only a responsible human or agency can make.

    \ No newline at end of file From 73b247dfe45a51386078e129435181e830f9e4aa Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:29:48 -0500 Subject: [PATCH 37/62] Style curriculum: Prompt: safe research practices --- docs/prompts/safe-research.html | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 docs/prompts/safe-research.html diff --git a/docs/prompts/safe-research.html b/docs/prompts/safe-research.html new file mode 100644 index 0000000..20ba625 --- /dev/null +++ b/docs/prompts/safe-research.html @@ -0,0 +1,4 @@ +Prompt: safe research practices — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Prompt: safe research practices

    Prompt: safe research practices

    + +
    Help me research the following question without requesting or exposing private identifiers: [question]. Use current authoritative sources and link directly to each source. Record the date each source was checked. Separate confirmed facts, reasonable inferences, and unresolved questions. Mark anything not supported by a current authoritative source as unverified. Identify the human or agency that has authority to decide this question and give me questions to ask them. Do not claim that AI research establishes eligibility, approval, legal status, or funding.
    +
    \ No newline at end of file From cf9e20ebb73e3512d7cc2b1d1e624d9f950c9527 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:29:50 -0500 Subject: [PATCH 38/62] Style curriculum: Prompt: find programs --- docs/prompts/find-programs.html | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 docs/prompts/find-programs.html diff --git a/docs/prompts/find-programs.html b/docs/prompts/find-programs.html new file mode 100644 index 0000000..065533d --- /dev/null +++ b/docs/prompts/find-programs.html @@ -0,0 +1,4 @@ +Prompt: find programs — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Prompt: find programs

    Prompt: find programs

    + +
    Find programs in [jurisdiction] that may relate to [vocational goal or documented need]. Start with current official government, educational, or program-owner sources. For each candidate, provide its exact name, responsible authority, official link, source verification date, stated purpose, and how a person applies or asks a question. Separate confirmed facts from possible relevance. Mark unconfirmed fit or availability as unverified. Do not predict eligibility or approval; identify the human decision-maker.
    +
    \ No newline at end of file From 81989fb00f8a6752327e878d1bbd88cfb30c2a90 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:29:54 -0500 Subject: [PATCH 39/62] Style curriculum: Prompt: verify eligibility information --- docs/prompts/verify-eligibility.html | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 docs/prompts/verify-eligibility.html diff --git a/docs/prompts/verify-eligibility.html b/docs/prompts/verify-eligibility.html new file mode 100644 index 0000000..5f080a4 --- /dev/null +++ b/docs/prompts/verify-eligibility.html @@ -0,0 +1,4 @@ +Prompt: verify eligibility information — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Prompt: verify eligibility information

    Prompt: verify eligibility information

    + +
    Audit the claim [claim] for [program and jurisdiction]. Use current authoritative sources, link to the controlling or most direct source, and state the date verified. Quote only the minimum language needed. Distinguish general eligibility rules from an individual decision, identify exceptions or missing facts, and mark unsupported claims as unverified. State who has authority to decide and prepare concise questions for that person. Do not request personal identifiers or confidential records.
    +
    \ No newline at end of file From 8294ef8101ec6ed976577f224f333bb5df6b07b8 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:29:57 -0500 Subject: [PATCH 40/62] Style curriculum: Prompt: research technology --- docs/prompts/research-technology.html | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 docs/prompts/research-technology.html diff --git a/docs/prompts/research-technology.html b/docs/prompts/research-technology.html new file mode 100644 index 0000000..a5c4953 --- /dev/null +++ b/docs/prompts/research-technology.html @@ -0,0 +1,4 @@ +Prompt: research technology — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Prompt: research technology

    Prompt: research technology

    + +
    Research technology capabilities for these work tasks: [tasks] and these functional barriers: [barriers]. Begin with required capabilities, then identify minimum, preferred, and alternative configurations. Use current manufacturer documentation and independent primary technical sources where available; include links and verification dates. Treat prices, availability, models, and specifications as dated facts. Separate verified specifications from assumptions and mark gaps unverified. Do not choose a product solely by brand, popularity, or price.
    +
    \ No newline at end of file From a04e890cd9d903dd24eda9710fb3589643081c62 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:14 -0500 Subject: [PATCH 41/62] Style curriculum: Prompt: compare costs and alternatives --- docs/prompts/compare-costs.html | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 docs/prompts/compare-costs.html diff --git a/docs/prompts/compare-costs.html b/docs/prompts/compare-costs.html new file mode 100644 index 0000000..9ec7f4c --- /dev/null +++ b/docs/prompts/compare-costs.html @@ -0,0 +1,4 @@ +Prompt: compare costs and alternatives — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Prompt: compare costs and alternatives

    Prompt: compare costs and alternatives

    + +
    Compare current ways to meet these documented capabilities: [capabilities] in [location/jurisdiction]. Include purchase, refurbishment, borrowing, public or maker-space access, training-lab access, cloud or remote services, and phased acquisition where relevant. Use current source links and verification dates. Separate one-time and recurring costs, note prerequisites and accessibility tradeoffs, and mark missing or changing information unverified. Do not treat the cheapest option as equivalent unless it performs the required tasks accessibly.
    +
    \ No newline at end of file From 5e87e102499b2d38bf3e9869790debb50f1e0bb7 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:17 -0500 Subject: [PATCH 42/62] Style curriculum: Prompt: build a request --- docs/prompts/build-request.html | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 docs/prompts/build-request.html diff --git a/docs/prompts/build-request.html b/docs/prompts/build-request.html new file mode 100644 index 0000000..3d06770 --- /dev/null +++ b/docs/prompts/build-request.html @@ -0,0 +1,4 @@ +Prompt: build a request — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Prompt: build a request

    Prompt: build a request

    + +
    Draft a preparation document for [human decision-maker] using only these confirmed inputs: [goal, tasks, barriers, capabilities, verified sources]. Organize it as goal, work tasks, functional barriers, essential capabilities, minimum configuration, preferred configuration, alternatives considered, current quotes, uncertainties, and questions requiring a decision. Do not invent facts, diagnoses, eligibility, authorization, or approval. Mark absent evidence unverified and flag every statement that needs human confirmation.
    +
    \ No newline at end of file From df81bece8f74f8759eb23433609e1742933e8d9e Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:20 -0500 Subject: [PATCH 43/62] Style curriculum: Prompt: audit existing information --- docs/prompts/audit-information.html | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 docs/prompts/audit-information.html diff --git a/docs/prompts/audit-information.html b/docs/prompts/audit-information.html new file mode 100644 index 0000000..6816f5e --- /dev/null +++ b/docs/prompts/audit-information.html @@ -0,0 +1,4 @@ +Prompt: audit existing information — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Prompt: audit existing information

    Prompt: audit existing information

    + +
    Audit the following material for outdated facts, unsupported assumptions, duplicated guidance, privacy risk, and claims that only a human authority can make: [material]. Check current authoritative sources and link them with verification dates. Classify each claim as confirmed, contradicted, uncertain, or unverified. Identify volatile facts that should move into dated research notes. Preserve substantive content unless you can state why it is superseded or intentionally retired.
    +
    \ No newline at end of file From dbe0db6664a1593ed3c79b6be7c228a9e61ce451 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:22 -0500 Subject: [PATCH 44/62] Style curriculum: Prompt: adapt research to another jurisdiction --- docs/prompts/adapt-jurisdiction.html | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 docs/prompts/adapt-jurisdiction.html diff --git a/docs/prompts/adapt-jurisdiction.html b/docs/prompts/adapt-jurisdiction.html new file mode 100644 index 0000000..718de41 --- /dev/null +++ b/docs/prompts/adapt-jurisdiction.html @@ -0,0 +1,4 @@ +Prompt: adapt research to another jurisdiction — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Prompt: adapt research to another jurisdiction

    Prompt: adapt research to another jurisdiction

    + +
    Adapt this research method—not its conclusions—from [current jurisdiction] to [new jurisdiction] for [question]. Identify the correct levels of authority and current official sources in the new jurisdiction. Provide links and verification dates, distinguish confirmed facts from uncertainty, and mark unsupported mappings unverified. Do not assume that program names, eligibility, funding, deadlines, appeals, or decision-makers transfer between jurisdictions.
    +
    \ No newline at end of file From f6e4c1b980b360d1630802315606b6bd80b91804 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:24 -0500 Subject: [PATCH 45/62] Style curriculum: Needs statement --- docs/templates/needs-statement.html | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 docs/templates/needs-statement.html diff --git a/docs/templates/needs-statement.html b/docs/templates/needs-statement.html new file mode 100644 index 0000000..317294f --- /dev/null +++ b/docs/templates/needs-statement.html @@ -0,0 +1,12 @@ +Needs statement — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Needs statement

    Needs statement

    + +

    • Vocational goal:

    +

    • Work tasks affected:

    +

    • Functional barrier for each task:

    +

    • Capability needed:

    +

    • Current method and why it is insufficient:

    +

    • Evidence or demonstration available:

    +

    • Questions requiring human assessment:

    + +

    Describe function, not unnecessary medical history. Keep identifying records outside public workspaces.

    +
    \ No newline at end of file From 7d86f422f10ab60ca1ef8bee2881436631332b9b Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:27 -0500 Subject: [PATCH 46/62] Style curriculum: Technology plan --- docs/templates/technology-plan.html | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 docs/templates/technology-plan.html diff --git a/docs/templates/technology-plan.html b/docs/templates/technology-plan.html new file mode 100644 index 0000000..65db51f --- /dev/null +++ b/docs/templates/technology-plan.html @@ -0,0 +1,8 @@ +Technology plan — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Technology plan

    Technology plan

    + +

    | Work task | Barrier | Required capability | Minimum | Preferred | Alternatives | Evidence needed |

    +

    | --- | --- | --- | --- | --- | --- | --- |

    +

    | | | | | | | |

    + +

    Classify every capability as essential, preferred, or optional. Put dated models, specifications, prices, and quotes in the evidence column or a linked research record.

    +
    \ No newline at end of file From 26866c6606242bad087421a4e696548348cc467f Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:29 -0500 Subject: [PATCH 47/62] Style curriculum: Equipment justification --- docs/templates/equipment-justification.html | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 docs/templates/equipment-justification.html diff --git a/docs/templates/equipment-justification.html b/docs/templates/equipment-justification.html new file mode 100644 index 0000000..e372a60 --- /dev/null +++ b/docs/templates/equipment-justification.html @@ -0,0 +1,13 @@ +Equipment justification — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Equipment justification

    Equipment justification

    + +

    • Item or configuration:

    +

    • Work tasks it enables:

    +

    • Functional barrier addressed:

    +

    • Essential capability provided:

    +

    • Minimum acceptable specification and why:

    +

    • Preferred specification and material benefit:

    +

    • Alternatives considered:

    +

    • Representative workflow test:

    +

    • Current dated sources and quotes:

    +

    • Decision still required:

    +
    \ No newline at end of file From 64566c6851cdc7f253f4c3b030563bac27a598f3 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:32 -0500 Subject: [PATCH 48/62] Style curriculum: Training plan --- docs/templates/training-plan.html | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 docs/templates/training-plan.html diff --git a/docs/templates/training-plan.html b/docs/templates/training-plan.html new file mode 100644 index 0000000..ad4b420 --- /dev/null +++ b/docs/templates/training-plan.html @@ -0,0 +1,13 @@ +Training plan — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING

    Guide home

    Training plan

    Training plan

    + +

    • Vocational outcome:

    +

    • Entry skills and evidence:

    +

    • Learning objectives:

    +

    • Accessible instruction or participation needs:

    +

    • Modules and sequence:

    +

    • Practice artifacts:

    +

    • Assessment method:

    +

    • Completion evidence:

    +

    • Human support or decision points:

    +

    • Review date:

    +
    \ No newline at end of file From 20b475551a65e734477d36dd87d34f559250afdb Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:48 -0500 Subject: [PATCH 49/62] Style curriculum: Quote comparison --- docs/templates/quote-comparison.html | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 docs/templates/quote-comparison.html diff --git a/docs/templates/quote-comparison.html b/docs/templates/quote-comparison.html new file mode 100644 index 0000000..c71934d --- /dev/null +++ b/docs/templates/quote-comparison.html @@ -0,0 +1,8 @@ +Quote comparison — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    Quote comparison

    Quote comparison

    + +

    | Date checked | Vendor/source | Configuration | Required capabilities met | One-time cost | Recurring cost | Availability | Accessibility notes |

    +

    | --- | --- | --- | --- | --- | --- | --- | --- |

    +

    | | | | | | | | |

    + +

    Compare like-for-like configurations. Record taxes, shipping, warranties, subscriptions, peripherals, training, and return constraints where material.

    +
    \ No newline at end of file From 9ff12845d2ad81404b0706463a52013ed4d93059 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:51 -0500 Subject: [PATCH 50/62] Style curriculum: Questions for a counselor or decision-maker --- docs/templates/decision-maker-questions.html | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 docs/templates/decision-maker-questions.html diff --git a/docs/templates/decision-maker-questions.html b/docs/templates/decision-maker-questions.html new file mode 100644 index 0000000..dd51515 --- /dev/null +++ b/docs/templates/decision-maker-questions.html @@ -0,0 +1,11 @@ +Questions for a counselor or decision-maker — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    Questions for a counselor or decision-maker

    Questions for a counselor or decision-maker

    + +

    • Which office or person has authority to decide this request?

    +

    • What current rule, policy, or plan governs the decision?

    +

    • What evidence is required, and what information is unnecessary?

    +

    • Is written authorization required before purchase, enrollment, or work begins?

    +

    • How are alternatives compared?

    +

    • What is the expected review sequence and communication method?

    +

    • How can an error, delay, or disagreement be corrected or appealed?

    +

    • When should changing rules or circumstances be re-verified?

    +
    \ No newline at end of file From 8450e121b2f0cffa40a638028ed813fd6393e00a Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:54 -0500 Subject: [PATCH 51/62] Style curriculum: Approval packet checklist --- docs/templates/approval-packet.html | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 docs/templates/approval-packet.html diff --git a/docs/templates/approval-packet.html b/docs/templates/approval-packet.html new file mode 100644 index 0000000..43be6ea --- /dev/null +++ b/docs/templates/approval-packet.html @@ -0,0 +1,13 @@ +Approval packet checklist — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    Approval packet checklist

    Approval packet checklist

    + +

    • [ ] Vocational goal and work tasks

    +

    • [ ] Functional barriers and essential capabilities

    +

    • [ ] Minimum, preferred, and alternative configurations

    +

    • [ ] Training plan, if relevant

    +

    • [ ] Current source-verification records

    +

    • [ ] Comparable dated quotes

    +

    • [ ] Questions requiring a human decision

    +

    • [ ] Written authorization requirements identified

    +

    • [ ] Private records excluded from public copies

    +

    • [ ] Final packet reviewed for unsupported eligibility or funding claims

    +
    \ No newline at end of file From efe2c7f5abe473664f0dc3eb1b920de868ba0c3a Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:56 -0500 Subject: [PATCH 52/62] Style curriculum: Source-verification record --- docs/templates/source-verification-record.html | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 docs/templates/source-verification-record.html diff --git a/docs/templates/source-verification-record.html b/docs/templates/source-verification-record.html new file mode 100644 index 0000000..72efe10 --- /dev/null +++ b/docs/templates/source-verification-record.html @@ -0,0 +1,13 @@ +Source-verification record — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    Source-verification record

    Source-verification record

    + +

    • Claim or question:

    +

    • Responsible jurisdiction and authority:

    +

    • Official source title and link:

    +

    • Publication/update date:

    +

    • Date checked:

    +

    • What the source confirms:

    +

    • What it does not establish:

    +

    • Uncertainty or conflict:

    +

    • Human decision-maker:

    +

    • Next verification date:

    +
    \ No newline at end of file From 363d749e00ef2f2251f2e78be8bf39bc4149a0cd Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:30:58 -0500 Subject: [PATCH 53/62] Style curriculum: 1. Vocational goal --- docs/case-study/01-vocational-goal.html | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 docs/case-study/01-vocational-goal.html diff --git a/docs/case-study/01-vocational-goal.html b/docs/case-study/01-vocational-goal.html new file mode 100644 index 0000000..0b329fb --- /dev/null +++ b/docs/case-study/01-vocational-goal.html @@ -0,0 +1,6 @@ +1. Vocational goal — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    1. Vocational goal

    1. Vocational goal

    + +

    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.

    + +

    Next: Identify the work tasks.

    +
    \ No newline at end of file From 13898ed5f5ca7ad065128f267ac1e6ca715f75db Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:31:00 -0500 Subject: [PATCH 54/62] Style curriculum: 2. Work tasks --- docs/case-study/02-work-tasks.html | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 docs/case-study/02-work-tasks.html diff --git a/docs/case-study/02-work-tasks.html b/docs/case-study/02-work-tasks.html new file mode 100644 index 0000000..4b02b21 --- /dev/null +++ b/docs/case-study/02-work-tasks.html @@ -0,0 +1,8 @@ +2. Work tasks — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    2. Work tasks

    2. Work tasks

    + +

    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.

    + +

    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.

    + +

    Next: Identify accessibility requirements.

    +
    \ No newline at end of file From b54d609a2b573ebf5731717cf6f00837a5f8b91e Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:31:03 -0500 Subject: [PATCH 55/62] Style curriculum: 3. Accessibility requirements --- docs/case-study/03-accessibility-requirements.html | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 docs/case-study/03-accessibility-requirements.html diff --git a/docs/case-study/03-accessibility-requirements.html b/docs/case-study/03-accessibility-requirements.html new file mode 100644 index 0000000..4ca4f2e --- /dev/null +++ b/docs/case-study/03-accessibility-requirements.html @@ -0,0 +1,8 @@ +3. Accessibility requirements — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    3. Accessibility requirements

    3. Accessibility requirements

    + +

    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.

    + +

    Each need is tied to a task and linked to the centralized accessibility guidance, avoiding repeated or inconsistent accommodation text.

    + +

    Next: Translate requirements into a technology assessment.

    +
    \ No newline at end of file From 08c14f304047f220c847b8ccbdf407e23a81bb85 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:31:05 -0500 Subject: [PATCH 56/62] Style curriculum: 4. Technology assessment --- docs/case-study/04-technology-assessment.html | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 docs/case-study/04-technology-assessment.html diff --git a/docs/case-study/04-technology-assessment.html b/docs/case-study/04-technology-assessment.html new file mode 100644 index 0000000..60f5c34 --- /dev/null +++ b/docs/case-study/04-technology-assessment.html @@ -0,0 +1,8 @@ +4. Technology assessment — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    4. Technology assessment

    4. Technology assessment

    + +

    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.

    + +

    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.

    + +

    Next: Research possible funding.

    +
    \ No newline at end of file From 23a483aae7acebf5085b519e66621c82930f79a0 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:31:08 -0500 Subject: [PATCH 57/62] Style curriculum: 5. Funding research --- docs/case-study/05-funding-research.html | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 docs/case-study/05-funding-research.html diff --git a/docs/case-study/05-funding-research.html b/docs/case-study/05-funding-research.html new file mode 100644 index 0000000..2c9ae5f --- /dev/null +++ b/docs/case-study/05-funding-research.html @@ -0,0 +1,8 @@ +5. Funding research — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    5. Funding research

    5. Funding research

    + +

    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 unverified, and questions are prepared for the responsible counselor or agency.

    + +

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

    + +

    Next: Assemble the approval packet.

    +
    \ No newline at end of file From 6ea5fd4488e80d9bcacae91c0d0fc69ddd061a61 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:31:24 -0500 Subject: [PATCH 58/62] Style curriculum: 6. Approval packet --- docs/case-study/06-approval-packet.html | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 docs/case-study/06-approval-packet.html diff --git a/docs/case-study/06-approval-packet.html b/docs/case-study/06-approval-packet.html new file mode 100644 index 0000000..1236109 --- /dev/null +++ b/docs/case-study/06-approval-packet.html @@ -0,0 +1,8 @@ +6. Approval packet — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    6. Approval packet

    6. Approval packet

    + +

    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.

    + +

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

    + +

    Next: Review lessons learned.

    +
    \ No newline at end of file From 3981c46e5fd71c5113405727d29ae162ed84e312 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:31:28 -0500 Subject: [PATCH 59/62] Style curriculum: 7. Lessons learned --- docs/case-study/07-lessons-learned.html | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 docs/case-study/07-lessons-learned.html diff --git a/docs/case-study/07-lessons-learned.html b/docs/case-study/07-lessons-learned.html new file mode 100644 index 0000000..5e0ed20 --- /dev/null +++ b/docs/case-study/07-lessons-learned.html @@ -0,0 +1,12 @@ +7. Lessons learned — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    7. Lessons learned

    7. Lessons learned

    + +

    • Beginning with work tasks produces a defensible plan; beginning with a desired product produces assumptions.

    +

    • Accessibility is a system requirement throughout the workflow, not a final checklist.

    +

    • AI can structure research and expose uncertainty, but it cannot make an agency decision or prove that a human completed a review.

    +

    • Jurisdiction, authority, source date, and verification date must stay visible.

    +

    • Minimum, preferred, and alternative paths make the request more resilient.

    +

    • Privacy improves when functional evidence is separated from identifying records.

    +

    • Proposed, implemented, tested, and approved are different statuses and must remain distinct.

    + +

    Return to the guide homepage or copy the preparation templates for a new plan.

    +
    \ No newline at end of file From fd77f771bba9e4e4b96ef2861c57dd3f84bd3208 Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:31:31 -0500 Subject: [PATCH 60/62] Style curriculum: United States federal context --- .../funding/jurisdictions/united-states/federal/README.html | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 docs/funding/jurisdictions/united-states/federal/README.html diff --git a/docs/funding/jurisdictions/united-states/federal/README.html b/docs/funding/jurisdictions/united-states/federal/README.html new file mode 100644 index 0000000..bf07d48 --- /dev/null +++ b/docs/funding/jurisdictions/united-states/federal/README.html @@ -0,0 +1,6 @@ +United States federal context — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    United States federal context

    United States federal context

    + +

    Federal law and national programs may shape state or local services, but the responsible state, tribal, territorial, local, educational, workforce, or benefits authority may make the individual decision. Research the current official federal source, then identify the office that can answer the participant's specific question.

    + +

    Record facts using the program research template. Label anything not confirmed by a current official source as unverified.

    +
    \ No newline at end of file From 39c889c7ada7a67a808b6b295e61b5b89ea2605d Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:31:33 -0500 Subject: [PATCH 61/62] Style curriculum: Minnesota funding research --- .../united-states/state/minnesota/README.html | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 docs/funding/jurisdictions/united-states/state/minnesota/README.html diff --git a/docs/funding/jurisdictions/united-states/state/minnesota/README.html b/docs/funding/jurisdictions/united-states/state/minnesota/README.html new file mode 100644 index 0000000..ddaa14d --- /dev/null +++ b/docs/funding/jurisdictions/united-states/state/minnesota/README.html @@ -0,0 +1,13 @@ +Minnesota funding research — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    Minnesota funding research

    Minnesota funding research

    + +

    Minnesota is the first worked jurisdiction, not the default architecture. Begin with current official Minnesota sources and confirm the responsible program and decision-maker before relying on any rule.

    + +

    Preserved repo modules provide deeper historical context:

    + +

    • Minnesota VRS participant path

    +

    • Agency review boundary

    +

    • Benefits-safe founder path

    +

    • Provider readiness roadmap

    + +

    These documents may contain dated statements. Re-verify agency status, eligibility, authorization, benefits, housing, and provider requirements with current authoritative sources. Use the program research template for each question.

    +
    \ No newline at end of file From 0042472002fc75981ea82c6071e54920ca33d51a Mon Sep 17 00:00:00 2001 From: Dominique Devereaux <90852374+ibloud@users.noreply.github.com> Date: Tue, 13 Oct 2026 06:31:36 -0500 Subject: [PATCH 62/62] Style curriculum: Program research record --- docs/funding/program-research-template.html | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 docs/funding/program-research-template.html diff --git a/docs/funding/program-research-template.html b/docs/funding/program-research-template.html new file mode 100644 index 0000000..35d0e3b --- /dev/null +++ b/docs/funding/program-research-template.html @@ -0,0 +1,16 @@ +Program research record — Loptr Lab
    LOPTR LAB / ACCESSIBLE TECHNOLOGY PLANNING
    Guide home

    Program research record

    Program research record

    + +

    • Jurisdiction and responsible authority:

    +

    • Program and official source:

    +

    • Question being researched:

    +

    • Source publication or update date:

    +

    • Date verified:

    +

    • Confirmed facts:

    +

    • Uncertainty or conflicting information:

    +

    • Eligibility decision-maker:

    +

    • Authorization required before spending or beginning work:

    +

    • Questions to ask the human decision-maker:

    +

    • Next verification date:

    + +

    Do not include case numbers, government identifiers, benefit letters, medical records, credentials, or private correspondence.

    +
    \ No newline at end of file