01 · Publication state
A template cannot accept terms on behalf of a company
Enforceable terms need a clearly identified contracting party, a real contact method, a description of the service, eligibility and account rules, acceptable use, payment and refund terms, intellectual-property language, warranty and liability terms, termination, dispute handling, governing law, and an effective date.
The current template does not contain approved answers to those questions. This noindex page prevents the empty fields from being mistaken for a finished agreement.
02 · Current boundary
The Studio is pre-launch and planned offers are not for sale
The marketing site describes intended Single Piece, Signature, and Wedding Bundle packages. The production catalog and fulfillment path do not yet enforce those packages, and the current site does not offer checkout.
Legacy catalog items or development purchase surfaces must not be treated as the approved public offer. Store metadata, app behavior, server entitlements, and final terms must agree before launch.
03 · Commercial blocker
Credits and access must be enforceable on the server
A paid rewrite allowance is meaningful only if authentication, token verification, receipt validation, entitlement state, the credit ledger, and server-side consumption are implemented and tested. Client-side masking does not create a paid boundary.
Final terms must describe what a purchase grants, when a rewrite is consumed, how restore works, what happens after failure, and whether any access expires. The implementation must then match that description.
04 · Editorial boundary
The speaker must review the final manuscript
Vow & Voice can help preserve supplied details and shape language, but it cannot verify every fact, infer consent to share a story, or decide whether a joke is appropriate for a particular room.
Final terms should clearly assign review responsibility without using the contract to excuse misleading product claims. Names, relationships, events, quotations, promises, and potentially sensitive disclosures should all be checked before use.
05 · Legal blocker
Do not promise ownership until the governing language is approved
The public site does not make a blanket guarantee that a user owns every generated line or that output is unique. Final language must account for user-supplied material, service-provider terms, generated output, example-library content, and the limits of exclusivity.
The example library is authored product content. Selecting an example carries safe direction rather than the example prose into a new draft.
06 · Launch blockers
Decisions required before final publication
The project needs the legal entity and contact, eligibility rules, account and authentication terms, final product and credit definitions, prices and taxes, refund and restore rules, acceptable use, user-content permissions, output and example-library rights, termination, disclaimers, liability limits, indemnity if appropriate, governing law, dispute process, effective date, and update notice.
Counsel and the product owner must resolve those fields against the final purchase and data flows. A visual or engineering implementation cannot decide them safely.