think through the list of items in pqubed

[zippy]

The list crosses categories and is not well differentiated/grouped.

For example, Semantic Trees and Semtrex seem to be particular portions of the technology, whereas Semantic Alternation is more a description of how semantic trees are structured, Match Triggers is very technically detailed, and Optimized for Evolution is much more general. We should use header levels to group these and differentiate.

Additionally probably "Optimized for Evolution" should probably be the First item, not the last, as this is the aspect of P3 that makes it's stand-alone potential clear. Maybe even pushed to "purpose."

[GerryG]

Is there an actual list somewhere that could be linked?

If I get what you are saying, I think this would help me a lot. I want to understand better what you are doing so we can find related work that can help us. A little looking around makes me think a lot of this is used in compiler design and implementation, and go is particularly rich in these tools and application. It isn't exactly the same, but we should need to implement parsers from the ground up. The go syntax trees that are generated by the parser (ast) seem like just the ticket.