WeWeb + Xano MVP Completion (Execution-Only – Spec Provided)

PROJECT OVERVIEW

I am building a supplier-readiness SaaS platform (DHML IQ) using:
- Frontend: WeWeb (partially complete)
- Backend: Xano (database + APIs already structured)

This project is NOT for designing a system. This is a strict execution role. You will implement features based on fully defined specifications, API contracts, and UI expectations that I will provide.

IMPORTANT: ROLE EXPECTATION
This is not a product design or architecture role. You are responsible for:
- implementing UI in WeWeb
- connecting to Xano APIs
- ensuring data flows correctly

You are NOT responsible for:
- defining logic
- designing system behavior
- making assumptions about functionality

STOP and ask if anything is unclear; do not infer.

CURRENT STATE
- WeWeb frontend is partially built
- Xano backend exists with core endpoints
- Dashboard UI exists but is not fully wired
- Scoring, blockers, and remediation logic are defined conceptually but need implementation

PROJECT OBJECTIVE
Complete the MVP by connecting and implementing the following system components:
1. Dashboard (Readiness Overview)
You will:
- connect dashboard to API
- display:
- overall readiness score
- readiness label (e.g., Developing, Progressing)
- last calculated timestamp

2. Readiness Breakdown
Display 3 categories:
- AI / Digital Readiness
- Compliance Readiness
- Contract Readiness

Each must:
- pull score from API
- display status (Strong / Needs Attention)

3. Blockers Section
You will display blockers dynamically from API
Each blocker includes:
- title
- description
- severity (High / Medium / Low)
- category (Compliance, Documentation, Profile)

4. Recommended Actions
Each blocker must map to a task:
Examples:
- Missing W-9 → “Upload W-9”
- Expired COI → “Upload COI”
- Incomplete profile → “Update profile”

Each task must:
- display CTA button
- trigger correct action (upload / navigate)

5. Document Upload (Critical)
You will connect file upload to Xano
- Implement W-9 and COI upload using existing Xano endpoints
- Connect upload UI in WeWeb to backend
- After upload, trigger data refresh
- Ensure dashboard updates accordingly (blockers removed, scores updated)

6. Profile Completion
You will:
- connect profile form fields to backend
- ensure updates persist
- trigger recalculation after save

7. Readiness Recalculation (UI Behavior)
When user completes actions:
- upload document
- update profile
You must:
- trigger refresh endpoint
- update UI dynamically

8. Recent Activity Feed
Display activity logs:
- profile updates
- document uploads
- assessment completion

API INTEGRATION (YOU WILL RECEIVE)
You will be provided:
- Xano Base URL
- Endpoint list
- Request/response examples
- Auth method
- Test user credentials

You are responsible for:
- connecting endpoints in WeWeb
- mapping responses to UI

SYSTEM LOGIC
Examples:
- Missing W-9 → blocker triggered
- Expired COI → blocker triggered
- Missing profile fields → score capped
- Document uploaded → blocker removed
- Task completed → score updates

You will implement UI behavior based on this logic, not redefine it.

WHAT YOU MUST NOT DO
- Do NOT redesign data structure
- Do NOT change logic
- Do NOT introduce new flows
- Do NOT assume missing behavior

WORKFLOW
This will be done in checkpoints:
- Dashboard wired
- Blockers + tasks working
- Document upload working
- Profile updates working
- Full refresh + recalculation verified

Each step must be:
- submitted
- reviewed
- approved
before moving forward.

SUCCESS CRITERIA
The MVP is complete when:
- dashboard reflects real data
- blockers appear correctly
- tasks map correctly
- uploads trigger updates
- scores change after actions

IDEAL DEVELOPER
- Strong with WeWeb
- Comfortable with REST APIs
- Can follow detailed instructions
- Communicates clearly when blocked

FINAL NOTE
This project is highly structured and success depends on:
- precise execution
- not making assumptions
- consistent communication