IMR_Abstract_Template_Amended.docx

DOCX document 45 KB Posted

Attached to
Intrinsic Market Resilience (IMR)
Solicitation number
DARPA-PS-26-138
Issued by

About this file

This is an abstract template document for the Intrinsic Market Resilience (IMR) program solicitation. The template is designed to guide offerors in preparing abstracts for submission to DARPA's IMR program (Solicitation Number DARPA-PS-26-138). The IMR program aims to develop tools and methodologies to protect essential economic sectors against adversarial attacks that exploit vulnerabilities in modern market systems, including equities, bonds, energy, and cloud computing resources markets.

The program seeks to combine Large Language Model (LLM)-based automation with rigorous modeling and analysis to identify and assess market design weaknesses and recommend repairs to increase market resilience. Offerors are expected to develop formal notations to describe market operations, create machine-analyzable models from regulatory filings and technical specifications, and formulate "resilience conjectures" as mathematical statements about desirable market properties. The abstract template provides the structured format that prospective contractors must use when responding to this DARPA solicitation, establishing the presentation standard for initial technical proposals addressing market vulnerability identification, automated modeling, and resilience analysis solutions.

View the file

Other files

File Type Posted
DARPA-PS-26-138-Amendment-01.pdf PDF
IMR_Abstract_Template_Final.docx DOCX document
DARPA-PS-26-138.pdf PDF
IMR_CUIG_SEP_2026_v1.0.pdf PDF
IMR_Abstract_Summary_Slide_Template_Final.pptx PPTX presentation

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

COVER SHEET

[PRIME ORGANIZATION LOGO optional]

Abstract Title

Technical Area
☐ TA1

☐ TA2

☐ TA1 & TA2

☐ TA3

Proposer Organization

SAM.gov Unique Entity ID (UEI)

Technical Point of Contact (POC)
Name:

Mailing Address:

Telephone:

Email:

Administrative POC
Name:

Mailing Address:

Telephone:

Email:

Other Team Members (subcontractors and consultants), if known/applicable
Technical POC Name:

Organization:

Technical POC Name:

Organization:

Award Instrument
OT for Prototype
Estimated Total Price (Base + Options)
$
Estimated Period of Performance
32 months

Identify any other solicitation(s) to which this concept has been proposed.

ABSTRACT GUIDELINES: Use of this template is required for all abstract submissions. Proposers must include all information in this template to constitute a fully conforming abstract submission.

Page Limit Requirement: Abstracts shall not exceed a maximum of 5 pages. This page limit does NOT include the following:

· Abstract Coversheet

· Table of Contents

· 1-slide Abstract Slide Summary (see IMR Abstract Summary Slide Template)

· Disclosure of Artificial Intelligence (AI) Utilization

· Bibliography (Optional)

· Technical Papers (Optional)

Formatting Requirements: All submissions must be typed in English on 8.5" by 11" pages using 12-point, font with 1" margins all around. 8 or 10-point fonts may be used for figures, tables, and charts. Use of diagram(s) or figure(s) to depict the essence of the proposed solution is encouraged. Do NOT include elaborate brochures or marketing materials.

Content Requirements: Content requirements are noted in blue font under each section of the abstract template. Proposers should delete all content requirements prior to abstract submission.

Submission Requirements: Abstract submissions must be submitted in PDF or Microsoft Word formats. The recommended file naming convention is “Organization Name_IMR Abstract.” All proprietary information should be appropriately marked. NOTE: "Confidential" is a classification marking used to control the dissemination of U.S. Government National Security Information as dictated in Executive Order 13526 and should not be used to identify proprietary business information.

UNCLASSIFIED abstracts must be submitted via DARPA’s Broad Agency Announcement Tool (BAAT). Please visit Proposer Instructions and General Terms and Conditions for specific information regarding submission methods through BAAT. Please note, BAAT is a method of secure transmission for CUI documentation. Submissions sent through other mediums, channels, or after the prescribed deadline will not be accepted.

CLASSIFIED abstracts must be submitted in accordance with the requirements, instructions, and procedures contained within the classified addendum. Classified submissions must NOT be submitted through BAAT.

Table of Contents

1.Goals and Impact3
2.Technical Approach3
3.Capabilities/Management Plan3
4.Rough Order of Magnitude3
5.Disclosure of Artificial Intelligence (AI) Utilization3
6.Bibliography5
7.Technical Papers5

DARPA-PS-26-138

IMR Abstract Source Selection Sensitive

[Content requirements are stated in blue font and should be deleted prior to abstract submission.] Goals and Impact [Describe what is being proposed and what difference it will make (qualitatively and quantitatively) if successful. Describe the innovative aspects of the project in the context of existing capabilities and approaches, clearly delineating the relationship of this work to any other projects from the past and present.] Technical Approach [Provide answers to the following questions:

· What is the proposed work attempting to accomplish or do?

· How is the work performed today (what is the state of the art or practice), and what are the limitations?

· What is new in your approach, and why do you think it will be successful?

· How much will it cost (rough order of magnitude), and how long will it take?

Outline and address technical challenges inherent in the approach and possible solutions for overcoming potential problems. Provide appropriate measurable milestones (quantitative if possible) at intermediate stages of the project to demonstrate progress and a plan for achieving the milestones.]

Capabilities/Management Plan [Provide a brief summary of the expertise of the team, including subcontractors and key personnel. While teaming arrangements do not need to be finalized at the time of abstract submission, mention of potential teaming/collaboration arrangements is highly encouraged. Identify a principal investigator for the project and include a description of the team’s organization, including roles and responsibilities.]

Rough Order of Magnitude [Provide a price estimate for resources (e.g. labor, materials) and any subcontractors over the entire program. Please ensure it conforms with the Solicitation Section 4.4 Informed Budget.] Disclosure of Artificial Intelligence (AI) Utilization Proposers must disclose how AI tools were used in the preparation of this abstract, and how AI will be leveraged during the performance of the proposed research.

· Rule of Use: AI may be used for administrative drafting, formatting, or editorial refinement of this abstract. However, the core scientific hypotheses, technical methodologies, and proposed operational solutions must be the original product of the human authors.

· Adjunct, Not Replacement: The use of AI to enhance and accelerate technical aspects of the proposed research is permitted, but AI may only be used as an adjunct to—and not a replacement for—human creativity, insight, and direction.

Part A: AI Use in Abstract Preparation Check all that apply:

☐ No AI tools were used in the preparation, drafting, or formatting of this abstract.

☐ AI tools were used during the development of this abstract. (If selected, you must complete the table in Part B below).

Part B: AI Use in the Performance of Proposed Research For every phase of the abstract development where AI was leveraged, indicate the specific tool used, the nature of its application, and how human authorship and scientific direction were maintained.

Abstract Development Phase
Specific AI Tool(s) Used
How the Tool Was Utilized
Human Authorship & Validation Safeguard
1. Brainstorming & Concept Exploration
e.g., ChatGPT-4o, Claude 3.5 Sonnet, etc.
Example: Used to brainstorm potential edge cases for our proposed testing framework or query historical analogies.
Example: All proposed hypotheses and technical methodologies were generated by the PI; AI was only used to stress-test our pre-existing assumptions.
[Proposer Input]
[Proposer Input]
2. Literature Synthesis & Prior Art
e.g., Consensus, Elicit, Perplexity, etc.
Example: Used to rapidly identify peer-reviewed articles on [Insert Topic] to ensure our background section was comprehensive.
Example: Human authors manually retrieved and verified every cited source to ensure no "hallucinated" citations or false claims were included.
[Proposer Input]
[Proposer Input]
3. Technical Drafting & Expansion
e.g., Gemini, Copilot, etc.
Example: Used to expand rough technical bullet points drafted by the subject matter expert (SME) into cohesive paragraphs for Section 2.
Example: The core scientific formulas, architectures, and performance metrics were drafted by the SME; AI was only used to improve sentence flow.
[Proposer Input]
[Proposer Input]
4. Editorial Refinement & Constraints
e.g., Grammarly, Hemingway, etc.
Example: Used to edit the draft for active voice, correct grammatical errors, and reduce word count to fit the 5-page BAA limit.
Example: Human authors reviewed every suggested edit to ensure the precise scientific meaning of our technical terminology was not altered.
[Proposer Input]
[Proposer Input]
5. Formatting & Structuring
e.g., Custom markdown/LaTeX formatters.
Example: Used to generate the Markdown code for tables and convert raw bullet points into the required BAA template format.
Example: Human authors verified that all tables accurately mapped to our program's proposed milestones and budget figures.
[Proposer Input]
[Proposer Input]

Bibliography [Provide a brief bibliography with links to relevant papers, references, reports, etc.]

Technical Papers Are technical papers included as an attachment to this submission? ☐ YES ☐ NO

File details come from the government source that posted it. Updated .