Repository navigation
v0.3.0
Version 0.3.0 (versions/0.3.0.md), the coherence release: one
breaking change (allowed pre-1.0), the rest additive.
Changed
- Breaking:
ownership.shareis a base-10 decimal string in [0, 1] (was a JSON
number), so ownership arithmetic follows the same no-float rule as money and
quantities. Migration: quote the value (0.5becomes"0.5"). transaction.type,institution.kindandinstrument.kindare open vocabularies
(string plus recommended values), aligning the schema with the section 9 rule that
consumers treat unknown values generically.holding.natureandsubject.type
stay closed. Every previously-valid value remains valid.
Added
transferIdon transactions: an opaque id shared by the legs of one internal
movement (a transfer's debit and credit, a trade and its cash settlement), netting
to zero, so flow analytics stop double-counting internal moves.quantityon valuations: the units held as of the valuation date, making a
valuation a self-sufficient position snapshot.- ISO format patterns for the identifiers that are never masked (
bic,isin,
lei,mic); maskable identifiers (iban,number) stay free-form. - Document integrity conventions (section 4): ids MUST be unique within their
collection; references SHOULD resolve in-document but MAY dangle under partial
disclosure, and consumers MUST tolerate that. - Clarifications: the primary subject is the first of
subjects;valuetakes
precedence overquantitytimesunitPrice; future-dated valuations are
projections and SHOULD carry a projectivesource; a liability's values are the
outstanding as stated, never double-negated; a bare date compares as the start of
that day, UTC. - Reference validator: on top of schema validation, a duplicate id is now an error
and an unresolved reference is reported informatively.