Source: https://guthlabs.ai/docs/field-guides/channel-rules/prerequisites/

field guide / candidate

# Channel rules — prerequisites

The distinct prerequisites record for Channel rules. This page is proposal-only.

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

## Record status

**Record ID**: field-guide:channel-rules

**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.

## Entry evidence and required records

Before the procedure starts, an operator must identify the source, owner, scope, and required records below. Missing evidence holds the guide.

- field-guide:channel-rules

- job:social-planning

- job:draft-preparation

- job:asset-coordination

- job:approval-routing

- job:post-performance-records

- source record with owner Rebecca and source locator agents/index.html#rebecca

- linked notes, files, drafts, approval receipts, and post-performance records

## Intended operators and ownership

- Rebecca

- Approval reviewers

- Agents supporting social planning

- Asset coordinators

Being listed as an intended operator does not grant execution or publication authority.

## Conditions that hold the guide before entry

- A channel rule may be invented or generalized without source evidence.

- A native route may be mistaken for a connected social provider or publication system.

- A draft may be treated as sent or published after local approval.

- Unverified metrics may be copied into post-performance records as if live data.

- Asset references may imply upload, protected storage, rights clearance, or delivery when those states are not verified.

- Missing accessibility descriptions may block review or reduce usability.

- Undated rules and approvals may become stale without a review-by date.

- Private notes, assets, approvals, and public-facing context may be mixed without visibility checks.

## Sources and evidence

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

- `source_record:field-guide:channel-rules`

- `agents/index.html#rebecca`

- `observed native contract: project_and_field_guide_collections`

- `observed native contract: deadlines`

- `observed native contract: records`

- `observed native contract: pointguard`

- `/app/notebook/field-guides/`

- `/app/notebook/agent-logs/`

- `/app/notebook/approvals/`

- `/app/notebook/messages/`

- `/app/notebook/files/`

- `/app/notebook/notes/`