Free Tier, AI Assistant Revisions, and Project ZIP

This guide describes the current AI Blueprint workflow: what the Free Tier includes, how to revise a Blueprint through the AI Assistant without silent document changes, how to unlock the Project ZIP, and how to hand the ZIP to an AI coding agent.

1. Understand the Two Free Access Paths

The ordinary free preview is available once to an eligible new registrant who has not purchased a plan. It runs through App Map and is read-only. Downloads, the AI Assistant, final approval, Project ZIP, and documents after App Map are unavailable.

A free-trial AI-credit coupon is different. It adds AI Credits and unlocks every workspace feature for 7 days. Unused promotional credits expire with that access. The credit value comes from the displayed campaign and should never be inferred from an old example.

After an ordinary preview is complete and a plan payment is confirmed, you can regenerate the trial idea as a full Blueprint or start a new idea.

2. Prepare the Blueprint

1. Open the Blueprint and wait for every active run to finish.
2. Read the documents related to the requested change.
3. Write down the outcome, target document, reason, and content that must remain unchanged.
4. Confirm that a plan or promotional access is active and that enough AI Credits are available.

The AI Assistant uses approved Blueprint context. Never include passwords, API keys, tokens, OTPs, or customer personal data in the conversation.

3. Create a Proposal with the AI Assistant

Open the AI Assistant from Blueprint Summary or from a document selection action. Ask explicitly for a proposal when you want a change.

Create a proposal to add manager approval before an expense is paid.
Target Access & Security and the affected expense flow.
Preserve the approved login, other roles, and audit process.

If the Assistant gives advice first, say: Create a proposal from that recommendation. A proposal remains a draft. No document changes until you press Apply.

4. Choose the Right Revision Type

• Direct edit replaces a precise literal such as a colour, label, number, or duration in one document. Confirm both the old and replacement values.
• Rewrite one document when one document needs new wording or reasoning. State what must improve and what must remain.
• Major revision covers actors, features, rules, integrations, or scope. Keep related changes in separate reviewable proposals.
• Regeneration from a proposal rewrites affected documents from the currently approved Blueprint authority.

Review the summary, scope, impact level, target documents, and credit cost on every proposal card. Decline a proposal that expands scope without approval.

5. Apply, Verify, and Preserve Versions

1. Press Apply only on a correct proposal.
2. For several related changes, stage the proposals and use Apply all so regeneration does not run repeatedly without a need.
3. Wait for the run to finish. Do not create duplicate proposals while it is active.
4. Open every new document version and compare it with the request.
5. Use Revision history to inspect an earlier version when needed.
6. Resolve review notes and Sign Approve again after the Blueprint changes.

If credits are insufficient, the proposal remains safe to retry after a top-up. If the result is wrong, create a more specific correction proposal instead of overwriting it without history.

6. Unlock and Download Project ZIP

Project ZIP unlocks for a full Blueprint after every current document has been opened and reviewed, no run remains active, and Sign Approve Blueprint is complete.

When the workspace says Project ZIP is unlocked:

1. Open Blueprint Summary.
2. Press Export Project ZIP.
3. Save the ZIP to a local working folder.
4. Do not code inside the compressed file. Use Extract all first.

Package contents vary by project. Treat the actual manifest.json, implementation guide, PRD, schema, docs/, and staged prompts as the source of truth.

7. Start Coding with an AI Coding Agent

After extraction:

1. Make sure .env.local contains no production secrets and remains ignored by Git.
2. Create a Git baseline before the agent edits anything.
3. Ask the agent to read the manifest, implementation guide, AGENTS.md, PRD, schema, and relevant documents.
4. Run PROMPT_1.md for analysis and planning. Do not immediately ask the agent to build everything.
5. Review PLAN.md, conflicts, risks, and acceptance criteria.
6. Implement one stage or one vertical slice.
7. Run lint, typecheck, tests, build, UI inspection, and review git diff.
8. Commit verified work before the next stage.

Continue with the complete Project ZIP to Code guide.

8. Pre-development Checklist

• Correct proposals have been applied.
• Every changed document has been reviewed.
• The latest full Blueprint is approved.
• Project ZIP is downloaded and extracted.
• Secrets are absent from the repository and prompts.
• A Git baseline exists.
• The coding agent understands sources of truth and acceptance criteria.
• The first stage is small enough to verify.

Sources and Next Guides

• AI Blueprint Terms: /terms
• Project ZIP to Code: /en/learning/ai-coding/blueprint-to-code
• Git documentation: https://git-scm.com/docs
• OpenAI Codex documentation: https://developers.openai.com/codex