> For the complete documentation index, see [llms.txt](https://docs.tactyc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tactyc.io/portfolio-construction/faqs/fractional-investments.md).

# Fractional investments

Why are the number of investments fractions?

Tactyc’s calculation logic attempts to deploy **all** of your available capital. This can commonly lead to investments being fractions. For e.g. if your model is deploying $10mm capital and but the check sizes are $1.5mm, the result will be 6.67 investments.

By hiding the decimals into integers we don't want you get tripped up by rounding. Our calculation engine computes out decimals, so rounding figures up (or down), loses some accuracy - and can end up implying some "unused capital" for your fund. So we've decided to be as transparent as possible to show you exactly the number of investments implied so the totals can all match up over the dashboard.

In our experience, LPs completely understand the uncertain and probablistic nature of fund level forecasts and fractional investments should not be confusing to the audience.


---

# 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://docs.tactyc.io/portfolio-construction/faqs/fractional-investments.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.