2.1 The Hybrid Client-Side Monolith

MD Colab utilizes a unique architecture that behaves like a complex Single Page Application (SPA) while being hosted as a static site. This approach provides the performance of a static build with the dynamic capabilities of a BaaS-powered application.

2.2 Backend-as-a-Service (BaaS) Dependency Map

The entire backend logic is offloaded to managed services, primarily Google Firebase. This includes real-time database (Firestore), authentication (Firebase Auth), and hosting, allowing the core team to focus exclusively on frontend and AI innovation.

2.3 The Edge Network Strategy (Vercel & Firebase)

Static assets are deployed globally via Vercel's Edge Network, ensuring minimal latency for the initial application load. All subsequent data operations are handled by Firebase's regional servers, providing low-latency data synchronization for users worldwide.

2.4 Service Workers & PWA Capabilities

MD Colab is architected as a Progressive Web App (PWA). A service worker handles caching of static assets, enabling offline access to the core platform and previously loaded project data. This is critical for users in regions with intermittent internet connectivity.

MD Colab leverages Google Firestore for its elasticity and real-time WebSocket capabilities. The database design creates a balance between "Read Costs" and "Relational Integrity."

3.1 Root Collection Strategy vs. Sub-Collection Sharding

The database is partitioned into primary root collections to maximize query performance and separate concerns:

• users: Stores global identity profiles and portfolio metadata.
• collab_teams: Stores organizational metadata and member roles.
• collab_projects: Stores workspace data (Kanban, Chat, Files).
• verification_requests: (New) Stores VPC applications with strict validation rules for Admin review.

3.3 The Virtual File System (VFS) Schema

Perhaps the most complex aspect of MD Colab is implementing a file system on top of a flat NoSQL database. The decision to store code as documents instead of in blob storage is key to the platform's real-time and AI capabilities.

{
  "id": "string (sanitized_filename, e.g., src_components_header_js)",
  "filename": "string (e.g., src/components/header.js)",
  "content": "string (raw text content, 1MB limit)",
  "lastModified": "timestamp",
  "modifiedBy": "uid_reference"
}

Operational Theory

Unlike standard approaches that use AWS S3 or Firebase Storage for files, MD Colab stores code as Database Documents. This provides two critical advantages:

1. Real-time Synchronization: If User A types a character, User B sees it immediately via Firestore listeners without any manual refetching.
2. AI Indexing: Since the code is text in the DB, the AI Agent (Zainin) can query, read, and rewrite code without performing HTTP downloads of blob storage, making AI operations significantly faster.

4.1 The Persistence Layer

User sessions are managed by Firebase Auth, which utilizes browser indexedDB for session persistence. This ensures users remain logged in across browser sessions, providing a seamless experience.

4.2 MD Pin Generation Algorithms

The unique "MD Pin" is an 8-digit, human-readable identifier. It is generated client-side upon user registration using a cryptographically secure random number generator and checked against the database for uniqueness before being assigned.

4.3 Role-Based Access Control (RBAC) in Teams

While the current implementation is simple, the schema is prepared for RBAC. The collab_teams collection will contain a members map with roles (e.g., owner, editor, viewer), which will be enforced by Firestore Security Rules.

5.1 CodeMirror 5 Implementation Details

The IDE core is built upon CodeMirror 5. While version 6 exists, version 5 was selected for its battle-tested stability and ease of direct DOM manipulation without a build pipeline.

{
    theme: "dracula",           // Minimize eye strain
    lineNumbers: true,          // Essential for debugging
    lineWrapping: true,         // Prevents horizontal scroll on small screens
    styleActiveLine: true,      // UX enhancement to track cursor
    autoCloseBrackets: true
}

5.2 Dynamic Mode Switching & MIME Type Detection

The platform utilizes a heuristic detection system to set syntax highlighting. When a file is selected in the VFS, the filename string is parsed, and its extension is mapped to a CodeMirror MIME type via a switch statement.

5.3 The Live Preview Sandbox (Iframe Isolation)

To render code safely, MD Colab uses an <iframe>. This provides a security sandbox preventing user code from accessing the parent MD Colab localStorage or cookies (XSS protection).

5.4 GitHub Integration & Raw Content Proxying

The "Run" mechanism injects a <base href="..."> tag into the preview iframe's HTML. In "GitHub Mode", this tag points to a raw content proxy like raw.githack.com, allowing relative links within a repository (e.g., <link href="./style.css">) to resolve correctly.

6.1 Assistive Design Philosophy

Zainin is designed as an assistive AI layer, not an autonomous system. It responds only when explicitly invoked by the user and operates entirely within the visible project context.

6.2 Context Scope

When triggered, Zainin may receive limited contextual data such as active file content, project structure, task states, and recent chat messages. This context is constructed dynamically and is not persisted long-term.

6.3 Human-in-the-Loop Model

All actions suggested by Zainin require human review and confirmation. The AI exists to assist reasoning and productivity, not replace human judgment or responsibility.

7.1 Experimental Web-Augmented Queries

Some AI queries may optionally use external information sources. This functionality is experimental and may not always be active or available.

7.2 Database Interaction Boundaries

Zainin may suggest structured changes to project data, such as drafting files or reorganizing tasks. These changes are applied only after explicit user confirmation.

8.1 The "Interstellar" Dark Mode Palette

MD Colab uses a strict Design System defined in CSS variables to ensure consistency. The palette is designed for high contrast and low eye strain during long coding sessions.

:root {
    --bg-body: #09090b;        /* Deep Space */
    --bg-sidebar: #0f1014;    /* Nebula */
    --bg-card: #18181b;        /* Asteroid Surface */
    --accent: #FF6F00;         /* Solar Flare Orange */
    --text-primary: #e4e4e7;  /* Star White */
    --text-secondary: #a1a1aa; /* Distant Galaxy */
    --border-subtle: #27272a; /* Orbital Path */
}

8.2 Glassmorphism Physics & CSS Variables

To create a modern, "layered" feel without high GPU cost, we use backdrop-filter: blur(4px) on modal overlays and semi-transparent borders (rgba(255, 255, 255, 0.1)) to define edges rather than solid lines.

8.3 Toast Notification Queue Logic

The toast notification system is a DOM-injection engine. It creates a <div> element dynamically, appends it to a fixed container, uses CSS keyframe animations for entrance/exit, and utilizes setTimeout for auto-dismissal to prevent DOM bloating.

8.4 Modal Registry & State Management

A simple, global JavaScript object acts as a modal registry. Functions like openModal('settings') and closeModal() toggle CSS classes on the corresponding modal elements, managing their visibility without a complex state library.

9.1 Kanban Logic: State Transitions & Drag Heuristics

The Kanban board is a direct visual representation of the tasks sub-collection in Firestore. There are three hard-coded states: todo, progress, and done.

Rendering Strategy

The loadKanban function subscribes to real-time updates using Firestore's onSnapshot listener. On any data change, it clears the DOM columns and rebuilds them. While computationally expensive for 1000+ tasks, for typical projects (<100 tasks), this ensures 100% state synchronization without complex diffing algorithms.

State Transition

Moving a task via drag-and-drop triggers a Firestore update() call, changing the document's status field. The onSnapshot listener then automatically moves the card in the UI for all connected users instantly.

9.2 CRM Module: Lead Capture & Data sanitization

The integrated CRM module provides a simple interface for lead capture. All user-submitted data is sanitized on the client side to prevent XSS before being written to a dedicated leads collection in Firestore.

MD Colab is agnostic to hosting providers but is optimized for Vercel due to its seamless Git integration and global edge network.

Static Generation

The project is a pure static site (HTML, CSS, JS). No server-side rendering (SSR) or build step is required, leading to instantaneous deployments. Any push to the `main` branch on GitHub automatically triggers a new deployment on Vercel.

Data Redundancy

Firestore automatically replicates data across multiple geographic zones within the selected region (e.g., us-central). This provides protection against a zone-level failure.

Client-Side Resilience

If a user's internet connection is lost, Firestore's offline persistence (enabled by default in our configuration) caches all reads. Users can continue to view loaded data. Any writes they make are queued locally and automatically synced upon reconnection.

12.1 Platform Refinement

Future development will focus on improving collaboration stability, performance optimizations, and developer experience across existing tools.

12.2 AI Experimentation

MD Colab may experiment with additional AI-assisted workflows, prototype tools, and contextual helpers. These efforts will remain optional, assistive, and human-controlled.

12.3 Ecosystem Growth

Expansion will prioritize sustainability, clarity, and trust rather than aggressive scaling or automation.

The Collab Workspace is your central hub for project development. After selecting a team from the main sidebar, you choose a project to load this powerful, integrated environment.

Key Areas of the Workspace:

• Project Header: At the top, you'll see the project name and its linked GitHub repository. To the right, you can see the profile pictures of all active team members. Click their avatars to view their profiles. The Settings button allows you to manage the project's details.
• Main Tabs: The core of the workspace is divided into several powerful tabs:
  • Chat: Communicate in real-time with your team and interact with the Zainin AI agent.
  • Kanban: Visualize and manage project tasks in a simple To Do, In Progress, and Done format.
  • Code: Access the integrated IDE. Here you can browse GitHub repositories, manage cloud-saved files, write code, and launch a live preview.
  • Design: A professional-grade vector design and prototyping tool, fully collaborative and integrated with your project.
  • Leads: A lightweight CRM tool for tracking project contacts and potential clients.

How to Access Your Profile

To access your personal dashboard, click your profile name and avatar in the bottom-left corner of the main sidebar on the Collab page. This centralizes all your personal information and account settings.

Features of the Profile Dashboard:

14.1 Profile Card & Customization

This is your identity hub. Click the Edit Profile button to update your name, location, bio, skills, and social media links. You can also add unlimited custom links to showcase your blog, personal site, or any other web presence.

14.2 Verification Tick

The orange tick next to a user's name is a symbol of authenticity and credibility. It signifies that the user has met MD Colab's verification criteria, which include having a complete profile, a verifiable professional presence outside the platform, and an account in good standing. This feature helps build a trustworthy community.

14.3 Portfolio Builder

In the Portfolio tab, you can create a beautiful, publicly shareable portfolio page. You can set a unique URL, choose your profession to unlock specific fields (like "Featured Projects" for developers or "Gallery" for designers), and write a detailed "About" section using Markdown.

14.4 Account Security

The Account tab provides essential security features. Here, you can change your password or, if necessary, permanently delete your account and all associated data.

14.5 Overview & Statistics

The Overview tab gives you an at-a-glance summary of your activity, including the number of teams and projects you are a part of, as well as a list of your most recent collaborations.

15.1 Philosophy: The Meritocratic Marketplace

The MD Talent Hub is an integrated discovery engine designed to connect project founders with skilled contributors. Unlike traditional freelance platforms that prioritize bidding wars, the Talent Hub prioritizes Verified Portfolios and Project History.

15.2 Data Architecture (The Talent Schema)

To be searchable in the Talent Hub, a user's Firestore document is augmented with a specific talentHub object. This separation ensures that casual users do not pollute the professional search index.

{
  "enabled": boolean,           // Must be true to appear in search
  "searchable": boolean,        // Administrative override flag
  "role": "developer" | "designer" | "writer", 
  "hourlyRate": number,         // Optional
  "availability": "open" | "busy" | "collaboration-only",
  "experienceLevel": "junior" | "mid" | "senior"
}

15.3 The Discovery Algorithm

The Talent Hub search engine uses a client-side filtering mechanism optimized for speed. When the directory loads, it performs a single optimized query to fetch "Active Talent" and then filters locally based on:

• Role Matching: Strict equality check against the user's declared profession.
• Availability Status: Users marked as "Busy" are visually dimmed or deprioritized.
• Keyword Search: A fuzzy search implementation that scans the user's Name, Username, Bio, and Skills array simultaneously.

15.4 Engagement Workflow (Chat Integration)

The Talent Hub does not use a traditional "Apply" button. Instead, it leverages the platform's Direct Messaging (DM) infrastructure.

1. Discovery: A founder finds a talent profile via the Hub.
2. Verification Check: The founder reviews the "Verified Tick" and linked portfolio projects.
3. Connection: Clicking "Message" initiates a secure Firestore DM channel.
4. Context: The system automatically pre-fills the conversation context (e.g., "Hi, I saw your profile on Talent Hub...").

The MD Colab Orange Tick is more than just a badge; it's a symbol of trust, active contribution, and authenticity within our community. It helps others identify collaborators who are serious about their work and have a verifiable presence. This guide outlines the universal criteria every user must meet to be considered for verification.

The Core Meaning of the Tick

When you see a verified tick next to a user's name, it signifies that:

• The user is an authentic individual whose identity has been reasonably confirmed.
• The user is an active contributor to the MD Colab ecosystem.
• The user's account is in good standing and adheres to our community guidelines.

Universal Verification Criteria

To be eligible for the Orange Tick, a user must meet all of the following requirements. Our team manually reviews each request to ensure fairness and maintain the integrity of the badge.

1. Profile Completeness (The Foundation)

Your profile must be fully filled out to be considered. This is the first step to filter out incomplete or inactive accounts.

• Real Name & Role: Your full name and professional role/title must be provided.
• Profile Picture: You must have a clear, recognizable profile picture.
• Detailed Bio & Skills: Your bio should describe who you are, and you must list your relevant skills.
• Linked Professional Presence: You must have at least one valid social link pointing to a professional platform like GitHub, LinkedIn, or a personal portfolio website.

2. Active & Public Portfolio

MD Colab's core feature is the portfolio builder. A verified user is expected to maintain a high-quality, public portfolio.

• Public Visibility: Your portfolio must be set to "Public" in your profile settings.
• Unique Username: You must have a unique @username for your portfolio URL.
• Filled Sections: Your portfolio should be well-maintained with relevant content, such as featured projects, work experience, or a gallery, depending on your profession.

3. Active Contribution on MD Colab

Verification is a reward for active participation. Simply creating an account is not enough.

• Project Involvement: You must have created or been an active member of at least one project on the platform.
• Recent Activity: Your account should show signs of recent activity within the last 30-60 days.

4. Account in Good Standing

Trust is earned and must be maintained. A clean record is mandatory.

• No Policy Violations: Your account must be free of any confirmed reports for spam, providing false information, or violating community guidelines.

How to Request Verification

If you believe you meet all the criteria above, you can request a review by sending an email to our team. Please include links to your MD Colab profile and other relevant professional sites to help us confirm your authenticity.

Request a review mdcolab99@gmail.com

The Verified Creator Program is a platform-level trust initiative designed to give developers and creators a verifiable digital identity. Unlike automated systems, this is a manually reviewed ecosystem.

17.1 The "Orange Tick" Significance

The Orange Verified Badge is a cryptographic signal within the MD Colab ecosystem that asserts:

• Identity: The creator is a real human with a validated professional presence.
• Originality: The creator has declared authorship of their hosted projects.
• Trust: The account has passed a manual review by MD Colab Administrators.

17.2 Program Benefits

Verified Creators receive structural advantages within the platform architecture:

• Priority Indexing: Profiles are prioritized in internal search algorithms and sitemaps for Google/Gemini indexing.
• Visual Distinction: The Orange Badge appears on leaderboards, project headers, and team views.
• Early Access: "Early Creator Status" tags (e.g., Verified 2026) are permanently attached to the user document.

17.3 The Verification Workflow

The technical flow for earning verification involves three stages:

1. Submission: The user submits the VPC Application Form. The data is validated for strict URL patterns (must match mdcolab.vercel.app/@username) and written to the verification_requests Firestore collection.
2. Admin Review: An Admin reviews the request via the secured Admin Panel, checking the portfolio for quality and authenticity.
3. Immutable Update: Upon approval, the system atomically updates the user's document isVerified: true field and triggers an automated email notification via FormSubmit.

18.1 Platform vs. Legal Verification

It is architecturally critical to distinguish between MD Colab's Platform Verification and Legal Copyright.

• Platform Verification: Confirms that a user claims authorship and has a consistent digital footprint. It is a trust signal within the MD Colab ecosystem.
• Legal Copyright: MD Colab does not act as a government copyright office. The "Verified Creator Certificate" is a digital artifact of platform trust, not a legal document usable in court for copyright enforcement.

18.2 Content Ownership Schema

As defined in the Copyright Disclaimer, users retain full intellectual property rights to the code, designs, and content they host on MD Colab. The platform acts solely as a hosting and discovery layer.

1.3 Reporting Mechanism

To maintain ecosystem health, MD Colab implements a reporting pipeline. Users can report portfolios via the /report-portfolio interface. These reports are aggregated in the reports collection and flagged for Admin review to detect impersonation or stolen work.

19.1 The Hybrid Indexing Strategy

The MD Colab Search Engine (v5.0) utilizes a Client-Side Hybrid Index. Unlike traditional server-side search (like Algolia or Elasticsearch) which can be costly and latent, our engine builds a transient index in the user's browser memory upon load.

const masterIndex = [
  ...SEED_DATA,          // Hardcoded core navigation & guides
  ...Firestore_Users,    // Real-time fetched Public Profiles
  ...Firestore_Projects, // Real-time fetched Public Projects
  ...Static_Sitemap      // Crawled HTML meta-data
];

This approach ensures Zero-Latency filtering once the page is loaded, as no network requests are made during typing.

19.2 Fuzzy Logic & Typo Tolerance

To handle user error, the engine implements the Levenshtein Distance Algorithm. This calculates the number of single-character edits required to change one word into another.

• Exact Match: 100 Points (e.g., "Ora" matches "Ora").
• Partial Match: 50 Points (e.g., "Dev" matches "Developer").
• Fuzzy Match: 10 Points (e.g., "Ooa" matches "Ora" via distance calc).

19.3 AI Mode (Zainin Search)

When the "AI Mode" tab is selected, the engine switches renderers. It does not query an external LLM (to preserve privacy and speed). Instead, it uses a Deterministic Context Builder.

It identifies the intent of the result (e.g., is this a Guide? A Person?) and constructs a natural language response dynamically using pre-defined templates. This ensures 100% factual accuracy based on platform data, avoiding AI hallucinations.

The MD Colab Invoice App isn't just a document generator; it is a micro-ERP (Enterprise Resource Planning) system that manages the entire lifecycle of a professional transaction.

Step 1: Configuration (The Foundation)

Before creating your first invoice, go to Settings. Enter your company name, email, and tax ID. Crucially, enter your UPI ID (e.g., 9876543210@ybl). This ensures that every invoice you send includes an automated payment link.

Step 2: Setup your Catalog

Navigate to Products and Customers. Adding your regular clients and standard services (like "UI Design" or "API Development") here saves you from manual typing during the billing process. The builder will "auto-suggest" these items as you type.

Step 3: Building the Invoice

Click "New Invoice" on the Dashboard. Select a customer from the dropdown to auto-fill their address. Add your line items. You can adjust tax rates and discounts per invoice. Upload your logo—it will be saved for future invoices.

Step 4: Posting & Journalizing

You have two choices:

• Save Draft: Saves the data so you can edit it later. It does not affect your accounting books.
• Post & Journalize: This is the "Finalize" step. It locks the invoice, creates a record in your General Ledger, and generates a high-quality Invoice Image stored on the cloud.

Step 5: Sharing & Payment

Once you click "Post," a WhatsApp window will open. It sends your client two things: a Direct Link to the Invoice Image and a Link to the Payment Portal. The client scans the QR code, pays you, and you can then mark the invoice as "Paid" in your dashboard to balance the ledger.

22.1 The Asset Pipeline

To solve the "C:\fakepath" and "CSS breaking" issues, MD Colab uses a sophisticated cloning logic. When generating an image, the system creates a hidden, clean clone of your invoice, converts all input fields into standard text spans, and captures the result at 2x resolution using html2canvas. This image is then transmitted via an unsigned POST request to Cloudinary.

22.2 Ledger Integrity

The app uses a Journal-Ref system. Every record in the invoice_journal contains a refId pointing back to the specific Invoice. If an invoice is deleted, the corresponding ledger entry remains but is flagged, ensuring your historical revenue charts remain accurate for tax purposes.

23.1 The Unified Business Model

MD Business is the central "source of truth" for your financial and commercial identity within the ecosystem. Rather than configuring billing and tax details separately for every app, the Business Module acts as a singleton profile.

23.2 Integration Workflow

When you create a Business Profile, the system generates a unique identifier that links your MDInvoice and MDDropShip instances. This enables:

• KYC Synchronization: Your PAN/GST and Bank details are stored once and shared across apps, ensuring regulatory compliance.
• Payment Gateway Routing: The system maps your verified Razorpay account ID to your Business ID, ensuring that customers paying in your MDDropShip store or via your MDInvoice links are routed to your account.
• Asset Management: Your Logo and Business Metadata (Address, Email) are cached to be reused across all invoices and storefronts.

23.3 Verification Status

The "Verified Business" badge is issued after manual review of your submitted KYC documents (PAN/GST/Bank Details). Until verification is complete, your business module remains in "Pending" status, limiting access to automated payout features.

24.1 Nature of Collaboration

By applying to join MD Colab, participants enter a collaborative startup environment focused on building digital products and developing practical skills. Participation does not constitute employment and is strictly a voluntary opportunity centered on learning, experimentation, and contribution.

24.2 The 7-Day Trial Roadmap

The structured onboarding trial begins on March 1, 2026. This evaluation phase is designed to assess technical ability, consistency, and collaboration readiness.

• Daily Assignments: Contributors receive skill-aligned tasks tailored to their domain expertise and interests.
• Strict Submission Protocol: Tasks assigned on any day must be completed and submitted by 7:00 PM IST on the following day.
• Final Evaluation: A formal interview is conducted on Day 7 to determine permanent inclusion and role placement.
• Supplementary Resources: Throughout the trial, collaboration files, concept documentation, and project datasets are provided.

24.3 Mandatory Talent Hub Activation

All applicants must activate and fully configure their professional profile within the MD Talent Hub before trial commencement. This serves as a mandatory prerequisite for workflow integration. Failure to establish a functional Talent Hub profile results in automatic application cancellation.

24.4 Communication & Data Exchange Protocol

To maintain centralized coordination, all communication, file distribution, and task submissions occur exclusively via Talent Hub Chat. Participants are expected to maintain responsiveness and regularly monitor messages for updates, feedback, and project assets. Prolonged inactivity or communication gaps may lead to removal.

24.5 Compensation Structure

MD Colab currently operates under a ₹0 salary model. There is no guaranteed financial compensation. Future monetization opportunities, including revenue sharing or paid roles, depend on platform growth metrics and individual contributor impact.

24.6 AI Usage Policy

AI-assisted tools such as ChatGPT and Copilot are permitted for productivity enhancement; however, blind copy-pasting is strictly prohibited. Contributors must demonstrate comprehension of all submitted work, including code logic and content rationale, emphasizing critical thinking over automated output.

24.7 Role Responsibility Framework

Contributors must operate within their assigned role boundaries. Cross-departmental intervention requires prior discussion and approval. Any role reassignment requests are subject to founder review and authorization.

24.8 Intellectual Property Governance

All collaborative output—including codebases, design assets, written content, and strategic frameworks—is considered MD Colab intellectual property unless otherwise agreed. Contributors retain the right to showcase their specific contributions within personal portfolios for professional representation.

24.9 Decision Authority

The founder maintains final authority over trial outcomes, role allocations, project direction, and membership status. Decisions are binding and not subject to dispute.

24.10 Removal Policy

MD Colab enforces a strict professionalism standard. Removal may occur without prior notice in cases involving repeated deadline violations, communication negligence, or disruptive behavior affecting team cohesion.

24.11 Growth-Oriented Culture Statement

MD Colab is designed for individuals committed to building solutions from the ground up. Those seeking casual participation or immediate financial returns may find misalignment with the platform’s long-term innovation ethos.

"MD Colab is for builders, not spectators."

25.1 Modal Access & Account Verification Layer

The trial application operates inside a gated modal interface designed to prevent unauthorized submissions. Upon trigger, the system initiates an account verification sequence where user authentication status and portfolio availability are validated before form exposure. If requirements are not satisfied, the user is redirected to account creation or login flow.

25.2 Digital Identity Auto-Population

The first section captures identity metadata derived directly from the authenticated user profile. Fields such as Full Name and Email Address are read-only to preserve data integrity. Additionally, the system auto-detects the contributor’s MD Colab portfolio URL, ensuring all applicants possess a verified digital presence prior to evaluation.

25.3 Role & Passion Mapping

The role selection grid enables applicants to declare their primary domain alignment through a single-choice radio system. This classification supports downstream task assignment and includes technical, creative, marketing, and operational roles such as frontend development, AI engineering, design, content writing, community management, and project coordination.

25.4 Experience & Consistency Metrics

This section gathers contextual signals about contributor availability and reliability. Applicants specify their current professional status and weekly time commitment, allowing the evaluation engine to assess realistic workload capacity. Contact and timezone information further facilitate synchronous collaboration and communication planning.

25.5 Project Interest Targeting

The project preference selector enables contributors to align with specific ecosystem initiatives. This mapping assists in cohort segmentation and ensures contributors are deployed into projects matching their motivation and technical orientation.

25.6 Skill & Capability Disclosure

Applicants provide explicit information about tools and technologies actively used in their workflow. This self-declared capability matrix assists in designing personalized assignments and validating domain proficiency during trial execution.

25.7 Work History & Achievement Context

The past work field captures concise descriptions of notable projects or achievements. This qualitative input supports reviewer assessment of practical experience, problem-solving exposure, and execution depth.

25.8 Vision Alignment Statement

The intent section evaluates long-term motivation and philosophical alignment with the ecosystem’s collaborative innovation model. Contributors articulate their strategic interest in building within MD Colab and their anticipated contribution trajectory.

25.9 Accountability Agreement

Prior to submission, applicants must explicitly acknowledge a participation agreement confirming commitment to daily updates and responsiveness. This contractual acknowledgement enforces accountability standards and defines removal conditions for inactivity.

25.10 Submission Trigger & Workflow Transition

Upon final submission, the system packages application data into the onboarding pipeline for cohort review and task allocation. Successful applicants transition into the structured 7-day trial evaluation process documented within the collaboration policy. The modal implementation and gating workflow are defined within the MD Colab onboarding interface :contentReference[oaicite:0]{index=0}.

MD DropShip is a fully integrated, AI-powered e-commerce and dropshipping automation suite embedded within the MD Colab platform. It abstracts the profound complexities of storefront deployment, global product sourcing, payment routing, and automated order fulfillment into a singular dashboard interface.

By leveraging a combination of Firebase serverless infrastructure, the Gemini AI cognitive engine, Razorpay route accounts, and edge deployment via Vercel/Netlify/Cloudflare, MD DropShip allows creators to deploy globally scalable businesses with zero code.

27.1 The Store Document Schema

Store metadata is decoupled from the frontend application and stored securely within the stores Firestore collection. The application maps the unique slug identifier to dynamically hydrate the storefront SPA.

{
  "ownerId": "string (Firebase UID)",
  "name": "string (e.g. Trendify)",
  "slug": "string (e.g. trendify-shop)",
  "currency": "string (USD | INR)",
  "themeColor": "string (Hex)",
  "domain": "string (Custom Domain or MD Colab URL)",
  "deploymentType": "MD_Stores | Netlify | Custom"
}

27.2 Dynamic Storefront Hydration

When a customer visits a storefront (e.g., /store/?shop=slug), the global storeApp engine intercepts the slug, queries the stores and products collections, and dynamically applies the store's branding (theme colors, logo, and SEO meta tags) via JavaScript before rendering the DOM.

28.1 External Catalog Querying

The platform integrates with the AliExpress Datahub (via RapidAPI) to fetch live product data. Queries execute through a secure serverless proxy (/api/cj-products) to conceal the RapidAPI key from the client-side execution environment.

28.2 The 1-Click Import Workflow

When an entrepreneur selects a product to import, the system intercepts the external supplier data and processes it:

1. Markup Injection: The system automatically calculates a baseline retail price by executing a 2x multiplier on the supplier's targetSalePrice.
2. Image Processing: High-resolution thumbnails and gallery images are captured and, if manipulated locally, compressed to WebP format via a local canvas implementation to conserve Firestore bandwidth.
3. AI Content Enhancement: The raw, often poorly translated supplier title is fed to the Gemini AI pipeline to generate conversion-optimized short and long descriptions.

29.1 The Split-Payment Architecture (Razorpay Route)

MD DropShip handles payments without holding the merchant's funds. It utilizes Razorpay Route to instantly transfer the sale amount to the store owner's linked razorpayAccountId.

29.2 Webhook State Validation

Payments are asynchronous. An order remains in Pending status until the /api/payment-webhook endpoint receives the order.paid event. The webhook employs HMAC SHA-256 signature validation using the x-razorpay-signature header to guarantee payload authenticity before updating the Firestore document to Paid.

30.1 Fulfillment Evaluation Logic

When an entrepreneur clicks "Fulfill Order" in the dashboard, the /api/fulfill-order endpoint evaluates the order's supplier origin:

• CJ Dropshipping Mode: If the product is linked to CJ, the endpoint constructs a JSON payload containing shipping data and executes an authorized POST request to CJ's createOrderV2 API. The Firestore document is instantly marked as Processing.
• Manual / AliExpress Mode: If the API link is absent, the system flags the order as Manual and returns a structured object of customer shipping data to the dashboard, prompting the merchant to complete the purchase directly on the supplier's website.

MD DropShip provides a multi-tier deployment strategy to balance instantaneous testing with professional scaling.

31.1 Native Edge Hosting (MD Stores)

The default deployment utilizes internal path-based routing (e.g., mdcolab.app/store/slug). The SPA reads the URL parameter and hydrates the store interface dynamically. This requires zero build time and updates instantly upon database writes.

31.2 The Netlify Proxy Pipeline

For merchants requiring top-level domains without complex DNS mapping, the /api/deploy-netlify-site endpoint programmatically creates a new site on Netlify. It uploads an index.html file containing an iframe proxy pointing to the native MD Colab store path. This leverages Netlify's SSL and CDN distribution.

31.3 Cloudflare CNAME Mapping

For custom domain integration, the platform communicates with the Cloudflare API via /api/create-store-domain to inject a new CNAME record dynamically. This maps the merchant's chosen subdomain directly to the Vercel edge network handling MD Colab.

To mitigate the difficulty of dropshipping customer acquisition, MD DropShip includes a marketing generator powered by Gemini 1.5 Flash.

The /api/generate-ad-copy endpoint accepts product, audience, and platform parameters. The system utilizes context-aware prompt engineering to format the output uniquely for the target platform (e.g., injecting heavy emoji usage and hooks for TikTok, versus concise benefit-driven copy for Google Search Ads).

The core intelligence of MD DropShip is routed through the /api/generate-product-description multi-mode endpoint.

33.1 Mode: Product Description Synthesis

When a product is imported, the AI strips the supplier's raw title and generates two distinct string outputs: a shortDesc optimized for grid UI cards, and a detailed HTML-formatted description outlining benefits, specifications, and trust signals to maximize checkout conversions.

33.2 Mode: SEO Metadata Generation

To optimize organic ranking, the AI evaluates the store's name and description. It generates a perfectly truncated Meta Title (<60 chars) and Meta Description (<160 chars) injected into the DOM <head> during storefront hydration.

MD DropShip architecture deliberately decouples the Discovery API from the Fulfillment API. This multi-supplier architecture prevents platform lock-in.

• Discovery (RapidAPI/AliExpress): Used exclusively for querying massive databases of product metadata, scraping images, and establishing baseline costs.
• Fulfillment (CJ Dropshipping): Used for secure order injection. Because CJ Dropshipping handles logistical APIs natively, the payload bridges the gap between the AliExpress data found during discovery and the shipping requirements established at checkout.

35.1 API Secret Obfuscation

The client-side SPA never possesses API keys for Cloudflare, Netlify, Gemini, Razorpay, or CJ Dropshipping. All interactions are routed through Vercel Serverless Functions mapping to environmental variables or encrypted Firestore settings/api_keys documents via a custom _utils.js fetching utility.

35.2 Transaction State Protection

The create-order endpoint enforces strict read rules. It fetches the price directly from the Firestore products collection, ignoring any price data sent in the frontend POST request body. This prevents malicious actors from tampering with network payloads to alter the checkout amount before the Razorpay instance initializes.

36.1 The Two-Sided Marketplace

MD DropShip connects two types of users on a single platform. Dropshippers build branded storefronts and import products to sell. Suppliers provide the physical inventory, fulfil the orders, and receive payment automatically. The supplier never deals with a customer directly — the dropshipper owns the relationship, the supplier owns the product.

36.2 Supplier Portal Navigation

The portal sidebar has the following sections, each covered in detail in this guide:

36.3 How Payouts Work (Overview)

When a customer places an order on a dropshipper's store that contains your product:

1. Razorpay captures the full payment from the customer.
2. Razorpay Route automatically splits the amount: your base cost goes to your linked account, the dropshipper's margin goes to their account, and the MD Colab platform fee (5%) is retained.
3. The split happens at capture time. Funds arrive in your bank within the standard T+2 business day settlement cycle.
4. Every transaction is recorded in your Payouts section with full breakdowns.

37.1 Prerequisites

Before you can activate a Supplier Shop, you need:

• An MD Colab account (sign up at mdcolab.vercel.app).
• An MD Business profile with your business name, category, and valid contact details.
• A Razorpay linked account — this is the bank account where your payouts are deposited. Link it through MD Business → Business Identity.

37.2 Step-by-Step: Activating Your Supplier Shop

37.3 Supplier Verification Status

Your shop has a status indicator in the bottom-left of the Supplier Portal sidebar. The three states are:

38.1 Shop Profile Fields

Navigate to Supplier Hub → Shop Profile to configure your profile. All fields are saved to suppliers/{uid} in Firestore.

38.2 AI Shop Generator

On the Shop Profile page there is an AI Generator banner at the top. Type your product niche (e.g. "Wireless Bluetooth Accessories") and click Generate. Gemini AI will auto-fill every field above — name, tagline, description, policies, SEO text, and brand colour — tailored to your niche. You can then edit any field before saving.

38.3 Policy Regeneration

Individual policy fields (Return Policy, Quality Policy) have their own AI Write button. Clicking it calls mode: "policies_only" and rewrites only those two fields without affecting the rest of your profile.

39.1 Adding a Product — Manual Entry

Click Add Product in the top-right corner of the My Products page. A slide-in drawer panel opens. Fill in the following fields:

39.2 AI Product Generator

At the top of the catalog drawer is an AI Product Generator strip. Enter a product name and your base cost, then click Generate. Gemini AI returns a complete listing — title, short description, full HTML description, category, SKU, material, size, weight, shipping time, keywords, handling notes, and a suggested minimum selling price (auto-calculated as 2.5× base cost).

All generated fields populate the form automatically. Review and adjust any field before saving. The AI generator calls POST /api/generate-product-description with mode: "supplier_product".

39.3 Live Pricing Calculator

The drawer contains a real-time pricing calculator below the Base Cost field:

• Base Cost — what you receive per sale (what you entered).
• Platform Fee (5%) — automatically calculated on base cost.
• Suggested Selling Price — 2.5× base cost. Shown as a recommendation to dropshippers.
• Dropshipper Margin — selling price minus base cost minus platform fee.

39.4 Product Status Management

Every product has one of four statuses:

39.5 Stock Sync

When an order is fulfilled and the webhook fires, stock is automatically decremented on your supplier_products document. That updated stock count is then batch-propagated to every store_products document (all dropshipper stores that imported your product), ensuring consistency across the entire marketplace in real time.

40.1 Order Lifecycle

Every order moves through the following status pipeline. You control movement through stages 2–4. Stages 1 and 5 are system-assigned.

40.2 The Fulfill / Ship Modal

When you click Fulfill on a Processing or Packed order, a modal opens with:

• Courier — dropdown of Indian courier partners (Delhivery, BlueDart, DTDC, FedEx, Xpressbees, Shadowfax, Shiprocket, India Post, Ekart, Ecom Express, Amazon Logistics, Gati, Professional Couriers).
• Tracking Number — your AWB/consignment number from the courier.
• Estimated Delivery Date — optional target delivery date shown to the customer via the dropshipper's store.
• Customer Address — displayed for reference so you can print/label correctly.

40.3 Order Detail Panel

Click the eye icon on any order row to open the full detail slide-in panel. It contains:

• Complete order timeline with timestamps for each stage transition.
• Full customer delivery address.
• Financial breakdown: customer paid, your base cost, platform fee, dropshipper earnings.
• Current tracking information if shipped.
• A direct tracking link that opens the courier's website pre-filled with the AWB number.

40.4 Filtering & Search

The orders table has a search bar (searches by order ID or product name) and a status filter dropdown. The four status pills at the top of the page show live counts: Paid, Processing, Shipped, Delivered.

41.1 Overview Dashboard — KPI Cards

The Overview page displays real-time KPI cards populated from Firestore:

41.2 Analytics Charts

The Analytics section provides historical performance charts:

• Revenue Over Time — daily/weekly revenue bar chart for the last 30 days.
• Orders by Status — donut chart showing the proportion of Paid / Processing / Shipped / Delivered orders.
• Top Products — ranked list of your highest-revenue products with order count and total earnings.
• Order Volume Trend — line chart showing order frequency over the selected time period.

41.3 Payouts Section

The Payouts page shows every transaction where your account received (or will receive) a payment. Each row contains:

• Order Reference — links back to the corresponding supplier order.
• Customer Payment — full amount the customer paid to the store.
• Your Base Cost — the amount transferred to your linked account.
• Platform Fee (5%) — deducted before your transfer.
• Transfer Status — pending, processed, settled, or failed.
• Settlement Date — estimated date the funds arrive in your bank (T+2 business days from capture).

42.1 Warehouse — Bulk Stock Management

The Warehouse section provides a compact view of all your products with their current stock levels. Instead of opening each product individually, you can update stock counts for multiple products at once from a single table.

• Products with stock ≤ 10 are highlighted with a Low Stock warning badge — this same count drives the badge on the sidebar nav item.
• Products with stock = 0 are shown with an Out of Stock status. You can replenish directly from this view.
• Click any stock value to edit it inline. Changes are saved to supplier_products.stock and propagated to all linked store_products records in real time.

42.2 Shipping Settings

Navigate to Shipping Settings to configure your default logistics rules. These apply to all products unless overridden at the product level.

42.3 Reviews

The Reviews section aggregates ratings left by dropshippers after receiving fulfilled orders. Each review contains a star rating (1–5), a text comment, and the order reference. Your overall average rating is calculated from all reviews and displayed:

• On your Supplier Shop Profile visible to dropshippers.
• As the Avg. Rating KPI on your Overview dashboard.
• In the Supplier Marketplace listing used by dropshippers to browse suppliers.

You cannot delete reviews, but you can respond to them. A consistent 4★+ rating increases discoverability and import rate for your products.

42.4 Support Tickets

Use the Support section to raise tickets for:

• Payout discrepancies or failed transfers.
• Order disputes where a return or refund has been escalated.
• Technical issues with the Supplier Portal or product listings.
• Verification or linked account questions.

Each ticket has a status (open, in_progress, resolved) and a thread for back-and-forth communication with the MD Colab team. Open ticket count is shown as a badge on the Support sidebar item.

42.5 Notifications

Real-time in-portal notifications are fired to your account for:

• Every new order received — "New Order: Product Name × Qty".
• Transfer failures — "Route Transfer Failed — manual payout needed".
• Low stock threshold breaches.
• New reviews posted against your shop.
• Support ticket replies from the MD Colab team.

Notifications are stored in notifications/{docId} with userId: supplierId and are marked read: true when you open the notification panel.