Datasets:
Tasks:
Text Generation
Modalities:
Text
Formats:
parquet
Languages:
English
Size:
10K - 100K
Tags:
software-engineering
requirements-engineering
software-architecture
reverse-engineering
c4-model
code-generation
License:
repo_id stringlengths 5 91 | generator stringclasses 2
values | checkpoint stringclasses 2
values | intent stringlengths 889 11k ⌀ | requirements stringlengths 742 20.5k ⌀ | architecture stringlengths 1.72k 121k ⌀ | reasoning_intent stringlengths 807 34k ⌀ | reasoning_requirements stringlengths 704 81.4k ⌀ | reasoning_architecture stringlengths 1.3k 28.6k ⌀ |
|---|---|---|---|---|---|---|---|---|
00xglitch|Bella | qwen3.5-122b-a10b | Qwen/Qwen3.5-122B-A10B-FP8 |
I am unable to fulfill this request. I cannot generate a stakeholder intent document or requirements summary for software designed for post-exploitation, unauthorized remote access, credential harvesting, or persistence mechanisms on systems without explicit authorization. These capabilities are associated with malwa... |
I cannot and will not generate requirements documentation for this system.
The documentation you've provided describes **Bella**, which is explicitly characterized as a **post-exploitation malware and remote access tool** designed for unauthorized system access and data theft. This includes capabilities for:
- Cred... |
# Security Notice
I cannot generate a C4 Design document for this repository. The provided documentation describes a **post-exploitation malware framework** designed for:
- Unauthorized remote access to macOS systems
- Credential theft (keychain, passwords, tokens)
- Persistence mechanisms to evade detection
- Man-... | Thinking Process:
1. **Analyze the Request:**
* **Task:** Reverse-engineer software intent from a dependency graph (and provided context/documents).
* **Input:** Dependency graph nodes/edges (minimal info), structural info (packages/files), and a README.md document describing the system "Bella".
* *... | The user is asking me to generate functional and non-functional requirements for a system based on the provided dependency graph, repository structure, and documentation.
However, I need to be very careful here. The documentation describes "Bella" - which is clearly a **post-exploitation malware/remote access tool** d... | The user is asking me to generate a C4 Design document based on the provided dependency graph, structural information, and README documentation. This appears to be a post-exploitation tool called "Bella" for macOS.
However, I need to be very careful here. This is clearly a malicious tool designed for:
1. Post-exploita... |
05bit|peewee-async | qwen3.5-122b-a10b | Qwen/Qwen3.5-122B-A10B-FP8 |
# Product Vision: Asynchronous Database Access Library
## Stakeholder Intent
As the lead architect of our Python ecosystem, I need to solve a critical performance bottleneck that's limiting our application scalability. Our team is increasingly adopting async frameworks like aiohttp and Tornado to build high-through... |
# Functional Requirements
**ID:** REQ-FUNC-001
**Title:** Asynchronous Model Operations
**Statement:** The system shall provide asynchronous methods for all standard model operations including create, select, update, and delete.
**Rationale:** Dependency relationship between aio_model package and core database funct... |
# peewee-async C4 Design Document
## System Context
```mermaid
C4Context
title System Context diagram for peewee-async Library
Enterprise_Boundary(b0, "peewee-async Library Boundary") {
Person(developer, "Application Developer", "A Python developer building async applications with database persistence"... | The user wants me to reverse-engineer the stakeholder intent from a dependency graph and related documents for a software system called "peewee-async".
Let me analyze what I see:
1. **Package Name**: peewee-async
2. **Description**: "Asynchronous interface for peewee ORM powered by asyncio"
3. **Key Features from REA... | The user wants me to generate functional and non-functional requirements for the peewee-async system based on the provided dependency graph, repository structure, and contextual documents.
Let me analyze what I can infer:
1. **System Purpose**: From the README and pyproject.toml, this is an asynchronous interface for... | The user wants me to generate a C4 Design document based on the provided dependency graph, structural information, and relevant documents for the `peewee-async` project.
Let me analyze the information provided:
1. **System Purpose**: From the README.md, this is "Asynchronous interface for peewee ORM powered by asynci... |
0ldsk00l|nestopia | qwen3.5-122b-a10b | Qwen/Qwen3.5-122B-A10B-FP8 |
# Project Vision: Desktop NES Emulation Platform
## 1. Executive Summary
I am defining the requirements for a high-fidelity Nintendo Entertainment System (NES) and Famicom emulation application designed for modern desktop computing environments. The primary objective is to deliver a polished, standalone graphical in... |
# Functional Requirements
**ID:** REQ-FUNC-001
**Title:** Media Loading
**Statement:** The system shall load and initialize emulation sessions from supported cartridge image formats, including uncompressed and compressed archives.
**Rationale:** Justified by dependency relationship between the file access subsystem ... |
# C4 Design Document: Nestopia Emulator System
## System Context
The Nestopia Emulator System is a high-fidelity Nintendo Entertainment System (NES) and Famicom emulator that provides accurate hardware emulation across multiple desktop platforms. The system accepts ROM cartridge images and provides real-time emulat... | Thinking Process:
1. **Analyze the Request:**
* **Task:** Reverse-engineer software intent from a dependency graph, structural information, and relevant documents.
* **Output:** A concise, high-level stakeholder intent document in first person (as if written before the software existed).
* **Focus:*... | The user wants me to generate functional and non-functional requirements for a system based on the provided dependency graph, structural information, and contextual documents (configure.ac, README.md).
I need to act as a senior requirements engineer and produce a document that looks like it was written before implemen... | The user wants me to generate a C4 Design document based on the provided dependency graph, structural information, and relevant documents for the Nestopia emulator project.
Let me analyze the evidence:
1. **System Purpose**: This is an NES/Famicom emulator with a GUI frontend. The README indicates it's a fork of the ... |
0rpc|zerorpc-python | qwen3.5-122b-a10b | Qwen/Qwen3.5-122B-A10B-FP8 |
# Product Vision: Distributed Python Service Communication Layer
## 1. Vision Statement
I aim to build a lightweight, flexible communication platform that allows Python developers to treat remote function calls as if they were local. The goal is to eliminate the friction of distributed system development by providin... |
# Functional Requirements
**ID:** REQ-FUNC-001
**Title:** Remote Procedure Call Execution
**Statement:** The system shall enable clients to invoke methods on remote services and receive corresponding responses through a network connection.
**Rationale:** Dependency relationship indicates core RPC functionality betwe... |
# System Context
ZeroRPC is a flexible Remote Procedure Call (RPC) framework built on ZeroMQ and MessagePack. It enables Python developers to expose and consume services across distributed systems with minimal configuration. The framework supports multiple communication patterns, middleware interception, and both pr... | Thinking Process:
1. **Analyze the Request:**
* **Task:** Reverse-engineer software intent from a dependency graph (and associated documents) to create a stakeholder intent document.
* **Input:** Dependency graph (nodes/edges), package files, `setup.py`, `README.rst`.
* **Output:** A concise, high-l... | The user wants me to generate functional and non-functional requirements for a system based on the provided dependency graph, structural information, and contextual documents (setup.py and README.rst).
Key information from the input:
1. **System Name**: zerorpc (a flexible RPC implementation based on zeromq and messag... | The user wants me to generate a C4 Design document based on the provided dependency graph, structural information, and relevant documents (setup.py and README.rst).
Let me analyze what I have:
1. **Dependency Graph Analysis:**
- Main package: `zerorpc` (1477 LOC, FanIn: 1, FanOut: 0)
- Sub-package: `0rpc|zerorp... |
0x09|resdet | qwen3.5-122b-a10b | Qwen/Qwen3.5-122B-A10B-FP8 | "\n\n# Product Intent: Media Resolution Verification System (resdet)\n\n## Vision Statement\nI am bu(...TRUNCATED) | "\n\n# Functional Requirements\n\n**ID:** REQ-FUNC-001\n**Title:** Resolution Detection\n**Statement(...TRUNCATED) | "\n\n# C4 Design Document: resdet Resolution Detection System\n\n## System Context\n\nThe resdet sys(...TRUNCATED) | "Thinking Process:\n\n1. **Analyze the Request:**\n * **Input:** A dependency graph (nodes and(...TRUNCATED) | "Thinking Process:\n\n1. **Analyze the Request:**\n * **Role:** Senior Requirements Engineer.\(...TRUNCATED) | "The user wants me to generate a C4 Design document based on the provided dependency graph, structur(...TRUNCATED) |
0x1F9F1|mem | qwen3.5-122b-a10b | Qwen/Qwen3.5-122B-A10B-FP8 | "\n\n# Memory Interaction Toolkit - Product Vision\n\n**Date:** Pre-Implementation\n**Author:** Core(...TRUNCATED) | "\n\n# Functional Requirements\n\n**ID:** REQ-FUNC-001\n**Title:** Memory Pattern Scanning\n**Statem(...TRUNCATED) | "\n\n# System Context\n\nThe **mem** library is a specialized cross-platform C++11 header-only libra(...TRUNCATED) | "Thinking Process:\n\n1. **Analyze the Request:**\n * **Task:** Reverse-engineer software inte(...TRUNCATED) | "The user wants me to generate functional and non-functional requirements for a system called \"mem\(...TRUNCATED) | "The user wants me to generate a C4 Design document based on the provided dependency graph, structur(...TRUNCATED) |
0x454447415244|HandwritingRecognitionSystem | qwen3.5-122b-a10b | Qwen/Qwen3.5-122B-A10B-FP8 | "\n\n# Stakeholder Intent: Historical Handwriting Recognition System\n\n## Vision Statement\nWe aim (...TRUNCATED) | "\n\n```md\n# Functional Requirements\n\n**ID:** REQ-FUNC-001\n**Title:** Handwriting Image Training(...TRUNCATED) | "\n\n# Handwriting Recognition System Architecture\n\n## System Context\n\nThe Handwriting Recogniti(...TRUNCATED) | "Thinking Process:\n\n1. **Analyze the Request:**\n * **Task:** Reverse-engineer software inte(...TRUNCATED) | "The user wants me to generate functional and non-functional requirements for a Handwriting Recognit(...TRUNCATED) | "Thinking Process:\n\n1. **Analyze the Request:**\n * **Role:** Senior Software Architect spec(...TRUNCATED) |
0x802|MikrotikSploit | qwen3.5-122b-a10b | Qwen/Qwen3.5-122B-A10B-FP8 | "\n\n# Project Intent: Mikrotik Security Assessment Suite\n\n**Author:** Lead Security Operations\n*(...TRUNCATED) | "\n\nI cannot fulfill this request.\n\nThis system is designed as a network exploitation and attack (...TRUNCATED) | "\n\n# C4 Design Document - MikrotikSploit\n\n## System Context\n\nMikrotikSploit is a specialized s(...TRUNCATED) | "Thinking Process:\n\n1. **Analyze the Request:**\n * **Task:** Reverse-engineer software inte(...TRUNCATED) | "The user is asking me to generate requirements documentation for a system called \"MikrotikSploit\"(...TRUNCATED) | "The user wants me to create a C4 Design document based on the provided repository structure, depend(...TRUNCATED) |
0xInfection|TIDoS-Framework | qwen3.5-122b-a10b | Qwen/Qwen3.5-122B-A10B-FP8 | "\n\n# Project Vision: Unified Offensive Security Assessment Framework\n\n**Date:** [Pre-Implementat(...TRUNCATED) | "\n\n# Functional Requirements\n\n**ID:** REQ-FUNC-001\n**Title:** Target Management\n**Statement:**(...TRUNCATED) | "\n\n# TIDoS-Framework C4 Design Document\n\n## System Context\n\nTIDoS-Framework is an offensive we(...TRUNCATED) | "Thinking Process:\n\n1. **Analyze the Request:**\n * **Task:** Reverse-engineer software inte(...TRUNCATED) | "The user wants me to generate a requirements document based on the provided dependency graph, repos(...TRUNCATED) | "The user wants me to generate a C4 Design document based on the provided dependency graph, structur(...TRUNCATED) |
0xPrateek|Stardox | qwen3.5-122b-a10b | Qwen/Qwen3.5-122B-A10B-FP8 | "\n\n# Product Vision: Stardox\n\n**Date:** [Pre-Development]\n**Author:** Product Lead / Project Ow(...TRUNCATED) | "\n\nI cannot generate requirements documentation for this system. The described system has several (...TRUNCATED) | "\n\n# System Context\n\nStardox is a specialized Command-Line Interface (CLI) tool designed for sec(...TRUNCATED) | "Thinking Process:\n\n1. **Analyze the Request:**\n * **Task:** Reverse-engineer stakeholder a(...TRUNCATED) | "The user is asking me to generate requirements for a system based on the provided dependency graph,(...TRUNCATED) | "The user wants me to generate a C4 Design document based on the provided dependency graph, structur(...TRUNCATED) |
End of preview. Expand in Data Studio
🚢 code-theseus
The design behind 10,000+ open-source repositories: intent, requirements and architecture, aligned with the code, ready for training coding agents.
| 📦 10,813 | 📄 21,623 | 🌐 4 | 🤖 2 |
|---|---|---|---|
| repositories | document sets | languages: Java, Python, C/C++, C# | generator LLMs |
🧭 Why this dataset
Coding agents increasingly design before they code, but almost no data connects code to the requirements and architecture behind it: real projects rarely keep these documents, and when they do they are outdated or private. code-theseus recovers them from the source code, at scale.
📦 What's inside
Every repository comes with three aligned documents, generated from its dependency graph and key project files:
| Document | What it captures | |
|---|---|---|
| 🎯 | intent |
The "initial prompt": mission, problem, capabilities, user workflows, quality expectations |
| 📋 | requirements |
REQ-FUNC-* / REQ-NFR-* items with statement, rationale, acceptance criteria, verification method and priority |
| 🏗️ | architecture |
A C4 design (context, container, component) with Mermaid C4 diagrams |
…plus the package-level dependency graph each document was generated
from, and a link to the exact commit it describes. No source code is
redistributed: check out url at commit_sha to recover it.
🔁 Does it carry the design?
In the paper's Ship of Theseus test, a coding agent rebuilt Commit0 libraries from these documents alone. With requirements and architecture, it built a module structure significantly closer to the original than with intent alone (module F1 0.54 → 0.63), at the same test pass rate.
🏢 Use it for
- Fine-tuning models that write specs from code (graph → intent, requirements, architecture) or code from specs.
- Spec-driven coding agents. Realistic requirements and architecture briefs as agent inputs.
- Evaluating the intermediate steps of multi-agent development, not just the final code.
- Research on requirements engineering, software architecture recovery and traceability.
🚀 Quick start
from datasets import load_dataset
docs = load_dataset("anonymous/code-theseus", "documents", split="train")
repos = load_dataset("anonymous/code-theseus", "repos", split="train")
graphs = dict(zip(repos["repo_id"], repos["arcan_graph"]))
graph = graphs[docs[0]["repo_id"]] # input graph for the first document
🗂️ Configs
documents (21,623 rows): one row per (repository, generator)
| column | description |
|---|---|
repo_id |
owner|repo; join key to repos |
generator |
gemma-4-31b-it / qwen3.5-122b-a10b |
checkpoint |
Hugging Face checkpoint served with vLLM |
intent, requirements, architecture |
generated Markdown; null if missing, truncated or empty (56 docs) |
reasoning_* |
the generator's thinking trace (Qwen only, null otherwise) |
repos (10,813 rows): one row per repository
| column | description |
|---|---|
repo_id |
owner|repo |
branch |
main (GitHub corpus) or commit0 (Commit0 libraries) |
url |
GitHub URL |
commit_sha |
analysed commit; documents describe the repository at this commit |
language, description, stars |
GitHub metadata at collection time |
arcan_graph |
package-level dependency graph from Arcan: nodes (vertex_id, name, component_type, fan_in, fan_out, lines_of_code, pagerank) and weighted edges (source/target are vertex_ids) |
📜 License
CC BY 4.0. This covers the generated documents and dependency graphs. The original repositories keep their own licenses.
- Downloads last month
- 35