Appearance
Operations: Foundry Local
Scope
This is the operations page for Foundry Local, one of the three targets in ADR-0011. Compare all three targets on the Deployment targets hub.
This target has not been built yet
Nothing on this target has been deployed from this repository, and no automation exists for it yet. Everything below is drawn from accepted decisions and first-party research. Treat it as a design, not an as-built record.
What is decided today
- Re-running the install must exit zero having changed nothing, reporting
already-present,changed, orfailedper stage. - Run-command output is truncated to the last 4 KB, which bounds what a remote operator can see.
- Any observability must be metadata-only and opt-in. Prompts and content are never captured.
- The product emits no metric of any kind. No request count, no tokens, no latency, no error rate.
Microsoft.HybridComputehas no platform metrics either, so even host CPU and memory require the Azure Monitor Agent, a data collection rule, and per-GB ingestion. The entire model-usage row of the observability design is empty on this target, and ADR-0016 cannot be met here (SPIKE-27 Q9). - Arc run command cannot detect state, only run an action. Machine configuration is the drift mechanism ADR-0013 is missing (SPIKE-29).
- No documented update path exists for the MSIX install mechanism, and models have no version pinning: the CLI's "model ID" is a hardware variant, not a version.
The research and decisions behind this page
These were open when this page was first written. They are now written and linked below. Where a finding contradicted an earlier claim on this page, the page has been corrected and says so inline.