Project Rules (Project Memory)
Project Rules is where you manage per-file behavior in Genie.
What this surface does
Section titled “What this surface does”Project Rules helps Genie stay attached to the correct FileMaker file and reuse per-file guidance without turning every conversation into a blank slate.
It stores user-facing project state such as:
- detected file identity
- display name
- file lock state
- project-specific rules
It is separate from conversation history.
Where it appears
Section titled “Where it appears”- Header chip: shows the active project state
- Project button: opens the Project Rules modal
Header chip states
Section titled “Header chip states”- No Project / No File: Genie has not attached to a stable FileMaker file yet.
- Auto: Genie is following the active file automatically.
- Locked: Genie is pinned to the current file and will not switch automatically.
Opening the modal
Section titled “Opening the modal”Click the project chip or the project button to open the Project Rules modal.
Visible fields and controls
Section titled “Visible fields and controls”Active project name and status line
Section titled “Active project name and status line”The modal header area shows:
- the active project name
- a status line explaining the current state
- a state chip such as
No File,Auto, or the current lock state
Detected File
Section titled “Detected File”Shows the FileMaker file Genie currently sees.
Use this to verify that Genie is attached to the file you expect before sending high-impact requests.
Identity
Section titled “Identity”Shows the file identity summary Genie is using for this file.
This is informative only. You do not edit these identifiers yourself.
Save Name
Section titled “Save Name”Use Save Name to assign a clearer display label inside Genie.
This changes only the Genie label. It does not rename the FileMaker file.
Advanced: Lock to Current File
Section titled “Advanced: Lock to Current File”The advanced section contains the file lock control.
- Lock to Current File keeps Genie attached to the current file.
- Unlock File Lock returns Genie to automatic switching.
Leave Genie unlocked unless you have a reason to prevent switching.
Instructions
Section titled “Instructions”Instructions are the rules that shape Genie for this specific file.
They influence ASK, CODE, QUERY, and DATA behavior for this file only.
You can:
- add a rule
- enable or disable a rule
- remove a rule
Locked vs automatic behavior
Section titled “Locked vs automatic behavior”Automatic
Section titled “Automatic”In normal use, Genie follows the active FileMaker file.
When the active file changes, Genie can switch project context automatically.
Locked
Section titled “Locked”When the file is locked, Genie stays attached to that file even if FileMaker detects another file in front.
If the detected file and locked file no longer match, the modal shows a warning so you can decide whether to stay locked or unlock the file lock.
Rule guidance
Section titled “Rule guidance”Good rules describe conventions or preferences that should stay inside the requested scope.
Good examples:
Prefer delta edits over full rewrites when an existing script is already selected.Keep comments short and operational.Preserve our existing naming style for variables and script steps.
Poor rules try to widen scope automatically.
Avoid rules such as:
Always edit every related script.Always apply automatically.Always create missing schema.
Project Rules guide Genie, but they do not widen what Genie is allowed to change.