Hello,
A bit about myself.
Family: Single with two kids (two young boys 8 & 10 yrs old)
Passion: EoC and Sea Kayak (both building and navigating). Ho... Yes. I almost forgot: and computers
This is my racing baby (my true Wife): One Ocean Kayak Expedition Single (Only 50 Pounds :-p )
:
And I'm starting to build a One Ocean Kayak Cape Ann Double this Fall. Mainly to accommodate my girlfriend 
Soon after I finished my single last Fall, She became jealous and highly possessive I was not able to get out of the house so to speak LOLLL (I'm joking). So this is the reason why I decided to build another one.
The central bulkhead will be roomy enough to hold a 24-beers box (or a removable seat for one of my child). The aft bulkhead will hold the other removable seat.
:
career: Since 1990 I'm a Freelance IS/IT Consultant. My fields are : Strategic Advisory, Architecture & Modeling, Project Management (PMI PMP), Security & Hacking (yeah,yeah white&gray...) and IS/IT Audit (ISACA CISA).
My primary domain is military C4ISR (Command-Control-Communication-Computers-Intelligence-Search-Rescue). EoC game is a good example of a C4I system Thus, "Real World" C4ISR modeling is easily applicable to EoC as well. So don't be surprised if I'll propose some bits of C4I "best practices" inside the global Architecture at its upper levels. It may seems "disconnected" at first but at lower levels you will reall your existing components PLUS room for further expansion if desired but in an orderly manner. Just by adding the "behind the scene" integration logic at the modeling level, this will help the team to better locate and position added features and still keep the integrity and overall coverage of the EoC Universe. 
and greatly simplify design and development process and communications inside the team.