Map what is in scope
Agents, tools, models, data paths, credentials, owners, and action chains need an agreed record before controls can be reviewed consistently.
The company
Fugitive Intelligence offers fixed-scope AI Agent Exposure Reviews and private briefings. Fugitive Control, a vendor-neutral action-policy and evidence layer, remains in founding development.
Why Fugitive
The name describes software that has moved beyond the authority or operating boundaries its owners intended. It does not describe a service for locating people.
An agent may be compromised, over-permissioned, misconfigured, manipulated by untrusted context, or simply wrong. The practical question is whether its identity, delegated authority, requested action, and resulting evidence can be reviewed and controlled.
Autonomy should not exceed documented authority.
Agents, tools, models, data paths, credentials, owners, and action chains need an agreed record before controls can be reviewed consistently.
Security decisions become concrete where a request can change a business system, move value, or disclose sensitive information.
A response plan should isolate the smallest affected path where practical, preserve evidence, and avoid unnecessary business disruption.
Security teams, customers, reviewers, investigators, and leadership may need connected evidence from actual controls and actions.
Company boundaries
The brand name is memorable, but the operating scope must remain unambiguous.
Exposure reviews, architecture analysis, authorized testing, control planning, briefings, and a developing action-control platform.
No private investigation, bail enforcement, fugitive recovery, missing-person service, warrant service, surveillance of individuals, or public crime-tip intake.
No claim of law-enforcement authority, government status, regulatory approval, official intelligence-agency role, or power to compel records or action.
Bounded authority. Independent policy. Connected evidence.
Mission
Agents should be able to perform valuable work without inheriting unlimited access, operating through ambiguous identities, or leaving the business to reconstruct evidence after an incident.
Every agent should have a defined mandate before it receives a tool, credential, sensitive data source, or production action path.
Policies, training, prompts, and vendor statements are not substitutes for controls that can deny or constrain an action.
The action record should be produced during the decision, not assembled manually after a customer, auditor, or investigator asks.
Accountable people should remain in the loop where actions are sensitive, high-value, irreversible, regulated, or novel.
Control and evidence should survive changes in models, agent frameworks, clouds, identity systems, tools, and security platforms.
Prioritize the action paths that affect money, code, customers, regulated data, operations, or trust—not the largest pile of telemetry.
Operating model
Exposure reviews can create immediate value by documenting the environment and priorities. Repeated findings inform the Fugitive Control roadmap, but a service recommendation is not a promise that a software feature already exists.
Map agents, authority, data, tools, high-impact actions, evidence, and containment.
Validate an agreed subset of controls against one or two workflows under a separate written scope.
Use validated needs to shape reusable identity, policy, evidence, testing, and containment capabilities.
Organize control records for customer review, governance, investigations, audit support, and future assurance use cases.
What we will not promise
Absolute safety claims create false confidence. Useful security reduces exposure, constrains impact, preserves evidence, and improves response.
Every system has failure modes. The goal is layered prevention, bounded authority, detection, containment, and recovery.
Business value and risk remain linked. Controls should make the remaining risk visible, intentional, and owned.
Technology can provide evidence and support controls, but legal obligations and audit conclusions depend on context.
Evaluate actions against identity, authority, context, data, value, destination, workflow state, and approval requirements.
Replace broad inherited credentials with task-specific, short-lived, revocable authority wherever possible.
Preserve a connected action record that can support investigations, customer review, governance, and audit preparation.
Current stage
The near-term roadmap focuses on an agent and MCP tool-call policy gateway, accountable approvals, selective containment, and a connected action record. General availability and feature completeness are not claimed.