Dan Connolly

@AbnerZheng and I talked about this today. I don't have rights to merge PRs, but that's OK, at least for now; we want changes to go through @pyrocto anyway. For...

The purpose that interests me is that people who translated the architecture document know it well as a result.

https://github.com/rchain/mobile-process-calculi-for-blockchain/pull/3 is still pending, since January.

The diagrams and such from the [RChain VM talk][1] by @leithaus and co in Boulder are really good. I hope to integrate them into an arch doc revision. [1]: https://www.youtube.com/watch?v=3R3IL1bGm0s&t=616s

I made some review progress June 18; I used an [rchain-archdoc](https://discordapp.com/channels/458312138889363476/458312138889363478) discord server to take notes as I read along, and filed important stuff in the https://github.com/rchain/architecture-docs/ repo

I still plan to work on it. It's only tangentially related to Translation though...

@JoshOrndorff hopes to take a look at a chapter or so and sync with me next Thu. I brainstormed a little with @TrenchFloat about some options too. I'll let him...

The Mercury design isn't much to write home about. The architecture can be aspirational; we don't have to get there right away. The architecture document is a recruiting tool; at...

> I've forked the repo to https://github.com/rchain-community/architecture-docs so we can collaborate and merge each others PRs without the lag time in the main rchain repo. Oh. Commits there won't go...

> regarding the repo choice, I was thinking that not immediately publishing to RTD was a feature. That's what branches and such are for, no? Why shouldn't a merged PR...