Ameliorate

Cool to see this posted :) I'm the creator.

For those interested, I've slowed work on the app in favor of refining the app's ontology in markdown form[1], building an ontology playground[2], and building a prototype[3] to show off features that the updated ontology enables. I had some major changes I wanted to make and making it work in the real app was going to be too much effort.

I'll likely be making a Show HN for one/some of these soon^TM (in the next month or two?) but they're currently still a bit early.

[1] https://github.com/keyserj/reasoning-tools/blob/main/amelior...

[2] https://keyserj.github.io/reasoning-tools/ontology-playgroun...

[3] https://github.com/keyserj/reasoning-tools/tree/main/amelior... (not yet deployed)

This reminds me a web 2.0 startup in 2006. It was similar in that it wanted people to break down arguments into a flowchart. Had more of a public collaboration flavor to it at the time.

https://web.archive.org/web/20060427152801/http://www.standp...

Though I like this angle a bit better, it'd be interesting to look into why standpoint had a hard time.

Seems like an interesting way to both refine and serialize thoughts about something tricky. I think it could be a really useful backbone, but I question if the interface is optimal for creating the graphs vs something more conversational and using the graphs to hold and iterate on the state. Also, I think I would want some kind of essay version as a consumer of someone else's argument rather than reading thru the graph itself.

Really cool space to explore!

This might be more interesting if you could read other people's discussions. As it is, it's like visiting an empty forum.

In which direction are you supposed to read these charts? The arrows seem to point from conclusion/solution to reasoning, but the reasoning is at the top which makes me feel like I should read it first. It would be less confusing for there to be a single convention (eg “reasoning/evidence at the top with arrows flowing mostly down towards the conclusion”).

Similarly, I was confused by the use of both active and passive: eg sometimes “creates” and sometimes “created by,” with different arrow directions for each.

I expected scores and justifications to show up all the time, not just hover, no matter the view. Did you consider styling edge types differently to replace labels?

- stupid question: i really dont understand what your product does

- mind explaining it like how you would do to a 5yr old kid

Very nice. I think this can be a good visual way to run LEAN activities like 5 Why and A3 Problem Solving.

this is interesting, does it use IBIS on some level? i discovered IBIS and added it and mermaid diagrams to my app but it was a bit of a lark. i think what i pictured was similar to what you have here (and should be possible though i have not tested the IBIS > mermaid pipeline).

in any case: cool

I think the logical direction for such a product is to make data-backed decisions using causal inference, like so:

https://basisresearch.github.io/chirho/