Skip to content

Reference

The precise, load-bearing records the rest of these docs point back to.

  • REST API

    POST /v1/decide, the holds API, health, auth, and errors — every request and response captured live against the engine.

  • Action Envelope

    The universal shape every adapter produces: verb, three risk axes, magnitude, session, and approval.

  • Configuration

    Every environment variable — the engine server, policy, audit, holds, freeze, SIEM, and the adapter → core client trio.

  • Changelog

    The versioned history of reeflex-core and the adapters, and how releases are cut.

Recorded decisions & process

  • ADR 0001: deployment model — engine-as-service, the open-core boundary, and the two delivery variants (on-prem now, hosted on the roadmap).
  • ADR 0002: no LLM in the decision path — why /v1/decide contains zero LLM calls and zero free-text input, and where an LLM may legitimately sit (advisory only, outside the decision).
  • Releasing — the tagged-release flow that publishes to GitHub Releases, PyPI, npm, and GHCR from one commit.
  • Gate policy — which gate.py components block a merge versus are report-only, and the dated, reasoned register behind every allowed --allow-skips entry.