Micro-toolkit

microhealth

Firmware needs a bounded view of health metrics and threshold crossings.

A caller-owned monitor evaluates registered metrics and reports documented state changes.

DevelopmentMITC99
GitHubQuick Start
Last verified
Not audited against current README/docs
Platform scope
Portable C99; integration depends on caller-provided adapters

What it solves

Firmware needs a bounded view of health metrics and threshold crossings.

How it works

1Metrics→2thresholds→3health state→4callback

Use it when

Watch queue pressure
Raise a condition after a threshold crossing
Expose current health to diagnostics

Quick Start

#include "mhealth.h"
/* Register metrics in caller-owned storage and update sampled values. */

Engineering evidence

  • README, public header and tests are present in the local repository

Known limits

  • It reports health state; remediation remains application policy