M7 M7 Script

In development Language and console prototype; not a live production runtime

Remote workflows without host-level access.

M7 Script is an in-development, inline-capable programming language for host-controlled workflows. Its direction combines sandboxable capabilities with explicit instruction limits so a product can accept user-defined behavior without handing scripts general access to the underlying system.

Development model The intended execution boundary

Inline source, explicit authority, bounded work.

The host accepts a small script, exposes only allowed operations, applies execution limits, and returns a controlled result. The production runtime required to enforce that model is still in development.

  1. 01 Accept Receive an inline workflow definition.
  2. 02 Parse Turn source into a controlled language structure.
  3. 03 Limit Apply allowed capabilities and execution limits.
  4. 04 Return Produce a controlled result or bounded failure.
Current status Language and console prototype; production sandbox not yet established

01 / Why M7 Script

Back to top

User-defined workflows should not require host-level access.

Products often need a small programmable surface: an inline rule, an automation step, or a remote workflow. General-purpose runtimes can expose too much authority and make safe termination difficult.

M7 Script's direction

A small language inside a boundary the host controls.

The intended runtime combines inline source, capability-scoped operations, and enforceable execution limits. These are development goals, not current production guarantees.

02 / Use cases

Back to top

Let users define workflows remotely without giving them the system.

M7 Script is intended for product surfaces that need programmable behavior while the host retains control of authority, execution, and failure.

01 Workflow

A user needs to change behavior without a deployment

Send a bounded workflow to the product.

Submit a small script remotely and let the host parse and evaluate it inside the supported language surface.

Product fit
Rules, routing, transformations, and multi-step product workflows.
Required boundary
The production evaluator and sandbox required for this path are still in development.
Open the console
02 Capability

A workflow needs selected product operations

Expose actions without exposing the host.

Give the language named capabilities chosen by the product instead of general filesystem, process, network, or runtime access.

Product fit
Customer-configurable automation inside a product-owned security boundary.
Required boundary
The integrating host must define, validate, observe, and revoke every exposed capability.
Inspect the language prototype
03 Limit

User-defined work must stop predictably

End execution at a known boundary.

Apply explicit instruction limits so a malformed or uncooperative workflow cannot run indefinitely.

Product fit
Remote automation that needs a measurable execution budget and controlled failure path.
Required boundary
Production limits, cancellation, resource policy, and recovery behavior remain development work.
Review the development console