KinoForms Product and Design Draft Review

Status: Owner review requested; nothing in this document is a final pricing, brand, or legal commitment.

Last updated: 2026-07-13

What Was Drafted

• PRODUCT.md (repository root): default product register, users, purpose, personality, anti-references, principles, and accessibility target.
• DESIGN.md (repository root): extracted interface tokens and proposed rules for future product work.
• .agents/product-marketing.md (repository root): shared positioning context for future marketing tasks.

Decisions Already Supplied

• KinoForms remains free during early access; paid prices are not being invented in these drafts.
• The Free tier does not receive file storage.
• File-storage eligibility must be adjustable without another code change. The backend knob is FILE_STORAGE_ALLOWED_TIERS, defaulting to professional,enterprise.
• Product and design context may be drafted now and reviewed later.

Review Checklist

Mark each line approved, change, or add notes.

Topic	Draft hypothesis	Owner decision
Default register	Product UI first; marketing uses a per-task brand override	Pending
Primary audience	Agencies, program teams, operations teams, and client-service teams	Pending
Core positioning	Conditional logic form builder for controlled form submissions	Pending
Brand personality	Grounded, capable, careful	Pending
Creative north star	“The Navigator’s Workbench”	Pending
Accessibility target	WCAG 2.2 AA, keyboard complete, reduced motion, non-color-only state	Pending
Product typography	DM Sans for task UI; DM Serif reserved for marketing/rare high-level moments	Pending
Product palette	Keep the now-audited semantic OKLCH tatami palette as the product token source of truth	Pending
Anti-references	No generic form-builder toy aesthetic, generic SaaS scaffolding, or unsupported enterprise/compliance theater	Pending
Named visual references	Intentionally unset until owner supplies examples	Pending

Pricing and Packaging Still Open

These were intentionally not guessed:

• Paid tier names and prices.
• Final public storage quota per allowed tier; the current environment defaults are implementation policy, not approved packaging.
• Hard limit versus paid overage behavior.
• Downgrade and retention behavior for already stored objects.
• Billing provider activation and grandfathering policy.

The current implementation controls both eligibility and quota accounting for branding assets and private respondent attachments. FILE_STORAGE_ALLOWED_TIERS=professional,enterprise means those tiers may use configured storage, subject to the environment's per-tier quota and any audited team override; those values are not approved public packaging and do not promise unlimited storage.

Evidence Boundaries

• No validated customer quotations, approved testimonials, customer logos, conversion metrics, or outcome metrics were found.
• Marketing preview counts are illustrative UI data, not customer proof.
• “Secure” must describe concrete access, validation, roles, API scopes, and workspace separation; it must not imply certification.
• Respondent file uploads use private immutable object reservations, capability-bound claims, sanitized stored descriptors, authorized signed downloads, quota accounting, and retention cleanup. Public copy must still state that Free has no file storage and that availability depends on configured private storage plus the tier allowlist.
• AI remains feature-flagged and should not become the lead product position without an explicit product decision.

Security and Retention Decisions Still Open

• Respondent account claim: public duplicate registration now fails closed without changing the existing account, and recovery requires the existing password or emailed magic-link proof. Keep that ownership-proof contract unless the owner explicitly chooses a stricter access model.
• Deletion grace period: immediate undeploy plus a seven-day restore window is implemented as the operator-adjustable default. Confirm the duration before treating it as final product policy.
• Permanent purge: confirm how database records, object storage, audit records, and backups age out after the restore window.

Sources Used

• marketing.md for direct positioning and copy restrictions.
• apps/web/src/lib/public-seo.ts for current public positioning, use cases, and workflow language.
• apps/web/src/index.css for application tokens and typography.
• apps/web/src/pages/marketing.tsx for the public palette and layout conventions.
• apps/web/src/components/ui/ and apps/web/src/components/layout/ for product component behavior.
• packages/renderer/src/kits/shadcn/themes/presets.ts for respondent theme boundaries.
• docs/user-guide/forms/form-builder.md, docs/operations/private-attachment-storage.md, and featureflags.md for the current respondent-attachment boundary.

How to Review Later

Start with the ten-row checklist above. Then read PRODUCT.md for strategy and DESIGN.md for visual rules. Corrections should be applied to this review document first so the rationale remains visible, then propagated to both reference files and .agents/product-marketing.md.