Resilience and Repairs (Overview)
There is no separate “Repair” mode. Resilience is built into CODE. Each turn first plans what the request is allowed to touch, then generates only within that planned scope. Native validation runs before preview or apply actions are exposed.
Planned scope and bounded generation
Section titled “Planned scope and bounded generation”- Planning records the target script or selection, allowed operation shape, known metadata, and relevant constraints.
- Generation must stay inside that plan. Recovery can fix form and consistency for the same task; it cannot add new target scripts, broader edits, or unrelated FileMaker work.
If the model omitted something because Genie did not have enough context, clarify the prompt, refresh context, or resolve preflight questions and send again. Genie will not silently expand a draft into out-of-scope work.
Deterministic validation (before apply)
Section titled “Deterministic validation (before apply)”Built-in validation checks the generated FileMaker script output and apply plan before the user can apply it. It can reject target drift, malformed edit spans, missing script identity, unsupported output, and unsafe combinations.
When no safe apply path exists, Apply stays off even if a draft can be shown. Use Preview and Copy to inspect or recover reviewable text manually.
Warnings and codes
Section titled “Warnings and codes”When a draft is reviewable but has a support-worthy limitation, Genie shows a chat warning. Some warnings include a numeric error code and may still expose Preview, Copy, or Apply depending on what validation could prove.
Use Error Codes and Recovery to map codes to likely causes and next steps.
What you should do as the developer
Section titled “What you should do as the developer”- Read warnings and assumptions in the thread before applying.
- Compare generated output to intent in Preview, especially after warnings.
- Keep live selection and metadata current when the task depends on real script or schema identity.
- Treat unclear business rules or missing requirements as requirements problems—not something an automated pass can safely invent.