> For the complete documentation index, see [llms.txt](https://docs.output.industries/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.output.industries/technical-onboarding/release-notes/2026/week-6-or-2026.md).
# Week 6 | 2026
### **Featured Update: Edit Parts Per Cycle**
* "Edit PPC on tablet" is accessible if the feature flag is enabled in the station settings.
* This allows the operator to change the quantity they will produce for the next cycle only. The PPC will revert to the standard quantity after the cycle.
### **Featured Update: Next Schedule on Tablet**
* As standard, the operator can view the next schedule on the tablet.
* Tapping the grey box will dropdown and display the scheduling information for the upcoming schedule.
### **Improved Accuracy:** New look Cockpit
* The updated cockpit design, includes the addition of the "Next Schedule" display.
* There are also quick select buttons on the left to go straight to setting up a new schedule or view the operator tablet.
### Improved Accuracy: New look Reasons Management
• Reasons management now allows you to view the parent reasons with the individual reasons below using dropdown functionality.
---
# 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.output.industries/technical-onboarding/release-notes/2026/week-6-or-2026.md?ask=&goal=
```
`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.