autonomy

{
  "name": "autonomy",
  "version": "0.29.0",
  "description": "Contracts for governed autonomous agent operation: role topology, binding seam, telemetry, return accounting, trigger dispatch, a per-work-class guardrail matrix, a standing-routine catalog, and a runner charter. A guided setup skill writes an org's binding, wires OTLP telemetry (file default), human-attested return capture, and signal adapters behind one governed dispatch entrypoint, binds the guardrail matrix to isolation substrates after a live probe, and schedules routines.",
  "author": {
    "name": "Melodic Software",
    "email": "[email protected]"
  },
  "license": "MIT",
  "keywords": [
    "adoption",
    "autonomy",
    "binding",
    "governance",
    "guided-setup",
    "otlp",
    "return-accounting",
    "routines",
    "runner",
    "telemetry",
    "topology"
  ],
  "userConfig": {
    "lane_stop_gate_enabled": {
      "type": "boolean",
      "title": "Lane-stop gate",
      "description": "Opts an autonomous lane into the deterministic Stop-hook completion gate. Off by default, because a Stop-blocking hook must never engage for an interactive session. Honored from user or managed settings only; the harness-ops lane launcher arms per-session lanes instead.",
      "default": false
    },
    "lane_stop_gate_sentinel": {
      "type": "string",
      "title": "Lane-stop completion token",
      "description": "The exact token the agent emits in its final message to declare the lane's goal met and authorize a stop; default LANE-STOP-OK. Matched only when alone on its own line. Honored from user or managed settings or the launcher's arm record, never the bare environment.",
      "default": "LANE-STOP-OK"
    },
    "lane_stop_gate_marker": {
      "type": "string",
      "title": "Lane-stop completion marker file",
      "description": "Path to a completion-marker file whose existence also authorizes a stop (absolute, or relative to the session cwd). Empty, the default, disable