Social campaign — qualification

Record status

Record ID

project:social-campaign

Parent lifecycle

candidate

Page lane

qualification

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.

Qualification status

Result

NOT RUN

Disposition

HELD

Reviewer

Not recorded

Receipt

Not recorded

This page defines proposed acceptance criteria for the qualification lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect.

Outcome definitions

Verified

All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect.

Failed

One or more deterministic acceptance requirements failed with an inspectable reason.

Needs review

Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer.

Held

Authority, required evidence, safe execution conditions, or a principal gate is absent.

The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only.

Proposed deterministic acceptance tests

Route-resolution and distinct-content checks apply only to the admitted canonical routes in this record. Held source-proposed extensions are non-resolving proposals and are excluded.

• Submitting without campaign name, owner, purpose, objective, visibility, or campaign dates is rejected with field-level messages.
• Invalid dates, missing timezone, end-before-start, and deadline-after-publication combinations are rejected deterministically.
• A dependency pointing to a missing, deleted, or inaccessible record prevents approval and identifies the dependency.
• Changing the publication target recomputes only derived workback dates, shows the delta, and requires confirmation before saving.
• Changing an approved draft creates a new revision, marks the prior approval stale, and returns the campaign to Needs review.
• A draft cannot be marked Approved unless required reviewers, evidence links for claims, accessibility checks, privacy checks, and approval scope are complete.
• Final send or publication controls remain visibly human-held and do not claim provider connection, publication, customer indexing, or production effect.
• A failed save, conflict, unavailable record, or held provider effect preserves entered data locally where possible and exposes retry, cancel, and recovery state.
• Destructive deletion requires explicit confirmation naming the project and affected records; cancel leaves all records unchanged.
• Deleting a project with linked drafts, approvals, deadlines, or attachments is blocked or requires a reviewed archive flow; links must not silently break.
• Keyboard-only users can reach every field, error, dependency control, approval control, and destructive action in a logical order.
• Every validation error is programmatically associated with its field, announced to assistive technology, and not conveyed by color alone.
• Focus moves to the first invalid field after failed submission; error summaries provide links to all invalid fields.
• Contrast, visible focus, labels, captions or transcripts for media, text alternatives, and reduced-motion behavior are required before approval.
• Privacy tests confirm sensitive fields are minimized, masked where appropriate, excluded from public views, and not copied into public claims or attachments without explicit authority.
• Authority tests confirm only the designated owner or permitted reviewer can edit approval status, and approval records preserve actor, revision, scope, and timestamp.
• Search and visibility tests confirm private, held, and source-labelled records are not exposed through public context or unqualified search.
• If measurement data is absent or unsupported, the result remains Planned or Held and cannot be presented as a live campaign outcome.

Negative and held-state tests

• Confusing a local prototype or index with a connected publishing provider.
• Accidental publication or message send caused by ambiguous controls or inferred approval.
• Publishing unsupported claims, private information, or unreviewed attachments.
• Stale approval after draft, audience, channel, or schedule changes.
• Timezone, daylight-saving, recurrence, or workback calculations producing missed deadlines.
• Broken dependencies or silent loss of linked records during deletion.
• Accessibility barriers preventing review or approval.
• Treating planned metrics, estimates, or local observations as live customer or campaign performance.
• Unauthorized edits to approvals, audience notes, or sensitive records.
• Partial saves, duplicate submissions, conflicting revisions, or lost drafts during failure.

Qualification claim boundary

Potentially allowed only after the stated evidence

• This is a proposed project template for planning public communications.
• The project can define drafts, deadlines, dependencies, approvals, accessibility checks, privacy checks, and measurement plans.
• Publication and final sending are human-held in the observed contract.
• Records may preserve provenance, revisions, lifecycle, links, and attachments when implemented through the native record model.

Still held

• No claim that social providers are connected.
• No claim that content is published, scheduled externally, delivered, indexed, or visible to customers.
• No claim that campaign metrics are live, complete, or production-derived.
• No claim of database authority, credential availability, deployment, or qualification.
• No claim that approval guarantees legal, policy, platform, or audience suitability.

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 Agenda deadlines/workbacks
• Notebook records provenance and revisions
• PointGuard persistent cross-app context surface
• /app/notebook/projects/
• /app/notebook/agenda/
• /app/notebook/messages/
• /app/notebook/approvals/
• /app/notebook/to-dos/
• /app/notebook/notes/