keep returning to lack of time information and, changes. (ref: mentions)

we don’t track issue state. maybe we should, rather than just keeping a Status field, we keep a list of changes? as tags?

either refreshing the Status field automatically or just calculating on demand.

I fear it will lead to a large number of tags. maybe that’s inefficient? but I guess most GH issues only go through a few.

does it make sense to have them on the object? where else would we store them? then we could at least show the history of the object and calculate things like mentions if we stuck them in this changelog field. adding removing mentions, LSTM style that never gets compacted, last entry wins.

we don’t track issue deletion either. should things be deleted? or closed/archived? that would be referentially safer.

coming back to Tags (it’d be nice if this hyperlinked to search for that hashtag) this would be complicated structured data to stick in a stringly value.

I really would prefer a single tag shape to make editing easier. is that necessary? is it a UI/editing problem? the transport of the object between server and browser is the main issue. if it’s a single shape that’s easy, otherwise I have to recreate a certain amount of the python in js.

localisation is also an issue. “Start Date” is a very English language string.

need to save draft notes as .

The database community has the famous saying “The log is the database; everything else is cache (or materialized views)” - often attributed to Pat Helland. T