INTELLIGENCE IS NOT AUTHORITY

AI can propose.
Authority comes
from you.

A capable model still needs a boundary. Sekos keeps permission outside the model and checks it before a protected action can begin.

Externally issued permission. Inspectable decisions.

THE POINT OF CONSEQUENCEFIG. 01
01
MODEL

“Issue a refund.”

A proposal is a request for permission.

UNTRUSTED
EXTERNAL AUTHORITY

Identity · operation · target · limits

02
SCHEMEN GATE

Does this exact request
carry valid authority?

03
RESOURCE

Only an admitted action begins.

The decision and observed result can be inspected.

PERMISSION AT THE BOUNDARYActions / resources / credentials / computationRead the principle
01 / THE PRINCIPLEEXTERNALLY DEFINED. EXPLICITLY CHECKED.

Capability is what it can do.
Authority is what it may do.

The model can reason, plan, and ask. A separately issued grant defines which operation may touch which resource, under which conditions. The enforcement point checks that grant before the protected consequence.

I

Permission comes from outside.

An agent’s explanation of why it should act is evidence to consider. The resource owner decides the authority.

II

The exact request matters.

A grant can bind the operation, target, arguments, state, expiry, and use. Changing the request requires a fresh check.

III

Evidence closes the loop.

Inspect the decision and read back the effect. Keep confirmed results, refused requests, and unknown outcomes distinct.

02 / USE THE TECHNOLOGY

A real request.
A verifiable consequence.

Connect Customer Orders, approve an agent’s limits, and submit a refund. The live service compiles the request, checks signed authority with Substrate, and enforces it through the Resource Deputy.

YOU CONTROL THE PERMISSION

Northstar Online Store
Read · search · refund up to $50
3 refund tokens · 10 minutes

Fictional customers. A real isolated database, signed grants, admission decisions, and resource effects. No money moves. This Site connects to the service at demo.sekos.ai.

Open the full governed-actions workspace
GOVERNED ACTIONSNOT CONNECTED

Each browser gets its own resettable records.

03 / START WITH ONE WORKFLOWA CLEAR DECISION BEFORE BROADER PERMISSIONS

Does your agent stay
within its permissions?

In one week, we test one agent workflow. You see what passed, what failed, and what we couldn’t test, with evidence your team can inspect and tests it can repeat.

For teams preparing to launch an agent, connect a sensitive resource, or expand what an agent may do.

Describe your agent

Begin with a brief. Scope, access, and terms are agreed together.

AGENT ACTION BOUNDARY ASSESSMENT

$12,500fixed fee

One agent workflow · one week

What your team keeps

  • 01
    A clear result

    Passed, failed, and untested cases with supporting evidence.

  • 02
    Repeatable tests

    Check the same boundaries again after a change.

  • 03
    A runnable scenario demo

    Synthetic data, expected and observed cases, and a copy your team retains.

  • 04
    A practical fix plan

    Prioritized changes and criteria for retesting.

04 / DEMOS & RESEARCHFOLLOW THE EVIDENCE

Inspect the work.
Test the claim.

Explore the demonstrations and public implementation behind Sekos. Each has its own construction, assumptions, and limits.

Browse the research library

05 / THE EVIDENCE BOUNDARY

Strong claims
need sharp edges.

Authority checks apply at declared enforcement points. Their value depends on the issuer, key custody, trusted host, and whether alternate routes to the resource remain open.

A hash can reveal changed content. A signature can identify a signer. Replay can check consistency with declared inputs. These checks do not establish that a source is truthful, a policy is wise, or the whole system is safe.

Read the published evidence and limits

START WITH THE ACTION THAT MATTERS

What should your agent
never be allowed to do?

Tell us what it does, where it acts, and what worries you.

Start with your agent