Asset coordination — qualification

Record status

Record ID

job:rebecca:asset-coordination

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.

• Positive: a complete draft with source locator, SHA-256, revision, explicit channel label, chronology, privacy evidence, accessibility fields, and named human approval is represented as locally Approved for that exact revision and scope, while publication remains Held.
• Positive: a draft with an explicit timezone and ordered workback displays deterministic deadlines and preserves each revision.
• Negative: missing source locator, source hash, provenance, or canonical ID prevents qualification and produces Held with a missing-source failure.
• Negative: an unapproved account label, absent approver, or approval for a different revision prevents Approved state.
• Negative: any request to self-authorize publication, connect an account, trigger paid promotion, or make a direct-message commitment produces Held and no external action.
• Negative: customer proof marked invented, unsupported, or absent when required prevents approval; the system must not create testimonial or performance evidence.
• Negative: personal data without a recorded consent or rights reference, or with unresolved sensitive-data exposure, prevents approval and requires redaction or documented review.
• Negative: missing alt text for an informative image, missing caption or transcript for required audio/video content, non-descriptive link text, or unresolved contrast evidence produces an accessibility failure.
• Negative: contradictory timestamps, missing timezone, approval before draft creation, or a planned publish time earlier than approval produces a chronology failure.
• Negative: an expired, superseded, or held source revision cannot satisfy a current draft's evidence requirement.
• Negative: duplicate canonical IDs or a source-hash mismatch on revision update creates a provenance failure and preserves the prior record.
• Negative: final-send or publication controls are unavailable or held on the named prototype/index routes; the record must state that external effect is not verified.
• Positive: reopening an Approved draft after text, asset, channel, or scope change returns it to Needs review and creates a new revision.
• Positive: a failed check shows a human-readable reason, failure code, owner for resolution, next review time, and linked recovery record.
• Accessibility: all blocking errors are text-labelled, keyboard reachable, associated with their fields, and not communicated by color alone; status uses text such as Needs review, Approved, and Held.
• Privacy: private notes, source labels, customer details, and protected asset references are excluded from public-facing draft text unless explicitly cleared by the recorded human review.
• Authority: the qualification result identifies Rebecca as PROPOSED and never treats the named agent, native surface, or app route as proof of connected authority or deployment.
• Source: every externally meaningful claim in the draft is traceable to a supplied source record, approved campaign packet, or explicitly entered source reference; unsupported claims are Held.
• Chronology: the displayed workback orders all required steps consistently across Today, To-dos, and Agenda records without implying provider calendar writes.

Negative and held-state tests

• Confusing a proposed social operating agent with an authorized or connected production account.
• Treating prototype or indexed routes as evidence of publication, provider connection, database authority, customer indexing, or deployment.
• Publishing unsupported customer proof, metrics, testimonials, or campaign outcomes.
• Accidentally exposing personal data, private notes, source locators, credentials, or protected asset paths in public copy.
• Approving one revision while sending or publishing another.
• Ambiguous timezone or stale deadlines causing premature or missed communication.
• Using accessibility labels or contrast checks as a substitute for complete content accessibility review.
• Doorway documentation or duplicate route content that fragments authority instead of documenting distinct useful procedures.
• Hidden automation or external writes through agenda, messages, approvals, files, or capture surfaces.
• Failure states that silently discard drafts, receipts, provenance, or human decisions.

Qualification claim boundary

Potentially allowed only after the stated evidence

• This is a proposal for qualifying Rebecca's asset-coordination job.
• The supplied source record describes Rebecca as a proposed social media operating agent with draft, review, approval, and publication pipeline responsibilities.
• The package can define local draft, review, approval, accessibility, privacy, chronology, and failure records.
• Named Guth app routes and native contracts describe prototype or indexed surfaces and their stated bounded capabilities.
• The allowed WCAG Contrast Ratio Checker instrument may be designated for a local contrast check, subject to its verified-clean directory entry.

Still held

• Rebecca is deployed, active, authorized, or connected to any account.
• Any provider, credential, database, customer index, business page, publication channel, or production system is connected.
• Any post was published, sent, scheduled externally, promoted, or received by a customer.
• Any approval is legally, operationally, or externally effective.
• Any customer proof, testimonial, metric, campaign result, or social performance claim is true without source evidence.
• Any route is a connected web feature merely because a native surface or route is named.
• Any documentation URL represents a live production contract.
• Any file was uploaded, copied to protected storage, or made publicly available.
• Any instrument result has been executed or persisted in production.

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:asset-coordination
• job:rebecca:asset-coordination
• Observed native contract: project_and_field_guide_collections
• Observed native contract: deadlines
• Observed native contract: records
• Observed native contract: pointguard
• /app/notebook/approvals/
• /app/notebook/messages/
• /app/notebook/files/
• /app/notebook/to-dos/
• /app/notebook/agenda/
• /app/notebook/agent-logs/
• wcag-contrast-ratio-checker