Source: https://guthlabs.ai/docs/jobs/rebecca-draft-preparation/qualification/ job / candidate # Draft preparation โ€” qualification The distinct qualification record for Draft preparation. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: job:rebecca:draft-preparation **Parent lifecycle**: candidate **Page lane**: qualification **Lane lifecycle**: proposed **Owner**: Rebecca **Owner role**: Social media operating agent **Owner status**: PROPOSED **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. ## 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. ### Lane-specific instrument aids No verified instrument is assigned to this qualification lane. ## 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 valid package has one canonical draft ID, one owner, an explicit channel, intended account, requested publish time with timezone, and current lifecycle state. - A draft cannot reach Approved when account-connection status is unknown, unverified, or held. - A draft cannot reach Approved when any material claim lacks a source record, source locator, or explicit evidence status. - Customer proof is rejected unless a source-labelled evidence record and approval status are present; otherwise the draft is Held. - A draft containing invented metrics, testimonials, customer outcomes, endorsements, or availability claims is rejected and records the exact claim as a failure. - A draft cannot reach Approved when it includes an unapproved account, an implicit account switch, or an instruction to self-authorize publication. - A draft cannot reach Approved when paid promotion is requested but paid-promotion approval is absent. - A draft cannot reach Approved when it creates or promises a direct-message commitment, customer response, offer, deadline, or service level without explicit human approval. - Every media reference has an accessible text alternative field; missing alt text, transcript, caption, or equivalent description causes an accessibility failure unless the media is explicitly marked decorative. - The form is keyboard navigable, uses labelled controls, exposes validation errors in text, preserves focus on error, and does not rely on color alone for review state. - Private source records, customer details, account identifiers, credentials, and unpublished drafts are excluded from public-facing documentation and public indexing. - The package stores only the minimum customer information needed for the draft; credentials, access tokens, and protected uploads are rejected from draft fields and marked Held. - Chronology checks reject a claim whose source revision postdates the claimed event or whose publication window precedes required approval. - A changed source revision or changed draft text creates a new revision and invalidates prior approval. - If an evidence locator, source hash, or required record is missing, the system records a deterministic failure state rather than silently proceeding. - If a provider, credential, database, customer, publication, or production effect is requested, the package remains local and Held with the requested effect recorded. - The package never represents a named native surface as proof of a connected web feature. - A human approval receipt contains reviewer, decision, exact approved revision, timestamp, and comments or an explicit no-comment value. - A publication handoff without a human-provided external receipt remains Held and makes no publication claim. - Distinct documentation routes must provide distinct useful content: field-guide procedure, approval guidance, source/claim guidance, and receipt guidance; no doorway or keyword-spam pages are accepted. ## Negative and held-state tests - Self-authorized publication - Use of an unapproved account - Invented customer proof or unsupported performance claims - Privacy leakage through customer details, unpublished drafts, account identifiers, or credentials - Chronology errors caused by stale or future-dated sources - Approval attached to the wrong draft revision - Accessibility barriers in copy, media descriptions, controls, or review states - Implicit paid promotion or direct-message commitments - Confusing local prototype or index routes with connected provider behavior - Missed deadlines causing stale or unauthorized publication attempts - Duplicate or contradictory source records - Public indexing of private or held work ## Qualification claim boundary ### Potentially allowed only after the stated evidence - Rebecca is a proposed social media operating agent. - The package defines a draft, review, approval, and human-held publication workflow. - The workflow requires source-bound claims, accessibility metadata, explicit deadlines, and recorded failure states. - The named Notebook and Business routes are available as proposal targets or local prototype/index surfaces according to the observed contract. ### Still held - Rebecca is deployed or connected to a provider. - Any account is connected or authorized. - Any draft was published or scheduled externally. - Any customer was indexed, contacted, or represented by the agent. - Any publication receipt exists without a human-provided source record. - Any database, credential, production, or public-site effect occurred. - Any draft is qualified for publication before all listed tests pass. ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `agents/index.html#rebecca` - `source_record:job:rebecca:draft-preparation` - `observed_native_contract.project_and_field_guide_collections` - `observed_native_contract.deadlines` - `observed_native_contract.records` - `observed_native_contract.pointguard` - `app_routes:/app/notebook/approvals/` - `app_routes:/app/notebook/messages/` - `app_routes:/app/notebook/agent-logs/` - `app_routes:/app/notebook/field-guides/`