Design the audit trail and evidentiary record #21

New Issue

2026-08-02T03:05:54Z

christian commented

2026-08-02 03:05:54 +00:00

Question

Sourcing decisions get challenged, sometimes years later. The system needs to be able to answer who saw what, when, and why a bid ranked where it did.

Resolve: what events are recorded, what is immutable, how long records are kept, who can read them, and how a ranking is reconstructed after the model behind it has changed. Note the tension with the distribution-layer decision, which deliberately pushed retention and compliance obligations back onto the retailer — this ticket must find the line where the record is enough to defend a decision without becoming a system-of-record obligation.

Parent: #1

## Question Sourcing decisions get challenged, sometimes years later. The system needs to be able to answer who saw what, when, and why a bid ranked where it did. Resolve: what events are recorded, what is immutable, how long records are kept, who can read them, and how a ranking is reconstructed after the model behind it has changed. Note the tension with the distribution-layer decision, which deliberately pushed retention and compliance obligations back onto the retailer — this ticket must find the line where the record is enough to defend a decision without becoming a system-of-record obligation. --- Parent: #1

christian added the wayfinder:grilling wayfinder:ticket labels 2026-08-02 03:05:54 +00:00

christian added a new dependency 2026-08-02 03:06:26 +00:00

#15 Design AI bid ranking, scoring, and its defensibility

christian added a new dependency 2026-08-02 03:06:26 +00:00

#14 Specify the two-party data release rules

christian referenced this issue

2026-08-03 19:31:20 +00:00

Specify the two-party data release rules #14

christian referenced this issue

2026-08-03 20:19:10 +00:00

Design AI bid ranking, scoring, and its defensibility #15

christian referenced this issue