What is still open
Two lists, and we would rather you read them here than find them yourself. The first is where the ISC's own documents disagree with each other or leave something undecided. The second is what we need from outside and have not got.
In every case the system runs on a stated assumption in the meantime, and in every case the assumption is configuration rather than code: when the working group decides, the decision is a setting, not a rebuild.
Questions for the working group (16)
| Ref | The question | What we assume meanwhile | What we recommend | Effect |
|---|---|---|---|---|
| C-01 | Duplicate FR numbering in Bid to Bulletin v1.2 The same FR numbers are used for different requirements in 3.3.1, 3.3.2 and 3.3.3. Authority: v1.2 (cover sheet footnote confirms numbering may be revised). |
Traceability matrix cites the official number and the section in which it appears. | Preserve official numbers and add internal IDs B2B-001 to B2B-028. | Not blocking MANAGED |
| C-02 | Duplicate section numbers Section numbers reused; cover sheets replicate them with a footnote. Authority: Cover sheets 25 Aug 2026. |
Cover sheet checkboxes referenced by number and module name. | Use the cover sheet labels exactly, with module names to disambiguate. | Not blocking MANAGED |
| C-03 | Who records final bulletin approval FCEAD 3.1.1 places bulletin approval with the ISC Bureau before issue. Neither requirements document says which role records that approval in the system. Authority: FCEAD 3.1.1 for the approving body; the requirements documents for the workflow, which describe routing and edit rights only.. |
FAI Controller release and review by the 1st VP, the Bureau and the relevant Committee Chairs are covered by the design and shown in the demonstration. The final recorded bulletin approval authority remains configurable pending RTTWG confirmation. | We do not extrapolate annex 4.1 from bids to bulletins. The workflow implements FAI Controller release, routing to the 1st VP, the Bureau and the Committee Chairs, and the 1st VP and FAI Controller field-edit rights of 6.1 and 6.2. The role that records the final bulletin approval is a configuration setting with no default asserted as correct. | Not blocking OPEN |
| C-04 | 7 December rule Authority for the 7 December date and behaviour of bids ready inside the window. Authority: v1.2. |
Dates are configuration; behaviour follows v1.2. | Implement exactly as v1.2 with configurable dates; bids ready inside the window are held as complete drafts and can be submitted from 8 December as late bids, subject to annex 4.2. | Not blocking MANAGED |
| C-05 | Opening Ceremony versus start date Two anchor dates for event-relative deadlines. Authority: Each FRS for its own scope. |
Every deadline states its anchor date on screen. | Deadline engine supports both anchors; each rule declares its anchor (Opening Ceremony or official competition start). | Not blocking MANAGED |
| C-06 | Who sends the OA Request Sender of record for the OA Request. Authority: Annex 1.4. |
The ISC FCE Management Platform produces the completed OA Request; issuance and signature remain with FAI. | System generates the completed form; either the organiser or the ISC (1st VP or Finance Secretary) sends it; a send action with audit is provided but not mandatory. | Not blocking MANAGED |
| C-07 | Account creation approval Contradictory requirements within v1.2. Authority: Both in v1.2; unresolved by annex. |
Both behaviours supported; ISC selects the default. | Default self-registration with email verification and administrator purge (NFR-003); administrator approval switch available (FR-001). ISC chooses at configuration. | Not blocking OPEN |
| C-08 | Meaning of 'Account-only access' Resolved by annex. Authority: Annex 1.5. |
Singleton roles enforced for ISC Finance Secretary and FAI Controller. | Singleton role enforcement. | Not blocking CLOSED |
| C-09 | FAI API timing Production validation cannot be demonstrated before approval. Authority: v3.0. |
Clearly labelled as external dependency in cover sheet Notes. | Mock provider for demonstration; production adapter activated after credentials; fall-back lists retained. | Not blocking MANAGED |
| C-10 | Individual logins versus NAC-only submission Apparent tension. Authority: v3.0. |
Personal-field completion by individuals; submission by NAC. | Individuals edit personal fields only; NAC submits. | Not blocking CLOSED |
| C-11 | Timezone of deadlines Controlling timezone for 1 November, 7 November, 14 November, 7 December and event-relative deadlines. Authority: None. |
Deadlines are evaluated in the ISC-configured timezone displayed on screen. | Configurable ISC timezone (recommendation: Europe/Zurich, FAI seat) shown on every deadline; confirm with ISC. | Not blocking OPEN |
| C-12 | Fees Schedule values Amounts and offsets unknown. Authority: External. |
Fee amounts are ISC configuration, not code. | Fee rules configurable by ISC administrator; values loaded when supplied. | Not blocking OPEN |
| C-13 | June presentation open questions Many June questions are now answered. Authority: July material. |
OQ-01 numbering: managed (C-01). OQ-03 7 December: managed (C-04). OQ-04 fees: open external (C-12). OQ-05 dates: managed (C-05). OQ-10 OA sender: managed (C-06). OQ-11 bulletin approval: managed (C-03). OQ-29 proposal logistics: closed by cover sheets. OQ-30 R&R scope: closed by v3.0. Remaining June questions are not carried into the submission. | OQ-01 numbering: managed (C-01). OQ-03 7 December: managed (C-04). OQ-04 fees: open external (C-12). OQ-05 dates: managed (C-05). OQ-10 OA sender: managed (C-06). OQ-11 bulletin approval: managed (C-03). OQ-29 proposal logistics: closed by cover sheets. OQ-30 R&R scope: closed by v3.0. Remaining June questions are not carried into the submission. | Not blocking CLOSED |
| C-14 | Who pays the Sanction Fee The two lists differ. The RTTWG sheet adds Alternates and omits team videographers. Authority: Unresolved. The FCEAD is the ISC rule; the sheet is the RTTWG's own working specification for this tool.. |
Sanction fee liability is a per-role configuration flag. The FCEAD 2.2.2 list is the default; the differing list in the RTTWG field sheet is available as a preset. We ask the working group which governs. | The payer set is configuration, not code. The FCEAD list is the shipped default because it is the ISC rule; the RTTWG sheet list is offered as a one-click alternative preset, and both are shown in the demonstration with the difference highlighted. | Not blocking OPEN |
| C-15 | Two second response time and report generation Read literally, NFR-003 covers report generation of every kind, including a full multi-hundred-page PDF. Asynchronous rendering may be sound engineering and still not meet the words. Authority: v3.0 as written. |
Compliance is qualified in the cover sheet Notes and in the matrix: met for data entry, online views, CSV and the seven role report PDFs at acceptance scale; bulk PDF compilation is asynchronous and the interpretation is referred to the RTTWG. | We do not claim literal compliance. We commit to two seconds at P95 for data entry, for every online filtered report view, and for CSV generation of every required report on the acceptance dataset. For PDF we distinguish the seven role reports of FR-026, which we commit to render synchronously within two seconds at P95 at acceptance dataset scale, from bulk or full-event PDF compilations, which are queued with progress and a notification. This distinction is disclosed, not concealed. | Not blocking OPEN |
| C-16 | Obligation strength of the July annex lines The mandatory count was overstated by seven. Authority: The annex text itself. |
Counts published as 90 mandatory, 2 optional, 3 recommended, 4 clarifications, 99 official lines. | Every line reclassified from its own wording: 15 required process rules, 4 process clarifications, 3 recommendations. The three recommendations and all four clarifications are still implemented; they are simply not counted as mandatory requirements. | Not blocking CLOSED |
What we need from outside (7)
| Ref | What | Who owns it | What it is needed for | Status |
|---|---|---|---|---|
| D-01 | FAI Sporting Licence API Manual (an existing document; Appendix 3 of v3.0 says to request a copy from the working group) | RTTWG | Finalise ProductionFAIProvider field mapping, authentication and error handling | REQUESTED (blocking) |
| D-02 | Google Sheet of required, suggested and personal registration fields (Appendix 2 of v3.0) | RTTWG | Load the FCE field catalogue (FR-015, FR-020) | CLOSED |
| D-03 | FAI Fees Schedule (Application Fee, Performance Bond, Sanction Fee) and payment offsets | ISC Finance Secretary | Fee rule values for FR-017, FR-018 and sanction fee reports | REQUESTED |
| D-04 | RTTWG standard provider questions | RTTWG | Answer in the submission if issued | IDENTIFIED |
| D-05 | Corrected or re-numbered requirements and cover sheets | RTTWG | Re-map matrix and cover sheets if issued | IDENTIFIED |
| D-06 | Production FAI Sporting Licence API access and credentials (distinct from the API Manual at D-01) | FAI IT | Activate ProductionFAIProvider against the live database | IDENTIFIED (blocking) |
| D-07 | ISC configuration decisions: timezone, account approval mode, bulletin approval chain, retention periods | ISC / RTTWG | Configuration at implementation kick-off | IDENTIFIED |
Exported from the conflict and dependency registers on 2026-09-04. The full registers, with the source wording of both sides of every conflict, are the External Dependencies tab (06) and the Conflict Register tab (12) of the requirements traceability matrix.