Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

field guide / candidate

Brand voice — qualification

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

Status: proposedLifecycle: candidate

Record status

Record ID
field-guide:brand-voice
Parent lifecycle
candidate
Page lane
docs_urls
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 — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Qualification status

Result
NOT RUN
Disposition
HELD
Reviewer
Not recorded
Receipt
Not recorded

This page defines proposed acceptance criteria for the docs_urls lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect.

Lane-specific instrument aids

No verified instrument is assigned to this qualification lane.

Outcome definitions

Verified
All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect.
Failed
One or more deterministic acceptance requirements failed with an inspectable reason.
Needs review
Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer.
Held
Authority, required evidence, safe execution conditions, or a principal gate is absent.

The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only.

Proposed deterministic acceptance tests

Route-resolution and distinct-content checks apply only to the admitted canonical routes in this record. Held source-proposed extensions are non-resolving proposals and are excluded.

  • Every guide URL has distinct content: overview defines scope, steps define procedure, forms define fields, examples show bounded records, qualification defines readiness and failure states, and related-jobs maps dependencies.
  • The overview labels the guide proposed and states that app routes are prototypes or indexes where applicable.
  • A user can identify Rebecca as the source-record owner agent and navigate to the related jobs without a deployment claim.
  • The form captures audience, purpose, tone constraints, draft ownership, asset references, approval state, provenance, revisions, and deadlines.
  • A draft cannot be represented as sent, published, customer-indexed, or provider-connected by the guide content.
  • Approval states are limited to Needs review, Approved, and Held, with a receipt or explanation for each decision.
  • Accessibility checks include readable structure, plain-language review, alt-text or equivalent asset notes, and non-color-only status communication.
  • A failed evidence check produces a Held outcome with an explicit missing-source reason rather than an invented metric.
  • Related records retain canonical IDs, provenance, source locators, revisions, lifecycle, tags, links, and attachments where available.
  • Search and navigation do not expose private or held records as public documentation.

Negative and held-state tests

  • Treating a tone example as an authoritative policy without a source locator or owner review.
  • Confusing a locally approved draft with an externally sent or published communication.
  • Inventing performance results, audience response, provider delivery, or customer indexing.
  • Using duplicate pages with near-identical copy that create doorway content or keyword-spam URLs.
  • Attaching assets without recording custody, type, size, provenance, or accessibility notes.
  • Allowing Agent work to change canonical records or send messages without human review.
  • Missing revision history when multiple draft variants or reviewers are involved.
  • Publishing sensitive private notes, held approvals, or internal agent receipts through public documentation.
  • Using unsupported medical, financial, legal, or safety claims in brand copy.

Qualification claim boundary

Potentially allowed only after the stated evidence

  • This is a proposed field guide for brand-voice preparation and review.
  • The source record associates Brand voice with Rebecca and the listed related jobs.
  • The guide can describe bounded local drafting, note-taking, approval preparation, deadlines, provenance, and record-linking workflows.
  • The guide may link to named prototype or indexed app surfaces as navigation proposals, with their stated lifecycle labels.

Still held

  • Deployment or production availability of the guide or any connected workflow.
  • Provider, credential, database, customer, publication, or external messaging effects.
  • Live social-platform scheduling, delivery, analytics, reach, engagement, or post-performance metrics.
  • Qualification of a draft as brand-compliant without human review and recorded evidence.
  • Any claim that Rebecca, an Agent, or a specialist app can independently publish, send, approve externally, or modify canonical records.
  • Customer indexing, public discoverability, or security guarantees beyond the observed local visibility boundary.

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
  • agents/index.html#rebecca
  • field-guide:brand-voice
  • Observed native contract: project_and_field_guide_collections
  • Observed native contract: records
  • Observed native contract: deadlines
  • Observed native contract: pointguard
  • App route: /app/notebook/field-guides/
  • App route: /app/notebook/notes/
  • App route: /app/notebook/approvals/
  • App route: /app/notebook/messages/
  • App route: /app/notebook/files/
  • App route: /app/notebook/to-dos/
  • App route: /app/notebook/agent-logs/
  • App route: /app/notebook/search/