Skip to content

Open issues

The six open issues below are carried from the architecture spec §17. Each one has a decision owner and an implied deadline. They are tracked, not resolved — update this page as decisions land.

1. Digital-signature trust anchor

Decision required before M2 production cutover

Paths:

  1. Malaysian Digital Signature Act 1997 compliance via a licensed CA (MSC Trustgate, Pos Digicert).
  2. Interim self-signed organisational certs, upgraded to a licensed CA before M6 go-live.

Why it matters. Kertas Perakuan and SIGL carry regulatory weight; the signature must be legally recognised at production. Both paths are workable for dev / UAT; only path 1 is viable long-term.

Blocks: production cutover of signing-svc.

2. MyDigital ID requirement

Decision affects onboarding UX

Whether MyDigital ID is mandatory for any persona. GCP Identity Platform federation is designed to accommodate it, but the decision affects the PSP onboarding flow and any fallback path for non-MyDigital users.

Blocks: final PSP sign-up UX (not strictly blocking M2 build).

3. ACC / CDE integration

Affects bim-svc outbound sync design

Whether Autodesk Construction Cloud is the client's system-of-record for BIM federation. If yes, bim-svc needs an outbound sync path; if no, federation is SISS-internal only.

Blocks: M5 federated-view mode design.

4. Masterplan GIS service

Source for zoning envelope data (M5)

Source of zoning envelope data for the M5 zoning comparison:

  • SI-internal GIS — requires CMU data owner readiness.
  • Third-party provider — moves faster, but introduces an external dependency.

A stub interface is specified; the real integration depends on the data owner's readiness.

Blocks: M5 zoning-compare activation.

5. Email provider

Affects deliverability and per-recipient volume

Options for notification-svc email delivery:

  • SendGrid — easiest, highest deliverability, external provider.
  • Google Workspace SMTP — aligned with existing tenancy; lower volume.
  • Government mail gateway — mandated for some Malaysian gov projects; slowest onboarding.

Blocks: M2 production rollout of notifications (not dev / UAT).

6. AI comment-training data

Corpus needs to be sourced

The product backlog notes: "No clear pathway on how to train the AI to pre-fill each technical agency checking."

The ai-svc design assumes a curated corpus of historical comments per department. That corpus needs to be sourced from CMU / ATD / ATL archives.

Blocks: M3 AI-drafted comment quality (not strictly M2).

How this list is used

  • At every milestone gate review, each open issue is re-visited.
  • Decisions, once made, are recorded by removing the item from this page and linking the resulting implementation in the relevant architecture page.
  • Do not delete the item without a backlink — readers need to find where the decision landed.