This domain groups systems that solve Device Management problems - shared vocabulary, common interfaces, and repeatable operational constraints. Use this page to see which systems already exist, what they ingest and emit, and which patterns we repeatedly rely on in this problem space.
Domains are how we avoid reinventing the same solution in slightly different shapes. When a domain repeats, it’s a signal to standardize schemas, mapping layers, auth patterns, and operator workflows.
This domain groups systems focused on device management workflows, shared data models, and repeatable operational constraints.
No playbooks mapped yet.
Unify device inventory and compliance signals so operations can act on a single source of truth. Authenticate with Mosyle using access token, email, and …
Chromebook enrollment sketches and configuration code organized under Chrombook_Enrollment/. It ingests device configuration parameters and produces firmware …
Scripts transform ticket EML exports into a normalized knowledge base with tagging and optional redaction. Make scripts executable, then run them with input EML …
munki-client-configurator is a login-time automation layer that keeps every managed Mac aligned with district policy. It inspects the signed-in users Active …
Project Atlas is the documentation hub for AetherDev systems. Atlas and Showcase sections with canonical project schema. Taxonomy views for pipeline, domains, …
Exported clone directories used to standardize Samsung TV configuration. It ingests exported clone files and produces clone archives for TV setup.
No matching projects found. Try another keyword.
