/**
 * Resolve the architecture layer from a SysML file path.
 *
 * Uses the Apollo-11 convention: the immediate subdirectory under `sysml/`
 * determines the layer. The `relationships/` directory is special-cased
 * to "crosscutting" since relationships span layers.
 *
 * @example
 * resolveLayerFromPath("sysml/risk/risk-management.sysml")     → "risk"
 * resolveLayerFromPath("sysml/operational/operational.sysml")   → "operational"
 * resolveLayerFromPath("sysml/relationships/relationships.sysml") → "crosscutting"
 * resolveLayerFromPath("sysml/operational/purpose/business.sysml") → "operational"
 */
export declare function resolveLayerFromPath(filePath: string): string;
/**
 * Resolve the namespace path represented by an ontology source file.
 *
 * MEMO keeps namespace and folder paths aligned, so
 * `src/assurance/safety_risk/analysis/fmea.sysml` becomes
 * `["assurance", "safety_risk", "analysis"]`. Older ontology packages that
 * use `sysml/` receive the same treatment. The registry ships this path to
 * clients so they never need a second hardcoded kind taxonomy.
 */
export declare function resolveNamespaceFromPath(filePath: string): string[];
/**
 * For files under a compliance layer, extract the standard subdirectory.
 *
 * Convention: sysml/compliance/<standard>/<file>.sysml → standard name.
 *
 * @example
 * resolveStandardFromPath("sysml/compliance/iso-14971/rmf.sysml") → "iso-14971"
 * resolveStandardFromPath("sysml/safety/hazard.sysml")            → undefined
 */
export declare function resolveStandardFromPath(filePath: string): string | undefined;
//# sourceMappingURL=layer-resolver.d.ts.map