Fable
There was a city's granary whose access control was strict, yet whose ledgers were a mess
In a great northern city there was an imperial granary, newly rebuilt with high, thick protective walls and three layers of locks inside. The city warden summoned twelve grain suppliers and assigned each a separate compartment. The warden promised: the stored grain would not be mixed into the military grain pool. The suppliers all felt reassured.
A year later, the inspector at the city governor's office opened the granary's in-and-out ledger and found three major categories of information missing: after grain entered the granary, who sampled and tested its quality, to whom the test report was submitted, how long intake records were retained, and whether prices for grain sold to out-of-town merchants had been negotiated with the suppliers who stored the grain. The ledger contained only one line, "not mixed into the military grain pool"; every other column was blank.
The inspector impounded the account books and asked the city guard: you say the grain wasn't mixed in, and this is the access gate you installed. But what I'm now asking is, where did the grain quality data go? The testing station takes three catties of samples from the compartment each time; the samples are boiled, weighed and written into reports. Which shelf are the reports on, and who has the key to that shelf? The city guard could not answer.
The inspector pointed at the ledger and explained: the guarantee you gave is called data exclusion in the compliance framework—it protects only one path. Data usage rights are another path—they govern, after entering the warehouse, how many times each scoop of grain was used, who used it, and whether it was destroyed after use or put back into someone else's compartment.
The city guard summoned the suppliers to a meeting overnight. He took out a new form and added four columns after "whether mixed into the military grain pool": sample collection purpose, recipient of test reports, data retention period, and ownership of derivatives. He said that from today on, in addition to each no-mixing rule, four more lines must be filled in. One supplier stood up and asked: with so many lines to fill in, how many times has your review volume increased? The city guard said nothing, and the inspector answered: compliance costs certainly double, but whether the bill for accountability stops at your access gate or at your new form makes a completely different cost.
Later, a supplier got into a dispute because quality data was taken by a commercial entity attached to the city garrison office and used to improve its own grain seed formula. On the old form there was only a checkmark for "not mixed into the military grain pool," leaving the supplier with no basis. On the new form, the "ownership of derivatives" field was left blank—that dispute was handled as having no explicit authorization, and the supplier lost part of it. But with this field in place, at least it could be filled in next time.