Campaign chronology — tools

The distinct tools record for Campaign chronology. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: job:wick:campaign-chronology
Parent lifecycle: candidate
Page lane: package
Lane lifecycle: proposed
Owner: Wick
Owner role: World posts and outreach agent
Owner status: HELD
Qualification result: NOT RUN · held for evidence and human review

Working browser surface: Agent jobs — builder overview — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Authoritative package lane tools and interfaces

Canonical tools-page assignments

World recorder (interface · optional) — Stage and preserve source-linked world-posting context; it does not establish publication authority.
Outreach queue (interface · optional) — Organize drafts, recipients, deadlines, and review state while final send remains human-held.
Source lock (interface · optional) — Mark claims as source-bound, ambiguous, stale, or held before they enter a draft.
Response classifier (skill · optional) — Classify supplied responses consistently without asserting that any communication occurred.
Notebook (provider · optional) — Canonical local record surfaces for notes, files, to-dos, messages, approvals, projects, field guides, search, and agent logs; current routes are prototypes or indexes.
PointGuard (interface · optional) — Carry the current campaign context across specialist surfaces without becoming the canonical outreach owner.

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

External send and publication are human-held; Wick has no autonomous send or publish authority.
Do not impersonate Antonio or write as Antonio without explicit human-authored authorization and review.
Do not send from an unverified route, use an unverified account, or imply account access.
Do not invent relationship history, contact details, responses, commitments, pricing, availability, or campaign outcomes.
Do not treat a named native surface or app route as proof of connected web behavior, provider access, database authority, customer indexing, or production state.
Avoid exposing unnecessary personal or sensitive contact information in drafts, search results, logs, or shared context.
Ambiguous identity, duplicate accounts, stale sources, contradictory dates, and missing timezones must create a review state.
A response classifier may organize supplied text but cannot prove that a response was received or characterize intent beyond the available evidence.
Pricing statements, relationship commitments, account changes, and customer-impacting actions require separate human approval.
Instrument selection is intentionally empty because no verified instrument is needed for this communications-chronology job.

Sources and evidence

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

agents/index.html#wick
source_record:job:wick:campaign-chronology
observed_native_contract:project_and_field_guide_collections
observed_native_contract:deadlines
observed_native_contract:records
observed_native_contract:pointguard
app_routes:/app/notebook/messages/
app_routes:/app/notebook/approvals/
app_routes:/app/notebook/agent-logs/
app_routes:/app/business/messages/