Phase 1 · Deliverable 02 of 10

Assumptions, unresolved decisions and conflicts

What we assumed in order to proceed, what must be decided before Phase 2, and where the brief contradicts itself or arrived incomplete. Each item has an ID that the traceability matrix (R2) references.

DRAFT v0.1 · FOR APPROVAL EVERY ITEM BELOW IS A DESIGN ASSUMPTION OR PLACEHOLDER

Design assumptions (A-xx)

Used to proceed; each one is labelled "Design assumption" wherever it surfaces in a screen.

Assumption

Basis

Impact if wrong

A-01

Desktop-first at 1440 px, minimum supported 1280 px. Owner brief and alert acknowledgement are also readable at tablet and phone widths. Workbenches are desktop-only.

Executive daily use; dense workbenches

Owner mobile-first would reorder O-01/O-07 priorities

A-02

All monetary values are shown in synthetic currency units ('₹ m'). FX appears as an exposure, never as translation logic.

No client currency given; truth rules

Multi-currency display requires a currency selector in the header

A-03

The reporting period is monthly with a daily flash, YTD and a rolling forecast. Period labels such as 'P07' are synthetic.

Common for industrial MIS (assumption)

Weekly cadence changes trend charts and certification calendar

A-04

Refresh cadences are shown as [REFRESH CADENCE — PLACEHOLDER] per source category. The header shows the oldest relevant refresh for the page.

No source systems may be named

Near-real-time plant feeds need a 'live' indicator variant

A-05

The hierarchy is Group → Business → Entity → Plant → Production Line. Synthetic structure: 3 businesses, 6 entities; Entity A1 has Plants 01–03; Plant 02 has Lines L1–L3.

Brief's required drill hierarchy

Matrix organisations (business × region) need a second hierarchy

A-06

'Owner' is a role (controlling shareholder or chair office), not a named person. One role, possibly several users.

Brief uses role names only

None to layout; affects notification routing

A-07

Entitlements come from enterprise identity management (placeholder). The app enforces scope by hierarchy node and by domain.

Least-privilege requirement

If scope is not node-based, the scope selector changes

A-08

Materiality is a multi-dimension score that maps to Critical / High / Medium / Low. All weights and thresholds are placeholders.

Brief: do not invent thresholds

Rule-based (non-scored) materiality changes the breakdown component

A-09

AI assistants read only governed data within the requester's entitlements. Their outputs are stored as AI-generated artefacts with provenance and are never auto-applied.

Brief's AI boundary

—

A-10

Notifications are in-app plus a daily digest (channel placeholder). No messaging product is named.

Truth rules

Chat-ops integration would add acknowledge-from-message flows

A-11

English UI with locale-neutral number formatting (placeholder). Thousands separators and units are shown on every value.

Not specified

Localisation adds width to KPI cards

A-12

Evidence can be a file, a link to a source record (placeholder) or a structured attestation. Evidence is immutable once submitted; corrections are new versions.

Audit expectations

If evidence is externally stored, show link state (available / broken)

A-13

The audit trail is append-only and visible according to role. Platform capability is assumed.

Brief: evidence and audit trail route

—

A-14

Production unit is kt (synthetic) and cost is shown per tonne. Other businesses use 'unit' as a placeholder.

Diversified industrial; no product given

Unit labels per business need configuration

A-16

Severity and materiality are different fields. Severity is the intrinsic seriousness of the event (rule-assigned at detection; the owner may adjust it with a reason). Materiality is the business-significance score (placeholder model). Both appear in the header (v0.2).

Brief lists both without defining them

If they are the same concept, one header field and DS-18 change

A-15

An Administrator console (mappings, configuration) exists but is outside this design scope. Only its effects (mapping change → re-certification) are shown.

Brief lists the Administrator role but no admin route

Adds a route family if it is in scope

Unresolved decisions (D-xx)

Decisions that change screens, states or permissions. Each has a recommendation; the deciding role is a role name, not a person. Items marked GATE blocked Phase 2.

Status 2026-10-03: accepted by the user. All recommendations below are adopted as the working architecture. Thresholds, authority limits and similar values stay PLACEHOLDER until the named role approves them.

Decision

Options

Recommendation

Decided by (role)

Gate

D-01

Alert, Case, Incident and War Room object model

(a) one object with states; (b) Alert → Case → Incident → War Room as escalating objects

(b): Alert is system-detected. Case begins when a human accepts ownership. Incident is a Case at materiality ≥ High with a commander. War Room is a collaboration mode of an Incident. Keeps one ID lineage.

Core Group Executive + product owner

GATE

D-02

Can a Metric Owner certify their own KPI?

(a) allowed; (b) never; (c) never for leadership KPIs

(c): separation of duties for leadership KPIs; same-person allowed elsewhere with Assurance Reviewer sampling.

Assurance Reviewer + Core Group (finance)

GATE

D-03

Materiality dimensions, weights, thresholds

Brief text truncated; see C-10

Approve the dimension list in R3. Weights and thresholds stay PLACEHOLDER until risk and finance approve.

Core Group (risk, finance)

GATE

D-04

Can the Owner pull sub-threshold issues?

(a) push and pull only above threshold; (b) pull allowed, labelled 'below materiality'

(b): no push below threshold, but Ask and search may return in-scope items labelled 'Below materiality threshold'.

Owner office

—

D-05

Owner's permitted strategic decisions

Needs a delegation-of-authority matrix

Use [DoA LIMIT — PLACEHOLDER] on decision cards. Route above-limit decisions to the Owner only when materiality is Critical.

Owner office + Core Group

—

D-06

Closure approver for material cases

(a) Entity Executive; (b) Core Group; (c) tiered

(c): Medium → Entity Executive; High → Core Group Executive; Critical → Core Group Executive with Assurance Reviewer evidence check. The action owner never self-approves.

Core Group

GATE

D-07

Disclosure-review authority

The role is missing from the role model

Add a placeholder governance assignment 'Disclosure Authority (PLACEHOLDER)'. No legal rule is modelled; only the clock and state are shown.

Owner office / legal (placeholder)

—

D-08

Escalation ladder and clock durations

Levels and durations unspecified

Ladder L0 Entity → L1 Business → L2 Core Group → L3 Owner. Durations [PLACEHOLDER]. Clocks are rule-based, never AI-set.

Core Group

—

D-09

Who may save and publish scenarios

(a) anyone runs, Core Group publishes; (b) entity publishes locally

Anyone in scope may run. Entity Executive publishes for local decisions; Core Group publishes for cross-entity decisions. Owner requests.

Core Group

—

D-10

Source of the 'Board number' for the variance KPI

Placeholder in brief

[BOARD-REPORTED FIGURE — PLACEHOLDER], read-only, shown in G-08 drill only.

Core Group (finance)

—

D-11

Daily brief time and channel

Not specified

[BRIEF TIME — PLACEHOLDER], shown as 06:30 (SYNTHETIC). In-app plus digest.

Owner office

—

D-12

Restricted state: show existence or hide?

(a) hide entirely; (b) show 'restricted' with no detail; (c) show to parent scope only

(c): show the restricted placeholder only where the user's parent scope already implies the item exists. Never show counts, names or values. Search and AI never confirm existence.

Assurance Reviewer

GATE

D-13

Does the six-card limit apply to workbenches?

(a) yes; (b) workbenches use counters plus tables

(b): main pages ≤6 KPI cards; workbench (T-E) pages ≤4 workflow counters plus an action table.

Product owner

—

D-14

'Briefing Pack' versus 'Inquiry Pack'

Different names in lens list and route list

One route, G-10 'Briefing and Inquiry Pack'.

Product owner

—

D-15

One or two routes for Reliability / Supply

Brief joins them in the route list, separates them in the lens list

Two routes (E-03, E-04) on the same template C.

Product owner

—

D-16

Peer benchmarks for Entity users

(a) none; (b) anonymised quartiles

(a) by default (least privilege). (b) only with Core Group approval per KPI.

Core Group

—

D-17

What can be overridden and by whom

Manual overrides are counted but not defined

KPI value override only by the Certifier in scope with a mandatory reason and evidence; counted in GOV-002 and reviewed by Assurance.

Assurance Reviewer

—

D-18

Reopen control

Who can reopen and for how long

Core Group Executive or Assurance Reviewer, within [REOPEN WINDOW — PLACEHOLDER]. The entity may request it.

Core Group

—

D-19

Unaccepted AI routing

What happens if no human accepts?

After [ACCEPTANCE CLOCK — PLACEHOLDER] the alert goes to 'Unowned', counts in EFF-006 and escalates by rule to the next level. AI never assigns.

Core Group

—

D-20

Added routes S-09 to S-13

Not in the brief's route list but needed by the journeys and Theme 3

Approve: Entity Contribution, Operations Impact and Cash Exposure drills, the No-Surprises Signal Board and Ask Control Tower.

Product owner

GATE

D-21

Owner access to the Core Group lens (v0.2)

(a) Owner lens only; (b) Core Group lens read-only

(b) read-only, no workbench controls; the Owner's own landing pages remain summary-depth.

Owner office

—

D-22

Where consolidated (group) KPIs are certified (v0.2)

(a) separate group workbench route; (b) E-08 parameterised by scope

(b): one Number Assurance Workbench whose scope comes from the certifier's assignment; group scope is opened from G-08. Avoids a 42nd route.

Core Group (finance) + Assurance Reviewer

GATE

D-23

Who may be appointed Incident Commander (v0.2)

Brief names the role but not its source

Appointed per incident by the Core Group Executive (Critical) or Entity Executive (High) from Functional Leader or Entity Executive roles; recorded as a governance assignment.

Core Group

—

Conflicts and gaps in the brief (C-xx)

Contradictions, duplicate measures and text that arrived truncated or garbled. The proposed resolution applies until it is explicitly overruled.

Conflict or gap

Where in the brief

Proposed resolution

C-01

The six-card rule versus Theme 1, which lists 18 measures and requires risk and strategic coverage on the Owner home.

Theme 1, Principles

Six selected cards (05, O-01); the rest go into four named drill tabs: Financial, Operational, Strategic, Risk.

C-02

Owner 'cannot certify operational KPIs by default' implies the Owner could certify some KPIs.

Role-based action rights

The Owner certifies nothing in-app. Any exception requires an explicit certifier assignment.

C-03

Core Group 'governs certification', but certification belongs to the Metric Owner/Certifier.

Lenses vs roles

Core Group sees the calendar, coverage and overdue items and can escalate. It certifies only if separately assigned.

C-04

The Administrator maintains mappings, and mapping changes can alter certified numbers.

Admin rights

Any mapping change moves affected KPIs to 'Pending certification' and records an audit entry. Admin cannot certify.

C-05

Entity sees Production-to-Cash including Upstreaming, but upstreaming is a group treasury concern.

Theme 4, Entity lens

Entity sees its own upstream obligation and status only; group treasury positions are restricted.

C-06

Sustainability (water, emissions, energy) is in both Theme 5 and Theme 7.

Themes 5 and 7

One governed KPI each (SUS-001..003), reused with page context (R1).

C-07

'Recovery percentage' and 'Yield or recovery' both appear under Plant.

Theme 5

Two definitions: PLT-004 Recovery % and PLT-005 Yield. Confirm whether they are the same measure.

C-08

FX exposure, Free Cash Flow, Capacity utilization, Open critical alerts and Production vs plan each appear in two or more themes.

Themes 1, 3, 4, 5, 8

One canonical KPI ID each; alias rows in R1 point to the canonical ID.

C-09

Theme 5 reliability list is cut off at 'Preventive-'.

Theme 5

Assumed REL-005 'Preventive-maintenance compliance' (Design assumption).

C-10

The materiality section is garbled ('calculate or dispe; Production exposure: Liguidient…').

Materiality model

Dimensions reconstructed in R3: Financial, Liquidity, Production, Regulatory, Reputation, EHS, plus a time-to-breach modifier. All need confirmation (D-03).

C-11

Theme 2 list is cut off at 'related break or'.

Theme 2

Read as 'related break or finding'.

C-12

Stray characters and broken arrows: 'I' in route lists, '-7-Action', 'Cash Exposure - Case Detail', '(PI Card', 'issurance', 'Vlew'.

Routes, journeys

Read as typos: KPI Card, Number Assurance, View, and → between steps.

C-13

The ACT question is truncated: 'is the matter moving to evidence-based'.

Four questions

Read as '…moving to evidence-based closure'.

C-14

Owner journey needs Operations Impact, but Owner must not see plant work queues.

Owner lens, primary journey

S-10 shows Owner-depth plant summary down to plant level, with no queues and no line-level transactions.