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

project template / candidate

Social campaign — tools

The distinct tools record for Social campaign. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
project:social-campaign
Parent lifecycle
candidate
Page lane
app_features
Lane lifecycle
proposed
Owner
Not separately recorded
Owner role
Not separately recorded
Owner status
Not separately recorded
Qualification result
NOT RUN · held for evidence and human review

Working browser surface: Project templates & workflows — overview — Create a local project from this template and validate its forms. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Authoritative app_features lane tools and interfaces

Canonical tools-page assignments

  • Notebook Projects (interface · required) — Owns the campaign grouping, lifecycle, linked records, and evidence view.
  • Notebook To-dos (interface · required) — Owns milestones, due dates, priorities, completion state, and review signals.
  • Notebook Agenda (interface · required) — Shows campaign windows, workback blocks, and draft conflicts without provider writes.
  • Notebook Messages (interface · required) — Owns communication drafts, recipients or audience labels, source context, and held send state.
  • Notebook Approvals (interface · required) — Provides the local decision gate and preserves approval receipts.
  • Notebook Paper (interface · required) — Supports longer briefs, copy packages, and revision-linked documents.
  • Notebook Search (interface · required) — Filters local campaign records while respecting private and held partitions.
  • PointGuard (interface · required) — Carries the current campaign room, blockers, approvals, and projection context across surfaces.
  • Date & Duration Calculator (provider · optional) — Provides a verified local calculation aid for campaign windows and workback intervals.

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

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

Use boundary

  • A planned date may be mistaken for a confirmed publication date.
  • Draft metrics may be mistaken for live provider analytics.
  • Audience descriptions may contain personal or sensitive information; minimize and locally label them.
  • Copied links may be malformed, inaccessible, or point to an unverified destination.
  • Approval can be misread as authorization to publish or send externally.
  • Timezone and daylight-saving changes can shift workback interpretation.
  • Recurrence candidates may create hidden automation if treated as schedules.
  • Projection outputs can create false precision when assumptions or baselines are weak.
  • External uploads, provider connections, customer indexing, publication, and final sending are held.
  • Accessibility checks are advisory unless a human verifies the rendered external destination.

Sources and evidence

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

  • source_record:project:social-campaign
  • NotebookCollectionKind.project
  • NotebookTodoPayload.dueAt
  • Notebook records provenance, source locators, SHA-256, revisions, lifecycle, tags, links, and attachments
  • Notebook Agenda deadlines/workbacks
  • Observed web boundary: provider, credential, database, customer, publication, and production effects are held
  • /app/notebook/projects/
  • /app/notebook/to-dos/
  • /app/notebook/agenda/
  • /app/notebook/messages/
  • /app/notebook/approvals/
  • /app/notebook/paper/
  • /app/pointguard/