Cross-check product behavior against market rules

Why use this

1. A product team comparing game mechanics with market requirements may find that similar features are described differently across sources. A broad category match can hide exceptions, jurisdiction scope or rules that changed after the product brief was written.

2. This job could prepare a sourced comparison that makes those uncertainties visible for qualified review. Keeping product facts separate from legal interpretation helps the team identify questions to resolve before changing or releasing a feature.

Why an agent / simpler alternative

Useful judgment

Map concrete mechanics to relevant rule questions, distinguish source statements from interpretation and flag scope mismatches.

Simpler alternative

Ask qualified counsel a narrow question when the mechanic and market are already clearly defined.

Unsuitable when

The output would authorize market entry, certify compliance or suggest evading applicable requirements.

Proposed inputs

1. Name

   Product behavior brief

   Owner

   Authorized product owner

   Minimum scope

   Actual mechanics, user flows and target markets

   Quality check

   Avoid vague feature labels and identify optional behavior

2. Name

   Approved rule evidence

   Owner

   Qualified reviewer

   Minimum scope

   Relevant source excerpts, dates and jurisdiction scope

   Quality check

   Record authority and unresolved interpretation

Access and setup — proposed or unknown

Proposed minimum

1. Use fictional mechanics and placeholder rule excerpts; no regulated-source queries, product changes or legal advice.

Compatibility unknowns

1. Current knowledge-source coverage, rule freshness, connector access and runtime compatibility are unknown.

External actions requiring approval

1. Disclosing confidential product details, changing mechanics, publishing legal claims or launching requires authorization and qualified review.

Expected deliverable and review checks

Proposed artifact

Behavior-to-rule comparison with evidence pointers, possible applicability and reviewer questions.

Critical checks

1. Match actual behavior rather than labels; preserve dates/exceptions; distinguish unknown from permitted; avoid compliance conclusions.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   A rule concerns a different market

   Why it matters

   A superficially similar requirement is misapplied

   Proposed response

   Show jurisdiction scope and hold interpretation.

2. Signal

   An optional mechanic is omitted from the brief

   Why it matters

   The assessment misses behavior users can encounter

   Proposed response

   Request the complete flow before comparison.

Effort and cost — unknown

Setup work

1. Define behavior scope and authoritative review ownership.

Ongoing review

1. Qualified specialists resolve applicability and approve consequential decisions.

Unknowns

1. Rule completeness, legal interpretation, product evidence and research costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent a game flow with an optional mechanic and two placeholder rules from different markets; prepare an applicability-question table.

Acceptance checks

1. Flag scope gaps; preserve uncertainty; recommend no launch or rule-avoidance action.

Stop conditions

1. Stop if current authority or the full product behavior is unavailable.

Limits

1. A sourced comparison cannot establish legal compliance, permission to operate or suitability for a particular jurisdiction.