Ownership
Ownership of Prompts, Content, and Outputs
The client should own the site, the source, and the instructions that shape it. A model vendor should not.
Published pages are project files
Once a draft is approved, it lives in the repository as content the client can take with them. It is not trapped in a chat transcript.
That is the same ownership rule we use for design and code.
Prompts are deliverables
Instructions that define voice, exclusions, and task shape belong in the project. If we leave, the next person should not have to reconstruct them from memory.
Personal prompt libraries are fine for experiments. They are not the production record.
Accounts are named and transferable
Provider accounts for GPT, Gemini, Grok, or Claude, when used in production, should be the client’s. We can help configure them. We should not be the only person who can turn the feature off.
Billing, keys, and admin access are part of launch, not a later favor.
Continue
What Building Sites for the Future Means
A concrete definition of a future-ready Alaska website: static delivery, owned source, and optional use of GPT, Gemini, Grok, and Claude.
Read →Sites Built for the Future
How alaskawebsite.dev builds for what comes next: fast static sites, and practical integration of GPT, Gemini, Grok, and Claude.
Read →Integrating GPT into Website Projects
Where GPT fits in an Alaska website project: drafting, structured extraction, coding assistance, and selective live features.
Read →