> For the complete documentation index, see [llms.txt](https://data-programs.gitbook.io/singularity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://data-programs.gitbook.io/singularity/kr/deal-making/create-a-deal-schedule.md).

# 거래 일정 만들기

저장 공급 업체와 거래를 시작해 보십시오. 먼저 거래 푸시 서비스를 실행합니다.

```
singularity run deal-pusher
```

## 한 번에 모든 거래 전송하기

더 작은 데이터세트의 경우, 모든 거래를 한꺼번에 저장 공급 업체에 전송할 수 있습니다. 이를 위해서는 다음 명령을 사용할 수 있습니다.

```sh
singularity deal schedule create <preparation> <provider_id>
```

하지만 데이터세트가 큰 경우, 거래 제안이 만료되기 전에 그만큼 많은 거래를 저장 공급 업체가 처리하지 못할 수도 있으므로 일정을 만들 수 있습니다.

## 일정을 갖고 거래 전송하기

같은 명령을 사용하여 얼마나 빠르고 얼마나 자주 거래를 저장 공급 업체에 전송할지를 제어하는 자체 일정을 만들 수 있습니다.

```sh
singularity deal schedule create -h
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://data-programs.gitbook.io/singularity/kr/deal-making/create-a-deal-schedule.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.