Styxis
Company
Knowledge

Prepare entity-role evidence before choosing a data-centre licensing subject

A facility label and supplier name do not determine the responsible legal entity; declared roles need separate corporate evidence.

The immediate task is not to choose the entity

Preparing for data-centre regulation can invite an assumption that facility owner, operator and service provider are one legal entity. A defensible immediate action is to gather entities and role evidence instead of selecting an answer automatically. Truthound can check a limited row constraint in that declared-role inventory. It does not determine effective control, legal responsibility or which entity must be licensed.

The official explanation leaves an assessment duty

Singapore’s MDDI closing speech in the bill’s 2nd-reading debate on 7 October 2026 says IMDA will provide further clarity about assessing which entity controls a data centre and should be licensed. It discusses corporate structures and individual details. The speech alone does not establish a particular entity’s legal status or a current commencement date for the requirements.

Record facilities and entities separately

A proposed preparation register distinguishes facility identity, legal-entity identity, declared role and corporate or contract references. Staff confirm which entity a shared brand name denotes. Do not fill owner and contractual operator as the same party by assumption. The inventory should reveal questions needed for the next assessment, rather than supplying a legal conclusion from an apparently complete row of names.

Check a small declared-role condition

Truthound Core Python SDK 3.3.4 (open-source SDK, Polars backend) documents ColumnPairInSetValidator for operator-approved entity-class and role pairs supplied as valid_pairs. Define ignore_nulls and missingness explicitly. The check establishes whether the declared values meet that inventory condition. It does not discover whether a role document is true or whether the named entity exercises effective control over the facility in practice.

Know when to stop collecting an automatic answer

If several entities connect to one facility, or contract and corporate explanations differ, return the question to its owner. Do not select a familiar supplier merely because evidence is sparse. Nor should multiple roles automatically be treated as a defect. Preserve what remains unresolved and refer it for qualified legal or regulatory assessment. That is the boundary of the immediate preparation action.

Compare only the same row constraint

Pandera 0.35.0 (MIT open-source Python DataFrame validation library; pandas, Polars and other supported backends) documents custom checks through a caller-implemented predicate that could express the declared-role condition. Truthound instead receives the approved role pairs. Compare that narrow condition on the same table and null policy, not the entire corporate-evidence or legal-review task. A correct existing Pandera contract can remain; neither route supplies a licence determination or demonstrated superiority for the wider workflow.

Begin with grounds for one facility

Have the owner explain why each entity appears in one facility’s register. Do not fill missing corporate or contract evidence with a format-valid value. Establish actual applicability through authoritative rules and appropriate interpretation. Avoid a shortcut that classifies the legal subject automatically from one capacity figure or facility name; the regulatory question requires evidence about the relevant parties and their relationships.

Hand over questions that can be assessed

The useful output is an inventory of parties, grounds and unresolved questions, not an automatic answer naming a licensee. Evidence about operator and contracting party makes the next review more specific. Describe the data check narrowly as checking the declared record condition. Preserving that boundary prevents fast preparation from becoming an unsupported legal judgement while still giving responsible reviewers something concrete to examine.

Conditions

Use an authorized inventory of facilities, entities, declared roles and corporate or contract references.

Alternatives

Comparison with a Pandera 0.35.0 predicate is limited to the same row constraint, not equivalence of the overall legal review.

Limitations

  • Valid declared-role combinations establish neither effective control nor legal responsibility or licensee status.

Evidence

Event checked
Subject checked
Modified