import type { LoweringDescriptor, PackageDescriptor, ProviderContext, Transport, ValidatorDescriptor } from '../registry.js';
/** The one place this string is written. Everything else reads it from here. */
export declare const INTERNAL_PROVIDER_ID = "internal";
/** The binary this adapter speaks to when the transport is `process`. */
export declare const SYSMLC_COMMAND = "memo-sysmlc";
export interface InternalToolConfig {
    /** `in-process` (default) or `process`. */
    transport?: Transport;
    /** Path to a `memo-sysmlc` binary. Defaults to the bundled one, then PATH. */
    executable?: string;
}
export declare function resolveSysmlcCommand(context: ProviderContext): string;
/**
 * Validator role — "is this valid SysML?" answered by MEMO's Langium grammar.
 *
 * The grammar is a MEMO subset, so this answers a narrower question than
 * `syside` does. That is exactly why the roles are separate and why a failure
 * here, when another validator accepted the file, is an ingest problem rather
 * than a SysML error.
 */
export declare const internalValidatorDescriptor: ValidatorDescriptor;
/**
 * Lowering role — "what can MEMO ingest from this revision?"
 *
 * Its diagnostics are `memo-ingest` by construction: this step is MEMO reading
 * the source, so anything it cannot read is MEMO's limitation to report, not a
 * verdict on the source. When MEMO is also the validator the caller collapses
 * the duplicate, so one failure is still reported once.
 */
export declare const internalLoweringDescriptor: LoweringDescriptor;
/** Package role — the built-in gzip-tar MEMO bundle writer. */
export declare const internalPackageDescriptor: PackageDescriptor;
//# sourceMappingURL=internal.d.ts.map