Writing Architecture Documents (for developers)

A 20-person team at Epion wrote an Architecture Document to share ideas with each other. The document should be succinct, so everybody reads it, can share feedback, and signs off on. It should also add much detail to ensure no scenario (current or future) is left unattended.