Transport strawman ladder

[zealsham]

This document describes the transport mechanism of fungi as a strawman ladder.

[arminsabouri]

@bc1cindy @0xZaddyy this document should describe largely your work so far. please review in that lense

[arminsabouri]

Suggested change

	The Desing follows two main rules.
	The design follows two main rules.

[arminsabouri]

Suggested change

	Framing costs 4 bytes per message on stream transports. The channel contract deliberately exposes no ordering across channels and no deduplication to kep the sneakernet degradation requirement.
	Framing costs 4 bytes per message on stream transports. The channel contract deliberately exposes no ordering across channels and no deduplication to keep the sneakernet degradation requirement.

[zealsham]

Thanks for catching that, i'll fix it

[bc1cindy]

I might be partly at fault here for mixing the expositional purpose of the outline with the implementation i've been working on (which was pretty useful)

but the idea of this doc is to be an expositional outline and this reads more like a spec, even though the design hasn't stabilized yet

I believe a good path would be to rewrite the outline using only high-level bullets to guide the actual writing, like explaining the progression of communication patterns and their trade-offs

please take a look at this comment this should be for expositional purposes, no need to go into details

[zealsham]

I might be partly at fault here for mixing the expositional purpose of the outline with the implementation i've been working on (which was pretty useful)

but the idea of this doc is to be an expositional outline and this reads more like a spec, even though the design hasn't stabilized yet

I believe a good path would be to rewrite the outline using only high-level bullets to guide the actual writing, like explaining the progression of communication patterns and their trade-offs

please take a look at this comment this should be for expositional purposes, no need to go into details

i agree that some technical details spilled into the doc , as i strictly followed the outline. However in some places a reader actually do need to understand the technical reason behind a solution being problematic. i'll keep the technicalities for such cases and remove it where its not needed.