Rules

Keep guidance reusable

flowchart LR
    Scattered[Scattered instructions] --> Rule[Rule record]
    Rule --> Consistent[Consistent guidance]
    Rule --> Connected[Entity connections]
    Rule --> Governed[Version-controlled logic]

Teams rarely fail because they lack instructions. They fail because the same guidance is scattered across documents, emails, and meeting notes, so no one can tell whether the latest version has been applied and where.

A rule gives the team one governed place to answer questions such as:

• what is this instruction or piece of logic
• what exactly does the rule say
• which trials, personas, or other records should follow this rule
• has the rule changed since it was last reviewed

That matters because downstream decisions depend on consistent, version-tracked guidance rather than copied fragments.

Connect logic to the work

flowchart LR
    Rule[Rule] --> Trials[Trials]
    Rule --> Personas[Personas]
    Rule --> Media[Media]

A rule becomes useful when it is connected to the right records or workflow surfaces. The value is not the text alone. The value is where that guidance shows up and how consistently it shapes behavior.

Use rules when consistency matters

flowchart LR
    Rule[Rule record] --> Define[Define the instruction]
    Rule --> Connect[Link to records]
    Rule --> Review[Review where it applies]
    Rule --> Govern[Track changes over time]

Rules are a good fit when:

• the same instruction should influence more than one record or workflow
• teams want a governed, reusable source of truth instead of copied guidance
• downstream work should be shaped by connected logic rather than manual reminders
• reviewers need to see the history of rule changes

On the page

The rule page is intentionally minimal — one section for the rule itself plus relationship tabs showing where it applies.

Surface	Purpose	What users do there
Summary	Define the rule content	Maintain title and rich-text instructions
Relationship tabs	Show where the rule matters	Review linked trials, personas, media

classDiagram
    class RulePage {
        +Summary
        +RelationshipTabs
    }

    class Summary {
        +Title
        +Content
    }

    class RelationshipTabs {
        +Trials
        +Personas
        +Media
    }

    RulePage *-- Summary
    RulePage *-- RelationshipTabs

What to capture

mindmap
  root((Strong rules))
    Clear title
    Complete instructions
    Connected records
    Version history

A strong rule is not just a note. It makes clear what the instruction is, what it says, and where it connects.

Good rules usually do two things well:

• they carry a clear title and complete, self-contained rich-text instructions
• they are connected to the entities that should follow the guidance

Both Title and Content are required. Rules exist to be read and applied, so content is never optional.

Summary

mindmap
  root((Summary))
    Title
    Content

This section holds the rule definition itself.

Label	Description	Type
Title	Display name for the rule — should be clear enough to identify the instruction at a glance	Text
Content	Full rule instructions, logic, or guidance in rich-text format	Rich text