# VertexLineup public study specimens: source and usage notes

1 October 2026. The studies demonstrate studio-owned work and newly labelled illustrative calculations. No client commission or outcome is claimed.

## Identity

- Ink and Space SVGs are original studio deliverables from `assets/brand/` and `outputs/vertexlineup-ink-and-space/assets/logos/`.
- Signature SVGs are the studio's historical outlined logo deliverables from `outputs/vertexlineup-brand-system/svg/`.
- Palette, type roles and the Signature branch follow the selected identity in `VL-CONTEXT.md` and the implemented `BRAND-SYSTEM.md`.
- Application covers are studio-owned specimens, not client projects.
- Copy before/after examples quote current `about.html` paragraphs and propose labelled editorial revisions. No performance uplift is claimed.
- Downloading a studio logo for inspection does not transfer the VertexLineup identity or grant permission to use it as another business's logo.

## Planning

- The ten-section plan structure and selected model mechanics come from `VL-BUSINESS-PLAN.md` and `VL-MODEL-NOTES.md`.
- The public example uses sixteen explicitly classified inputs. Owner-approved prices and website terms remain different from unmeasured hours and fictional sales inputs.
- `illustrative-default-forecast.csv` contains the unchanged twelve-period default specimen. The browser CSV export captures the viewer's edited inputs.
- `forecast-assumption-register.csv` records all fixed and editable defaults with units, evidence class, source basis and the check needed before use.
- `business-plan-review-checklist.md` is a reusable blank preparation checklist.
- The small example uses twelve equal thirty-day periods, uniform project starts and one website/care mix. It excludes GST, owner drawings, income tax, finance, capital purchases, bad debt, delayed final collections and automatic contractors.
- These files are not financial statements, tax advice, a funded application or a lender's acceptance. The actual business's records and qualified review are required.

## Automation

- Scope and review boundaries follow `VL-PUBLIC-SERVICES.md`, `VL-CONTEXT.md` and the studio AI workflow in `VL-BUSINESS-PLAN.md`.
- The public routing rules are deterministic and browser-local.
- `intake-routing-specimen.md` is the default worked example. The visible-brief export captures the sample currently shown on the page.
- No external AI, mailbox, customer database or business account is connected.
- No sample input is sent, saved or executed by these study scripts. Shared optional-analytics behaviour remains governed by the site's privacy controls.
- Connected-account logging, duplicate control and real execution need a separate scoped implementation and tests.

## Review boundary

Dhairya remains responsible for scope, facts, permission, design decisions, testing and release. Specialist accounting, legal, funding or regulatory decisions require the relevant qualified reviewer. These samples make the work inspectable; they do not establish paid demand or client results.