The project-scoped page Q10 and Q15 require: what this job is called, how much notice the homeowner needs, and the rule that a builder override can only make the runway longer.
These apply to the Hollis House, not to your whole account.
Frame 15 owns account and notification settings. This page owns facts about one build. Putting the lead-time default on 15 would make it look global, which is the bug Q15 exists to prevent.
Q10 says the default is {last_name} Home. The screen does not ask for a marketing name at signup; it lets the homeowner rename the binder once there is a binder to rename.
HouseChalk uses the longer notice period.
effective = max(homeowner, builder) is the backend rule, but the homeowner should not need to trust an invisible calculation. The screen says which value won and why.
The homeowner controls their runway. The builder controls his own production signal. Each side sees the result; neither side edits the other's value.
Lead-time settings affect derived due dates, but they do not mutate terms already sent through a link. A link is a record of what was asked at that moment.
PATCH /projects/:p/settings recomputes future system-derived dates in the same transaction. It does not rewrite sent link payloads or settled decision history.
These apply to the Hollis House, not to your whole account.
Central Texas. Expect heat load, expansive clay soil, and no freeze protection worries.
A new house
An addition
A renovation
Still working that out
Still figuring out what to build
No land, no plan. Everything is open.
We have land, no plan yet
The lot decides some of this. The layout is still yours.
We have a plan, not building yet
The best moment there is. Everything on that drawing is still a redraw.
We are building now
I will ask which stage next, and skip what's behind you.
This job is in a phase, Framing & Structure. The state can not move off "We are building now" while a phase is set, because the phase is where the work is. The change was not saved.
The setup facts are about this job, which is what the project-settings place is for. They join the built /house/settings screen as a second section rather than becoming a place of their own, so the name, the lead days and the three setup facts all live on one project-scoped page.
The line under the ZIP is computed on the device against bundle content. It is not a field the server returns, so the frame draws it as a reflection of the saved code rather than as data that came back from a save. A round trip for a string the device can already derive is the defect this line exists to prevent.
While a phase is set, the state can not leave "We are building now". The option stays tappable and the screen says what happens rather than graying it out, which is the deck's posture on every constrained control. The save is refused at the field, not the whole form.
These apply to the Hollis House, not to your whole account.
Account settings answer who you are and how you are told. Project settings answer what this one job is called and how much decision runway it needs. They are not the same object, and a screen that blends them would teach the wrong ownership model.
The homeowner default is the floor for their own runway. A builder can ask for more time, never less; the effective value is the longer of the two. Saving a project setting changes future derived dates, not already-sent links.