Skip to main content
Foundational Guidelines move legacy customer Rules into the same management system as Skills, giving teams one governed place to manage the brand standards, compliance requirements, workflow rules, and QA guidance Grady depends on. Functionally, Grady uses the same customer guidance during work tasks after migration — the difference is that the guidance now lives in a versioned, auditable, and easily editable library instead of the legacy Rules surface.
Foundational Guidelines must be enabled for your organization by the Gradial team, and rollout is staged: the guideline library is enabled first so your team can build and validate it, and Grady is switched over to guidelines as its rulebook source only after your legacy rules have been migrated. Contact your Gradial team to plan a migration.

​
Where Guidelines Live

Foundational Guidelines are managed under Skills → Foundational Guidelines. Guidelines are organized into typed folders with sidebar grouping, and rows can be moved across sections with drag-and-drop.

​
Building the Guideline Library

​
Import from a spreadsheet

Bring existing rules in bulk:
  1. Open Skills → Foundational Guidelines
  2. Import your rules from a CSV file
  3. Review and edit the imported rows in the sheet-style editor
  4. Set each guideline’s enablement, scope, agents, and integrations before rolling it into Grady’s rulebook
You can also export the library back to CSV at any point for offline review or bulk editing.

​
Add guidelines manually

Individual guidelines can be added directly in the sheet-style editor — useful for new standards that never existed as legacy rules.

​
Let Grady capture guidelines

With Learning Mode, Grady can create or update guidelines from real work, the same way it proposes Skills — so guidance that surfaces during tasks can be captured into the governed library instead of living only in someone’s head.

​
Governance Controls

Each guideline row carries the controls that determine how it applies: Guidelines keep full version history, and guideline management follows the existing Skills and admin permission model.

​
Migrating from Legacy Rules

The migration is designed to be safe and reversible rather than a one-way cutover:
  1. Build the library first. The guideline library is enabled while Grady continues using your legacy Rules — nothing changes in agent behavior yet.
  2. Import and validate. Migrate your legacy rules (and any relevant captured guidance) into enabled guidelines, and review them in the sheet editor.
  3. Cut over. Once the library is complete, the Gradial team switches Grady’s customer rulebook to source from enabled guidelines. Legacy Rules surfaces are hidden from that point.
  4. Rollback is available. If something isn’t right, the cutover can be reversed while you adjust the library.
Migrate every legacy rule you still rely on into an enabled guideline before the rulebook cutover — after cutover, Grady’s customer rulebook comes from enabled guidelines only.