tracking: one ledger, one authority — prune protection and replace-vs-add answered from the same records, fail-safe on unreadable state

This commit is contained in:
2026-07-30 19:44:11 -04:00
parent 7bd911d58b
commit 7f70d94228
40 changed files with 1546 additions and 633 deletions
+10
View File
@@ -0,0 +1,10 @@
reasampler_pure_library(origin_ledger SOURCES origin_ledger.cpp LINK PRIVATE json)
reasampler_test(origin_ledger LINK origin_ledger json)
# prune_reconcile + bank_book are linked into the authority's test, not the library:
# the test proves end-to-end that a tied usage can never reach the orphan set, which
# is the "consumers cannot disagree" property stated at the pure layer.
reasampler_pure_library(tracking_authority
SOURCES tracking_authority.cpp
LINK PUBLIC origin_ledger sample_usage)
reasampler_test(tracking_authority LINK tracking_authority prune_reconcile bank_book)