Creative intent should travel with the work.

1. The problem

Creative briefs, reference boards, license notes, model prompts, and review responsibilities often live in separate tools. That fragmentation makes it difficult for an independent creator, studio, or client to reconstruct what was intended and which rights assumptions informed the work.

A polished output alone cannot explain provenance. Formaia focuses on the earlier decision trail: intent, source status, permitted transformations, prohibited uses, human accountability, and required attribution.

2. The product

The workspace contains four connected layers: a Visual Brief, an Assets & Rights list, AI Use Boundaries, and a deterministic completeness check. A user can then issue a portable JSON manifest with a SHA-256 content receipt.

Formaia does not generate imagery, inspect source files, upload user assets, call an AI model, or decide whether a use is legally permitted. It structures user-provided declarations so people can review them together.

3. Local-first data flow

1. The user enters project labels and rights information in the browser.
2. The draft is stored in that browser’s local storage.
3. Deterministic rules evaluate required fields and declared risk states.
4. When requested, the browser normalizes the data and calculates a receipt.
5. The user may copy or download the JSON. No automatic upload occurs.

Clearing site data, changing browsers, or using a different device can remove or isolate the draft. Users should download manifests they need to retain.

4. Manifest schema

The versioned payload includes four top-level areas: brief, assets, boundaries, and completeness. Brief fields cover project name, visual goal, use case, and style keywords. Asset records cover name, source type, authorization status, AI-training permission, generative-editing permission, and notes. Boundary records cover tool name, permitted use, prohibited use, human reviewer, and attribution.

Identifiers used only by the editing interface are omitted from the normalized payload. Whitespace is normalized and object keys are sorted before hashing so equivalent content produces a stable receipt.

5. SHA-256 verification

Formaia uses the browser’s Web Crypto implementation of SHA-256 over canonical JSON. The receipt has the form sha256:<64 hexadecimal characters>. Verification recomputes the digest from the manifest payload and compares it with the stored receipt.

The receipt detects content changes. It does not independently prove who created the record, when the rights were obtained, whether a statement is true, or whether a legal claim is valid. The human-readable generation time is metadata and is not a trusted timestamp.

6. Wallet identity and optional proof

Wallet connection is a separate read-only action. It requests only the user-selected public account and active chain ID. Connection does not request a signature, approval, payment, token allowance, or transaction.

A future deployment could add a separately reviewed on-chain anchor for a manifest receipt. This public release has no trusted anchoring contract configured. Receipts therefore remain honestly labeled local; the interface does not fabricate pending or confirmed chain states.

7. Points and optional 0.01 BOT upgrade

A user may activate 100 points as a distinct local action without connecting a wallet. An optional upgrade is displayed as exactly 0.01 BOT for 200 total points. It requires an initial preview and a second explicit confirmation. The preview shows the amount, recipient configuration, network label, and wallet state.

When no trusted recipient is configured—as in this release—the confirmation records only a clearly labeled simulated local state and sends no transaction. Points have no cash value. They are not an investment, security, deposit, entitlement, or promise of an airdrop. Any future benefit remains uncertain and discretionary.

8. Risks and responsibilities

• Users can enter inaccurate or incomplete rights information.
• A cleared label is a declaration, not legal verification.
• A hash can prove payload consistency but not truth or lawful use.
• Wallet addresses are public identifiers and may expose activity on public networks.
• Optional transactions, if configured later, can be irreversible and incur network fees.

Users remain responsible for source rights, releases, license compatibility, tool terms, disclosure duties, attribution, human review, and the final use of creative work.

9. Privacy and security

The core draft stays in local storage and assets are not uploaded. Formaia intentionally avoids analytics, advertising trackers, remote model calls, and unnecessary third-party services. A user chooses whether to copy, download, connect a wallet, or take any optional transaction action.

Local-first design reduces collection but does not make a device immune to compromise. Users should protect their browser profile, downloaded manifests, and wallet. Never treat the manifest as a place for secrets, private keys, passwords, or sensitive personal data.

10. Roadmap

Near-term work may include manifest import, version comparison, organization-specific rule packs, accessible print layouts, and interoperable schema documentation. Longer-term exploration may include optional proof anchors and collaborative handoffs, but only with explicit consent, transparent configuration, and honest state reporting.

11. Non-commitment statement

This whitepaper describes a present product and possible directions. It is not legal, financial, or investment advice; it is not an offer to sell anything; and it does not promise a token, airdrop, return, marketplace, chain deployment, or future feature.