# Zusey — Setup Worksheet

Use this worksheet to define one AI work-product project before substantial work begins. Complete what you know and write `To be determined` where a decision has not been made.

The worksheet can be completed by one person, by a team, or in conversation with an AI assistant. Do not include confidential, regulated, personal, or commercially sensitive information unless the project location and AI service are approved for it.

## 1. Project identity

- **Project name:**
- **Project owner:**
- **Solo or team project:**
- **Business purpose:**
- **Primary outcome:**
- **Primary audience:**
- **Why this work needs to survive the original conversation:**
- **Definition of done:**
- **Target date, if applicable:**

## 2. Expected work products

What should exist as named files when this project is complete?

- **Primary deliverable:**
- **Supporting deliverables:**
- **Decisions that must be recorded:**
- **Status or continuity information that must be maintained:**
- **Final format needed:** Markdown / Word / PDF / PowerPoint / Spreadsheet / Web page / Other:

## 3. System of record

The system of record is the location containing the authoritative project files. It should remain understandable without the original AI conversation.

- **Parent location:**
- **Actual child project folder:**
- **Folder owner:**
- **Who can access it:**
- **Synchronization service, if any:**
- **Version history available:** Yes / No / Unknown
- **Backup or recovery method:**
- **Retention requirements:**
- **Approved for the project's sensitivity:** Yes / No / Needs review

Confirm each item before relying on this location:

- [ ] I know where the authoritative files live.
- [ ] I can recover an earlier version or backup.
- [ ] Access is limited to appropriate people.
- [ ] The location is approved for the information involved.
- [ ] Another authorized person could find the project if I were unavailable.

## 4. Codex project type

Select one:

- [ ] **Local** — Codex works directly with the actual project folder on this computer. This is the default for the AI Work Product System.
- [ ] **Remote** — The actual project folder lives on an approved connected machine.
- [ ] **Cloud** — The project uses hosted context and requires a separate preservation process.

If Cloud is selected:

- **External system of record:**
- **Export or synchronization owner:**
- **Checkpoint frequency:**
- **Recovery test:**

## 5. Work-product profile

Select the primary kind of work. Choose based on the main deliverable, even when the project includes supporting activities.

- [ ] General Purpose — mixed work, unfamiliar work, or early exploration
- [ ] Content Publishing — articles, posts, newsletters, or thought leadership
- [ ] Startup Exploration — business idea, venture research, or validation
- [ ] Creative Writing — novel, screenplay, story, or narrative project
- [ ] Research and Report — evidence-backed research, findings, or recommendations
- [ ] Client Engagement — consulting, advisory, agency, or professional services
- [ ] Product Planning — product discovery, requirements, roadmap, or launch
- [ ] Course and Training — curriculum, lessons, workshops, or assessments
- [ ] Policy and Procedure — policies, procedures, standards, or controls
- [ ] Data Analysis — spreadsheet analysis, reporting, forecasting, or findings
- [ ] Proposal and Bid — proposal, RFP, bid, grant, or formal submission

- **Selected profile:**
- **Reason it fits:**
- **Profile version, when installed:**

## 6. Sources and intake

List the material the AI may need to reference.

| Source or source type | Owner | Location | Authority | Sensitivity or rights concern |
|---|---|---|---|---|
| Example: approved brand guide | Marketing | `02 Sources/brand-guide.pdf` | Authoritative | Internal use |
|  |  |  |  |  |
|  |  |  |  |  |
|  |  |  |  |  |

Possible sources include spreadsheets, research, logos, brand guidance, customer notes, transcripts, templates, earlier plans, policies, and client-provided material.

- **May the AI organize new Intake files?** Yes / No / Ask first
- **Must original source files remain unchanged?** Yes / No
- **Who decides whether a source is authoritative?**
- **Who may authorize the use of licensed or third-party material?**

## 7. Working states and approval

- **Working state names:**
- **Review state:**
- **Approved or final state:**
- **Archive or superseded location:**
- **Who reviews the work:**
- **Who can approve it:**
- **Who can authorize publication or external sharing:**
- **Who can authorize deletion or replacement of approved material:**

The AI may help prepare and organize work, but it must not declare material approved, final, published, or authorized for external use without the designated person's confirmation.

## 8. AI working permissions

For each activity, select `Allowed`, `Ask first`, or `Not allowed`.

| Activity | Choice |
|---|---|
| Create new working documents |  |
| Update existing working documents |  |
| Organize files placed in Intake |  |
| Move or rename existing files |  |
| Replace a file |  |
| Delete a file |  |
| Change approved or final material |  |
| Use external websites or connected sources |  |
| Publish or send material externally |  |

- **Actions that always require a person:**
- **Files or folders the AI must not change:**
- **Required citation or source-identification behavior:**

## 9. Save-checkpoint behavior

The AI should suggest saving when reusable work exists only in the conversation.

Select the natural checkpoints that apply:

- [ ] A substantial draft, plan, analysis, or other reusable output emerges.
- [ ] An important decision is accepted.
- [ ] Evidence supports or contradicts a material claim.
- [ ] The project direction changes.
- [ ] The user changes topics after substantial work.
- [ ] The session appears to be ending.

- **Preferred checkpoint document:**
- **Preferred status document:**
- **Anything that should remain chat-only:**

## 10. Team responsibilities

Complete this section for a team project.

| Responsibility | Person or role |
|---|---|
| Project owner |  |
| Source owner |  |
| Primary editor |  |
| Reviewer |  |
| Final approver |  |
| Storage and access administrator |  |
| Recovery or backup owner |  |

- **How will team members know which version is current?**
- **How will review comments and decisions be recorded?**
- **What happens when an owner leaves or becomes unavailable?**

## 11. Setup completion check

- [ ] The project has one clear purpose and owner.
- [ ] The actual child project folder is selected as the Codex project folder.
- [ ] A suitable profile has been installed.
- [ ] A root `AGENTS.md` contains the permanent project instructions.
- [ ] The brief has been initialized from this worksheet.
- [ ] Intake and source locations exist.
- [ ] Source-handling rules are clear.
- [ ] Working, review, approved/final, and archive boundaries are clear.
- [ ] Human approval authority is recorded.
- [ ] The AI's allowed and restricted actions are recorded.
- [ ] A new Codex task can summarize the project without the setup conversation.
- [ ] Recovery or version history has been tested.

## Codex setup prompt

After completing this worksheet and placing it in the intended project folder, start a Codex task with:

> Read `PROJECT-SETUP-WORKSHEET.md`. Summarize the intended project and identify missing or conflicting answers. Recommend the best work-product profile. Then show me the proposed folder structure, documents, and file changes required to complete setup. Preserve all existing files and ask before moving, replacing, or deleting anything. Do not make changes until I approve the setup plan.

After the setup plan is approved and completed, start a fresh task with:

> Summarize the project purpose, current status, source-handling rules, save-checkpoint behavior, and approval boundaries you found in this folder. Do not change any files yet.