abe-flow
Send only the actions Abe escalates to Flow's judgment service, and get back a decision, a reason and a falsifiable record.
pip install abe-ai abe-flow
export FLOW_API_KEY=fjp_live_... # https://fjp.flowinfo.co
import os
from abe import Abe
from abe_flow import FlowResolver
abe = Abe("abe-policy.yaml", resolver=FlowResolver(api_key=os.environ["FLOW_API_KEY"]))
r = abe.check(action={"type": "purchase", "amount": 12500}, context={"agent_id": "procurement-agent"},
evidence={"vendor_approved": True})
r.gate_decision # "ESCALATE" (the Gate's own call, kept in records[0])
r.decision # "ACT" / "BLOCK" / "ESCALATE" after Flow
r.records # (gate record, linked Flow RESOLUTION record with Flow's own JGR inside)
| Gate | Flow called? | Result |
|---|---|---|
| ACT | no | ACT |
| BLOCK | no (a resolver can never loosen a BLOCK) | BLOCK |
| ESCALATE (human approval / user confirmation / evaluation failure) | no | ESCALATE |
| ESCALATE (anything else) | yes | Flow REACH → ACT (high/medium confidence), SKIP → BLOCK, WAIT / RESEARCH_FIRST / ESCALATE → ESCALATE |
Flow unreachable, out of credits (402), rate-limited (429), slow (timeout, default 10 s), or degraded output → the
result stays ESCALATE and a linked RESOLUTION record says why. Card, account, routing, IBAN, SSN, password,
token and key fields are redacted before anything leaves your process (redact_keys= to extend).
Report how a Flow judgment turned out (free; improves Flow's calibration):
FlowResolver().report_outcome(r.resolution["resolver"]["reference"], "CORRECT") # or WRONG / PARTIAL
Options: base_url (default https://resolve.flowinfo.co, env FLOW_RESOLVER_URL), timeout,
accept_act_confidence (default ("high", "medium")), redact_keys, include_context, include_evidence.
Apache-2.0. The judgment itself runs on Flow's service; this package is only the client.
Metadata
Release files for abe-flow 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| abe_flow-0.1.2.tar.gz | 13.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| abe_flow-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.0 kB
Release files / abe_flow-0.1.2.tar.gz
| Download URL | abe_flow-0.1.2.tar.gz |
|---|---|
| Size | 13.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bbe71fac15ce0e795088364ba6d4d50e17412dd30b45ada8d65d3b3c7a41e044
|
|
BLAKE2b-256 checksum How to use checksums |
7ed5c649f32d4f5ff2fe862296453ddce23fca266c2782ac2e5bf41974510883
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency logRelease files / abe_flow-0.1.2-py3-none-any.whl
| Download URL | abe_flow-0.1.2-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7ad9554c4150fdc1822bdc206c3dbd25f50b971b9aa4556c161bc25891b54ec1
|
|
BLAKE2b-256 checksum How to use checksums |
f11b583b421b339d4f8ba467e4a17842775432f64d36eaab3adaecf26a9df8ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency log