Source: https://guthlabs.ai/docs/field-guides/brand-voice/steps/

field guide / candidate

# Brand voice — steps

The distinct steps record for Brand voice. This page is proposal-only.

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

## Record status

**Record ID**: field-guide:brand-voice

**Parent lifecycle**: candidate

**Page lane**: plan

**Lane lifecycle**: proposed

**Owner**: Rebecca

**Owner role**: Not separately recorded

**Owner status**: Not separately recorded

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

**Working browser surface:** [Field guides — documentation](<https://guthlabs.ai/docs/field-guides/>) — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Ordered procedure

- Open the Brand voice field guide from Notebook Field Guides or PointGuard and confirm that the work is proposal-only.

- Open the source record field-guide:brand-voice and verify owner agent Rebecca, the related jobs, and source reference agents/index.html#rebecca.

- Create or link a source-labeled note. Record the source locator, provenance, revision, lifecycle, and any available source SHA-256; do not add unsupported voice rules as established facts.

- Select one related job: Social planning, Draft preparation, Asset coordination, Approval routing, or Post-performance records. Record the selected job and accountable owner.

- Collect the minimum evidence needed for the selected job. If a voice rule, audience, channel, asset, claim, or outcome is not present in the supplied source, mark it pending rather than inferring it.

- Prepare the draft or work plan and link each material claim, asset reference, and decision to a source-labeled record or mark it unsupported.

- Create explicit deadlines and a workback in Notebook To-dos. Use due dates, priorities, completion state, tags, and revision history; do not create hidden automation.

- Route the draft to Notebook Approvals with status Needs review. Preserve the proposal, reviewer, deadline, requested changes, and receipt.

- If approved locally, record the approval receipt and keep external send, publication, provider, credential, database, customer, and production effects held.

- If the work concerns post-performance records, record only supplied or observed evidence, identify unavailable metrics, and link any follow-up task.

- Mark the field-guide run complete only after the completion criteria pass and all unresolved questions are either resolved by evidence or explicitly handed off as held items.

## Deadline and chronology rules

- Set a due date for each selected related job before work begins.

- Set the approval deadline before routing a draft for review.

- Create a workback from the approval deadline for evidence collection, drafting, asset coordination, and review.

- If a deadline is missing from the source or requester, mark it pending and assign a human follow-up rather than inventing a date.

- Mark overdue or blocked items for review; do not imply an external deadline was met.

## Failure branches during execution

- The source record names Brand voice but supplies no actual voice principles; inventing tone, audience, channel, or style rules would exceed the source.

- A named owner or related job does not prove that Rebecca or any other agent has authority to publish, send, or change production state.

- Native app routes are local prototypes or indexes; route availability does not prove a connected web feature.

- Asset references may be mistaken for uploaded or protected files; upload and protected storage remain held.

- Approval may be recorded locally but must not be represented as external publication, customer communication, or qualification.

- Post-performance metrics may be unavailable; absence of evidence must remain explicit.

- Unresolved voice questions can create inconsistent drafts if they are not held for human review.

- Accessibility risk includes unlabeled review states, inaccessible deadline information, and relying on color alone for approval status.

## Sources and evidence

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

- `source_record:field-guide:brand-voice`

- `field-guide:brand-voice`

- `agents/index.html#rebecca`

- `Observed native contract: Notebook collections, deadlines, records, PointGuard, and held web boundary`

- `App routes: /app/notebook/field-guides/, /app/notebook/notes/, /app/notebook/files/, /app/notebook/projects/, /app/notebook/to-dos/, /app/notebook/approvals/, /app/notebook/messages/, /app/notebook/agent-logs/, /app/pointguard/`