Source: https://guthlabs.ai/docs/field-guides/channel-rules/qualification/ field guide / candidate # Channel rules โ€” qualification The distinct qualification 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**: 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 documentation route has a distinct purpose and content block: overview, steps, tools, forms, examples, qualification, or related jobs. - Overview identifies the owner agent Rebecca, all five related jobs, proposal-only lifecycle, and held external effects. - Steps preserve record ownership: Notebook owns notes, messages, files, approvals, to-dos, agenda drafts, and agent logs as applicable. - Form fields support source locators, provenance, revisions, deadlines, accessibility, asset state, approval state, and performance evidence. - A missing source locator, reviewer, timezone, asset reference, or approval decision produces a visible Needs review or Held state. - No page claims deployment, provider connection, credential use, database authority, customer indexing, publication, live scheduling, or qualification. - An accessibility review checks headings, keyboard access, labels, focus order, status announcements, contrast, and non-color status cues. - A route test confirms private work and public documentation are partitioned and that proposed records remain distinguishable from indexed or prototype surfaces. - A related-job page links only to Social planning, Draft preparation, Asset coordination, Approval routing, and Post-performance records, with a distinct explanation of handoff ownership. - A post-performance example cannot display a metric unless it has an explicit evidence locator and measurement date. ## Negative and held-state tests - Treating a channel rule or draft as a live channel integration. - Confusing local approval with permission to publish externally. - Publishing unsupported performance claims or inventing live metrics. - Using asset references as though files were uploaded or stored in a protected vault. - Missing timezone, review deadline, or workback dependency. - Doorway documentation pages that repeat the same channel keywords without distinct user value. - Accessibility failures in status badges, forms, keyboard navigation, or approval states. - Unclear ownership when PointGuard carries context but Notebook owns the canonical record. ## Qualification claim boundary ### Potentially allowed only after the stated evidence - This guide proposes a source-backed workflow for social planning, draft preparation, asset coordination, approval routing, and post-performance record preparation. - Notebook surfaces can be used as local or indexed prototype workflow surfaces according to their stated route labels. - Approval states, provenance, revisions, deadlines, and held outcomes should be recorded explicitly. - External publication and performance reporting require separately verified evidence and human review. ### Still held - Deployment or production readiness - Provider, credential, database, or customer connection - Live channel access, external scheduling, or publication - Customer indexing or public distribution of private work - Qualification, certification, or guaranteed performance outcome - Live metrics or post-performance results without a supplied source record ## 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/notes/` - `/app/notebook/files/` - `/app/notebook/messages/` - `/app/notebook/approvals/` - `/app/notebook/agent-logs/`