Manual application review

Sentinel SCA Founding Integration Application

Apply for voluntary, bounded testing access for one real workflow. If selected, the access window can run for up to 30 days.

Your workflow must be in production, near-production, or active development with real tasks.
You must identify a concrete execution boundary where Sentinel could evaluate authority before an action occurs.
Chat-only and demonstration-only projects are not eligible.

Sandbox and application are different paths. The sandbox simulates decision behavior. This application is a manual qualification process for bounded testing access; submitting it does not create an account, Tester ID, or execution authority.

Do not submit passwords, API keys, private keys, credentials, production secrets, or sensitive customer data through this application. We will agree any required access boundaries separately before testing.

About you

Tell us who will own the workflow evaluation and where you work.

Full name *

Email address *

Organization or project *

Country and time zone *

Your role *

Workflow owner *

Workflow and execution boundary

We are looking for a real task and a locatable point before the consequential side effect.

Current stage *

Describe the workflow *

Describe the agent or automation and how work progresses today.

One real task and its expected outcome *

Use a task the system actually performs or is actively being built to perform.

What consequential actions can it take? *

Examples include changing infrastructure, sending data, moving value, or affecting a customer.

What component performs the side effect? *

Name the worker, service, API, tool, device, or other execution component.

Where could Sentinel sit immediately before execution? *

Identify the specific call or transition Sentinel could govern.

What runs automatically? *

Describe the steps that currently proceed without human intervention.

What requires approval or escalation? *

Describe current decision points and what happens when approval is withheld.

Testing scope

Describe the evidence and environment needed to evaluate the boundary. Do not provide access or credentials here.

Tools and infrastructure involved *

List relevant frameworks, services, clouds, APIs, models, or devices.

What information could Sentinel observe? *

Describe proposed action metadata, identity, policy context, evidence, and outcomes.

What would testing require? *

Selecting an access type identifies a possible pilot requirement. It does not authorize access and you must not paste access material into this form.

Other testing requirement *

If you selected Other, describe it. Otherwise enter None.

What must stay inside your environment? *

Describe material or execution that cannot leave your boundary without including that material itself.

Sensitive or regulated information involved *

Describe data classes and constraints. Enter None if not applicable.

Optional availability

Share any availability or preferred testing cadence. Participation is voluntary and this does not create a time commitment.

Learning and success

What do you want to learn from the pilot? *

What would make the pilot successful? *

Participation preferences are optional.

A testing access window of up to 30 days would be useful for my workflow.I am open to sharing feedback about the integration and governance results.

Required confirmations

I understand this application does not guarantee acceptance, testing access, or a Tester ID.I confirm that I have not included credentials, passwords, private keys, tokens, customer data, or other secrets.I understand testing access and data boundaries must be agreed before onboarding.

Manual review. No account or execution access is created on submission.