Collaborators, approval, and AI
Let people and automation help without losing authority or traceability.
This capability is implemented for the scope described here. Production acceptance may still be named explicitly.
Separate people, separate credentials
Accounts invite collaborators with individual identities, expiry, role boundaries, session controls, and attributable activity. Shared passwords are not the collaboration model.
Preview before consequence
Editing a draft is different from publishing it. Content, reconstruction, theme, and AI changes are reviewed against the real renderer before an authorized approval creates a new draft or publication.
AI is an operator
AI uses supported structured operations. It does not receive permission to rewrite arbitrary HTML or silently publish. Requests, proposals, validation, decisions, and resulting versions remain attributable.
Request → Structured proposal → Validation
→ Diff and preview → Human decisionCurrent roles and future refinement
The proof supports owner and account-manager workflows with explicit publication authority. More outcome-oriented roles for editing, design, growth, integrations, and approval should be introduced only with tested permission boundaries.