VILS CTE Smart Solutions — Public Curriculum Reference

This repository publishes the public reference for the VILS CTE Smart Solutions Canvas course used by Irving ISD.

Public site: https://elbrielle.github.io/innovative-technology/

Canvas remains the student delivery and grading environment. The site presents the complete ordered course for curriculum review: teacher guides, student directions, assessments, rubrics, linked resources, and approved Canvas files.

Planning and backlog

The durable curriculum backlog is docs/BACKLOG.md. It records refinement epics, evidence gates, dependencies, and sprint-ready work without changing Canvas or generated public pages.

Standards reference

The immutable source record for Grade 8 Technology Applications TEKS is docs/standards/texas-technology-applications-grade-8-teks-2022.md. It preserves the exact wording of current 19 TAC §126.19(c). The matching VILS learning-contract and alignment pattern defines how the exact standards, lesson objective, and student evidence appear consistently in Canvas facilitator guides and their public-site equivalents.

Publication boundary

Public is the default. The only protected exception is OPTION · About Me Smartphone (Canvas module item 2633987) and its creator-approved district-only PDF/video. The public course map shows a protected entry so the sequence remains complete, but the activity body and file bytes are never written to this repository.

The fail-closed rule is stored in data/publication-policy.json. If the protected activity begins referencing a different file set, export stops and requires a human policy review.

Stable URLs for IPC and other courses

Each Canvas module item has a stable public URL based on its immutable module-item ID:

https://elbrielle.github.io/innovative-technology/lessons/<module_item_id>.html

The machine-readable mapping is data/public-links.json. IPC builders should look up the Canvas module-item ID there instead of guessing a title slug. A lesson title may change without breaking the public URL.

The earlier title-based lesson URLs remain as generated redirects, so existing bookmarks continue to reach the corresponding stable item-ID page.

One-command sync

From the repository root:

python3 scripts/sync_course.py --source-token-file ~/.canvas_vils_source_token

That command:

1. reads live Canvas course 23402 without changing it;
2. exports a deterministic, public-safe snapshot;
3. downloads or reuses every approved referenced file;
4. generates the course map, module pages, stable lesson pages, parity report, and public-link manifest;
5. verifies the repository against the snapshot; and
6. re-reads live Canvas to prove nothing drifted during the build.

The explicit token file is the recommended route because the Verizon source and Irving destinations use different Canvas instances. CANVAS_TOKEN remains supported. Never commit either token.

Teacher-course fleet parity

Multi-course distribution is audited with the reusable personal $canvas-fleet-parity skill. VILS keeps its source and protection policy in this project while live teacher-course registries and reports remain private. See docs/CANVAS_FLEET_PARITY.md. When the Verizon source is approved, use python3 scripts/ss_fleet_release.py approve-source --approval-note "..." followed by python3 scripts/ss_fleet_release.py audit. Destination apply is a separate approval gate.

Release workflow

1. Run python3 scripts/sync_course.py.
2. Review git diff --stat and data/site-manifest.json.
3. Run the responsive visual audit described in docs/SYNC_WORKFLOW.md.
4. Run the independent four-lens curriculum review gate and record consensus in docs/reviews/. Any HOLD keeps the PR unmerged.
5. Commit and push main. GitHub Pages deploys from the existing repository configuration.
6. Verify the public URL and several stable lesson URLs after deployment.

The CI workflow rebuilds the static pages and runs the repository parity gate. It does not need a Canvas token because live Canvas verification remains an intentional release action.

Credits

Instructional design by Elisha Lucero. Third-party images, videos, tools, and source materials retain the attribution or usage basis included in the lesson, facilitator guide, or speaker notes.

PowerPoint release quality

Start deck creation with the binding teacher-led slide authoring standard, the Lesson 1 and 2 retrospective, and the annotated approved exemplars. These preserve the owner's teaching sequence, visual comparisons and reveals, live demonstration, and complete work-time screen.

Follow the PowerPoint storage and release workflow before distributing new or revised decks. It covers projected image quality, conservative compression, protected slides, and retiring verified obsolete source files.