Page actions
field guide / candidate
Channel rules — related jobs
The distinct related jobs record for Channel rules. This page is proposal-only.
Status: proposedLifecycle: 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 — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.
Related Agent job handoffs
Handoff record requirements
The guide may supply evidence, checkpoints, and failure context to a job. The receiving job retains ownership and must record its own decision, approval, and receipt.
- 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
- Project record for the campaign or channel activity
- Field guide record for this procedure
- Source-labelled notes for channel rules and decisions
- Draft message records with recipients and source context
- File-reference records for assets
- To-do records for preparation, review, and follow-up
- Approval records with Needs review, Approved, or Held state
- Post-performance record with source locator and revision history
Ownership boundary
The guide supports these jobs without importing their package descriptions, becoming the job owner, or gaining independent authority.
- 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-rulesagents/index.html#rebeccaobserved native contract: project_and_field_guide_collectionsobserved native contract: deadlinesobserved native contract: recordsobserved native contract: pointguard/app/notebook/field-guides//app/notebook/agent-logs//app/notebook/approvals//app/notebook/messages//app/notebook/files//app/notebook/notes/Observed native contract: project_and_field_guide_collectionsObserved native contract: deadlinesObserved native contract: recordsObserved native contract: pointguard/app/pointguard//app/notebook/projects//app/notebook/agenda//app/notebook/to-dos//app/notebook/search/