Source: https://guthlabs.ai/docs/field-guides/channel-rules/examples/ field guide / candidate # Channel rules — examples The distinct examples 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]() — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held. ## Hypothetical scenarios A reviewer opens the Channel rules guide for bounded local rehearsals. Every fixture uses invented placeholders, performs no provider or external action, and remains held until source evidence and human review are recorded. ### 1. Guided inquiry fixture A reviewer records a bounded question, links only supplied source references, and marks every unanswered point Needs review. **Fixture ID**: channel-rules-example-001 **Evidence**: Hypothetical source placeholders only **Decision**: HELD · human review required **External effects**: None ### 2. Source comparison fixture A reviewer compares two hypothetical source locators, preserves disagreement, and holds any conclusion until provenance is supplied. **Fixture ID**: channel-rules-example-002 **Evidence**: Hypothetical source placeholders only **Decision**: HELD · human review required **External effects**: None ### 3. Uncertainty and pathway fixture A reviewer constructs a local procedure or study pathway with checkpoints while labelling uncertainty and leaving external effects Held. **Fixture ID**: channel-rules-example-003 **Evidence**: Hypothetical source placeholders only **Decision**: HELD · human review required **External effects**: None ### 4. Potentially allowed claim fixture A hypothetical claim may advance only when its exact evidence locator, scope, reviewer, and decision rationale are recorded; this fixture asserts no fact. **Fixture ID**: channel-rules-example-004 **Evidence**: Hypothetical source placeholders only **Decision**: HELD · human review required **External effects**: None ### 5. Held claim fixture A hypothetical unsupported claim remains Held with missing evidence and human-review rationale visible; it is not published or indexed. **Fixture ID**: channel-rules-example-005 **Evidence**: Hypothetical source placeholders only **Decision**: HELD · human review required **External effects**: None ## Filled example fields ### Scope and ownership fixture Declare the bounded work, owner, source, and current lifecycle before preparation begins. **guide title**: Example value to be supplied and reviewed **owner agent**: Named human or Agent owner required **related jobs**: Example value to be supplied and reviewed **source record ID**: fixture-source-001 (hypothetical; no external claim) **source locator**: fixture-source-001 (hypothetical; no external claim) **source SHA-256**: fixture-source-001 (hypothetical; no external claim) ### Channel rule set fixture Capture the rules that govern each proposed channel without inventing rules not present in the source record. **channel name**: Example value to be supplied and reviewed **rule statement**: Held — pending human review **rule source or locator**: fixture-source-001 (hypothetical; no external claim) **audience**: Example value to be supplied and reviewed **content boundary**: Example value to be supplied and reviewed **required asset types**: Example value to be supplied and reviewed ### Draft preparation fixture Create a reviewable draft tied to its channel rules and source evidence. **draft title**: Example value to be supplied and reviewed **channel**: Example value to be supplied and reviewed **purpose**: Example value to be supplied and reviewed **body text**: Example value to be supplied and reviewed **call to action**: Example value to be supplied and reviewed **proposed timing**: Example value to be supplied and reviewed ## Review questions - A new activity can be created with an owner, channel, objective, source references, visibility, and planned performance date. - Every milestone has an owner, due date, completion state, and visible dependency or blocker field. - A draft can link to source notes, asset references, intended recipients, accessibility checks, and a revision identifier. - An approval record visibly shows Needs review, Approved, or Held and includes reviewer, decision deadline, and rationale. - A held approval prevents the guide from representing the draft as sent, published, or externally scheduled. - File records display local reference metadata and linked records without presenting hidden upload or protected-storage behavior. - Agenda changes are visibly drafts and do not write to an external provider. - Post-performance records preserve source locator, provenance, revision, and unresolved questions. ## 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/` - `Observed native contract: project_and_field_guide_collections` - `Observed native contract: deadlines` - `Observed native contract: records` - `Observed native contract: pointguard` - `/app/pointguard/` - `/app/notebook/projects/` - `/app/notebook/agenda/` - `/app/notebook/to-dos/` - `/app/notebook/search/`