Your dev team already decided this. Nobody remembers why.
We build kgai — shared memory for dev teams building with AI. Your agent records
decisions as you work, recalls them before changing code,
The Authority section is the part most memory writeups skip, glad it's here. One thing I'd push on is the validity window. For engineering decisions the end of validity is rarely a date, it's another decision. The June migration is what closed the Redux fact, so the honest record isn't "valid March to June", it's "superseded by this one, here's why". The window falls out of that link. Store only the window and you lose which decision closed it, and whether anyone later reversed the reversal.
Your dev team already decided this. Nobody remembers why.
We build kgai — shared memory for dev teams building with AI. Your agent records
decisions as you work, recalls them before changing code,
Who closed it, on what evidence: the superseding decision isn't a pointer, it's a full record. Author, rationale, refs, timestamp. supersedes is a field on that record, so the link carries exactly what the record carries.
Successor deleted or made invisible: nothing in the log is ever deleted. Retracting a decision is another decision that supersedes it. So "retired by something that no longer exists" isn't a state the model has. What it does have is a successor that was itself superseded later, and that is one more link in the same log.
Authority: we don't model it. We record who closed it, not whether they were allowed to. Your revocation authority point is open for us too.
We build kgai, and that is its shape. The repo is public under kgaidev on GitHub, the architecture doc has the long version.
Building persistent memory for AI agents at Mnemoverse.
I write about the unglamorous half: forgetting, contradiction, and the moment an agent confidently repeats a fact you retracted.
You were right about the window and the link, and your three answers close most of what I raised. Making retraction itself a decision is the move. If nothing is ever removed, a pointer cannot outlive its target, and my dangling successor is just a link that acquired one more link. I had been treating deletion as the hard case and it is the easy one.
Worth saying why append-only is not really a design choice at this point. Extrapolate storage and the wall arrives on its own, so something has to give. Deleting gives back space and takes the causal chain with it, which is the more expensive half. Compression only survives that if the compressed thing carries references to what it was built from. Once you accept both, deletion and in-place merge are gone as operations and accessibility becomes the tuning knob instead of existence. Your log is the same conclusion reached from the audit side rather than the scaling side.
Which leaves the case append-only does not cover, and it is the one I actually met: privacy rather than deletion. The successor stayed in the log and became invisible to the reader asking. From that reader's side it is indistinguishable from a dangling pointer, because the record says superseded by X and X cannot be resolved. An immutable log removes deletion from the threat model and leaves permission in it, and permission is the one that scales with the number of people sharing a store.
Your concession on authority is the same hole we have, and neither of us has closed it. A log that records who closed a fact but not whether they could is a log where the policy layer grows monotonically, because every entry reads as equally official later. Recording the actor makes the question answerable. It does not make it answered.
We're a place where coders share, stay up-to-date and grow their careers.
The Authority section is the part most memory writeups skip, glad it's here. One thing I'd push on is the validity window. For engineering decisions the end of validity is rarely a date, it's another decision. The June migration is what closed the Redux fact, so the honest record isn't "valid March to June", it's "superseded by this one, here's why". The window falls out of that link. Store only the window and you lose which decision closed it, and whether anyone later reversed the reversal.
Taking your three in order.
Who closed it, on what evidence: the superseding decision isn't a pointer, it's a full record. Author, rationale, refs, timestamp.
supersedesis a field on that record, so the link carries exactly what the record carries.Successor deleted or made invisible: nothing in the log is ever deleted. Retracting a decision is another decision that supersedes it. So "retired by something that no longer exists" isn't a state the model has. What it does have is a successor that was itself superseded later, and that is one more link in the same log.
Authority: we don't model it. We record who closed it, not whether they were allowed to. Your revocation authority point is open for us too.
We build kgai, and that is its shape. The repo is public under kgaidev on GitHub, the architecture doc has the long version.
You were right about the window and the link, and your three answers close most of what I raised. Making retraction itself a decision is the move. If nothing is ever removed, a pointer cannot outlive its target, and my dangling successor is just a link that acquired one more link. I had been treating deletion as the hard case and it is the easy one.
Worth saying why append-only is not really a design choice at this point. Extrapolate storage and the wall arrives on its own, so something has to give. Deleting gives back space and takes the causal chain with it, which is the more expensive half. Compression only survives that if the compressed thing carries references to what it was built from. Once you accept both, deletion and in-place merge are gone as operations and accessibility becomes the tuning knob instead of existence. Your log is the same conclusion reached from the audit side rather than the scaling side.
Which leaves the case append-only does not cover, and it is the one I actually met: privacy rather than deletion. The successor stayed in the log and became invisible to the reader asking. From that reader's side it is indistinguishable from a dangling pointer, because the record says superseded by X and X cannot be resolved. An immutable log removes deletion from the threat model and leaves permission in it, and permission is the one that scales with the number of people sharing a store.
Your concession on authority is the same hole we have, and neither of us has closed it. A log that records who closed a fact but not whether they could is a log where the policy layer grows monotonically, because every entry reads as equally official later. Recording the actor makes the question answerable. It does not make it answered.