memory
Owned the near-line working-memory lane for an AI career assistant.
The definition
What everyone assumes: Retention is whatever the config says. The setting read 30 days, so memory lasted 30 days. Corrected to: Retention is whatever the units on both sides actually agree on. The config states an intention. The contract is what happens.
Where it broke. Two sides of a contract disagreed about units. One wrote a duration in seconds, the other read it as milliseconds. Nothing threw, because both are perfectly valid numbers.
- Intended
- 30 days
- Actual
- ~43 minutes
- Off by
- ~1000x short
The contract is a number. The units live in two different heads.
On the wire2,592,000no unit attached
Result: 30 days ~43 minutes~1000x short
Built with
What I dropped
A stateful PyFlink prototype. I published v0.0.12 and got it to one JobManager and four TaskManagers in staging, then isolated an operator startup failure to a null worker PYTHONPATH and stopped. It never ran end to end, so it never became a claim.