Day 7 Data Structure Codex AI Architect

Data design tasks based on Codex Client Workspace

Differences in data structure understanding, terminology fragmentation, and change impact propagation issues that startups face during the MVP development stage
This is a practical AI collaboration task board that automatically analyzes and resolves using Codex.

Day 7 Startup MVP Tasks

From connecting functions to static screens, verifying user journey movements, and detecting abnormal input errors — use Codex as a scenario coach and collaboration partner to assemble a high-quality service.

TASK 1
Task 1

Task 1. Practice resolving gaps in data structure understanding

Task 01: Alignment of data structure between planning and development (Data Structure Alignment)

By deriving key entities and relationships (Mermaid ERD) from planning meeting minutes written in natural language, the gap in data model understanding between planners and developers is resolved with AI.

target numberCompletion of ERD schema and data structure definition
core toolsCodex Client Workspace
scope of practiceData Structure Alignment
Step 1 📂 Prepare meeting minutes file (day7_meeting_notes.md) and upload Codex
Step 2 🔍 Request Codex to derive entities and create Mermaid ERD
ERD Entity Mapping Data Alignment
expected output erd-schema.md (Data Specification and ERD)
Task 1 Entry to the lab
TASK 2
Task 2

Task 2. Practice verifying user scenarios

Task 02: Multi-screen path information leakage analysis and preservation guard (User Scenario Review)

Find disconnections in the user journey, such as the search filter being released when going to details in the list, and correct them with sessionStorage caching.

target number100% filtering recovery rate when going back
core toolsCodex Client Workspace
scope of practiceState Hydration & Session Caching
Step 1 📁 Submit user scenario specification (day7_user_flow.md) analysis
Step 2 🔍 Request Codex to create an information recovery session helper script
Scenario flow SessionStorage State Backups
expected output day7_scenario_solution.js (Escape Guard script)
Task 2 Entry to the lab
TASK 3
Task 3

Task 3. Practice finding functional errors

Task 03: Continuous submission lock and visual boundary guard (Feature Validation)

Guard logic is inserted by detecting duplicate database insertion errors caused by multiple mouse clicks and past time reservation registration malfunction points.

target numberOperation to prevent duplicate hitting and past date registration
core toolsCodex Client Workspace
scope of practiceDefensive coding & Logic Boundary
Step 1 📂 View and upload vulnerable code (day7_feature_validation.js)
Step 2 🔄 Request application of isSubmitting lock variable and validity period comparison formula to Codex
Double Submit Lock Disabled State Logic Guard
expected output day7_robust_validation.js (Security Guard Completion Source)
Task 3 Entry to the lab
🚀 In-depth Mission — AI-based software function completion process
MISSION 1
Mission 1

Mission 1. Design decision recording practice

Mission 01: Automatic creation of Design Decision Log (Record Why)

By writing the database normalization and architecture decision background into a Design Decision Log standardized in Codex, duplicate discussions and design mistakes are prevented when new team members join.

target numberComplete design decision record document (DDL)
core toolsCodex Client Workspace
scope of practiceDesign Decision Log & Knowledge Mgmt
Step 1 📂 Preparation of technical design meeting conversation transcript (tech-design-meeting.md)
Step 2 🔍 Request Codex to standardize resolution items, background reasons, and alternative review
Decision Log Architecture Knowledge Mgmt
expected output design-decision-log.md (Decision record document)
Mission 1 Lab Entry
MISSION 2
Mission 2

Mission 2. Exception scenario discovery practice

Mission 02: Derive all concurrency and integrity edge cases (Edge Case Discovery)

Edge cases such as concurrency errors, referential integrity collapse, and hard delete failures that may occur in the defined DB schema and foreign key reference structure are discovered in advance using Codex.

target numberCompletion of exception scenario report and response plan
core toolsCodex Client Workspace
scope of practiceEdge Case Discovery & Integrity Guard
Step 1 📂 Preparation of DB physical schema definition (database-schema.md)
Step 2 🛡️ Derive all concurrency and integrity exception cases and establish countermeasures with Codex
Edge Cases Concurrency Soft Delete
expected output edge-case-analysis.md (Exception scenario report)
Mission 2 Lab Entry