[P0] Confirm build rules, checkpoint constraints, and submission requirements

[TFT444]

Objective

Remove external ambiguity that could invalidate the technical submission or force late architectural changes.

Questions to confirm

• Is pre-event code permitted, and what must be created during the live window?
• Which payment protocols or sponsor technologies are mandatory at checkpoints?
• What are the judging dimensions and elimination conditions?
• What repository, licensing, team, and submission evidence is required?
• Are sandbox transactions acceptable, or is a specific network required?
• What presentation duration and equipment will be available?

Acceptance criteria

• Organizer responses are recorded with source and date.
• Mandatory requirements are mapped to existing technical issues.
• Any scope change is reflected in priority labels before implementation.
• Unconfirmed assumptions remain visibly marked as assumptions.

Keywords: requirements, submission rules, checkpoint constraints, judging criteria, compliance, scope control