Kent Shikama

Would using a different hashing algorithm that was secure by current computing standards not solve the issue too?

@rikschennink It looks like `destroy` isn't called after the first render and so when strict mode goes for its second render it isn't starting from a clean slate.

A few notes to clarify this issue. If a record contains any “meaningfully open” cases, then all charges are ineligible. A case is “meaningfully open” if - OECI doesn’t say...

@hmarcks > If so we could potentially automatically update the case to closed, but this may be confusing to the user. I like this. In fact, I don't think it...

@michaelzhang43 Did we still want the summary panel to show the results as if the meaningfully open cases were ignored even if no questions have been answered?

@michaelzhang43 So if I understand correctly Probation = Quantum state between convicted and probation revoked Conditional discharge = Quantum state between dismissed and convicted

@hmarcks @michaelzhang43 In my head, a case can be both "meaningfully closed" and "open" at the same time, and vice versa. Let us change the term "meaningfully open" to "super-blocking"....

@michaelzhang43 @hmarcks @wittejm But I don't think the re-terming hits the fundamental problem where we want to be both entirely accurate and useful at the same time. Here are two...

After more thought, I feel like the charge summary panel should always side on "useful" as I'm guessing @michaelzhang43 wants to give out PDF print outs before asking the client...

Another thing is that even if we marked all cases as ineligible as would be "accurate", we still need to trust the user to take care of the other assumptions...