Chapter 31 Underworld Backend Management System (3)

At the same time, in the underworld.

Lord Yama was happily admiring the new dress Zhang Mo had chosen for her while directing the ox-headed and horse-faced demons to put the new equipment they had received into the warehouse.

At this moment, a judge who was helping her handed her a black folder respectfully: "Your Majesty, this was just burned. It says on it, 'To Your Majesty, please confirm immediately.'"

Jingci curiously took it and opened it—

Underworld Backend Management System V1.0 - Product Requirements Document (PRD)

I. Basic Document Information

Project Name: Underworld Backend Management System

Version Number | V1.0.0 |

|Author|Zhang Mo|

|Scope of Application| Core business management of the underworld (automatic calculation of the Book of Life and Death, historical error correction, reincarnation process, personnel attendance, etc.)|

|Research and Development Cycle|7 working days|

-------

II. Background and Objectives

1. Background of the requirement

The management of the Book of Life and Death in the underworld relies on handwritten records by judges and manual calculations, which frequently leads to errors such as "inconsistencies between operation records and actual deductions" (e.g., the log record for "animal abuse" deducts 2 years of lifespan, but the actual total deduction is 20 years), resulting in chaotic lifespan accounts and an accumulation of historical errors.

The Heavenly Dao assesses the Underworld's error rate every thousand years (the current error rate has reached 5%, far exceeding the passing line of 0.1%). If it does not rectify the situation, it will face the punishment of "annihilation".

2. Core Objectives

The entire process of "operation-calculation-recording" of life expectancy is automated, eliminating new errors such as "inconsistency between logs and totals" and ensuring zero errors in newly generated life expectancy data.

Complete the screening and correction of historical lifespan errors, accurately locate the accounts that the judge miscalculated, and deal with them separately according to the two scenarios of "not dead" and "already dead", so as to completely solve the problem of balancing accounts.

Digital management of the cycle process and attendance of underworld personnel improves overall office efficiency.

-------

III. User Roles and Permissions

|Role|Scope of Responsibilities|System Permissions|

|King of Hell| Approves quotas for resurrected individuals, views global data, modifies system rules, and customizes the error lifespan allocation for deceased individuals | Full permissions (including deletion, approval, rule configuration, and custom lifespan allocation)|

|Judge| Enters data on behavior in the mortal realm, processes newly generated lifespan error warnings, and assists in screening historical error data. |Data entry, new error processing, and assistance with historical error screening (no deletion or lifespan allocation permissions)|

|Ox-Head and Horse-Face| Register information on deceased souls, execute reincarnation assignments| Basic data entry, status update (primarily read-only permissions)|

|Meng Po (to be recruited)|Records Meng Po soup consumption and usage|Entry permission only for the "Meng Po soup management" module|

-------

IV. Detailed Requirements of Core Functional Modules

1. Book of Life and Death Management Module (Core, Key Optimization)

1.1 Automatic lifespan calculation (eliminating new errors)

- Function Description: This function automates the entire process of "entering behavior in the mortal realm - matching rules - automatically deducting/increasing lifespan - synchronously generating logs," ensuring that operation records are consistent with the total lifespan in real time and eliminating errors from manual calculation.

- Rule Configuration: Supports custom rules for Yama (example below). The rules have built-in "forced validation logic". After the behavior is entered, the rules are automatically matched and calculated. The deduction/increment values ​​cannot be manually modified.

|Behavior in the living world|Impact on lifespan|

|Killed 1 person|-5 years|

Animal abuse | -2 years |

-Interaction logic:

1. When the judge selects a "type of behavior in the mortal world" (such as "animal abuse"), the system will automatically display the corresponding impact on lifespan (-2 years), which cannot be modified;

2. After the judge confirms the "Dead Soul ID/Name", the system updates the "Remaining Lifespan" of the dead soul in real time and generates a log simultaneously (format: [Time] Judge XXX entered "Zhang San abused animals", lifespan -2 years according to the rules, current remaining lifespan is 68 years).

3. Logs are forcibly linked to "remaining lifespan" data. Modifications to logs require approval from the King of Hell, and the system automatically recalculates lifespan after modification to avoid data disconnection.

1.2 Historical lifespan error screening (locating legacy issues)

- Function Description: The system automatically compares the "historical handwritten log records" with the "actual lifespan deduction total", locates all error data where "records and totals are inconsistent", and generates a "historical error list".

- Screening rules:

1. Using the "Dead Soul ID" as the unique identifier, batch import historical handwritten logs (the "Bamboo Slip Data Digitization" must be completed first, with the judge assisting in entering the data into the system).

2. The system automatically calculates the "cumulative lifespan impact of logs";

3. Compare the "cumulative lifetime impact of logs" with the "remaining lifetime of historical records". If the difference is ≥1 year (including positive and negative deviations), mark it as "error data" and include it in the list.

- Error list fields: Soul ID, Name, Gender, Date of Birth, Cumulative Lifespan Impact from Historical Logs, Remaining Lifespan from Historical Records, Error Value (positive number means "less lifespan deducted", negative number means "more lifespan deducted"), Corresponding Judge, Error Type (e.g., "Animal Abuse Record -2 years, Actual Deduction -20 years, Error -18 years").

1.3 Historical Error Correction (Scenario-Specific Processing)

- Function Description: For the data in the "Historical Error List", it is processed separately according to two scenarios: "not dead" and "dead", to ensure that all residual errors are cleared.

-Processing flow:

1. The system automatically marks the status of the deceased souls ("not dead" or "dead", based on the "deceased soul status database" in the underworld).

2. Divide and conquer according to state:

Scene 1: Undead Souls

Operation logic: The judge views the error details (e.g., "Li Si, error -18 years", meaning 18 years were deducted too much), clicks "One-click correction", and the system automatically adds the error value (+18 years) to the current remaining lifespan and generates a correction log (format: [Time] Corrected Li Si's historical error -18 years, remaining lifespan after correction is 75 years, handler XXX).

Scene 2: The Souls of the Dead

Operation logic:

Step 1: The system automatically matches the deceased's immediate family members (based on the "Underworld Bloodline Database", prioritizing parents and children, and displaying a list of relatives and the current remaining lifespan of each relative).

Step 2: Choose one of two allocation methods (only Yama has the authority to do so):

Automatic Allocation: After Yama selects "Automatic Allocation", the system will allocate the error value (such as the extra 20 years) to the lifespan of relatives according to two strategies: "relatives' remaining lifespan from least to most" and "average allocation" (which can be selected by Yama). After allocation, a record will be generated synchronously (format: [Time] Yama Jingci automatically allocates Wang Wu's historical error + 20 years, allocates to son Wang Xiao Wu + 10 years, and queen Xiao Ya + 10 years).

Custom allocation: Yama manually enters the allocation values ​​for each relative (the sum of the allocation values ​​for all relatives must satisfy the error value). After submission, the system verifies and updates the lifespan of the relatives, and generates a custom allocation log.

Constraints: The maximum lifespan allocated to a single relative in a single transaction is 50 years; once allocated, it cannot be revoked, and the allocation certificate must be retained for verification by the Heavenly Court.

2. Recurrence Process Management Module

2.1 Registration at the Bridge of Helplessness

- Function: Records the time and status of the deceased souls crossing the Bridge of Helplessness (such as "passing normally", "refusing to drink soup", "causing trouble").

- Fields: Soul ID, Name, Crossing Time, Person in Charge (Ox-Head/Horse-Face), Exception Notes (optional).

2.2 Management of Meng Po Soup

- Function: Records the inbound and outbound data of instant Meng Po soup to prevent the loss of special supplies.

- Fields: Soul ID, Drinking Time, Person in Charge, Whether Amnesia is Confirmed (default "Yes", troublemakers are marked "No").

- Anomaly Handling: If marked "No", the system will automatically add the deceased soul to the "Key Monitoring List" and push it to the personnel on duty in the Reincarnation Path.

2.3 Allocation of the Cycle of Reincarnation

- Function: Automatically recommends a reincarnation path (human, animal, or heavenly realms, etc.) based on the deceased's good and evil deeds in life, and supports manual adjustment.

- Rule: A good/evil score of ≥60 points is recommended for "humanity", and a score of <60 points is recommended for "animality" (the threshold can be modified by Yama).

- Interaction: After clicking the "Assign" button, the system generates a "Reincarnation Certificate" (containing a QR code for scanning and verification at the Reincarnation Path entrance).

3. Underworld Personnel Management Module

3.1 Attendance Management

- Function: Records the working hours and leave status of judges, ox-headed and horse-faced guardians, etc.

- Rule: There are no fixed working hours, but the working hours on weekdays must be ≥8 hours.

- Abnormal alert: If you fail to clock in for 3 consecutive days or work less than 8 hours, the system will automatically send a warning to the authorities.

3.2 Access Control

- Function: Assign permissions based on roles, with a focus on controlling highly sensitive operations such as "lifetime allocation" and "error correction".

-Permission details:

King Yama: Approval of lifespan rule modification, custom allocation of historical error, resurrection, and log modification;

Judge: Recording of behavior in the mortal world, one-click correction of errors for non-dead souls, and digital entry of historical logs;

Other roles: Basic data entry only, with read-only access.

-Special Permissions: Yama's exclusive "Emergency Freeze" permission - can temporarily freeze the reincarnation process of any deceased soul (such as when a major misjudgment is discovered).

4. Data Statistics and Reporting Module

4.1 Core Dashboard

Key metrics displayed: total number of dead, new dead today, historical error correction completion rate (number of corrected errors / total number of errors), and zero error rate for newly generated lifespan data.

It supports filtering by "hall" (such as the Hall of King Qin Guang, the Hall of King Yama, etc.) to view the historical error status and correction progress of each hall.

4.2 Report Generation

Automatically generate the "Historical Lifespan Error Correction Report" (including error screening details, correction method distribution, and uncorrected pending tasks), the "Monthly Lifespan Zero Error Rate Report" (new data accounting status), the "Reincarnation Path Allocation Trend Chart," and the "Underworld Personnel Attendance Sheet."

It supports exporting as "bamboo slip electronic version" (a format specific to the underworld) or "living world Excel".

-------

V. Non-functional requirements

1. Performance Requirements

Supports ≥10,000 concurrent online users.

The automatic life expectancy calculation response time is ≤1 second, and the time for batch screening of historical errors (within 1 million data points) is ≤30 seconds.

Supports data storage for hundreds of millions of dead souls (historical data is automatically archived to the "Wangchuan Database" and can be retrieved at any time).

2. Security Requirements

All operation logs (including lifespan entry, error correction, and lifespan allocation) must not be tampered with and must be retained for ≥3000 years (for Heavenly Dao assessment). The logs must be linked to the operator's identity information (such as Judge ID or Yama's fingerprint record).

The approval process for resurrected individuals and the custom allocation based on historical errors require dual verification using both "King Yama's fingerprint" and "ghost fire password".

3. UI/UX Requirements

Overall style: dark gothic style, with buttons and icons incorporating elements such as skulls and crosses; the "historical error correction" module uses red warning color to mark errors to be processed and green to mark errors that have been corrected, making the visual distinction clear.

Simplified operation: Commonly used functions (such as one-click correction of errors for undead souls and quick entry of behavior in the mortal world) support "one-click operation"; Yama's "custom lifespan allocation" module provides "numerical input verification" (such as prompting "the current total allocation is insufficient, please supplement"), reducing operation errors.

-------

VI. Online Acceptance Standards

1. Historical lifespan error correction completion rate ≥ 99% (all screened errors have been processed without omission).

2. The error rate of newly generated lifespan data is ≥99% (within 1 month after going live, there are no new errors of "logs and totals are inconsistent").

3. The error rate of life expectancy has been reduced from 5% to below 0.1% (including historical corrections and new data).

4. Yama can use the "Custom allocation of lifespan for deceased souls" function normally, and the operation process is smooth without any lag or data errors.

-------

Jingci: ""

That's so professional!!!