Member Junction
    Preparing search index...

    High-level intent — the Designer LLM fills this from the user's natural-language request and any prior conversation context. The Builder uses it (together with the existing-override state) to decide:

    • Create vs Modify
    • VersionBumpKind to pass to Modify
    interface FormBuilderIntent {
        EntityName: string;
        Operation: "create" | "modify" | "auto";
        UserPromptSummary: string;
        VersionBumpKind?: "auto" | "in-place" | "patch" | "minor" | "major";
    }
    Index

    Properties

    EntityName: string

    Fully-qualified entity name the form binds to, e.g. "MJ: Applications".

    Operation: "create" | "modify" | "auto"

    Whether the result should be a brand-new override (Create) or an update to an existing one (Modify). 'auto' lets the Builder decide based on ExistingOverride presence.

    UserPromptSummary: string

    One-line restatement of what the user asked for. Useful for log + Notes.

    VersionBumpKind?: "auto" | "in-place" | "patch" | "minor" | "major"

    How to bump the version when calling Modify. 'auto' lets the Builder pick based on source status: Pending→in-place, Active→minor, Inactive→patch. Used only by Modify (not Create).