Outreach campaign — qualification

Record status

Record ID

project:outreach-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.

• A blank campaign name, purpose, owner, visibility, or campaign deadline prevents submission and places focus on the first invalid field.
• A campaign deadline without timezone, or with an invalid date, is rejected with a field-level error.
• A task due after the campaign deadline is rejected deterministically.
• A dependency cycle is rejected and identifies every record in the cycle.
• A task cannot be completed when a required predecessor is incomplete, held, or deleted.
• A qualified account requires all configured qualification criteria and at least one source-labelled evidence record.
• An account with an exclusion criterion cannot be marked qualified even when other criteria pass.
• A dossier missing source locator, provenance, or source SHA-256 remains Needs review rather than becoming ready.
• A recipient record must be explicitly selected; free-text recipient data alone cannot authorize a draft as ready.
• A draft with an empty subject or body, unresolved personalization token, missing channel, or missing recipient is blocked.
• A draft linked to a private source cannot be exposed outside the configured visibility boundary.
• The interface exposes labels, instructions, errors, status, and dependencies without relying on color alone.
• Every actionable control is keyboard reachable, has a visible focus state, and has an accessible name.
• Validation errors are announced to assistive technology and identify the associated field.
• Long account names, message content, and error text remain readable at increased text size and narrow widths.
• A revision preserves the prior content, editor, timestamp, reason, and linked approval state.
• Editing an approved draft changes its status to Needs review and invalidates the prior approval receipt.
• Deleting a dossier, message, file reference, or project requires an explicit confirmation naming the record and consequence.
• Canceling a destructive confirmation leaves the record unchanged.
• A failed save leaves entered values available locally, reports that no authoritative save occurred, and offers retry without duplicate submission.
• A held provider write displays the held state and does not claim calendar creation, customer indexing, publication, credential use, or external send.
• An approval action records approver, decision, timestamp, scope, and receipt; it does not send the message.
• An unauthorized user cannot approve, delete, alter visibility, or change authority scope.
• Search results respect visibility and do not expose private dossiers through public or unpartitioned results.
• If a source file reference is unavailable, the dossier remains held and clearly identifies the missing reference.
• If a workback conflict exists, the project remains Needs review until a human resolves or accepts the conflict.
• Project readiness is false whenever required records, approvals, dependencies, privacy review, accessibility checks, or authority checks are incomplete.

Negative and held-state tests

• Accidental external send caused by treating a draft or approval as a send command.
• Unsupported claims about provider connection, customer indexing, publication, database authority, or production state.
• Over-collection or accidental exposure of personal, confidential, or account-sensitive information.
• Stale account evidence being used after source revisions or changed qualification criteria.
• Deadline drift, timezone errors, dependency cycles, or silent conflict resolution.
• Duplicate drafts or records after retrying a failed save.
• Approval remaining valid after a material draft, recipient, source, or deadline change.
• Destructive deletion removing provenance, revisions, or linked approval receipts.
• Inaccessible validation, status, focus order, or confirmation behavior.
• Agent or user acting outside the recorded authority scope.

Qualification claim boundary

Potentially allowed only after the stated evidence

• This is a proposed project template for organizing account dossiers and staged outreach.
• The project can be designed around source-labelled records, workback deadlines, revisions, approvals, and held external effects.
• The observed contract includes local prototype or indexed surfaces for projects, to-dos, agenda, messages, approvals, notes, files, search, and agent logs.

Still held

• No external message has been sent.
• No provider, credential, calendar, database, customer, publication, or production connection is established.
• No account has been qualified by this proposal.
• No customer indexing or external recipient validation is claimed.
• No deployment or live project backend is claimed.

Sources and evidence

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

• source_record:project:outreach-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/to-dos/
• /app/notebook/agenda/
• /app/notebook/messages/
• /app/notebook/approvals/
• /app/notebook/agent-logs/