Owner: DevOps Lead — Abdul Moiz
Contributors: PM (deployment request) · AI Engineer (build requirements) ·
HoD (technical review)
Department: D5 — Infrastructure & Compliance
Entity: PrivateAI
Status: Recommended draft · Pending DevOps Lead (Moiz) review
Version: 0.1 | Last updated: 2026-07-18
Classification: Confidential
⚠️ This is a recommended draft. Moiz to review and correct all
technical specifics before this is treated as operational.
What this workflow does: Governs how a new per-client AWS environment is
provisioned for every AI Project, AIe, and AIc engagement — from the deployment
request through to a live, tested, isolated client environment handed over to
the AI Engineer for build.
What triggers it: CS-01c (AI Project or AIc Onboarding) Step 5 — PM sends
the infrastructure provisioning request to Moiz once scope is locked and payment
is cleared.
What it produces: A live, isolated per-client AWS environment — with all
required services provisioned, access credentials issued to the AI Engineer,
smoke-tested, and documented in the client's infrastructure record.
Why it matters: Every AI Project and AIc engagement starts with an environment
provision. A slow, inconsistent, or insecure environment setup delays delivery
and creates client risk. A standard, repeatable provisioning process means the
AI Engineer can start building on day one.
| Role | Department | Responsibility | CEO? |
|---|---|---|---|
| PM | D4 | Sends deployment request to Moiz with full project brief · coordinates client access requirements | No |
| DevOps Lead (Moiz) | D5 | Provisions the environment · configures all AWS services · issues credentials · smoke tests | No |
| AI Engineer | D4 | Provides build requirements brief (integrations, data sources, compute needs) · receives and tests credentials | No |
| HoD | D4 | Reviews environment spec for complex deployments · signs off before AI Engineer begins build | No |
Step 1 — Deployment request received
Step 2 — Environment specification
Step 3 — Environment provisioning
Step 4 — n8n instance configuration (if required)
Step 5 — Credentials issued to AI Engineer
Step 6 — Smoke testing
Step 7 — Environment documented
/Infrastructure/Clients/[ClientName]/.| Tool | How it's used | Agent-ready |
|---|---|---|
| AWS | Per-client environment provisioning — all services | Yes — confirmed |
| AWS IAM | Least-privilege access control per environment | Yes — API |
| n8n | Automation platform deployed per client (if dedicated instance) | Yes — native |
| Jira | Deployment request tracking · smoke test log | Yes — confirmed |
| Google Workspace | Environment spec · infrastructure record | Yes — API + MCP |
| Discord | Deployment request notification · credential handoff coordination | Yes — API |
| IaC tool | Infrastructure as code provisioning (TBD — pending OPS-O02) | TBD |
| Secret management | Credential storage and handoff (TBD — pending OPS-O02) | TBD |
Deployment complexity (Step 2)
| Condition | Action | Owner |
|---|---|---|
| Standard AI Project | Moiz provisions per spec — no HoD review needed | Moiz |
| Complex or compliance-sensitive (AIc, GDPR, HIPAA) | HoD reviews spec before provisioning | HoD → Moiz |
Smoke test outcome (Step 6)
| Outcome | Action | Owner |
|---|---|---|
| All tests pass | Hand over to AI Engineer | Moiz |
| Test fails | Moiz investigates and re-tests | Moiz |
| Scenario | How to handle | Escalation |
|---|---|---|
| Client requires specific cloud region for data sovereignty | Moiz confirms with Legal Lead before provisioning · document in environment spec | Moiz → Legal Lead |
| Provisioning delayed beyond 2-day SLA | PM flags to HoD · Moiz provides revised ETA | HoD |
| AI Engineer identifies environment gap after build starts | AI Engineer raises in Jira · Moiz adds missing component · no build pause unless critical | Moiz |
| Cost estimate significantly exceeded | Moiz flags to HoD and Finance Lead before proceeding | HoD → Finance Lead |
| Client requests access to their own environment | PM and Account Lead coordinate with Moiz · client access provisioned with least-privilege IAM | Moiz + Account Lead |
| Metric | Type | Target |
|---|---|---|
| Environment provisioned within 2 business days of confirmed spec (%) | Process | 100% |
| Smoke tests passed before AI Engineer handover (%) | Process | 100% |
| Client infrastructure record filed at provisioning (%) | Process | 100% |
| Zero cross-client environment access incidents | Lagging | 0 |
| Credentials issued via approved secret management only (%) | Process | 100% |
Upstream:
Downstream:
| Version | Date | Description | Author |
|---|---|---|---|
| 0.1 | 2026-07-18 | Recommended draft — 7-step provisioning process, environment specification, smoke testing, credential handoff, infrastructure record. Pending Moiz review. | BA (Hammad Akram) |
← Back to Infrastructure Hub · ← Back to Company Operating System