Reuse the plan, not the packing list
A kit carries reusable structure into an event. The event keeps its own packing decisions, then preserves review by cycle so the next run starts with context.
By Jak
Copying an old packing list can be a useful start. The copy does not automatically become wrong, but it has no shared source and may not explain what changed after the last use.
BorderKit separates the reusable part from the decisions that belong to one event. A kit carries the structure worth using again. The event keeps its own plan, packing state and review.
Put reusable structure in a kit
A kit is a purpose-driven planning asset. It can link directly to owned gear, hold category requirements, or combine both. A charging kit might name a particular adaptor and cable while leaving another requirement at the category level until the right item is known.
That is more useful than defining a kit as a folder. The point is not where an item is filed. The point is that a recurring preparation need has one place to be maintained.
This does not mean every bundle deserves a kit. A one-off selection can stay in one event. A kit earns its place when its purpose and composition provide a useful starting point in more than one real situation.
Bring the kit into a real event
An event is a planned use, not a reusable template. Adding a kit copies its current gear and requirements into the event with a record of where they came from. The event can then adjust quantities, resolve different gear or remove something without changing the source kit.
The connection remains deliberate. If the source kit changes later, BorderKit can preview an explicit sync. It does not silently push the change into every event. This protects the decisions already made for a particular use while still making kit improvements available to consider.
Carry the plan into the next cycle
After an active event has been reviewed, Start next cycle keeps its entries and kit links, resets packing, returns the event to planning and advances the cycle number. The next run begins with the existing plan rather than an empty page.
Quick Review stores a thumbs-up or thumbs-down only when you choose one for an item, requirement or whole kit. A thumbs-down can include a specific reason and an optional note. The review belongs to that event and cycle; it does not change gear, kits or categories by itself.
On the next cycle, BorderKit can show the previous outcome beside the relevant row and offer a direct refinement such as adjusting a quantity, swapping gear or removing the row. The person preparing still decides whether to act. Review provides context, not an automatic verdict.
Preserve the lesson without freezing the plan
Reviews are stored by cycle, so a later run does not overwrite an earlier one. Once the next cycle starts, the closed cycle's review cannot be edited. The gear and kit detail pages can still show that history across events.
The event itself remains usable. It can move between planning and packing, start another cycle, or be archived as a read-only record and restored later. Reusable preparation is not a promise that every trip stays the same. It is a way to begin with what is already known, keep each event's decisions local, and carry evidence from one use into the next.