Passport Modes - Complior

	Mode 1: Auto	Mode 2: Runtime
Input	Source code (AST)	MCP tool calls + Eval
Command	`complior init`	`complior proxy` / `eval`
Auto-fill	65–70%	40–70%
Confidence	~0.42	0.55
Verification	Code-verified	Behavior-observed
Use case	Own code	Black-box vendor agent
User	Developer	DevOps / Platform Eng
Status	Production	Planned

Mode 1: Auto

Mode 2: Runtime

Input

Source code (AST)

MCP tool calls + Eval

Command

complior init

complior proxy / eval

Auto-fill

65–70%

40–70%

Confidence

~0.42

0.55

Verification

Code-verified

Behavior-observed

Use case

Own code

Black-box vendor agent

User

Developer

DevOps / Platform Eng

Status

Production

Planned

Mode 1: Auto (from code)

complior init          # auto-discovers agents during project init
complior agent init    # optional: manual re-discovery / --force regenerate

Scans your codebase through AST analysis. Detects frameworks (57+), models, permissions, human gates, autonomy level, kill-switch. Risk class computed from autonomy × project domain.

Best for: Your own AI agents where source code is available.

Mode 2: Runtime (from observation)

Two data sources:

MCP Proxy — intercepts MCP tool calls from black-box agents (Cursor, Windsurf, vendor agents). Records tools_used, data_access, timing, success/error rates.

Eval — complior eval --target <url> tests the system with 680 probes and records behavioral data.

Best for: Vendor AI agents you deploy but don’t have source code for.

Mode 2 is planned. MCP Proxy infrastructure is 60% built. Eval integration is in development.

​Mode comparison

​Mode 1: Auto (from code)

​Mode 2: Runtime (from observation)

Mode comparison

Mode 1: Auto (from code)

Mode 2: Runtime (from observation)