# Salesforce-to-Glider Nexus Prototype

A **contract-based mock prototype** demonstrating a controlled, AI-assisted
asset-change pipeline:

```
Natural-language request
-> controlled asset discovery
-> user review
-> immutable request manifest
-> deterministic manager routing
-> mandatory approval
-> execution-time revalidation
-> mock authoritative update
-> complete reconciliation and audit
```

This prototype uses **assumed contracts and synthetic data only**. It does
not represent a working integration with real Salesforce or Glider Nexus
systems. See [`docs/scope.md`](docs/scope.md) and
[`docs/assumptions.md`](docs/assumptions.md) before relying on anything
here.

## Current status: Phase 0 (skeleton)

Only the repository skeleton, shared contracts, and service health checks
exist so far. See `docs/scope.md` for what's in and out of scope at this
phase, and the build-phase plan in the source spec for what comes next.

## Local setup

```bash
python3.11 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
cp .env.example .env
```

## Running tests

```bash
pytest
```

## Running a service locally (Phase 0: health checks only)

```bash
uvicorn mock_glider.app.main:app --reload --port 8001
uvicorn mock_salesforce.app.main:app --reload --port 8002
uvicorn integration.app.main:app --reload --port 8003
```

Then check, e.g.:

```bash
curl http://localhost:8001/health
```

## Docker

Docker Compose orchestration is added once individual services have real
functionality (from Phase 1 onward). Not yet available in Phase 0.

## Repository layout

See `docs/scope.md` for the full phase plan. Top-level directories:

- `shared/` - contracts (enums, schemas, errors, correlation) used by all services
- `mock_glider/` - mock authoritative asset system
- `mock_salesforce/` - mock request/approval system
- `integration/` - deterministic workflow, validation, approval routing, execution
- `assistant/` - conversational parser and optional LLM adapter
- `frontend/` - Operations/manager/status UI
- `mcp_server/` - governed MCP tools (optional, added last)
- `config/` - approval rules, responsibility mappings, status transitions
- `scripts/` - seed data, demo, reset, performance test scripts
- `docs/` - scope, assumptions, architecture, contracts, test plan, demo script