Skip to content

Ways to Use Engineering Runtime

The same engrt binary serves three consumers. Behaviour is identical — Bootstrap → Context → Policy → Auth → Execution → Audit — only the caller changes.

┌─────────────┐   ┌─────────────┐   ┌──────────────────┐
│   Human     │   │   CI/CD     │   │  AI / Runtime    │
│  engineer   │   │  pipeline   │   │     Agent        │
└──────┬──────┘   └──────┬──────┘   └────────┬─────────┘
       │                 │                   │
       └────────────┬────┴───────────────────┘
                    ▼
              engrt binary
                    ▼
           Engineering platforms
Mode Who drives Typical entry Guide
Local (human) You, in a terminal engrt github …, engrt capability execute … Local setup
CI/CD A pipeline job Provisioned runner → engrt capability execute … CI/CD
AI agent Claude / Cursor / any agent under the Runtime Agent contract Agent may only invoke engrt … AI agent

What every mode shares

  1. One binary. Follow Installation. No daemon, no language runtime.
  2. One Runtime Home for contracts and working state. Specs, commands and audit live there. Config/policy, capability definitions, tool context and provider credentials keep their external owners — see Runtime Home.
  3. Two execution surfaces.
  4. Provider operations: engrt github …, engrt files …
  5. Command Engine: engrt command run <binary> …
  6. Capabilities. Markdown workflows that compose the surfaces above — engrt capability validate|execute ….
  7. Governance before work. Policy can deny before auth or execution; every outcome (including denial) is audited.

Pick a path

  1. Install
  2. Quick Start
  3. Deeper local notes: Local setup
  1. Add the verified binary to your runner
  2. Set ENGRT_GITHUB_TOKEN only for GitHub work; pass any org explicitly
  3. Call engrt capability execute … or provider commands
  4. Full contract: CI/CD
  1. Install engrt and bootstrap
  2. Open the engineering-runtime-agent repo (or apply the same hooks/rules)
  3. Ask in natural language — the agent may only call engrt
  4. Full contract: AI agent

Identity on the audit trail

Set ENGRT_CONSUMER for the caller class, plus optional actor/session labels so audit records show which run drove the binary:

Value Use when
human Interactive terminal (default when unset and not CI)
ci Pipelines — samples set this explicitly
ai Runtime Agent sessions
export ENGRT_CONSUMER=ai
export ENGRT_ACTOR_NAME=repo-maintenance-agent
export ENGRT_SESSION_ID=task-123
engrt github user get
engrt audit tail -n 1
Resource Role
Release access Versioned binaries + checksums
engineering-runtime-capabilities Shared / company capability store
engineering-runtime-ci Working CI workflows + setup-runtime action
engineering-runtime-agent Runtime Agent contract + shell hooks
Engineering Runtime site Vision and architecture essays

Operational examples on this site were verified against Runtime 0.14.0. After bootstrap, the version-exact files in Runtime Home win.