Source: https://guthlabs.ai/docs/project-templates/website-surface/forms/

project template / candidate

# Website surface — forms

The distinct forms record for Website surface. This page is proposal-only.

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: project:website-surface

**Parent lifecycle**: candidate

**Page lane**: forms

**Lane lifecycle**: proposed

**Owner**: Not separately recorded

**Owner role**: Not separately recorded

**Owner status**: Not separately recorded

**Qualification result**: NOT RUN · held for evidence and human review

**Working browser surface:** [Project templates & workflows — overview](<https://guthlabs.ai/labs.html#templates-workflows>) — Create a local project from this template and validate its forms. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

### Intake

Define why the website surface is being proposed and establish accountable ownership.

- project title

- requestor

- project owner

- business or public purpose

- target audience

- proposed surface type

- requested start date

- target release date

- success measures

- known constraints

- source records and locators

- visibility classification

### Scope and claim boundary

Separate included work from exclusions and prevent unsupported public claims.

- in-scope pages or sections

- out-of-scope pages or sections

- supported claims

- claim evidence references

- claims requiring review

- claims explicitly held

- crawl and indexing intent

- accessibility target

- content and media requirements

- release definition

- non-production disclaimer

### Milestones and deliverables

Create ordered deliverables with owners, dates, acceptance criteria, and status.

- milestone name

- deliverable

- milestone owner

- planned start

- planned finish

- status

- preceding milestone IDs

- acceptance criteria

- evidence required

- review required

- revision notes

### Deadlines and workback

Turn the target release date into dated, reviewable workback items.

- target release date

- deadline name

- due date and time

- priority

- recurrence candidate

- completion state

- responsible owner

- reviewer

- buffer days

- dependency IDs

- late action

- reschedule reason

- revision history

### Dependencies and handoffs

Record prerequisites, external inputs, blocked states, and handoff conditions.

- dependency description

- dependency type

- source or owning record

- dependency owner

- needed-by date

- status

- blocking severity

- handoff artifact

- failure or fallback path

- last checked timestamp

- resolution note

### Owners and authority

Make record ownership and approval authority explicit without implying automated authority.

- role

- named owner

- backup owner

- owned records

- decision authority

- review authority

- handoff date

- contact or context note

- unavailable-state procedure

### Tools and guides

Link designated local surfaces and source-backed procedures to each project stage.

- tool or guide name

- kind

- route or record reference

- intended use

- stage

- owner

- inputs required

- outputs produced

- authority boundary

- held capability note

### Evidence and receipts

Preserve traceable support for content, crawl, accessibility, and release decisions.

- evidence ID

- evidence type

- related claim or requirement

- source locator

- source SHA-256 if available

- capture date

- captured by

- attachment or local file reference

- result

- limitations

- revision

- provenance note

### Approvals and release gates

Collect independent review decisions and preserve held or approved outcomes.

- approval gate

- proposal under review

- reviewer

- decision: Needs review/Approved/Held

- decision date

- conditions

- supporting evidence IDs

- unresolved issues

- receipt or revision reference

- next action

### Risks and failure states

Expose delivery, claim, crawl, accessibility, privacy, and release risks before closure.

- risk description

- category

- likelihood

- impact

- severity

- trigger

- owner

- mitigation

- contingency

- status

- review date

- residual risk

- blocked release flag

### Closure

Confirm what was completed, what remains held, and how the project record is preserved.

- closure date

- closure owner

- delivered scope

- deferred scope

- approved claims

- held claims

- completed milestones

- open risks

- evidence completeness

- approval completeness

- final record revision

- follow-up work

- closure decision

- reason if not closed

### Accessible state contract

- Every field requires a visible and programmatic label.

- Required and optional fields must be stated in text.

- Invalid entries require an actionable message linked to the field.

- Blocked and Held states remain visible without relying on color alone.

## Supporting documentation fields

These fields come from the app_features lane and remain separate from the primary operating form.

### Surface identity

Define ownership and the bounded website surface.

- project title

- surface purpose

- owner

- working status

- target audience

- canonical local project ID

- visibility

### Scope and routes

Record the pages and route candidates without implying deployment.

- route or page title

- proposed path

- page purpose

- audience

- content owner

- source record links

- in-scope flag

- external dependency note

### Claims and evidence

Separate proposed public claims from evidence and held claims.

- claim text

- claim type

- source locator

- source SHA-256 if available

- provenance note

- confidence

- public-claim status

- reviewer

- review note

### Crawl and link review

Track local review of links, destinations, labels, and failure states.

- source page

- link label

- destination

- link type

- expected status

- observed local status

- failure description

- replacement or hold note

- review date

### Accessibility gate

Review keyboard, semantics, text alternatives, focus, motion, and contrast before release review.

- criterion

- page or component

- test method

- result

- evidence link

- severity

- remediation owner

- remediation due date

- reviewer

### Deadline and workback

Turn a target review or release date into explicit local work.

- target date

- date type

- timezone

- milestone name

- milestone due date

- duration estimate

- dependency IDs

- owner

- priority

- recurrence candidate

- completion state

### Release decision

Preserve a human-reviewed proposal and its unresolved gates.

- decision status

- approver

- approval date

- open blockers

- held effects

- release notes

- receipt links

- next review date

## Required or proposed record references

No record existence is asserted by this documentation page.

- project record

- scope record

- milestone records

- deadline to-dos

- dependency records

- owner assignments

- workback record

- tool and guide links

- evidence records

- approval records

- risk records

- closure record

- claim records

- page or route records

- source-labelled notes

- file references

- accessibility review records

- crawl review records

- workback milestones

- approval record

- release receipt

## Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

- `source_record:project:website-surface`

- `NotebookCollectionKind.project`

- `NotebookTodoPayload.dueAt`

- `Notebook Agenda deadlines/workbacks`

- `Observed native contract: project_and_field_guide_collections`

- `Observed native contract: deadlines`

- `Observed native contract: records`

- `Observed native contract: pointguard`

- `Observed native contract: web_boundary`

- `APP_ROUTES:/app/notebook/projects/`

- `APP_ROUTES:/app/notebook/to-dos/`

- `APP_ROUTES:/app/notebook/agenda/`

- `APP_ROUTES:/app/notebook/approvals/`

- `APP_ROUTES:/app/notebook/notes/`

- `APP_ROUTES:/app/notebook/files/`

- `APP_ROUTES:/app/notebook/field-guides/`

- `APP_ROUTES:/app/notebook/search/`

- `APP_ROUTES:/app/pointguard/`

- `project:website-surface`

- `Notebook records provenance and revision contract`

- `PointGuard persistent cross-app context surface`

- `APP_ROUTES:/app/notebook/paper/`

- `ALLOWED_INSTRUMENTS:wcag-contrast-ratio-checker`

- `ALLOWED_INSTRUMENTS:reading-time-estimator`
