Eino Support Copilot is a synthetic SaaS support system designed around evidence, observable execution, and explicit human control. It contains no employer code, production data, or proprietary prompts.
flowchart LR
Customer[Customer portal] --> API[Go HTTP API]
Agent[Agent workspace] --> API
Ops[Runs / Eval / Knowledge] --> API
API --> Conversation[Conversation service]
Conversation --> Engine{Agent Engine}
Engine -->|mock| Mock[Deterministic Mock Engine]
Engine -->|openai-compatible| Eino[Eino ChatModelAgent]
Mock --> RAG[Hybrid retrieval]
Eino --> MCP[MCP client adapter]
Eino --> RAG
MCP --> MCPServer[Read-only MCP server]
MCPServer --> Business[(Synthetic business state)]
RAG --> PG[(PostgreSQL + pgvector)]
Conversation --> Trace[Persisted run events]
Trace --> PG
Engine --> Guard[Evidence and risk guard]
Guard -->|safe| Reply[Assistant reply]
Guard -->|P0/P1 or weak evidence| Review[Human review ticket]
- The customer message is persisted before execution begins.
- The Agent Run is created in
runningstate. - Classifier, retrieval, MCP tool, citation, and draft events are persisted before being streamed to the browser.
- The guard evaluates priority, confidence, citations, facts, and tool failures.
- Safe answers are appended to the conversation. Risky answers become
waiting_reviewand are never sent automatically. - Agent approval atomically writes an audit record, final message, Ticket state, and Run state.
- Retrieval combines PostgreSQL full-text search and pgvector candidates with reciprocal rank fusion.
- Every citation carries a document name, locator, excerpt, and stable chunk ID.
- Business facts only come from three schema-validated read-only tools.
- The UI shows safe stage and tool summaries; hidden prompts and chain-of-thought are never exposed.
- All state transitions are persisted in PostgreSQL.
- Human review is a single database transaction.
- Model output has strict JSON validation and one repair attempt.
- Transient model and MCP errors have bounded retries; permanent errors do not retry.
- Run replay creates a linked Run and never mutates the source Run.
- Tool arguments are recursively redacted before Run API responses.
mock mode is a deterministic contract test for orchestration, schemas, scoring, and UI behavior. It is not a claim about model quality. Real-model evaluation requires openai-compatible mode and results produced with a named model/configuration.