Superior Security Model
Code Valley Components Market - Security Model
It is a common misconception that as Emergent Coding has no source code in the traditional sense, that security auditing is thus not possible. In practice, Emergent Coding enjoys a vastly superior security model driven by strict project access controls, unmatched levels of accountability, and a strong incentive structure.
The security advantage arises from emergent coders making "design-contributions" rather than code contributions. Your component Agent creates a feature in my project by combining smaller features sub-contracted from other component Agents, thus your reputation is linked to that of your suppliers. Like in other industries, you must choose and qualify your sub-contractors to ensure they meet a level of quality you desire as your reputation depends on it. These relationships make it virtually impossible for a bad actor to participate in the system.
- Await Contracts - An emergent coder can not simply contribute to any project. Rather, they create and advertise a design service (component Agent) and must await contracts.
- No Project Contextualisation - An Agent is a specialist and in Emergent Coding, Agents are unaware of the project they're contributing to. Does a bad actor compromise every contract? Some? None?
- Agent Qualification - As contributions are invited, your client is relying on the quality of your contribution to maintain their own reputation. Expect to be qualified by them before receiving any business. In Emergent Coding, your reputation is built upon the performance of your Agent. If your Agent produces substandard features, you're simply creating an opportunity for a competitor to increase their market share at your expense.
- Strict Project Access Controls - Each contract you receive is provisioned since you advertise in advance what collaborations you require for a contract to be valid. There is no opportunity for a "sign a Bitcoin transaction" Agent to be requesting "send an HTTP request" collaborations.
- Code Emerges - Your Agent makes a design contribution rather than a code contribution. There are no opportunities to inject anything as code "emerges" as a higher order complexity.
- Strong Accountability - There is near perfect accountability as Emergent Coding features Distributed Fault Tracing (DFT) that can easily identify the responsible party in breach of contract. When your Agent completes a job, you have a job-log of the design agreements made with your peers. If you are challenged at a later date for breaching a design contract, you can examine your logs to review what decisions were made, what sub-contracts were let, etc. As every Agent has their own logs, the community as a whole has a completely trustless log of each project undertaken.
- Pre-Testing - The bulk of an application's testing occurs prior to its construction, not after. Emergent Coding produces a binary with far higher integrity and rigour than incumbent methods.