Repository navigation
v0.4.0
Version 0.4.0 (versions/0.4.0.md): additive, and states what
0.3.0 left unsaid. Proposals 0001 to 0004 in proposals/.
Added
fromanduntilon ownership rows: the interval during which a share holds, so
a share that changes is history rather than a rewrite. Two rows of one subject on
one holding MUST NOT overlap; the reference validator reports an overlap as an
error.- Document integrity (section 4): a
parentIdchain MUST be acyclic; the reference
validator reports a cycle as an error. - Conformance corpus
tests/conformance/0.4.0.json: the 0.3.0 cases plus ownership
intervals, overlaps, cycles, a liability child, a repayment on both legs.
Changed
- Section 6, the derivation: each leaf holding is signed by its own
nature(a
liability held inside an asset account is subtracted); a holding contributes
nothing beforeopenedAtor on and afterclosedAt; ownership is read on the
root of the chain and as of the date. - Section 5.6: the sign of
amountis the holding's own, in the direction of its
value (a repayment on a liability is negative); the legs of onetransferIdnet
to zero once each is signed by its holding's nature. - Section 5.3 and 14: a producer SHOULD emit a final valuation when a holding closes.
- The household example and section 16 carry a mortgage payment on both sides.
Fixed
- The household example (in
examples/household.jsonand section 16 of
versions/0.3.0.md) gives the brokerage accounth2its ownership row. With
ownershippresent and no row forh2, the derivation of section 6 owns it at
zero, which contradicted the net worth the example announces (132730.55 EUR). - Schema: a calendar date must exist.
2026-99-99matched theYYYY-MM-DD
pattern ofdateand of the date branch ofdateOrTimestamp(asOf, a
transaction'sdate,openedAt,closedAt) and validated; thedate
format now applies on top of the pattern, as thedate-timeformat already
did for timestamps. No document carrying a real date changes validity.