Based on Foresight technology

FCR gates execution against the current state of its dependencies.

Foresight plans the work. FCR checks whether the planned action can be released to a connector when execution is requested.

Try the gate API View API status

planned action publish.customer.update

FCR HOLD fail closed on unresolved support

connector not released

Demo state: one critical dependency is stale, so the connector stays closed.

Product boundary

Foresight plans. FCR executes the gate.

FCR is a separate product developed alongside the patent work and based on the Foresight protocol. It receives a candidate action and dependency state, evaluates the current closure, and returns a gate decision.

This deployed preview exposes the API shape and deterministic gate behavior. A production connector deployment must also bind credentials and current-state reads inside the execution path.

Live API

Send a candidate action to FCR.

POST /api/fcr/gate

hold waiting

{}

Action specific

The gate evaluates the dependencies for the action being requested, not a general permission alone.

Current state

Stale, missing, contradicted, or expired support causes a hold in the preview API.

Inspectable record

The response includes the action, policy, dependency summary, decision, and audit note.

Runtime status

API endpoints

Health: /api/health
Status: /api/fcr/status
Gate: POST /api/fcr/gate