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

field guide / candidate

Channel rules — tools

The distinct tools 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
tools
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.

Authoritative tools lane tools and interfaces

Canonical tools-page assignments

  • PointGuard (interface · required) — Provides a persistent contextual room for the current channel activity and links Notebook records; it must not be treated as the execution owner or evidence of an external channel connection.
  • Notebook Projects (interface · required) — Owns the activity grouping and relationships among drafts, assets, approvals, tasks, and post-performance records; it does not imply an active project backend.
  • Notebook Notes (interface · required) — Captures source-labelled channel rules, decisions, and working context with provenance and revisions; it must not be used as an untraceable policy authority.
  • Notebook To-dos (interface · required) — Tracks workback dates, priority, completion, tags, and human-review signals; it must not silently trigger posting, sending, or scheduling.
  • Notebook Files (interface · required) — Keeps source-labelled local file references beside records and supports type, size, and linkage inspection; it must not be described as upload or protected storage.
  • Notebook Messages (interface · required) — Prepares drafts, recipients, attachments, and source context while final send remains human-held; it must not be used to claim delivery or publication.
  • Notebook Approvals (interface · required) — Records Needs review, Approved, or Held decisions and preserves receipts; approval must remain local and must not be described as external authorization.
  • Notebook Agenda (interface · required) — Supports source-bound time blocks, draft schedule changes, and conflict review; external calendar writes remain held.
  • Notebook Agent Logs (interface · optional) — Makes Agent work, authority boundaries, receipts, and current state inspectable; it must not be used to expand Rebecca's authority.
  • Notebook Search (interface · optional) — Finds linked local records while respecting visibility partitions; it must not be described as customer, public-web, or external-channel indexing.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

Canonical tools-page assignments

No verified instrument is assigned to this tools lane.

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

  • A named Messages, Agenda, Sites, or PointGuard surface does not prove a connected social provider or web feature.
  • Do not publish, send, schedule, index customers, or claim performance results without source-backed evidence and explicit human-held completion.
  • Do not store sensitive credentials or imply that file references are protected uploads.
  • Avoid duplicating channel rules across unrelated pages; keep one owned source-labelled record and link to it.
  • Do not convert approval into automatic execution or treat an Agent receipt as external confirmation.
  • Avoid inaccessible status indicators that rely on colour, hidden focus, or unlabeled controls.
  • Do not create doorway documentation pages; each route should contain distinct operational content.

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/pointguard/
  • /app/notebook/field-guides/
  • /app/notebook/projects/
  • /app/notebook/notes/
  • /app/notebook/files/
  • /app/notebook/agenda/
  • /app/notebook/messages/
  • /app/notebook/approvals/
  • /app/notebook/to-dos/
  • /app/notebook/agent-logs/
  • /app/notebook/search/