Application to collect firewood

When someone describes a proposed firewood collection, the rules work out two things automatically:

• What is and isn't allowed — whether the person may collect firewood, and which related activities (towing logs, using heavy machinery) are off-limits.
• What the application must contain — which details become mandatory when someone nominates another person to collect on their behalf.

Everything below is worked out by the same small set of rules, evaluated top-to-bottom: when two rules touch the same thing, the later one wins. That single idea explains the whole “can you collect?” decision.

You provide a fact the applicant enters. Rules work out a conclusion the rules calculate.

The status of “may the person collect firewood?” changes as three rules apply in order (later rules win): a Forbidden default; opened to Permitted when in a collection area and in season; then back to Forbidden if it also involves cutting/taking away trees and is within 20 m of a watercourse.

If the applicant nominates a person to act on their behalf, a set of Applicant and Nominee details become Required (given name and full address, plus the applicant's phone); title, other names and apartment number stay Optional. If no one is nominated, this section adds no requirements.

The six scenarios are well chosen as situations: collecting in a designated area during a season, collecting near a watercourse, towing/winching, bringing in heavy equipment, and the two nomination cases together touch every branch of the logic. The problem is that not one of them asserts an expected outcome — each supplies inputs but declares no expectation, so the suite runs the rules without ever checking them. A green run here proves only that evaluation didn't error, not that the answers are right.

To make the coverage real, add expectations such as: the designated-area-and-season case expects collectFirewood = Permitted; the cutting/taking-near-water case expects Forbidden (the watercourse override); the towing case expects includesTowingTrees = Forbidden; the two heavy-machinery cases expect their activity Forbidden; and the “with nomination” case expects the applicant and nominee fields to become required. A negative baseline (outside any area or season → Forbidden) and a case that would expose the missing family-name requirement would close the remaining gaps.