ProgInsight · Security

Issue Identification
System.

Every issue reported across the ProgInsight ecosystem is assigned a unique, structured ID — fully self-contained and human-readable without a lookup table.

Found something that doesn't look right?
Report a security issue directly to our team. Use the subject line Security and include the relevant ID if you have one.
[email protected]

ID Structure

Every issue ID is self-contained — anyone reading it can determine the product, category, severity, date, time, and version without a lookup table.

[PRODUCT]-[CATEGORY]-[SEVERITY][YYYYMMDD][HHMM]V[VERSION]
4ASM-SEC-H202605181432V1000
4ASMProduct
SECCategory
HSeverity
20260518Date
1432Time
V1000Version
4allStream — Security Vulnerability — High Severity — 2026 May 18, 14:32 — Version 1.0.0

Product Families

ProgInsight organises its products into four families, each with its own code derivation rule.

Prefix: 4A   Rule: 4A + first letter + last letter of product name

CodeProduct
4ASM4allStream
4ACR4allConverter
4ADR4allDownloader
4AMR4allMediaPlayer
4ASE4allShare
4ASC4allSync
4ACT4allCast
4AWE4allWorkspace

Prefix: I   Rule: I + first letter + last letter of the distinguishing word (drop "Intelligent")

CodeProductDerived from
IWRIntelligent WriterWriter
IRRIntelligent ResearcherResearcher
IPRIntelligent PlannerPlanner
ILRIntelligent LearnerLearner

Prefix: W   Rule: W + first letter + last letter of the app's own name

CodeApp
WDADatalimora

Fixed codes assigned at registration — no derivation rule applies.

CodeProduct
YTEYT-DLite
CodeMeaning
SECSecurity vulnerability
BUGFunctional bug
PERFPerformance regression
PRIVPrivacy issue
CodeLevel
CCritical
HHigh
MMedium
LLow

Format: YYYYMMDD followed immediately by HHMM in 24-hour time. No separators. The timestamp is the moment the issue is formally logged, not when it was discovered.

2026 May 18, 14:32 → 202605181432

The application version where the issue was discovered. Always V + a leading zero + each version segment as a single digit. No version segment ever exceeds 9.

V + 0 + [MAJOR(1)] + [MINOR(1)] + [PATCH(1)]
App VersionEncoded
1.0.0V0100
2.4.5V0245
3.0.1V0301
1.2.3V0123
ID Product Category Severity Date Time Version
4ASM-SEC-H202605181432V01004allStreamSecurityHigh2026-05-1814:321.0.0
4ADR-BUG-M202606010900V01014allDownloaderBugMedium2026-06-0109:001.0.1
4AWE-PRIV-C202607151200V02004allWorkspacePrivacyCritical2026-07-1512:002.0.0
4ACT-PERF-L202608302359V02454allCastPerformanceLow2026-08-3023:592.4.5
IWR-BUG-H202606120830V0100Intelligent WriterBugHigh2026-06-1208:301.0.0
IRR-SEC-C202607011100V0200Intelligent ResearcherSecurityCritical2026-07-0111:002.0.0
IPR-PERF-M202607181430V0110Intelligent PlannerPerformanceMedium2026-07-1814:301.1.0
ILR-PRIV-L202608051600V0101Intelligent LearnerPrivacyLow2026-08-0516:001.0.1
WDA-PERF-M202607041500V0110DatalimoraPerformanceMedium2026-07-0415:001.1.0
YTE-BUG-L202606200745V0101YT-DLiteBugLow2026-06-2007:451.0.1
  • IDs are assigned at the moment of formal logging, not discovery
  • Timestamps use 24-hour format with no separators
  • Version is always three numeric segments stripped of dots, prefixed with a leading zero
  • 4all Ecosystem: code = 4A + first + last letter of product name
  • Intelligent Suite: code = I + first + last letter of the distinguishing product word (drop "Intelligent")
  • Web Apps: code = W + first + last letter of the specific app name
  • Standalone Products: fixed code assigned at registration — no derivation rule
  • Category and severity codes are always uppercase
  • Segments are separated by a single hyphen, except between severity and date
  • Including minutes in the timestamp makes same-ID collisions practically impossible in normal reporting