HTTP://DEVELOPMENT.EXECHANGE: The Dev 3.0 CommunityOur goal is to build a system such that every individual involved wants to be dedicated to their work while simultaneously providing he compensation and support structure for everyone’s initiative. While compensation is obviously a key reason for employment, those at the pinnacle of their careers have higher priorities in choosing their professional field. There are many in the development fields, and we think very generally and abstract here, that are well compensated yet dissatisfied with their life in general – we contend this is because project space it not shared across organization space and therefore human resources have limited ability to define and choose projects.More than just software, development 3.0 is at its core about manifesting ideas into reality by the creation, and sharing, of toolkits. Open Source is only part of the solution - and at development.exchange we encourage the use of “copyfree” licensing, that is source code that is modifiable and exchangeable without attribution or republish, i.e.: the least restrictive possible – we must develop compensation mechanisms that go beyond exchange medium. The dev.ex paradigm is to manifest creation through communications.Jason L. LindJLL_640c27a0-3a5a-11eb-add7-d4d02d83ea00USAFEmployersIn today’s environment work assignment is a unilateral contract where the employer takes ownership of an individual’s ability to make decisions. While this is ostensibly effective from a top down, chain of command, management perspective, we contend it is not only wrong and unfair but undermines the effectiveness of the organization. (Lind Innovation Mission Statement, Lind 2008)OrganizationsLarge modern organizations almost certainly have a number of subjects who are unhappy with their position within the organization and the organization in general.EmployeesMake no mistake about it, when a person joins an organization become a subject of that organization – regardless of the type of that organization. Organizations exist to accomplish goals and more often than not the statement of those goals are ambiguous to the extent that many subjects are unable to understand them. Often the processes to implement the goals of an organization are so complex that it is impossible to expect all those involved to understand the motivation and intent behind those processes. Processes are defined and implemented by all subjects of the organization, both formal and informal, and those processes are constantly in flux.GroupsSince it is impossible for any one group of people to understand the implementation of an organization, hierarchical command and control may be effective from setting high level goals but it cannot be effective in the implementation of those goals. An underlying assertion in the chain of command solution is that every goal requires a single solution – when in reality it is often impractical to determine the correct solution until competing solutions are in place. Development.exchange delivers this functionality to organizations large and small.Field & Factor GroupsFIELDS AND FACTORSWarfightersWARFIGHTING -- “An active struggle between competing entities”: Sun Tzu’s thousands of years old treatise: “The Art of War” has been used by business and political leaders for generations to frame decisions that go well beyond armed conflict. This part of the field is responsible for interacting with competition organizations.EducatorsEDUCATION -- While the other four fields could be describes as “Operations Focused”, according to ATR Operations – while existing in a complex relationship with Operations, is indeed on the opposite side of the spectrum. If we had to pick one, and only one, field as the most important it’s a very easy case to make that organizations that deal with imparting knowledge and training on their subjects are going to be more successful than those who do not.GovernorsGOVERNANCE -- “Direct or strongly influence the behavior of”: the Governance Field is responsible for setting high level policy and procedures for the entire organization.ArchitectsARCHITECTURE & ENGINEERING -- Whereas Architecture is about design, Engineering is about application – however, like all 5 fields, it is impossible to separate one without the other.EngineersICANNXDS enabled domains are built on top of ICANN and the existing DNS infrastructure – it is a protocol, with a public reference architecture utilized by agency assets, that defines available operations in a next-order logical functional mapping over DNS Zones. In addition to mapping subdomain paths, it provides hints at the schema of blocks and their operations and implementing protocols.SwaggerThink of it as a more abstract and syndicated version of Swagger.Department of DefenseOur goal is to find a DoD sponsor (US CYBERCOM?) for *.us.mil.* that will take the responsibility of administering the authority of the US Military Namespace on the Nf3.agency Suite. Ideas manifested in reality ... a world without borders_640c2912-3a5a-11eb-add7-d4d02d83ea00To enable organizations to determine correct solutions_640c2a34-3a5a-11eb-add7-d4d02d83ea00DedicationCompensationSupportWorkLeverageALL-DOMAIN TRANSFORMATION (ADT) -- At development.exchange we recognize that Strategy, Culture, Capital and Knowledge exist on a continuum: that is it is impossible to affect one facet without the others. This is a fact many modern organizations fail to account for, let alone leverage.StrategyCultureCapitalKnowledgeTransformationThe diagram to the right expresses the Transformative Continuum which dev.ex leverages: specifically that Global Level Domains Create, Communicate and Manifest into the 4 facets.CreationCommunicationManifestationNetworkingIt is important note these domains are not traditional ICANN tld’s: development.exchange sits in .int having participating organizations federating with each other in an ad hoc network – each representing any number of geo’s including .us, .uk, .jp or even .cn as in order to onboard some of our allies we cannot outright reject any actor and the platform.TrustworthinessOstensibly this may seem to have obvious OPSEC and INFOSEC implications: however this platform is architected around a distributed ZeroTrust model – in that development.exchange is actually a collection of components wholly deployed and managed by the implementer;Standardizationwe are simply orchestrating the standardization of API’s and languages to encourage a “common dialect” at scale.FacetsAt an even more abstract level: domains interact with reality through Facets – which in turn are built through Fields that are bounded through Factors.FieldsFields are logical constructs for interaction and there is an implication that each Facet and Domain operate in each of the five Fields: Warfighting, Education, Governance, Architecture and Engineering.FactorsFactors can loosely be defined as: component of thought that interact on the continuum with Human and Algorithmic being undisputed and others being more fluid between implementers.FederationDifferent organizations have different perceptions of their “Federating OPSEC Requirements”, but even more so there are natural order implications of applying warped interpretations of OPSEC for when Strategy and Culture are shared trust is built, development.exchange’s ambitions reach far beyond implementation of projects but rather implementation of policy in a world without borders.SecurityProper OPSEC does not entail hiding implementation details but rather developing an operation that is secure from failure – and providing mechanisms to research and develop enhanced OPSEC is in itself a project that would be ideal for execution on The Exchange.SuccessIn our view every successful actor, and hence organization, will find areas to not only take leadership roles but also have the wisdom to follow, or even get out of the way of, great leadership in the sense that reinventing the wheel is rarely a worthwhile endeavor.LeadershipFollowershipCollaborationCollaboration is the lifeblood of any successful actor and as such we anticipate significant demand for the development.exchange platform. dev.ex at its heart is Cognitive Warfare (CQW) as a service: providing an avenue for players in all positions to affect reality through cyberspace.WorkBuild a system in which individuals are dedicated, compensated, and supported in their work_640c2c00-3a5a-11eb-add7-d4d02d83ea00 SupportSupport member initiatives_640c2d18-3a5a-11eb-add7-d4d02d83ea001Initiative Support -- At development.exchange we seek to support all our members' initiativesControlEnable members to control their own destiny_640c2e4e-3a5a-11eb-add7-d4d02d83ea002Ownership -- Equity is more than stock shares and dividends - it about the ability to control your own destinyCompensationSupport multiple types of compensation_640c3222-3a5a-11eb-add7-d4d02d83ea003Compensation -- Monetary support only part of the equation: * Vanity * Reference * ExperienceExchangeAllocate work based on the needs of individuals_640c3358-3a5a-11eb-add7-d4d02d83ea004The Exchange -- Work is allocated on the needs of the individual not the needs of the apparatusTransformationStructure and automate transformation processes at scale_640c3470-3a5a-11eb-add7-d4d02d83ea005CDDT LOOP – NEXT-ORDER OODA -- This loop is occurring above the “Transformative Continuum” and between various entities on domains – and should not be interpreted as single project or solution as these processes are very abstract. At its core development.exchange is seeking to structure and automate these processes at scale. OODA on the other hand happens by individual actors, and probably not even organizations.ConceptualizationResearch and dream_640c372c-3a5a-11eb-add7-d4d02d83ea005.1CONCEPTUALIZE: RESEARCH AND DREAMPlatformConstruct a logical platform for each cycle_640c3858-3a5a-11eb-add7-d4d02d83ea005.1.1Department of DefenseOur Strategy to realize a fundamental shift in Capital and Culture in the DoD Energy arena begins with high level engagement of global level domains starting with handing over Exchange Directory Services (XDS) authority to various global governmental and non-governmental entities. XDS – under design - is a decentralized and distributed protocol for defining bindings between microservices, applications and widgets used by external resources and the platforms to achieve elegant cross boundary transformations and federations. KING’S KNIGHT TO BISHOP’S 3 – THE NF3.AGENCY -- Constructed around the CDDT Loop, with a logical platform for each cycle, The Knight to f3 Agency seeks to transform Command, Coalition and Operations at a macro level via CQW. Agency property will be 100% “copyfree” while deployments – including data/code and binaries – will be under the absolute control of their owner.DesignFormalize solutions_640c3966-3a5a-11eb-add7-d4d02d83ea005.2DESIGN: FORMALIZE SOLUTIONSAddressing & InteractionOffer a distributed and decentralized approach to account addressing and interaction_640c3a92-3a5a-11eb-add7-d4d02d83ea005.2.1ICANNThe top-level-domain/country-level-domain/global-level-domain path is unique across ICANN level domains implementing that XDS tenant. The slices (a) that come before the path are owned by the ICANN domain and are a meta representation of services or applications whereas the back end of the domain path is owned by the top/country/global path are implementations of those meta constraints. At the meta level XDS can be configured to produce directory listings of tenants and applications.Specifically we will be introducing an “Exchange Directory Services” (XDS) protocol that will offer a distributed and decentralized approach to account addressing and interaction across the *.exchange platform – as well as four languages, and services to syndicate them: StratML (already an ISO/ANSI standard) – for strategic modeling, CultureML – for describing cultural aspects such as formal and informal organizational structure, CapitalML – for describing human, technical and financial capital structures, and KnowML which will combine these three elements into knowledge... All XDS enabled domains have a metaservice its root with implementations for each top-country-global pair combination, applications do not have their own XDS. In addition to Read, XDS exposes secure management API’s for automated modification of the metadata.DevelopmentProduce an output_640c3bfa-3a5a-11eb-add7-d4d02d83ea005.3DEVELOP: PRODUCE WORK PRODUCTTestingCheck the solution_640c3dd0-3a5a-11eb-add7-d4d02d83ea005.4TEST: CHECK SOLUTION ImprovementConceptualize improvements_640c3f92-3a5a-11eb-add7-d4d02d83ea005.5-> CONCEPTUALIZE IMPROVEMENTS2020-12-09http://development.exchange/OwenAmburOwen.Ambur@verizon.net