Hangarnest is still being built. You cannot create an account yet. What these pages describe is finished and running — it is just not open.

Trip log, rentals and access for the workshop

Three things that belong together, because in all three somebody else is involved: the tax office, a customer, a workshop.

The trip log has no gaps because it cannot have them

Two properties matter in a trip log: it must have no gaps, and it must not be alterable afterwards. Both are built in here rather than merely intended.

Whether a trip log is accepted is for the tax office to decide, case by case, and an electronic one has to meet further requirements — entries made promptly, for one. The application builds in the two properties. That is not a promise about any tax outcome, and nobody should read one into it.

Complete: the starting reading is not typed in. It is the closing reading of the previous trip, or for the very first trip the current counter reading. A gap cannot be entered, not even by accident.

Unalterable: there is no function that changes or deletes a trip. A correction is a new row pointing at the old one; both remain, and the list shows both. Only the correction counts in the total, otherwise the log would contradict itself.

On a private trip only the distance is kept. Destination, purpose and business contact are discarded rather than rejected. Somebody who typed something in by mistake should get a trip without the entry, not an error message.

Which axis is counted comes from the module. There is no "km" anywhere in the code, and an item without a main counter keeps no trip log.

A rental is not a booking

Under shared ownership, co-owners share a boat they own, and the question is fairness between them. In a rental, a business hands its item to a customer, and the question is handover, return and wear.

Three steps, each depending on the one before: you hand over what is booked, you take back what is out. The page only ever shows the step that is due. Three forms side by side would be three chances to press the wrong one.

Wear is read, not estimated. Both readings are recorded as counter readings, and a return reading below the handover reading is rejected. Photos from the handover record belong to the rental and do not turn up in the item's gallery.

The customer is a name with contact details, not a row in a CRM. That is a separate product, and until somebody needs it a name is worth just as much and is far less data.

What a yard may do

A short list, held in exactly one place: read items, propose completions, attach certificates. No costs, no counters, no master data, no deleting.

While a proposal is unconfirmed it counts for nothing. It moves no deadline, appears in no log book and in no recent activity. Otherwise a stranger would shift the service intervals of an item that is not theirs, and a claim would look like a fact.

The row belongs to the owner, not to the yard. A separate pot for outside entries would be a second history, and at the latest on sale somebody would have to decide which one applies.

Withdrawing access takes effect at once. What the partner wrote stays.

The audit trail

Who did what: append only, never edited, never deleted. An audit trail that can be tidied up afterwards is not one. It compares two stored versions rather than the row against the form input, otherwise it would report "attributes changed" on every save.

It is visible to whoever administers the organisation. In a shared setting, anything else would be surveillance nobody asked for.