Source: https://guthlabs.ai/docs/jobs/wick-campaign-chronology/forms/ job / candidate # Campaign chronology โ€” forms The distinct forms record for Campaign chronology. This page is proposal-only. Status: **proposed**Lifecycle: **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. ## Proposed form sections Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth. ### Campaign brief Define the bounded campaign and its intended audience without assuming access or authority. - campaign name - campaign objective - requesting owner - owner role - audience or account segment - requested channels - desired outcome - known constraints - source locator ### Source and chronology inputs Bind each event and claim to inspectable source material and preserve provenance. - source record IDs - source URLs or locators - source SHA-256 when available - event date and timezone - event type - event summary - speaker or author - relationship status stated by source - confidence - unresolved ambiguity - source lock status ### Account and contact context Capture only verified account and contact context needed for a draft. - account identifier - contact identifier - contact name as sourced - role as sourced - prior interaction record IDs - known preferences or constraints - relationship commitments present - account-access status - privacy or sensitivity flag ### Draft communication Prepare a reviewable world post or outreach message with explicit boundaries. - communication type - target channel - recipient or audience - subject or opening - body - claims used - call to action - pricing language - commitment language - attachments or links - fallback wording - human-review notes ### Response and disposition Record observed or supplied responses without inventing outcomes. - response record ID - response date and timezone - response text or source locator - classification - sentiment if explicitly supported - requested follow-up - risk flag - recommended disposition - next owner ### Approval and scheduling Make every external effect human-held and time-bounded. - approver - approval state - approval scope - approval timestamp - send or publish deadline - workback milestones - conflict check - held reason - revision requested - final disposition ### Accessible state contract - Every field requires a visible and programmatic label. - Required and optional fields must be stated in text. - Invalid entries require an actionable message linked to the field. - Blocked and Held states remain visible without relying on color alone. ## Supporting documentation fields These fields come from the docs_urls lane and remain separate from the primary operating form. ### Campaign context Identify the campaign and define the bounded chronology without implying publication or active outreach. - campaign name - campaign purpose - world or account scope - owner agent - human reviewer - chronology start date - chronology end date - timezone - record lifecycle ### Source evidence Bind each chronology entry to inspectable source material and distinguish observed facts from unresolved items. - source record ID - source locator - source SHA-256 when available - source type - event date and time - event author or origin - quoted or summarized evidence - provenance note - confidence or review state - linked account dossier - linked contact history ### Chronology entries Represent outreach preparation and world-posting events in chronological order without treating drafts as sent communications. - event category - event timestamp - channel or route - intended recipient or audience - draft content reference - relationship commitment flag - pricing statement flag - account-access flag - send status - human decision required - supersedes record ID - notes ### Workback and review Set deadlines for preparation, review, and escalation while preserving human ownership of external effects. - target review deadline - draft-complete deadline - source-verification deadline - reviewer decision deadline - escalation owner - hold reason - approval receipt reference - next review date ## Required or proposed record references No record existence is asserted by this documentation page. - Source-linked campaign chronology record - World packet record - Outreach queue record - Account dossier record - Contact history record - Source lock record - Response classification record - Draft message or world-post record - Approval receipt - Deadline/to-do record - Agent log entry - World-post or outreach event records - Account dossier references - Contact history references - Draft message records - Review and approval receipts - Chronology revisions with canonical IDs, source locators, source SHA-256, provenance, lifecycle, tags, links, and attachments where applicable ## 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/`