New backend and data-plane slices should prefer Rust once their API, CLI, or fixture boundary is testable from the outside.
Agent-operable cloud
Efficient backends are part of the product.
LinkRidge Cloud is being bootstrapped on older, financed server hardware. Agents should help the platform get more useful work from each core, gigabyte, and watt instead of hiding waste behind larger machines.
TypeScript and Node stay useful for generated docs, UI surfaces, and changing control-plane rehearsal code.
Agent-written internals need contracts, fixtures, smoke tests, idempotency checks, audit IDs, and resource evidence.
Backend standard
Rust is capacity strategy, not novelty.
Old hardware makes runtime waste visible. LinkRidge Cloud should use agents to make efficient implementation practical: smaller binaries, lower idle memory, faster startup, predictable latency, and fewer layers in hot paths.
- Prefer Rust for CLIs, validators, importers, parsers, scoring engines, crawlers, workers, gateways, and stable API services.
- Keep Node for static generation, UI-heavy work, local fixtures, and control-plane experiments whose resource model is still moving.
- Move broad runtime code only after the API contract is stable enough that the rewrite is an implementation swap.
How agents should integrate
Expose APIs and CLIs before adding chatbot-only flows.
A user's own agent should be able to inspect, plan, and operate LinkRidge Cloud through documented contracts without clicking around the UI.
API contract
OpenAPI is the product contract.
Stable resource IDs, typed problem+json errors, pagination, idempotency keys, audit-event IDs, and explicit blocker states let agents reason about the platform safely.
CLI contract
Every serious service needs verbs.
Baseline verbs are status, health,
doctor, plan, apply,
import, and export, narrowed to the
service's real workflow.
Proof contract
Implementation can be a black box; behavior cannot.
Golden fixtures, smoke tests, resource-budget checks, and DevRail validation are the evidence that agent-written Rust or backend code is safe to run.
Migration order
Move sooner, but move from the edges inward.
-
Lock the
/v1control-plane contract around IDs, errors, idempotency, audit events, and approval states. -
Add the first
linkridge-cloudCLI contract against the existing dev server. - Move one leaf component to Rust and add resource-budget proof.
- Repeat for data-plane services before replacing the whole control-plane runtime.