that's why you shouldn't use _either_ of those as repositories of information ... they're great for the ephemeral discussions, but once consensus is reached, yo

that's why you shouldn't use _either_ of those as repositories of information ... they're great for the ephemeral discussions, but once consensus is reached, you should have other ways of tracking that, whether it's: github/devops/jira issues and tickets, or some kanban board somewhere, or design documents, or a wiki. The discussion itself shouldn't be the artifact that records the decision.