Research
Research
This area holds the investigations behind decisions: surveys of other frameworks and engines, comparisons, and experiments. Each document states its question and date, links every claim to a source, and says what it changed.
Research is evidence, not a commitment. A decision belongs in Decisions. A document belongs here when it answers a question about other systems or about options, cites sources for its claims, and has been checked against those sources by someone other than its author. A choice between options, with a status, belongs in a decision record.
Documents, in reading order
Start with the synthesis, then read the document for the layer you care about. Word counts are for the page body. The verdict is the reviewer’s final one; “Accept with fixes” means the document is usable once the reader applies the residual-error list at the end of the review.
| # | Document | What it answers | Words | Review verdict |
|---|---|---|---|---|
| 00 | Research synthesis | What do the seven research documents add up to, and what architecture do they suggest for Mesh? | 5,209 | No review file |
| 01 | Ash core feature inventory | What does Ash 3.x offer, feature by feature? | 10,575 | Accept with fixes |
| 02 | Ash DSL and extension system | How do Spark, extension authoring and Igniter let Ash define and extend its DSL? | 16,202 | Accept |
| 03 | Ash run-time architecture | How does Ash run an action: lifecycle, data layer contract, expressions, policies and loading? | 16,049 | Accept with fixes |
| 04 | The Ash ecosystem packages | Which Ash ecosystem packages matter for domain work, and what do they do? | 16,756 | Accept |
| 05 | Ash strengths and weaknesses | Where is Ash strongest and weakest, according to verified evidence? | 12,509 | Accept |
| 06 | TypeScript prior art | Which TypeScript projects already try to “declare the model, derive the rest”? | 14,079 | Accept with fixes |
| 07 | Candidate foundation libraries | Which libraries could Mesh build on, layer by layer? | 16,255 | Accept with fixes |
| 08 | Durable workflow engines | Which durable workflow engines exist, and what adapter interface could Mesh offer them? | 10,588 | Accept with fixes |
Reviews
Each review is an independent fact-check of one document against primary sources. They are moved here unchanged, so they refer to the original local file names.
- Review: Ash core feature inventory: Accept with fixes, 8,085 words.
- Review: Ash DSL and extension system: Accept, 7,592 words.
- Review: Ash run-time architecture: Accept with fixes, 8,647 words.
- Review: The Ash ecosystem packages: Accept, 9,507 words.
- Review: Ash strengths and weaknesses: Accept, 9,997 words.
- Review: TypeScript prior art: Accept with fixes, 11,365 words.
- Review: Candidate foundation libraries: Accept with fixes, 11,041 words.
- Review: Durable workflow engines: Accept with fixes, 7,592 words.