4. 2D Matrix Grids, Likert Scales & Chronological Pickers

2D Matrix Grids ([MATRIX])#

Allows respondents to evaluate multiple row items across the same column scale. Supports cross-row validation and logical constraints via [VALIDATE_MATRIX: ...].

• Canonical Activation Tag: [MATRIX].

UI Presentation, Category Grouping & Accessible Selects#

• Accessible Dropdown Selectors: Each row item features a modern, accessible dropdown selector (<select>) containing the defined COLUMNS: choices. This delivers unmatched legibility and responsiveness across both desktop and mobile viewports, especially with verbose statements.
• Category Grouping: Group related rows under distinct section headers by inserting non-numbered category titles directly within the ROWS: block (e.g. Biologics, Immunosuppressants).

Syntax Breakdown & Incompatibility Validation ([VALIDATE_MATRIX])#

The [VALIDATE_MATRIX: ...] directive enforces business logic and mutual exclusivity across matrix cells:

• INCOMPATIBLE ROWS (row_a, row_b): Defines row ID numbers that cannot simultaneously share the restricted answer.
• ON COLUMN N: Specifies the column position (1-indexed) where mutual exclusivity is strictly enforced (e.g. ON COLUMN 1 for "Currently in active use").
• ERROR "Message": Custom validation message displayed when an invalid combination is selected, preventing form submission until rectified.

S13. Please indicate your organization's adoption status for each of the following solutions:
[MATRIX]

COLUMNS:
1. Currently in active use
2. Used in the past, but not currently
3. Never used

ROWS:
1. Corporate Messaging Platform
2. Document Management System
18. On-Premise Data Warehouse
19. Cloud-Native Data Lake

[VALIDATE_MATRIX: INCOMPATIBLE ROWS (18, 19) ON COLUMN 1 ERROR "You cannot mark both On-Premise Warehouse and Cloud Data Lake as mutually exclusive primary solutions."]

Numeric Distribution Matrices with Total Sum ([OPEN NUMERIC] Matrix)#

Renders a structured numeric distribution grid where each category includes a sub-row definition (Definition: "..."), individual numeric input cells ([OPEN NUMERIC; min-max; unit]), and an automated total sum verification row (Total with directive [Sum; min-max; unit; if not equal X -> alert: ...]).

• Canonical Activation Tag: Matrix layout defined under COLUMNS: with sub-rows defining Definition: and Share: [OPEN NUMERIC; min-max; %] alongside a [Sum; ...] row.
• Automatic Total Calculation: The engine automatically excludes Total from user-editable inputs, calculating the cumulative sum dynamically and alerting the respondent in real-time if the total sum requirement (e.g. 100%) is unmet.

Q4. Across your organization's active technology projects, what percentage falls into the following technical complexity categories?

COLUMNS:
1.	Complexity
2.	Definition
3.	Share

ROWS:
Low
Definition: "Standard architecture with low technical uncertainty and minimal dependencies"
Share: [OPEN NUMERIC; 0-100; %]
Moderate
Definition: "Some uncertainty or integration with legacy platforms; manageable risk"
Share: [OPEN NUMERIC; 0-100; %]
High
Definition: "Highly distributed systems, mission-critical pipelines, or strict uptime requirements"
Share: [OPEN NUMERIC; 0-100; %]
Total
Definition:
Share: [Sum; 0- 100; %; if not equal 100 –> alert: sum must be 100% ]

Multi-Row Likert Agreement Matrices (1 to 7 Scale with Anchors)#

Allows respondents to evaluate multiple statements, product attributes, or use cases against a standardized 1 to 7 agreement scale with semantic anchors at the poles and midpoint.

• Canonical Activation Tag: [SINGLE CODE] or [MATRIX] with COLUMNS: and ROWS: blocks.
• Automatic Numeric Column Interpolation: Numeric indices declared with minimal syntax (2., 3., 5., 6.) are automatically compiled into clean numeric column values in the scale.
• Dual Responsive Layout: On desktop screens, renders a connected 7-point horizontal radio scale for each row; on mobile devices and documentation preview, stacks each evaluation row into an individual interactive card.

Q6. Please rate your level of agreement with the following platform capabilities on a 1 to 7 scale, where 1 is strongly disagree and 7 is strongly agree:
[SINGLE CODE]

COLUMNS:
1. Strongly Disagree
2.
3.
4. Neutral
5.
6.
7. Strongly Agree

ROWS:
1. Provides meaningful improvement in system observability and telemetry
2. Reduces need for manual incident triage and troubleshooting
3. Simplifies multi-cloud engineering workflows
4. Improves deployment confidence in mission-critical releases
5. Reduces dependencies on external consulting support

Horizontal Likert Scales#

Declaring a question with columns without rows compiles it as a clean Likert evaluation scale:

Q8. How satisfied are you with the platform performance and reliability?
[SINGLE CODE]

COLUMNS:
1. Very dissatisfied
2. Dissatisfied
3. Neutral
4. Satisfied
5. Very satisfied

Looped Date Pickers ([COMPONENT: MONTH_YEAR])#

Iterates over rows selected in a prior matrix using [LOOP: ...] to capture month and year:

S14. In approximately what month and year did you begin deploying [PIPE: ROW_LABEL]?
[COMPONENT: MONTH_YEAR]
[LOOP: S13 FOR 'Currently in active use' EXCLUDING CODES 2]
[VALIDATE: MIN_YEAR = CURRENT_YEAR - AGE_AT(S3) ERROR "Deployment date cannot precede company registration year."]

Unified Date Ranges ([COMPONENT: STARTSTOPMONTH_YEAR])#

Captures chronological intervals and enforces that the stop date cannot precede the start date:

S16. Thinking about the time period your company utilized [PIPE: ROW_LABEL], when did you start and when did you conclude that service agreement?
[COMPONENT: START_STOP_MONTH_YEAR]
[LOOP: S13 FOR 'Used in the past, but not currently' EXCLUDING CODES 2, 19]
Please give your best estimate of the start and stop dates.