Week 8: GuardScript - Backend Feature Development and Script Protection Modules

1. Objectives

  • Expand the backend into the main GuardScript functional areas.
  • Complete the management flow for project, file, license, team, and access control.
  • Implement script protection modules and prepare for AWS migration.

2. Weekly Tasks Breakdown

DayMain TaskDetailsStatus
MonProject and File Flow Development- Built APIs for script creation, content updates, file tree organization, and entry point assignment.
- Prepared the foundation for bundle generation and protected content flow.		Completed
TueLicense Management Completion- Implemented single and batch license creation.
- Supported license export, status toggling, HWID lock, and HWID reset flow.		Completed
WedTeam and Workspace Authorization- Built invitation flow and role-based team management inside the workspace.
- Standardized member and invitation handling through backend logic.		Completed
ThuAccess Control and Protection Module- Implemented access list handling with whitelist and blacklist logic.
- Integrated content encryption and prepared loaders for supported languages.		Completed
FriFrontend Integration Support- Checked API behavior with the workspace screens on the frontend.
- Adjusted response data to make integration and display more consistent.		Completed

3. Outcomes

  • The main backend modules of GuardScript were established in a much more complete form.
  • Workspace/project/license data flow became clearer and more integration-ready.
  • Script protection started to move from design into concrete implementation.

4. Issues & Solutions

  • Issue: Backend scope expanded quickly, requiring consistency across permissions, data models, and response formats.
  • Solution: Grouped logic by domain and standardized flows before extending more features.

5. Next Steps

  • Start migrating GuardScript toward AWS serverless architecture.
  • Shift focus to DynamoDB data organization, S3-based storage, and Lambda deployment.