Source: https://guthlabs.ai/docs/project-templates/social-campaign/forms/ project template / candidate # Social campaign โ€” forms The distinct forms record for Social campaign. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: project:social-campaign **Parent lifecycle**: candidate **Page lane**: forms **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. ## Proposed form sections Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth. ### Campaign intake Define why the campaign exists, who owns it, and what decision or outcome it supports. - campaign name - requestor - project owner - executive or accountable approver - campaign purpose - primary audience - secondary audience - communication channels - requested start date - requested end date - hard external deadline - success question - source references - sensitivity or privacy notes ### Scope and deliverables Make included work, excluded work, outputs, and acceptance boundaries explicit. - in-scope activities - out-of-scope activities - deliverable list - content formats - channel constraints - brand or policy constraints - accessibility requirements - language or localization needs - evidence required for each deliverable - definition of ready - definition of done ### Milestones and deadlines Create dated checkpoints and preserve the workback from the hard deadline. - milestone name - milestone owner - dueAt - priority - status - recurrenceCandidate - completion state - review window - approval required - linked deliverables - schedule source - revision note ### Dependencies and owners Record people, inputs, decisions, and systems that can block progress without implying connected provider state. - dependency name - dependency type - blocking milestone - dependency owner - needed-by date - current state - fallback plan - escalation owner - related record IDs - last checked at ### Workback schedule Translate the external deadline into ordered preparation, drafting, review, approval, and measurement tasks. - hard deadline - publication or release task - final approval deadline - accessibility review deadline - fact-check deadline - draft deadline - briefing or intake deadline - buffer duration - task sequence - task durations - task owners - slippage rule - next review date ### Tools, guides, and records Declare which local surfaces and source-backed procedures are intended for each task. - tool or route name - kind - task supported - canonical record owner - guide or procedure link - authority boundary - fallback if unavailable - local-only or held effect ### Evidence and measurement Define what will be recorded to support campaign review without inventing live metrics. - evidence item - source locator - capture date - evidence owner - content or message version - metric definition - measurement window - baseline if available - observed value - verification state - attachment or note link - unsupported-claim flag ### Reviews and approvals Require explicit human review before external communication or publication-related action. - reviewer - review type - submitted revision - review dueAt - decision state - decision note - required changes - approval receipt ID - approved scope - held action - decision timestamp ### Risks and failure states Surface blockers, content hazards, deadline failure, accessibility gaps, and unsupported claims. - risk or hazard - likelihood - impact - severity - owner - trigger - mitigation - contingency - related dependency - status - review date ### Closure and learning Confirm what was completed, what remains held, and what evidence or learning should be retained. - completion decision - delivered records - undelivered or held items - final approved revision - evidence completeness - deadline outcome - open risks - lessons learned - follow-up owner - follow-up dueAt - archive or retention note ### 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 app_features lane and remain separate from the primary operating form. ### Campaign brief Define the campaign without implying publication or provider connectivity. - campaign name - objective - working status - owner - internal audience description - public audience description - key message - call to action - start date - end date - timezone - success measures - risks and assumptions ### Channel plan Record proposed channels and message variants as local planning records. - channel name - channel status - variant label - intended format - character limit note - draft link - asset reference - planned publish window - channel-specific review requirement ### Workback and deadlines Turn the campaign window into explicit human-owned work. - milestone name - owner - due date and time - priority - dependency IDs - recurrence candidate - completion state - review required - fallback date - notes ### Message draft Prepare copy with source context, revision history, and approval state. - headline or opening - body copy - call to action - link target as text - alt text or media description - audience label - channel - draft status - source notes - revision reason ### Measurement snapshot Capture declared, source-labelled results without inventing live metrics. - observation date - metric name - value - unit - source locator - source captured at - comparison period - confidence note - interpretation - follow-up action ### Review and effect gate Separate local approval from any external publication or send. - reviewer - decision - decision timestamp - decision notes - claims checked - link checked locally - privacy check - accessibility check - publication instruction - human executor - receipt reference ## Required or proposed record references No record existence is asserted by this documentation page. - project record with canonical ID, origin, source locator, source SHA-256, provenance, revision, lifecycle, tags, links, and attachments - campaign intake record - scope and deliverables record - milestone and deadline records with dueAt, priority, completion state, tags, and revisions - dependency and risk records - owner and reviewer assignments - workback schedule - draft message or document records - evidence and measurement records - approval receipt - closure review - project record - campaign brief - audience note - channel plan - message draft - asset reference - campaign milestone to-do - agenda time block - review decision - measurement snapshot - external-effect receipt ## 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` - `project:social-campaign` - `NotebookCollectionKind.project` - `NotebookTodoPayload.dueAt` - `Notebook records provenance and revision contract` - `Notebook Agenda deadlines/workbacks` - `/app/notebook/projects/` - `/app/notebook/to-dos/` - `/app/notebook/agenda/` - `/app/notebook/messages/` - `/app/notebook/approvals/` - `/app/notebook/paper/` - `/app/notebook/field-guides/` - `/app/pointguard/` - `Notebook records provenance, source locators, SHA-256, revisions, lifecycle, tags, links, and attachments` - `Observed web boundary: provider, credential, database, customer, publication, and production effects are held`