Catalog PyPI
PACKAGE EXPLORERView in registry

abe-flow

PyPI

Send Abe escalations to Flow's judgment service (resolve.flowinfo.co). Only ESCALATE results are sent.

Versions collected1
Direct dependencies3From release 0.1.4
Last observed20 Oct, 17:19 UTC

README

Version 0.1.4 documentation

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)
GateFlow called?Result
ACTnoACT
BLOCKno (a resolver can never loosen a BLOCK)BLOCK
ESCALATE (human approval / user confirmation / evaluation failure)noESCALATE
ESCALATE (anything else)yesFlow 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.

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 1

Collected releases
VersionPublishedDirect dependenciesOpen version
0.1.413 Oct 20263

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
flowinfosystems-index/abe

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 20 Oct, 17:19 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:b0d8eade04c2d90b8b6937504129e226d0b6d64b58a4931bf28084137f540123