> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vinmake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# VinMake Brain

> An AI operations system for the VinMake team

# Welcome to Brain

Brain is VinMake's internal AI operations system. It helps the team move faster on the
work that drives the business: turning client RFQ emails into accurate quotations,
keeping tech-pack-to-BOM time low, and giving managers a single trustworthy answer to
"what is happening with this style?"

Brain is **not** a general chatbot. Every entry point is a defined workflow, skill, or
query. The AI drafts; humans approve. Every output traces back to a source artifact.

<Note>
  **Status:** Brain is in active development. This documentation is a commitment view —
  it tells the team what we are building, why, and what the system will and won't do.
  Pages are tagged with status indicators so it's clear what is live versus planned.
</Note>

## Who Brain is for

<CardGroup cols={2}>
  <Card title="Merchandisers" icon="user-pen" href="/brain/staging/roles/merchandiser">
    The daily users. Brain drafts client records, style records, BOMs, true costs, and
    quotation emails. Merchandisers review, edit, and approve.
  </Card>

  <Card title="Managers" icon="user-tie" href="/brain/staging/roles/manager">
    Get consistent, source-linked answers about any client, style, or order.
    See pipeline risk, response delays, and inquiries going cold.
  </Card>

  <Card title="Sourcing teams" icon="boxes-stacked" href="/brain/staging/workflows/material-sourcing">
    Brain suggests materials from the library; the sourcing team assigns the real ones.
  </Card>

  <Card title="The AI agent" icon="robot" href="/brain/staging/roles/agent">
    Drafts, suggests, surfaces. Never finalizes important actions without approval.
  </Card>
</CardGroup>

## What Brain does today and tomorrow

Brain is being built iteratively. The first capability is the highest-pain, highest-value
manual work in the studio: turning a client tech pack into a structured BOM.
Everything else gets built around that anchor.

<CardGroup cols={2}>
  <Card title="Vision" icon="compass" href="/brain/staging/vision">
    The product we're building and the bet behind it.
  </Card>

  <Card title="Principles" icon="scale-balanced" href="/brain/staging/principles">
    The non-negotiables that shape every workflow.
  </Card>

  <Card title="Roadmap" icon="map" href="/brain/staging/roadmap">
    Phases, what's shipping now, and what comes next.
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/brain/staging/workflows/index">
    The end-to-end RFQ→quotation lifecycle, step by step.
  </Card>
</CardGroup>

## How Brain relates to CutMake

CutMake remains VinMake's structured source of truth for clients, styles, BOMs, true
costs, and quotations. Brain reads from CutMake for context and writes its drafts and
workflow state to its own database. When a draft is approved, it gets promoted into
CutMake through the normal write path.

Brain doesn't replace CutMake. It removes the manual work between an RFQ email arriving
and the right record existing in CutMake.

## A working example

A client RFQ email from Kaimook at Jaspal arrives with a tech pack, POM sheet, and
measurement file. Brain:

1. Tags the email and creates a task in the Inbox.
2. Extracts the style fields (client, style ref, category, attachments, RFQ date).
3. Checks for duplicate styles in CutMake.
4. Shows Mai a draft style record for review.
5. After Mai approves, writes the style to CutMake and offers to draft the BOM next.
6. Reads the tech pack and produces a first-draft BOM with confidence scores.
7. After Mai reviews the BOM, drafts the true cost.
8. After approval, generates the quotation at the selected markup.
9. Drafts the client email back to Kaimook.
10. Waits for Mai's approval before sending.

Every step is reviewable. Every output links back to the source email, attachment, or
CutMake record. Every correction Mai makes is logged so the system improves.

## Where to go next

<CardGroup cols={2}>
  <Card title="Read the vision" icon="compass" href="/brain/staging/vision">
    Why we're building this and the bet we're making.
  </Card>

  <Card title="See the roadmap" icon="map" href="/brain/staging/roadmap">
    Phase by phase, what ships when.
  </Card>

  <Card title="Browse the workflows" icon="list-check" href="/brain/staging/workflows/index">
    The full RFQ→quotation flow, step by step.
  </Card>

  <Card title="Understand the architecture" icon="cubes" href="/brain/staging/architecture/index">
    Skills, workflows, agents, the runtime, and how data flows.
  </Card>
</CardGroup>