# Workspace

## Purpose

Workspace is the project-specific owner working area. It replaces the old `Owner` concept in the clean root and holds intake, drafts, assets, documents, references, exports, and scratch work that belong to this project.

Workspace keeps owner-owned material separate from reusable repository logic such as standards, capabilities, automation, durable plans, and publishable content.

## What Belongs Here

- Owner notes and rough ideas.
- Owner-specific open questions.
- Intake material, drafts, assets, documents, references, exports, and scratch notes.
- Platform notes, proof, profile material, portfolio material, website inputs, and marketing notes when they have a real project use.
- **Owner Preferences** — connector, intake, mirror, and import settings in `OwnerPreferences.md`.
- **Valuable References** — candidate and owner-approved external URLs in `ValuableReferences.md`.
- Working files that need review before promotion into a durable repository folder.

## What Does Not Belong Here

- Durable agent instructions. Use `AGENTS.md` when approved.
- Reusable standards. Use `Standards`.
- Reusable capability prompts, rules, or structures. Use `Capabilities`.
- Approved or structured plans, audits, reviews, or backlog material. Use `Plans`.
- Publishable website, product, or content source. Use `Content`.
- Automation or helper scripts. Use `Automation` only after a repeated need is approved.

## Promotion Boundary

Workspace is not durable agent instruction. Material here should affect future agent behavior only after it is intentionally promoted into `Ideas`, `Plans`, `Capabilities`, `Standards`, or `Content`.

## Core Boot Files (Present Now)

- `OwnerGoals.md` — practical outcomes from Quick Startup.
- Environment notes live in `OwnerPreferences.md` Environment section (optional).
- `OwnerMilestones.md` — measurable outcomes tied to Owner Goals (optional).
- `OwnerPreferences.md` — connector, intake, mirror, and import settings.
- `ValuableReferences.md` — candidate and approved external URLs; owner-reviewed.

## Child Folders (Create On First Use)

Do **not** pre-create empty child folders or `.gitkeep` stubs on the host or in
the consumer starter. When real content needs a home, add **one** folder with its
own `README.md`:

| Folder | Create when |
| --- | --- |
| `Notes/` | First rough owner note |
| `OpenQuestions/` | First owner-specific question (not repo `Plans/OpenQuestions.md`) |
| `Drafts/`, `Assets/`, etc. | See [IntendedRepositoryTree.md](../Capabilities/RepositoryScaffold/IntendedRepositoryTree.md) `[WHEN NEEDED]` |

Future folders such as `BusinessPlan`, `OnlinePresence`, `OnePageWebsite`,
`Resume`, `Profile`, `Portfolio`, `ProofAndAssets`, `PlatformSetup`, and
`Marketing` should wait until real content or an approved task exists.

See [../Capabilities/RepositoryScaffold/IntendedRepositoryTree.md](../Capabilities/RepositoryScaffold/IntendedRepositoryTree.md) for the consumer growth map.

## Agent Notes

- Treat Workspace as protected owner content.
- Do not invent owner facts, credentials, offers, proof, testimonials, business claims, or platform decisions.
- Do not overwrite, move, rename, or restructure owner files without explicit approval.
- Keep drafts in plain Markdown unless a future task explicitly chooses another format.
- Add new child folders only when they have an immediate purpose and their own `README.md`.
