Skip to content

Devostasis 0.1.2

Choose a tag to compare

View all tags
@drevendev drevendev released this 06 Sep 08:04
· 48 commits to master since this release
v0.1.2
7318597
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The first research judgements, adopted against real bundles. No numeric threshold or window changed.

  • Flow rule flow.bands.v1: a positively observed empty queue is NO_QUEUE whatever the historical merge median, and the classifier consumes the exact rational median merge latency in seconds (604800 s and 1209600 s are the exact conversions of 168 h and 336 h). The whole-hour value stays as a derived presentation projection.
  • Pulse rule pulse.bands.v1: a capped required enumeration is evaluated over every admissible completion of the missing tail, giving one forced band, every reachable band in possible_bands, or UNKNOWN.
  • Delta: a Vital whose rule version changed since the previous bundle is INCOMPARABLE on its own (RULE_VERSION_BOUNDARY) while the bundle stays COMPARABLE; historical bands are never reinterpreted.
  • Demand devostasis.demand.v2: the attention order is level rank, then canonical Vital order. The cross-Vital gauge tie-break of v1 is removed, because gauges of different Vitals measure different phenomena; attention_key is gone.
  • Verification adopts the stored effective config as the semantic authority of a bundle: fail-closed schema validation, the canonical member profile derived from it and checked against manifest, members and identity markers, and report replay only after those pass. Bundles of both effective-config schemas still verify.
  • Renderer devostasis.render.v4; the GitHub CI outcome map is confirmed (timed_out is a verification failure, startup_failure is UNKNOWN).
  • Documentation: gauges accepted for presentation and same-Vital ordering only; reporting decisions on permission-domain stores, optional report.html, retention, and self-observation output being convenience rather than durable history.

Bundle identities change for every project. History stays COMPARABLE; Flow and Pulse report RULE_VERSION_BOUNDARY once, on the first bundle after the upgrade.

Usage: uses: drevendev/devostasis/.github/workflows/observe-self.yml@v0.1.2 (see docs/deployment.md).

Generated with Claude Code.

Assets 2
Loading