Define
State the non-sensitive problem, desired outcome, interfaces, exclusions, acceptance criteria, and what evidence must accompany the result.
START SMALL. DEFINE THE EVIDENCE.
One bounded problem. Agreed deliverables. Explicit acceptance criteria.
A novel operating model should not require a large initial leap of faith. Start with a non-sensitive engineering problem that can be scoped, inspected, tested, and accepted—or rejected—on defined terms.
DIRECT ANSWER
What is an Autonomy Proof Sprint?
It is a proposed bounded first-engagement pattern: one unclassified problem, defined outputs, agreed acceptance criteria, explicit exclusions, and a decision at the end about whether further automation is justified. Scope, schedule, price, data rights, contracting entity, and security obligations are established separately in the applicable agreement; this page does not set those terms.
ENGAGEMENT SHAPE
Make the initial commitment smaller than the uncertainty.
A bounded evaluation is designed to let a program office or authorized prime inspect the work before expanding scope.
Demonstrate
Produce the agreed assessment, prototype, benign demonstration, test result, or change-impact package within the approved information boundary.
Evaluate
Review what passed, what failed, what remains uncertain, and whether further automation or integration is justified. A finding that autonomy is unsuitable can be a valid result.
FIRST CONTACT
Send enough context to qualify the problem—nothing controlled.
Useful first-contact information includes an unclassified opportunity or program identifier when releasable, the software or systems-engineering problem, desired role, anticipated schedule, known compliance requirements, expected information boundary, and the party responsible for establishing any controlled follow-on exchange.
Do not send classified information, CUI, export-controlled technical data, target data, operational mission data, vulnerabilities, credentials, customer-sensitive source, or weapon-employment parameters through ordinary email.
BEFORE YOU START
Common engagement questions
Can classified information, CUI, or other controlled data be sent through the public site?
No. Do not transmit classified information, CUI, export-controlled technical data, operational mission data, target data, credentials, vulnerabilities, or weapon-employment parameters through the public site or ordinary email.
Can supporting procurement or assurance documentation be provided upon request?
Where supporting material exists, is applicable to the contemplated engagement, and disclosure is permitted, authorized government or prime-contractor reviewers may request it. A request does not imply that a particular registration, certification, clearance, contract vehicle, customer reference, or other credential exists. Materials may be withheld, redacted, or routed through approved channels when required by law, regulation, classification, export control, contract, customer direction, confidentiality, privacy, security, or need-to-know restrictions.
What is a bounded pilot or Autonomy Proof Sprint?
It is a proposed first-engagement pattern for one unclassified problem with defined outputs, acceptance criteria, exclusions, and an explicit decision about whether further automation is justified. Scope, schedule, price, data rights, contracting entity, and security obligations are set in the applicable agreement rather than by the public website.