Turn policy language into exact, reusable authorization.
PolicyFuse is a non-custodial Intelligent Contract that binds an immutable policy, an exact action, a consumer, and validator-agreed rule states into one deterministic consequence: ALLOW, DENY, or REPAIR_REQUIRED.
0xF5066aE61456b1ADEC4871Da1650F64F1aE5C43FVerification at a glance
The technical proof is visible before a developer reads a line of integration code.
36/36
Direct Mode regression tests
5
Validators in supported runtime
8
Deployment + verification transactions
0
Additional authorized verification writes
Your developer path
Learn the primitive like a small protocol, not a black-box contract.
Understand the model
Policies, intents, rule vectors, decisions, and authorization currentness.
Integrate safely
Submit an exact intent, wait for finality, then verify exact consumer/action bindings.
Use the API
Seven writes and eight views, with no hidden custody or downstream execution surface.
Three outcomes. One exact derivation.
The model classifies rules. Contract code derives the consequence.
ALLOW
Every consequential rule is PASS.
- Authorization is created.
- Bound to consumer + action digest.
- Still requires currentness checks.
DENY
At least one rule is FAIL.
- Failure code: RULE_FAILED.
- No authorization is created.
- History remains queryable.
REPAIR_REQUIRED
No failures, but at least one rule is UNKNOWN.
- Failure code: RULE_UNKNOWN.
- Clarification can be revised.
- Action core cannot be substituted.
Preferred integration check
Never trust historical authorization existence by itself.
const current = await client.readContract({
address: POLICYFUSE,
functionName: 'is_authorization_current_for',
args: [authorizationId, consumer, actionCoreDigest],
transactionHashVariant: TransactionHashVariant.LATEST_FINAL,
});
if (!current) throw new Error('Authorization is not current');Currentness is recomputed from durable state.
Policy supersession, revocation, intent state, validity time, exact consumer, exact action digest, rule-vector binding, and stored identity checks all participate in the currentness boundary.
Read the security model →