Campaign chronology — field guides

Record status

Record ID

job:wick:campaign-chronology

Parent lifecycle

candidate

Page lane

docs_urls

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.

Related field-guide records

• /app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

Operating sequence

1. Create a campaign chronology record owned by Wick and set lifecycle to proposed or held.
2. Collect source-linked events, account dossiers, contact histories, world packets, and prior response records; do not fill gaps with assumptions.
3. Apply a source lock to each material claim and mark unsupported, ambiguous, stale, or conflicting items for review.
4. Normalize events into a dated chronology with timezone, source locator, provenance, revision, and confidence fields.
5. Check the chronology against the never-rules: no impersonation of Antonio, no unverified route, and no invented relationship history.
6. Prepare a bounded world packet or outreach draft using only locked claims and clearly labeled uncertainty.
7. Classify any supplied response using the response classifier record without claiming that a response was sent or received unless sourced.
8. Create review tasks for external send, publication, relationship commitments, pricing statements, account access, and unresolved claims.
9. Run a human approval and conflict check before any proposed deadline or schedule; external writes remain held.
10. Preserve the draft, sources, revisions, approval receipt, and held or failure state in the Agent Log and linked Notebook records.
11. Close the job only when the reviewer records approved, held, rejected, superseded, or blocked disposition and the next owner is explicit.

Handoff 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/
• Observed native contract: records preserve canonical IDs, provenance, source locators, source SHA-256, revisions, lifecycle, tags, links, and attachments
• Observed native contract: PointGuard is a persistent cross-app context surface and specialist apps remain execution and canonical-record owners
• Observed app route: /app/notebook/approvals/
• Observed app route: /app/notebook/messages/
• Observed app route: /app/notebook/agent-logs/