The Journey to Build SecurityCooperation.org from Idea to Execution
- Jimmy Stewart

- Feb 10
- 4 min read
I reached a turning point recently when I heard the term “vibe coding” described as the next wave of builders. At 54 years old, with years of experience leading application development teams, I realized I had never personally written code myself. That moment sparked a realization: I could finally build the platform I had been designing in my mind for decades. This blog post shares why I started SecurityCooperation.org, the gap I saw in the field, and what I aimed to achieve with this project.
The Moment I Decided to Build SecurityCooperation.org
I have spent much of my career managing teams that built software, but I rarely got my hands dirty with the actual coding. When I heard about “vibe coding,” a more intuitive, personal approach to building software, it felt like an invitation. I thought, Why not me? I had ideas that had been waiting for the right moment and tools to come together.
The idea was clear: create a platform that turns public-source defense and policy content into structured, evidence-linked briefs. I wanted something practical, consistent, and repeatable. The goal was not to chase flashy features but to build a tool that would help analysts, researchers, and reporters make sense of scattered public information.
The Gap I Saw in Public-Source Defense and Policy Information
Public information about defense and policy is abundant but scattered. It exists in reports, news articles, official statements, and databases, but it is rarely organized in a way that makes it easy to verify or reuse consistently.
I noticed that no one was doing this in a structured, evidence-linked way using only public sources. Many platforms rely on privileged or classified information, which limits transparency and repeatability. Others provide raw data dumps without clear connections to evidence or context.
The opportunity was to build a repeatable workflow that makes evidence easy to verify. This means every piece of information in the platform links back to its original source, allowing users to trace the data and check its validity. This approach supports transparency and trust, which are essential for anyone working with public-source information.
Why Public-Only Was the Point
Choosing to work exclusively with public information was a deliberate decision. Staying outside government systems keeps the platform flexible and transparent. It means anyone can check the sources and understand how conclusions are drawn.
This approach also opens a path to monetization without relying on privileged access. By building on public data, the platform can serve a wide audience without the legal and ethical complications that come with handling classified or restricted information.
Public-only data also encourages innovation. It forces the platform to focus on structure, consistency, and usability rather than secret or exclusive content. This makes the platform more resilient and adaptable over time.
What Good Looked Like Before Building
Before starting the build, I had a clear picture of what “good” meant for this platform:
Consistent structure: Every brief should follow a clear, repeatable format. This helps users find information quickly and understand it easily.
Evidence link: Every claim or data point must link back to its original public source. This ensures traceability and builds trust.
Repeatable pipeline: The process of turning raw public information into structured briefs should be automated as much as possible. This reduces errors and saves time.
Transparency: Users should see how the information was gathered and processed. This openness is key to credibility.
Practicality: The platform should serve real needs for analysts, researchers, and reporters who rely on public-source information.

This image shows the kind of structured, evidence-linked interface I aimed to build for SecurityCooperation.org.
Building the Platform Step by Step
Starting from scratch, I focused on creating a pipeline that could ingest public data, organize it, and output clear briefs. This involved:
Identifying reliable public sources for defense and policy information.
Designing a data model that captures key details while linking back to sources.
Developing tools to automate data collection and structuring.
Creating a user interface that presents briefs clearly and allows users to explore evidence links.
Each step required testing and iteration. I had to balance automation with manual checks to maintain quality. The goal was not to build a perfect system overnight but to create a foundation that could grow and improve.
Why This Matters to Analysts, Researchers, and Reporters
For those who work with public-source information, the challenge is often verification and consistency. It’s easy to find pieces of information, but hard to connect them reliably or check their origins.
SecurityCooperation.org aims to solve this by providing a platform where every brief is backed by clear evidence. This makes it easier to:
Verify facts quickly.
Build on existing knowledge without duplicating effort.
Share findings with confidence in their accuracy.
Track changes and updates in public information over time.
This kind of tool supports better analysis and reporting, which ultimately contributes to more informed public discussions.
What Comes Next
The journey to build SecurityCooperation.org is ongoing. The platform is a work in progress, evolving as I learn more about user needs and public data sources.
The next steps include:
Expanding the range of sources covered.
Improving automation to speed up brief creation.
Enhancing the user interface for easier navigation.
Gathering feedback from analysts and researchers to refine features.
The goal remains clear: build a practical, transparent, and repeatable platform that turns public-source defense and policy content into useful, evidence-linked briefs.
SecurityCooperation.org started with a simple idea and a moment of clarity. It grew from recognizing a gap in how public information is used and a commitment to build something practical and trustworthy. For anyone interested in public-source traceability, this platform offers a new way to work with data that is consistent, transparent, and easy to verify.



Comments