Design process rules

Identifies actionable design-process rules and constraints in Australian contexts: DR-numbered design rules carrying shall/must/prohibited/limit language. General design-guidance, engineering-standard, and intellectual-property topic references remain discovery-level context and do not enforce.

Type

regex

Engine

boost_regex

Confidence

medium

Confidence justification

category-aware structural regex with anchor and context constraints replaces phrase-only detection.

Detection quality

Topic false positive

Jurisdictions

global

Regulations

AML/CTF Act (Cth), HRIPA (Cth), IPA 2009 (Qld), My Health Records Act 2012 (Cth), NDB Scheme (Cth), Privacy Act 1988 (Cth), TIA Act 1979 (Cth), GDPR

Frameworks

ISO 27001, ISO 27701

Data categories

pii

Scope

wide

Risk rating

5

Platform compatibility

Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:design\s+process\s+rules|design\s+rules|design\s+guidelines|design\s+methodology|proprietary\s+design|design\s+specification|engineering\s+standard|intellectual\s+property|trade\s+secret|design\s+constraint)\b

Corroborative evidence keywords

design process rules, design, process, rules, intellectual, property, trade, secrets

Proximity: 300 characters

Should match

• design process rules — Primary topic phrase match
• design rules — Case-insensitive topic phrase match
• design guidelines — Alternative topic phrase match
• design methodology — Additional topic phrase match
• DR-184: connector pitch must be >= 2.2 mm; copper and alloy X must not be combined unless coating Z is used. — Numbered rule with measurable and conditional design constraints (enforcing branch)

Should not match

• unrelated generic text without domain phrases — No relevant topic phrases present
• placeholder value 12345 — Random text should not match topic-specific regex
• algorithm schematic — Generic word pair from old broad template should not match
• The public engineering standard offers design guidelines for ramps. — Public guidance topic must not reach the enforcing tiers
• RULE-77: applicants must lodge form 12. — Non-design numbered rule must not enforce (DR prefix required)
• Training sample RULE-001: width must be 10 mm. — Training/sample rule content must not enforce
• The event design follows a standard process for invitations. — Event-planning prose is outside scope

Known false positives

• Common words and phrases related to design process rules appearing in policy documents, training materials, HR templates, or compliance guidelines without actual personal data. Mitigation: Require corroborative evidence keywords within the proximity window to confirm sensitive data context rather than general discussion.
• In Australian English, similar terminology used in formal or administrative contexts (education, professional documentation) that does not constitute sensitive data collection. Mitigation: Layer with additional contextual signals such as structured identifiers, form fields, or database column headers to distinguish sensitive records from general references.
• High-frequency pattern matches in large document corpora due to broad regex anchors. Expected match rate is significantly higher than specific identifier patterns. Mitigation: Tune confidence thresholds for bulk scanning. Consider using this pattern primarily as a pre-filter with secondary validation.

References

• https://www.safeworkaustralia.gov.au/doc/model-code-practice-managing-risks-plant-workplace
• https://www.productsafety.gov.au/product-safety-laws