> For the complete documentation index, see [llms.txt](https://docs.yolkfi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yolkfi.com/02.-technical-architecture/physical-asset-and-batches.md).

# Physical Asset & Production Batches

### The Farm-as-a-Production-Partner Model

YolkFi establishes an institutional framework where capital formation is decoupled from physical farm operation:

1. **Capital Allocation:** YolkFi acts as the pre-financing capital layer for dedicated production batches.
2. **Operational Execution:** The participating farm (e.g., AT Grup) provides the physical land, bio-secure housing, labor, and automated systems to maintain the flock throughout its productive lifecycle (\~12–14 months).
3. **Commercial Offtake:** The farm sells commercial eggs to established supermarket and food processing channels.
4. **On-Chain Settlement:** Net commercial proceeds are reconciled and distributed on-chain according to predefined production agreements.

```
AT Grup (Season 1)
 └── Batch S1 (up to 30,000 Hens)
      ├── Hen #000001 ──> HenNFT #1
      ├── Hen #000002 ──> HenNFT #2
      └── ...

Future Certified Farm A (Season 2)
 └── Batch S2 (50,000 Hens)
```

***

### Production Batch Lifecycle

Every flock of laying hens is tracked through a structured state machine managed by `ProductionRegistry.rs`:

* **Registered:** Batch parameters, legal agreement hash, and maximum flock capacity recorded on-chain.
* **Active:** Hens are placed in production facilities; daily IoT telemetry and commercial yield distributions active.
* **Paused:** Emergency status if bio-security or operational anomalies occur.
* **Closed:** Productive lifecycle completed; final accounting reconciled; Hen NFTs retired/burned.

***

### Protocol Independence & Staging Telemetry Fallback

To ensure continuous development and deployment readiness, the on-chain smart contract protocol operates independently from biological placement schedules:

* **Staging Telemetry Ingestion:** If agricultural pullet placement dates shift due to seasonal farm cycles, the protocol initializes with real-world historical telemetry feeds from AT Grup’s existing active 200,000+ flock.
* **Seamless Live Switchover:** When the dedicated Season 1 batch becomes active, the Oracle Worker seamlessly updates the batch data stream to the live facility feeds without requiring smart contract modifications or migrations.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yolkfi.com/02.-technical-architecture/physical-asset-and-batches.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.