1. Start here1.3 Parties & sign-off
Coding Requirement Documentation (CRD) — Proposal
AIEE.DEV formal proposal document — customer requirements, coding specification, and delivery plan for SOQ TMS.
What is a CRD?
CRD = Coding Requirement Documentation — business need -> engineering delivery. SOQ approves what, how, and terms before scale build.
| Layer | Page |
|---|---|
| Customer baseline | 4.1 Attachment A |
| PRD | 4.2 Attachment B |
| Portals & modules | 4.3–4.9 |
| Delivery | 5.1–5.10 |
| Commercial | 2.1–2.3 - 3.1 |
Parties
SOQ (Customer)
Training provider — diploma, short courses, WSQ. Signatory TBC at contract.
AIEE.DEV leadership
| Name | Title | Role |
|---|---|---|
| Pei Han | CCO | Commercial - executive sponsor |
| Eddy | CPO | Product - UX - UAT - PRD author |
| HK | CSO | Solution - SWDA/Xero - Attachment A author |
| Andy Koh | CTO | Full-stack build leadership |
Engineering: 3x Software Engineers (L2 - L3 - L4) under CTO - aiee.dev
Attachments
| Attachment | Author | Page |
|---|---|---|
| A — Requirements | HK (CSO) | 4.1 - PDF |
| B — PRD v1.1 | Eddy (CPO) | 4.2 |
| Implementation Doc v1 | AIEE.DEV | 5.8 Tech spec |
Acceptance (proposal level)
- Attachments A + B = functional baseline (subject to discovery)
- Three-app boundary + SWDA Hub + Xero accepted
- Phased delivery preferred (MVP -> Funded -> CRM/Diploma)
- Named leadership = delivery authorities
- Full-stack build owned by Andy Koh (CTO) + 3x engineers
Sign-off
| Party | Name | Role | Signature | Date |
|---|---|---|---|---|
| Customer | SOQ Authorised Rep | |||
| AIEE.DEV | Pei Han | CCO | ||
| AIEE.DEV | Eddy | CPO | ||
| AIEE.DEV | HK | CSO | ||
| AIEE.DEV | Andy Koh | CTO |
Next steps
- 3.1 Discovery — SWDA, Singpass/SFC, Xero, Privyr
- 2.1 Plan SOQ-25K + 2.2 Grants + 5.10 Handover
- 5.2 Prototype sign-off before engineering burn
- Kickoff — calendar 5.1 Project control - scope 5.3 Roadmap