Social planning — qualification

Record status

Record ID

job:rebecca:social-planning

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.

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 draft creates a canonical local record with job ID, source_ref, owner Rebecca, revision ID, provenance, and lifecycle/status visible.
• A draft without an intended account or with an account not explicitly approved is rejected or marked Held; it cannot enter an Approved publication state.
• A draft containing unsupported customer proof is rejected with failure_state unsupported_claim and preserves the offending revision for review.
• A request for paid promotion or a direct-message commitment cannot be approved by Rebecca alone and is routed to Held with the requested effect recorded.
• A public-post record cannot transition to Approved without approver identity, approval timestamp, channel, account, draft revision, and completed privacy/accessibility checks.
• A publication action is never simulated as completed when the app route is only a local prototype or index; the receipt remains Held or Not evidenced.
• Out-of-order deadlines are rejected with a deterministic chronology error identifying the conflicting fields.
• A stale planned publish time without a receipt produces stale_unpublished and blocks publication-related progression.
• Changing draft text after approval creates a new revision and resets approval to Needs review.
• Search and visibility behavior keeps private drafts, approval notes, and customer-related material out of public documentation or public indexing.
• Keyboard-only review can reach every required field and action; focus is visible, labels and error messages are associated with fields, and status is conveyed without color alone.
• Missing optional media does not block a text-only draft; supplied media requires an accessible description or an explicit Held state.
• Source locator and SHA-256 are preserved on creation and revision; absent source evidence is surfaced as source_unverified rather than silently accepted.

Negative and held-state tests

• Self-authorized publication or implied send authority
• Use of an unapproved account
• Invented customer proof, testimonials, metrics, or campaign outcomes
• Accidental paid promotion
• Direct-message commitments that create business obligations
• Stale or timezone-ambiguous scheduling
• Approval applied to a different draft revision
• Personal or sensitive customer information copied into public content
• Inaccessible media descriptions, links, forms, or status communication
• Private approval notes or drafts exposed through search or public documentation
• Treating prototype routes as connected provider or production features
• Doorway documentation or duplicate pages lacking distinct useful content

Qualification claim boundary

Potentially allowed only after the stated evidence

• This is a proposed qualification package for Rebecca’s social planning job.
• The source record describes a draft, review, approval, and publish pipeline as proposed.
• The native contract supports local records, revisions, provenance, deadlines, approval states, and held external effects.
• The listed app routes can be used as prototype or indexed surfaces for local drafting, review, scheduling preparation, and inspection.

Still held

• Publication of any post
• Connection to social accounts or providers
• Credential validity or account authority
• Database authority or customer indexing
• Production deployment
• Paid promotion execution
• Direct-message delivery or commitment
• Existence of customer proof, campaign performance, or publication receipts
• Qualification of Rebecca’s agent beyond this proposal

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:social-planning
• source record: job:rebecca:social-planning
• source_ref: agents/index.html#rebecca
• observed native contract: project_and_field_guide_collections
• observed native contract: deadlines
• observed native contract: records
• observed native contract: pointguard
• app route: /app/notebook/approvals/
• app route: /app/notebook/messages/
• app route: /app/notebook/agenda/
• app route: /app/notebook/agent-logs/
• app route: /app/notebook/field-guides/
• app route: /app/notebook/projects/