Remote
Status: unsupported for local-provider remediation builds
Novice Summary
Use this page when you mean remote nodes or remote routing. Remote is not local provider support and should not be used as a fallback to make local provider failures look successful.
Surface
Remote AxiOwl nodes and remote provider routing.
Plain English version: remote is a different product boundary. It is not a fallback for local provider failures.
Delivery Method
Current local provider builds intentionally treat remote delivery as out of scope. Remote should not be used as a fallback to hide local provider failures.
Installer Action
Remote install options may exist, but they should be unchecked by default and only used when explicitly selected.
Requirements
| Requirement | Needed |
|---|---|
| Patch | No local provider patch. |
| Extension | No local provider extension. |
| MCP | Remote node contract required before support. |
| Config | Remote node config only when explicitly selected. |
Test Status
Not part of local provider support.
Known Risks
- Remote fallback can mask local install/delivery failures.
- Remote support needs its own explicit contract and validation.
Architecture Rationale
Remote should remain separate because it changes the trust boundary, delivery boundary, and failure model. Keeping it out of local-provider remediation makes local bugs easier to diagnose.