Daymark
Definition
Section titled “Definition”A Crux interaction point that turns a recognised event or tap into a clear acknowledgement and next action.
Crux usage
Section titled “Crux usage”DaymarkA Crux interaction point that turns a recognised event or tap into a clear acknowledgement and next action.Crux usage: Daymark follows the interaction principle “tap → receive → act” and supports NFC interaction, status presentation, acknowledgements, task actions, offline states, and MeshCore fallback.Open full definition follows the interaction principle “tap → receive → act” and supports NFCA short-range wireless technology that allows compatible devices or tags to exchange information when brought very close together.Crux usage: Crux uses NFC for Daymark taps, equipment identification, public interaction points, and locally initiated actions linked to Atlas.Open full definition interaction, status presentation, acknowledgements, task actions, offline states, and MeshCoreAn open-source, off-grid mesh communications system that uses LoRa-capable nodes to relay messages across a network.Crux usage: Crux uses MeshCore as a resilient public and fallback communications layer for field nodes, mobile diagnostics, and selected sensor or Daymark events. Private Crux operational data remains separately governed.Open full definition fallback.
Context
Section titled “Context”Use for the Crux Daymark workflow, stations, interfaces, and interaction model.
Aliases
Section titled “Aliases”Crux Daymark
Related terms
Section titled “Related terms”This entry is governed through the AtlasCrux’s governed operational intelligence system for interpreting system state, coordinating workflows, and presenting actions or decisions.Crux usage: Atlas connects engineering records, sensor data, communications, automation, evidence, and publishing. Material changes remain subject to validation rules and human approval.Open full definition Engineering System.