About duhaxmarum
duhaxmarum documents budgeting as a sequence of discrete states. Each recorded state captures a structured snapshot: labels, indexed categories, allocation descriptors, constraint annotations, and a timestamp. The format is intentionally declarative and archival; it preserves prior values by appending successor states rather than mutating historical entries. This model prioritizes traceability and human interpretability in reporting contexts.
Purpose
The purpose is descriptive documentation. The format clarifies how states are defined, how allocations are recorded, how reviews and adjustments are linked, and how archival packaging preserves provenance. It is suitable for organizations that require readable state histories for compliance or review workflows.
Design principles
duhaxmarum follows a limited set of principles to keep state records consistent and interpretable across time. The first principle is immutability: once a state is committed it remains unchanged. Subsequent changes are represented as successor states that reference antecedent identifiers. The second principle is schema stability: field names and units are standardized so that records remain readable across revisions and personnel changes. The third principle is explicit linking: transitions are separate metadata objects that capture rationale, validation attributes, and pointers to affected states.
Immutability
Records are snapshots. Correction or reallocation is captured as a new state that cites the original. This conserves the historical narrative and supports audit-oriented review.
Schema stability
Consistent field names and canonical formats (timestamps, labeled units) minimize interpretive ambiguity when entries are reviewed at later dates or by different actors.
Transition metadata
Transitions encode the why and when of change. They store validation attributes, references to antecedent identifiers, and concise rationale statements for traceability without altering original state content.
Record structure
Each state instance pairs a concise summary with a structured payload. The summary supports scanning; the payload contains labeled fields and optional narrative annotations. Fields include identifier, timestamp, category mapping, allocation descriptors, constraints, and provenance metadata. The format does not perform calculations; numeric fields are descriptive and include explicit unit labels and contextual notes to aid human review.
Summary line
A one-line summary captures the state type, key categories, and a timestamp. The summary is included in list displays to support quick navigation through a sequence of states.
Payload fields
The payload contains canonical fields for identifiers, category maps, allocation descriptors, and optional narrative notes. Each field is labeled and stored with explicit format hints (for example ISO timestamps) to ensure consistent interpretation.
Explore format
The format is intended for descriptive capture and archival clarity. It documents how states are defined, how transitions are represented, and how record consistency is preserved for later review. For a concise summary of canonical states and transition rules, refer to the landing page and the specification sections.