axiam::ConfigClampedEvent Struct Reference

Emitted at client construction, once per caller-supplied setting the SDK clamped (§19.1, §19.2 rule 6). More...

#include <telemetry.hpp>

Public Attributes
std::string	setting
	The builder setting's name, e.g. decision_memo_ttl.
std::string	requested
	The value the caller asked for, rendered.
std::string	effective
	The value actually in force, rendered.
std::string	contract_reference
	The §-reference for the limit, e.g. §17.1 rule 2.

Detailed Description

Emitted at client construction, once per caller-supplied setting the SDK clamped (§19.1, §19.2 rule 6).

Clamping rather than rejecting is the right call — rejecting would fail construction for a caller whose configuration was merely optimistic, and honoring would let one client become the herd §16 exists to prevent. Doing it SILENTLY is the part that is wrong: an operator who set a 60-second memo TTL believes their staleness bound is 60 seconds. It is five, and their revocation reasoning is off by a factor of twelve with nothing anywhere to say so.

It is NOT emitted for a value already within its limit: an event that fires when nothing happened trains its reader to ignore it.

Member Data Documentation

setting

std::string axiam::ConfigClampedEvent::setting

The builder setting's name, e.g. decision_memo_ttl.

requested

std::string axiam::ConfigClampedEvent::requested

The value the caller asked for, rendered.

effective

std::string axiam::ConfigClampedEvent::effective

The value actually in force, rendered.

contract_reference

std::string axiam::ConfigClampedEvent::contract_reference

The §-reference for the limit, e.g. §17.1 rule 2.

---

The documentation for this struct was generated from the following file:

• include/axiam/telemetry.hpp