# Hacker Divergents
# Phase 23 — Software Progression System

Status: IN PROGRESS

---

## 1. Objective

Phase 23 introduces the software progression system of Hacker Divergents.

Players do not simply receive advanced software automatically.

Software is constructed and upgraded by combining source fragments, code components and technical discoveries obtained through gameplay.

---

## 2. Core Progression

Primary flow:

Mission / Server / Event
    |
    v
Source Fragment
    |
    v
Player Fragment Inventory
    |
    v
Software Recipe
    |
    v
Software Construction
    |
    v
Player Software
    |
    v
Upgrade Recipe
    |
    v
Improved Software Version

---

## 3. Software Definitions

Software definitions represent the global catalog of software that can exist in the game.

Examples include:

- cracker
- scanner
- log cleaner
- firewall
- antivirus
- exploit tool
- packet analyzer
- malware builder
- network mapper
- password tool

A software definition does not represent player ownership.

It defines the identity and general behavior of a software family.

---

## 4. Source Fragments

Source fragments represent reusable or consumable pieces of technical knowledge/code obtained through gameplay.

A fragment may contain metadata such as:

- code
- family
- component type
- rarity
- description
- active status

Possible component types may include:

- core
- parser
- protocol
- engine
- optimization
- payload
- signature
- defense
- utility
- research

The exact catalog may expand in later phases.

---

## 5. Fragment Acquisition

Source fragments may originate from:

- missions;
- NPC servers;
- world servers;
- event rewards;
- research;
- exploration;
- rare drops;
- future game systems.

Acquisition history should remain auditable.

---

## 6. Player Fragment Inventory

Player fragment inventory represents fragments currently owned by a player.

The inventory must support:

- fragment ownership;
- quantity;
- acquisition;
- consumption;
- duplicate fragments.

Fragments belong permanently to the player unless consumed.

---

## 7. Software Recipes

Software construction is recipe-driven.

A recipe defines the fragments/components required to construct a specific software version.

Example:

Cracker 1.0

requires:

- cracker_core_01
- authentication_parser_01
- network_io_01

If all requirements are satisfied, the player may construct the software.

---

## 8. Player Software

Player software represents actual software constructed and owned by the player.

A player software record must be distinct from the global software definition.

It may contain:

- software definition;
- current version;
- progression state;
- construction timestamp;
- upgrade timestamp;
- future capability metadata.

---

## 9. Software Versions

Software progression is versioned.

Examples:

- 1.0
- 1.1
- 2.0
- 2.5
- 3.0

Version progression must be defined through explicit upgrade rules.

A software version MUST NOT be increased by directly editing a player record outside the authoritative upgrade service.

---

## 10. Upgrade Recipes

An upgrade recipe defines what is required to move from one software version to another.

Example:

Cracker 1.0
    +
advanced_auth_fragment
    +
optimization_fragment
        |
        v
Cracker 2.0

Upgrade requirements may later include:

- fragments;
- credits;
- research;
- player level;
- software dependencies;
- mission milestones.

Any economic cost must use existing authoritative ledger services.

---

## 11. Fragment Consumption

Fragments used by a construction or upgrade recipe may be consumed.

Consumption must be atomic with the construction or upgrade.

Either:

- required fragments are consumed;
- software is constructed/upgraded;

or neither occurs.

Partial consumption is forbidden.

---

## 12. Permanent Progression

Source fragment ownership and constructed player software are permanent progression.

World round rotation MUST NOT:

- erase player software;
- downgrade software;
- delete fragment inventory;
- reset software versions.

World rounds affect operational network state, not permanent technical progression.

---

## 13. Economy Separation

The software progression system is distinct from:

- credits;
- diamonds.

Credits may later be used as an explicit recipe cost.

Diamonds must not implicitly unlock gameplay software progression.

Premium purchases and software progression remain separate systems unless a future design explicitly introduces cosmetic or convenience integration.

---

## 14. Ownership Authority

Planned authority boundaries:

Fragment inventory mutations:
    PlayerFragmentInventoryService

Software construction:
    SoftwareConstructionService

Software upgrades:
    SoftwareUpgradeService

Player software version mutations:
    SoftwareUpgradeService

Direct scattered mutations are not allowed.

---

## 15. Auditability

The system should preserve history for:

- fragment acquisition;
- fragment consumption;
- software construction;
- software upgrades.

Historical events must not be rewritten when catalog definitions later change.

Snapshots may be introduced where required.

---

## 16. Initial Phase 23 Roadmap

23A — Architecture
23B — Domain IDs
23C — Software Definitions
23D — Source Fragment Catalog
23E — Player Fragment Inventory
23F — Fragment Acquisition History
23G — Software Recipes
23H — Software Construction Service
23I — Player Software Inventory
23J — Software Versions
23K — Upgrade Recipes
23L — Software Upgrade Service
23M — Fragment Consumption
23N — Duplicate Fragment Handling
23O — Rarity / Drop Metadata
23P — Software Capabilities
23Q — Gameplay Requirement Integration
23R — Round Persistence
23S — Audit / Regression
23Z — Final Consolidation

---

## 17. Phase Status

PHASE 23A — IN PROGRESS

Overall:

PHASE 23 — SOFTWARE PROGRESSION: IN PROGRESS