Structural catalog for annotation primitives
The structural catalog documents the set of annotation primitives used to express constraints, distributions, groups, and revision points within a record. Each primitive is defined by an explicit schema: a label, a type signature, required metadata fields, and a provenance pointer. A constraint primitive contains a scope descriptor, a qualifier field that indicates the constraint type (for example, capped value versus provisional marker), a source reference, and a revision token. Distribution primitives indicate the allocation set and an arithmetic descriptor that classifies the allocation as absolute, proportional, or baseline-indexed; membership references enumerate included lines or columns. Group primitives comprise an identifier, a descriptive label, and a membership rule expressed as a concise qualification phrase. Revision primitives are compact tokens that capture a timestamp, an author code, and an explanatory note. The catalog emphasizes structured metadata so that annotations remain machine-readable and human-resolvable. Presentation choices in the ledger preserve primary figures while placing primitive labels in margins or adjacent cells to allow scanning and cross-referencing without obscuring values.
Notation schema and compact legend
The notation schema prescribes a compact set of glyphs and alphanumeric codes for common annotation tasks. Glyphs convey boundary markers, provisional status, and index anchors; alphanumeric codes provide group identifiers and revision tokens. Each glyph is documented with an explicit meaning, expected placement relative to the primary figure, and display rules for vertical stacks of annotations. The compact legend that accompanies a record lists glyph meanings, group codes with membership shorthand, and distribution descriptor keys. The schema favors brevity to reduce visual load while ensuring that every annotation is resolvable from the legend. Presentation choices use restrained contrast and consistent alignment so that annotations form a readable layer that complements the ledger grid. The schema also includes accessibility notes describing how annotations should be exposed in plain text or machine-readable exports to maintain interpretive parity across formats.
Record presentation and layering
Record presentation separates primary numeric figures from annotation layers. Primary figures retain the highest visual weight; annotations are subdued in tone and positioned in margins, gutters, or adjacent micro-areas. Layering rules specify z-order, typographic scale, and spacing to avoid collisions between annotation elements and ledger content. Revision notes appear condensed with an unobtrusive separator while distribution descriptors include a compact inline marker that links to a legend entry. For records that include multiple coexisting distribution schemes, the presentation uses subtle separators and column markers to disambiguate parallel annotations. Where space is constrained, annotations collapse to an abbreviated form with an explicit expansion control in the footnote area. This layered approach preserves archival readability and enables a reader to follow structural relationships without conflating annotations with primary values. The presentation guidelines include examples illustrating common combinations of primitives and recommended treatments for dense records.
Interpreting constraint qualifiers and scope
Constraint qualifiers are explicit descriptors attached to constraint primitives that state the nature of the marker. A qualifier may label a marker as fixed-cap, soft-range, provisional, or reference-only. Scope indicators define the set of records affected and may use column references, row ranges, or group identifiers. Together, qualifier and scope form a minimal contract that records how a numeric limit is to be read. Each constraint primitive includes a source pointer that records the origin of the marker and a revision token that captures the change history. Representation rules require that qualifier labels be short, consistently placed, and accompanied by a revision entry when the qualifier or scope is altered. This structured approach allows readers to determine whether a constraint applies to a single cell, a column, multiple groups, or an entire page, and to follow the sequence of changes that altered its definition. The documentation provides canonical examples of qualifier-scope combinations and the expected annotation patterns for each case.