# equinoxbusinesslaw — planning

> Plans live here as individual `.md` files with `type: plan` frontmatter, so atlas can scan and render them. A plan is forward-looking; once it is delivered, its record belongs in the changelog and diary.

Read `brief.md` at the workspace root first, then the plan that matches your task. `scope.md` is
the contract; the other seven say how it gets delivered. None of them contains pricing; add-ons and
plans are named only. Paths in the table below are relative to this folder (`.logs/planning/`).

| File | What it answers | Read it when |
|---|---|---|
| `scope.md` | What was sold: every contracted deliverable from the accepted proposal (sent 2026-07-30, accepted 2026-08-13), add-on status (Hosting and Design Mockup and Review Round accepted 2026-08-13; Fractional General Counsel Landing Page with Tiered Pricing pending since 2026-08-13, client interested but wants to discuss further; Practice Area and Topic Hub Architecture not accepted, not mentioned in the 2026-08-13 acceptance), exclusions, assumptions, things to confirm. | Before starting any work item, or when someone asks "is that in scope?" |
| `build-plan.md` | How the build runs: locked decisions, phases with gates, week mapping, definition of done, risks. | Starting a session, planning a week, or deciding whether a gate has been passed. |
| `site-architecture.md` | The page inventory with a disposition per live URL, the target sitemap and navigation, the URL and redirect plan, the templates, and the 9-person team roster. | Creating, renaming, retiring, or redirecting any page; building nav, header or footer. |
| `content-migration.md` | Moving 513 posts (as of 2026-09-02), pages, media, users and taxonomy from the live site to staging: mechanics, the author audit, placeholder-content rules, verification. | Exporting, importing, or touching authors, categories, tags or media. |
| `schema-entity-plan.md` | The entity and structured-data plan, delivered by configuring `bw-ai-schema-pro`: the canonical firm entity, Person entities for the team, author-to-bio binding, Service, Article and FAQ schema, validation. | Installing or configuring schema, editing team bios, adding FAQ content. |
| `design-direction.md` | The client's written design requirements (2026-08-27), brand inputs, the mockup process and its gate, and the design checklist. | Before the mockup, during page build, and at every design review. |
| `homepage-mockup-brief.md` | Step 1 of the design mockup round, set 2026-09-02: two home-page mockups showing two design directions, home page only. What was promised, what the client said, what the home page must achieve, the section-by-section requirements, how the two directions must differ, the scope fence, the factors to carry into the build, the pre-flight checklist. | Before any design work, and whenever a design request arrives that might be outside scope. |
| `tracking-conversion.md` | The tag inventory and preservation checklist, CTA structure (direct plus transitional), forms, the Business Legal Health Assessment (name to be confirmed) embed, Pipedrive routing, and launch verification. | Touching GTM, forms, CTAs, the assessment, or preparing for launch. |