import type React from 'react';
import type { CanvasGraph } from '../graph-projection.js';
import type { YarramateOperation } from '../operations.js';
import type { VisualPatternOption } from '../adapters/visual/protocol-contract.js';
/**
 * Making a pattern INSTANCE, which is a different act from making a subject
 * (#473 phase 4, ADR 0146).
 *
 * Dropping "System API" is one gesture that mints an application, its
 * interface, its service and the wires between them. Assembling the same thing
 * from the layer bands is five drops and three connections, and every one of
 * them is a chance to bind the wrong slot.
 *
 * The form asks for the slots the PATTERN declares, in the order it declared
 * them, and stages ONE changeset: the drafted children first, then the instance
 * whose `parts` names them. Item 4.1 proved that batch lands, in either order.
 */
export declare const InstanceDraftPanel: ({ graph, pattern, documents, defaultDocument, reservedIds, onStage, onCancel, }: {
    readonly graph: CanvasGraph;
    readonly pattern: VisualPatternOption;
    readonly documents: readonly string[];
    readonly defaultDocument: string;
    /**
     * Ids the pending changeset already claims, on the same terms the subject
     * form takes them: the graph knows only what has landed (#315).
     */
    readonly reservedIds: readonly string[];
    readonly onStage: (operation: YarramateOperation) => void;
    readonly onCancel: () => void;
}) => React.ReactElement;