import type { ReferenceCatalog } from "@intentius/chant/lexicon";
/**
 * Fly reference catalog (#804) — how observed Fly resources reference each other,
 * so `chant graph --live` reconstructs the topology and draws the App as a
 * boundary box (the reference resolver, chant#778; containment, chant#779).
 *
 * Fly's relationships are app-centric and simple. `describeResources`
 * (./describe-resources.ts) already returns the rich per-resource shape — each
 * app-scoped resource carries its owning `app`, and a machine carries its full
 * `config` (with `mounts`) — so, unlike AWS (chant#784), Fly needs **no**
 * `enrichLiveAttrs`: the references are already in the observed attributes.
 *
 * Keyed to the `describeResources` attribute shape:
 *   - App        → `{ app }`           (physicalId = app name)
 *   - Machine    → `{ app, config }`   (config.mounts[].volume references a Volume)
 *   - Volume     → `{ app, volumeName }`
 *   - IPAddress  → `{ app, ... }`
 *   - Certificate→ `{ app, ... }`
 */
export declare const flyReferenceCatalog: ReferenceCatalog;
//# sourceMappingURL=reference-catalog.d.ts.map