PROGRAMMER FIELD TEST · EVIDENCE FIRST

Open it. Probe it. Tell us what breaks.

This is the shareable edge of MasiDyn: a local-first AI control plane with supervised BEAM services, native workers, and optional hosted provider routes. The status below comes from the live API; it does not turn green from sample data.

Checking the live runtime… No result has been assumed.

THREE ENTRY POINTS

Use the surface that matches the test.

01 · HOSTED

Developer account

Open the hosted developer account and access surface. Authentication and runtime failures stay visible.

Open account
02 · DESK

Developer desk

Inspect the browser-facing MasiDyn developer workspace. Desktop-only controls may remain unavailable in a browser build.

Open developer desk
03 · DOWNLOAD

Build access

The desktop IDE source is private and no signed installer is published yet. No download is offered until a signed artifact exists.

Installer not published

WHAT IS RUNNING

One public front door, separate trust boundaries.

  • masidyn.comPublic explanation and field-test entry.
  • account.masidyn.devDeveloper account and access workflow.
  • api.masidyn.devRate-limited edge in front of the private runtime tunnel.

TEST CONTRACT

Failure is data.

  • No fabricated healthAn unreachable runtime stays unavailable.
  • No browser-shipped provider keysProvider credentials remain behind the server boundary.
  • No fake downloadPrivate source and unsigned artifacts are labeled precisely.

Field-test status proves only the endpoint exercised. It does not claim every model, sensor, provider, or bare-metal target is ready.