Software design draft rules

I'm mostly just posting this here so my players can see it. Maybe at some point I'll expand on  it.

Software is made out of  code fragments (also known as code frags). Code frags can be created at a rate of one frag per 10 hours of work. They can also be found in information systems or recovered from broken code. Basic software requires 3 frags per level, and takes an hour to assemble. Special types of frags exist, such as eureka frags and dubious frags. Rules for these will be introduced when the're first found

Basic Programs Types

ICE - Counter intrusion software meant to thwart unauthorized users

ICE Breaker - Software designed to break ICE

Agent - Autonomous software that makes decisions and takes actions without input from the user. Can be combined with other programs like ice breakers and payloads

Payload - Software used to effect undefended systems. The two most common are Control Spikes, which grant control of the target system, and Data Siphons, which hijacked data. Other more exotic versions exist.

Red Queen decay

Digital Warfare is in a state of constant evolution. Strategies and counter strategies come and go. Frequently used software runs the risk of becoming obsolete. Each time a piece of soft ware is used, roll its Red Queen die. On a 1, that soft ware is now obsolete and users suffer disadvantage on all checks. Most programs have a Red Queen die of d6.