Atlas view

Device Management

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.

Domain guide

How to read this domain

Definition

This domain groups systems focused on device management workflows, shared data models, and repeatable operational constraints.

What belongs

  • Systems where device management is the primary problem space.
  • Integrations that move, validate, or enforce data in this domain.
  • Operational tools that reduce risk and manual work for this domain.

What doesn't

  • Generic tools where device management is incidental metadata.
  • One-off experiments without domain-specific constraints.

Typical integrations and constraints

  • Source-of-truth feeds, vendor APIs, and scheduled extracts.
  • Schema drift, credential scope, and compliance requirements.
  • Role-based access and operational review cycles.

Common interfaces

  • REST/JSON APIs and vendor export endpoints.
  • CSV, SQL views, or Sheets-based boundary objects.
  • Auth boundaries (service accounts, OAuth, SSO).
Results 6 projects
Component · Maintenance

Chromebook_Enrollment

Arduino Centipede-derived enrollment sketches with site-specific variants for Chromebook setup automation.

Automation Engines Operational Adoption
Open project
Component · Active

gpt_kit

Scripts transform ticket EML exports into a normalized knowledge base with tagging and optional redaction. Make scripts executable, then run them with input EML …

Automation Engines Reality Ingestion Human Interfaces Operational Adoption Canonical Storage
Open project
Component · Active

MDM Integration Automation (Mosyle)

Provide the Mosyle API tooling layer used by district reconciliation workflows while keeping the broader write-enabled production sync separate and explicit.

Human Interfaces Operational Adoption
Open project
Component · Active

Munki Client Configurator

Use login-time support automation to map Active Directory context to a Munki ClientIdentifier and keep managed Macs aligned with district software targeting …

Reality Ingestion Operational Adoption
Open project
Experiment · Maintenance

SamsungTVSettings

Exported clone directories used to standardize Samsung TV configuration. It ingests exported clone files and produces clone archives for TV setup.

Canonical Storage
Open project