FieldWeaverSIMULATION STUDIO
Local simulation

SECURITY ARCHITECTURE: BOUNDARY ASSURANCE

Keep the control
surface local.

The current API is built for local development and research simulation. Review these boundaries before exposing an instance to another network.

BOUNDARY ASSURANCE V1.0LOCAL DEVELOPMENTUPDATED NOV 4, 2026
POSTURE SCORECARD

Enforced Defense-in-Depth Boundaries

INTERFACE BINDINGBOUND
127.0.0.1 (Loopback)

FastAPI and Next.js bind to local loopback; no external network ports exposed by default.

SECRET QUARANTINESERVER SIDE
Backend Environment

Use a server environment key or enter a provider key for the current page session.

PROMPT BOUNDARYVALIDATED
Strict Schemas

Mission and agent responses are validated; model output is not executed as code.

SAFETY VALIDATIONSIMULATOR ONLY
Independent Checks

The simulator checks separation, clearance, boundaries, speed, and finite state.

01: SERVICE BOUNDARY

Do not expose the development API as-is.

The documented launch command binds the backend and frontend to loopback. The FastAPI service has no user authentication, authorization, or rate limiting. Its CORS allowlist helps browsers enforce origin rules, but does not prevent direct HTTP clients from reaching a network-accessible API.

For any shared or hosted deployment, add an authenticated reverse proxy, TLS, network restrictions, request limits, and a reviewed CORS configuration. Keep the API unreachable from untrusted networks until those controls are in place.

02: SECRET HYGIENE

Handle provider credentials carefully.

  • Store the key in BASETEN_API_KEY in the backend environment or local root .env.
  • The root .env is ignored by Git. Keep the placeholder-only .env.example free of real credentials.
  • Keys entered in the app are held in page memory and sent to the backend for live requests. Close or clear the page to remove them; use HTTPS except on the local computer.
  • Never use NEXT_PUBLIC_* for provider secrets or put real credentials in source, prompts, logs, screenshots, or test fixtures.
  • Use a restricted local account for the key, rotate it if it is exposed, and review provider account access.

03: MODEL AND MOTION BOUNDARIES

Generated output is treated as untrusted input.

Every mission and agent response is parsed and validated server-side. The model cannot provide executable code, arbitrary routes, actuator values, or safety-limit changes. Deterministic motion proposals pass through an independent validator, which can stop or reject an unsafe transition.

These protections apply to the simulator implementation only. They are not a certification or guarantee for physical robots, real sensors, actuators, or changed dynamics.

04: REPORT A VULNERABILITY

Share details privately.

Please do not include API keys, private mission data, or exploit details in a public issue. Use GitHub's private vulnerability reporting flow for the repository if it is enabled. If it is unavailable, contact the repository maintainers privately before publishing a report. No response-time commitment is currently stated.

Open private vulnerability report

05: DEPENDENCIES AND OPERATIONS

Keep the local stack current.

Install from the committed Python and npm lock/configuration files. Review dependency updates before deployment. Protect API logs and generated evaluation reports because they may contain request context or trajectory data. The latest run is stored in process memory and is cleared when the API process restarts.

Privacy policy Known limits

Security guidance reviewed November 4, 2026. Reassess before any non-local deployment.