Purpose
Capture and maintain site-specific Chromebook enrollment automation sketches while documenting their legacy/support boundary.
Current state
Repository contains multiple school-specific sketches and remains maintainable, but active field usage and succession plan need validation.
Next step
Confirm active sites, migrate credentials out of source, and decide whether to retain, modernize, or retire this toolchain.
Interfaces
Inputs- Site-specific enrollment constants
- Chromebook setup UI workflow assumptions
Outputs- Automated enrollment keystroke execution on target devices
Reality to Action trace
Reality IngestionNot in scope.
Canonical StorageNot in scope.
Automation EnginesContributes in this stage.
Human InterfacesNot in scope.
Operational AdoptionContributes in this stage.
Core workflow
TBD. Document the 5-10 steps that define the core workflow.
Artifacts
- <site>/<site>.ino sketches
Operational notes
Constraints and scars
- High dependence on UI timing and exact screen sequence.
- Credential hygiene is the primary governance risk.
Reliability posture
Automation is timing-sensitive and can break when ChromeOS UI flow changes.
Observability
- Physical device behavior
- Manual technician verification
Security and privacy
Enrollment and network credential handling must be tightly controlled. Remove hardcoded secrets from source and rotate any exposed credentials.
Dependencies
Upstream- Supported Arduino HID hardware
- ChromeOS enrollment screens
- District enrollment accounts
Downstream- Device onboarding workflows
Ownership
OwnersJosh Barton
UsersField technicians, Technology Services
Chromebook_Enrollment
Structure
Each top-level school folder contains a variant sketch tuned for local enrollment behavior.
Operational Notes
- Treat as legacy field automation unless current usage is explicitly confirmed.
- Test sketches on non-production devices after ChromeOS changes.