A RM40 modeled CAC clears the RM150m 5G growth screen
Find a modeled option that adds at least 1 million active 5G relationships within 24 months while keeping modeled launch spend below RM150 million by 31…
Axiata’s direct ownership link is to CelcomDigi, while Maxis is connected through shared participation in Digital Nasional Berhad. In the 24-month modeled launch option, reducing…
Full framing
Find a modeled option that adds at least 1 million active 5G relationships within 24 months while keeping modeled launch spend below RM150 million by 31 December 2028.
Axiata’s direct ownership link is to CelcomDigi, while Maxis is connected through shared participation in Digital Nasional Berhad. In the 24-month modeled launch option, reducing CAC to RM40 keeps 3.19 million active relationships within the RM150 million screen.
Public-news source spine
The public record behind the subject
Instrument evidence
One exact state for each modeled layer
Chapter 1 · cidx
The comparison is directional, not a verdict
The exact Q1 2026 CIDX state compares Maxis with Axiata-linked CelcomDigi across five weighted decision inputs and exposes the resulting cross-entity score distribution. These…
Boundary This layer gives the rest of the investigation a common comparison boundary and makes the public-governance connection…
The exact Q1 2026 CIDX state compares Maxis with Axiata-linked CelcomDigi across five weighted decision inputs and exposes the resulting cross-entity score distribution. These are analyst-authored scenario inputs, not operator telemetry or an observed performance ranking.
This layer gives the rest of the investigation a common comparison boundary and makes the public-governance connection explicit. It does not decide the 5G option by itself; the next test must ask whether the same direction remains plausible over the full decision horizon.
Open the analyzed state to inspect each entity score, the five dimension weights, and the attainable range. A material weighting change should be recomputed and registered as a new state before it changes the conclusion.
With the comparison framed, the next chapter asks whether the modeled system can sustain the same direction over 104 weeks.
Chapter 2 · comdyn
The growth direction survives only as a weak system proxy
The registered ComDyn state carries the comparison into a 104-week compartment flow and contrasts the no-action path with staged intervention markers. It is a weak…
Boundary The trajectory keeps a large active-5G relationship outcome mathematically plausible, but the modeled marker effects…
The registered ComDyn state carries the comparison into a 104-week compartment flow and contrasts the no-action path with staged intervention markers. It is a weak subscriber-flow proxy rather than operator telemetry, a company forecast, or evidence of deployed behavior.
The trajectory keeps a large active-5G relationship outcome mathematically plausible, but the modeled marker effects are not strong enough to establish a commercial choice. The decision therefore remains projected and must be tested against product-level economics.
Open the live model to inspect compartments, transition timing, and marker assumptions. Change a transition only as a hypothesis, then rerun and register the adjusted state before using it as evidence.
With the time path bounded, the next chapter tests the original product plan that would have to deliver it.
Chapter 3 · product-launch-sim
The first product option clears growth but breaks the cost screen
The exact Product Launch Sim state clears the modeled relationship threshold but reaches RM392.419 million in modeled launch spend by week 104. That figure is a simulator output…
Boundary The original option is not usable under the RM150 million screen. It establishes the commercial benchmark and isolates…
The exact Product Launch Sim state clears the modeled relationship threshold but reaches RM392.419 million in modeled launch spend by week 104. That figure is a simulator output under the registered product and lever assumptions, not committed funding or a company forecast.
The original option is not usable under the RM150 million screen. It establishes the commercial benchmark and isolates acquisition cost as the parameter that the reader-adjusted option must change without losing the modeled relationship outcome.
Open the live product state to inspect product economics, launch timing, portfolio choices, and design levers. Any material edit must return through a fresh engine run and a new registered scene.
That establishes the high-cost benchmark. The next chapter tests the reader's RM40 CAC adjustment against the same modeled outcome.
Chapter 4 · product-launch-sim
RM40 CAC clears the screen, with thin modeled headroom
After CAC was lowered from RM120 to RM40, the engine reran the exact adjusted state. Week-104 modeled active relationships remained 3,188,157; modeled cumulative CAC became…
Boundary The adjusted option clears the RM150 million screen by RM7.194 million, but that margin is thin and all figures remain…
After CAC was lowered from RM120 to RM40, the engine reran the exact adjusted state. Week-104 modeled active relationships remained 3,188,157; modeled cumulative CAC became RM124.806 million and, with RM18 million modeled build cost, total modeled launch spend became RM142.806 million.
The adjusted option clears the RM150 million screen by RM7.194 million, but that margin is thin and all figures remain planning proxies. CAC, channel capacity, referral costs, and DNB commercial terms still require current operator validation before any live budget or launch decision.
Open the exact adjusted state to inspect the RM40 product economics and the levers that preserve the relationship trajectory. Return any further adjustment for a fresh run, comparison scene, and superseding conclusion.
With one modeled option inside the screen and its limits explicit, the article now hands the approved parameter change to the exact governed DOIL operations contract below—not to execution.
Required evidence gap · Incident Sim
No verified Incident Sim scene is present
This Gate-A faculty has no snapshot bound to the published Study.
The finding cannot claim visual evidence from this required layer.
Register and verify the exact Incident Sim state, then publish a revised Study.
Required evidence gap · Press
No verified Press scene is present
This Gate-A faculty has no snapshot bound to the published Study.
The finding cannot claim visual evidence from this required layer.
Register and verify the exact Press state, then publish a revised Study.
Claim-bound findings What the evidence supports—and how strongly 2 bound claims
- supported
Axiata directly owns 33.1% of CelcomDigi; Maxis and Axiata-linked CelcomDigi are connected through separate participation in Digital Nasional Berhad, and the examined public…
Full claim wording
Axiata directly owns 33.1% of CelcomDigi; Maxis and Axiata-linked CelcomDigi are connected through separate participation in Digital Nasional Berhad, and the examined public record did not show direct Maxis–Axiata ownership.
- projected
After the reader lowered modeled CAC from RM120 to RM40 and the engine reran the exact adjusted state, week-104 modeled active relationships remained 3,188,157 while cumulative…
Full claim wording
After the reader lowered modeled CAC from RM120 to RM40 and the engine reran the exact adjusted state, week-104 modeled active relationships remained 3,188,157 while cumulative modeled CAC fell to RM124.806 million; with RM18 million modeled build cost, total modeled launch cost is RM142.806 million, RM7.194 million below the RM150 million cap.
Handoff to network / automation
Continue from analysis into governed implementation
Bounded operational handoff · DOIL
Apply the approved RM40-per-relationship acquisition-cost parameter to the governed DarkNOC product configuration resource pl_postpaid_5g,…
Apply the approved RM40 CAC parameter to the Malaysia 5G product configuration
Review scope, controls and rollback 8/8 required structural checks passed
Full bounded objective
Apply the approved RM40-per-relationship acquisition-cost parameter to the governed DarkNOC product configuration resource pl_postpaid_5g, preserve every non-target field, verify the effective value and exact allowed diff, and restore the captured prior version if any postcondition fails.
Limits carried forward
- This is DOIL-authored local review material. Desk coordinates and renders it but does not infer language semantics from compiler internals.
- The single .doil file is the sole portable operations contract. This projection, its package, IR, and receipts are derived review material and are not required by the receiver.
- The pinned contract-test clock is validation evidence, not the current time. A receiver must re-evaluate expiry and all time-sensitive preconditions at consumption.
- Exact source, fixtures, lineage, and deterministic observations are review evidence only; they do not certify semantic correctness or prove untested paths.
- No human approval, target authority, target generation, deployment, scheduling, network call, or external effect is performed by this handoff.
- A target-side generator must recompile the exact workspace with a supported DOIL verifier and preserve every approved requirement, guardrail, bound, approval, observation, recovery, and output.
- The reference preview completed as a zero-record structural preview; it contains no action or scenario evidence.
- This package preserves intent and structural proofs only; no target has certified it.
- Approval declarations are preserved as intent; this tool does not grant human authority.
- Future targets are portability labels only; no target-specific generator or adapter ran.
- The content-addressed Studio state becomes replayable after Desk persists the included StateDoc.
Exact structural evidence
The score and level measure source-structure declaration coverage for the selected profile only. A production-shaped level is not post-investigation Desk handoff eligibility, semantic validation, human approval, certification, live-network validation, target readiness, deployment authority, or execution authority.
Source checks
- Clean parse · No parser diagnostics
- Top-level definition · Agent, class, or pipeline definition exists
- Purpose text · Intent or description is declared
- Context hydration · Runtime context requirements and sources are explicit
- Data sources · Data inputs are named; intentionally not applicable to this strict contract
- Tool surface · Allowed actions are declared
- Triggers · Activation paths are declared; intentionally not applicable to this strict contract
- Runnable methods · Handlers or methods are defined
- Guardrails · Pre, during, or post execution controls are declared
- Lifecycle · Timeout, health, or restart policy is declared; intentionally not applicable to this strict contract
- Observability · Logs, metrics, alerts, or reports are declared; intentionally not applicable to this strict contract
- Recovery · Retry, escalation, or dead-letter policy is declared; intentionally not applicable to this strict contract
- Output/promotion · Generated plans and approval stages are declared
Handoff checks
- Strict Operations Contract Complete · The sole .doil file declares every strict operations-contract facet; all other views are derived.
- Parse Clean · Every workspace file parsed without diagnostics.
- Brief Complete · A title and objective are required to preserve the human intent.
- Approved Intent Textually Bound · Every approved requirement is bound exactly once to its full text in the DOIL source for human semantic review.
- Scenario Coverage Ready · No source-owned scenario fixtures were declared or run; structural readiness makes no scenario-coverage claim.
- Target Kind Requested · At least one future portability target must be selected; no target artifact is generated here.
- Tool Effects Explicit · Every declared tool states its backend-neutral effect as read, propose, or external_change.
- Post Investigation Operational Remedy · The selected entrypoint reaches an explicit external_change request: Desk investigation is upstream, while this handoff specifies the approved operational remedy.
- Launch Selector Unambiguous · The explicit handler or trigger resolves to one entrypoint.
- Entrypoint Resolved · Reference preview resolved apply_approved_cac_remedy.
- Reference Preview Completed · The deterministic reference preview completed without granting authority or producing external effects.
- Execution Mode Matches Source · Execution mode agrees with the selected source entrypoint.
- Repeatable Mode Bounded · Execution intent is one-shot or carries an explicit maxCycles/expiresAt bound.
- Expiry After Contract Test Clock · Any declared expiry is later than the fixed source-owned contract-test clock; current-time validity is not assessed.
- Clock Pinned · The reference preview uses the source-owned fixed contract-test clock and contains no current-time or wall-clock claim.
Executive readout
Decision summary
Supported finding
- The public record connects Maxis and Axiata-linked CelcomDigi through separate participation in Digital Nasional Berhad, not through direct Maxis–Axiata ownership.
Decision boundary
- The RM40 CAC option clears the modeled RM150 million screen, but the result is a planning proxy—not operator telemetry, funding approval, or a company forecast—and RM7.194…
Review 1 full note
- The RM40 CAC option clears the modeled RM150 million screen, but the result is a planning proxy—not operator telemetry, funding approval, or a company forecast—and RM7.194 million of modeled headroom is thin.
Question to resolve
- Validate CAC, channel capacity, referral costs, and DNB commercial terms with current operator data before any live budget or launch decision.
How this was governed
90% autonomous · 5 human checkpoints (gate_a & gate_b & published & gate_b & gate_b)
Verification
- Supported claims1
- Projected1
- Illustrative0
Evidence
- Cited (source)3
- Modeled5
- Observational0
Observation sources
- web publishable allowed
- web publishable allowed