Demonstration prototype — synthetic data only.

Resolution Package

MNC-SUP-2026-00395

Resolution record for request MNC-SUP-2026-00395.
Versions

1.Request identification

Request ID
MNC-SUP-2026-00395
Subject
Clarification regarding profile and signature priorities
Request type
Product Question
Submitted
Jul 10, 2026 · 09:30 UTC
Requester
Jordan Hale

2.Original issue as reported

Which signature takes precedence when both a profile-level and pattern-level match are present?

3.Business impact and Support Priority

Support Priority
P4 — Low
Reported impact
Analysts were uncertain which signature to cite in review notes
Reported urgency
Low
Affected users (reported)
Approx. 12 analysts
Frequency (reported)
Not recorded

Support Priority reflects the urgency of a support request. It is not an entity-risk score or a surveillance-risk tier.

4.Product context

Product module
Entity Profile
Environment
Production
Application version
2026.2
Browser / device
Not recorded

5.Investigation and findings

Investigation summary

MNC Support reproduced the described view in the 2026.2 build, compared the rendered signature ordering against the documented precedence rule, and confirmed that pattern-level signatures subsume profile-level signatures for display ordering.

Root cause

Root cause status
Confirmed
Confirmed root cause category
Product Clarification

Confirmed conclusion

No defect. Display ordering follows the documented precedence rule in which pattern-level signatures subsume profile-level signatures.

6.Resolution and outcome

Resolution statement

Confirmed the documented display-ordering precedence for profile-level and pattern-level signatures.

Corrective action taken

None required — behaviour is as designed and documented.

Customer action required

None.

Workaround provided

Not recorded

Resolved by
R. Delacroix · MNC Support
Resolution date
Jul 11, 2026

7.Lifecycle timeline

  1. Jul 10, 2026 · 09:30 UTCRequest status recorded as Submitted · Jordan Hale
  2. Jul 11, 2026 · 11:00 UTCRequest status recorded as Resolved · R. Delacroix
  3. Jul 11, 2026 · 11:00 UTCMNC Support response provided to the customer · R. Delacroix · MNC Support
  4. Jul 12, 2026 · 14:00 UTCRequest status recorded as Closed · Jordan Hale
  5. Jul 12, 2026 · 14:00 UTCCustomer confirmed the resolution · Jordan Hale

8.People and ownership

Requester
Jordan Hale
Client owner
Jordan Hale
Watchers
None
MNC Solutions ownership
MNC support owner
R. Delacroix
MNC participants
R. Delacroix · MNC Support

9.Attachments referenced

  • Signature precedence reference sheet (PDF)Shared with the response on 2026-07-11.

10.Related records

11.Confirmation and closure

Customer confirmation
Confirmed
Confirmed at
Jul 12, 2026 · 14:00 UTC
Confirmed by
Jordan Hale
Request closed
Jul 12, 2026 · 14:00 UTC by Jordan Hale
Package receipt acknowledged
Jul 12, 2026 · 15:02 UTC by Jordan Hale (Customer Admin)

Acknowledging receipt is optional and does not change the request status, Support Priority, resolution confirmation, or the right to reopen the request.

Demonstration prototype — synthetic data only. This Resolution Package is assembled from stored request data and contains no internal notes, internal deliberation or internal-only records.

Receipt acknowledged Jul 12, 2026 · 15:02 UTC by Jordan Hale.

Your secure workspace for MNC support requests, service communications, product updates, and client connectivity. Canonical documentation lives at MNC Solutions Academy.