Source: https://guthlabs.ai/docs/jobs/rebecca-approval-routing/qualification/ job / candidate # Approval routing โ€” qualification The distinct qualification record for Approval routing. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: job:rebecca:approval-routing **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. - Positive: a complete draft with source context, approved account reference, named human approver, bounded scope, accessible content, and valid chronology is represented as Needs review and can become Approved only through an explicit local human decision. - Negative: Rebecca cannot transition any item directly from Draft to Published or invoke a publication action. - Negative: a post marked paid promotion, containing a direct-message commitment, or targeting an unapproved account remains Held until the corresponding principal gate is explicitly approved. - Negative: missing source locator, missing draft revision, missing approver, missing account authorization, or missing timezone prevents approval. - Negative: customer proof, testimonials, metrics, or outcomes not present in supplied source records are rejected rather than completed by inference. - Privacy: drafts containing unnecessary personal data, private customer details, credentials, tokens, or protected account information are rejected or redacted before routing; access remains partitioned from public context. - Chronology: the system rejects any workback where deadlines are equal to or later than their dependent deadline, or where target_publish_at precedes approval_due_at. - Source: every factual claim has a linked source record or is labeled as draft language requiring review; source revision and provenance remain inspectable. - Authority: a named native surface is treated as an interface only; no provider connection, credential, database authority, customer indexing, publication, or production effect is asserted. - Accessibility: all form controls have programmatic labels, keyboard operation, visible focus, non-color status indicators, sufficient contrast, readable error text, and a logical heading and reading order; approval status is not conveyed by color alone. - Accessibility: draft text and decision reasons are available as text, not image-only content; all validation errors identify the field and remediation. - Failure-state: provider, credential, account, database, or export effect being unavailable produces Held with a specific reason and preserves the local proposal. - Failure-state: conflicting approvals, stale revision, missing receipt, or changed gate produces Needs review or Held and records the conflict without silently selecting a decision. - Ownership: the job remains owned by Rebecca as proposed owner agent, while final approval and external effect remain human-owned. - Record integrity: edits create a new revision and do not overwrite the prior draft, decision, provenance, or receipt. ## Negative and held-state tests - Self-authorization or accidental publication - Unapproved account use - Invented customer proof or unsupported performance claims - Approval applied to a stale or materially changed draft - Paid promotion or direct-message commitments bypassing review - Exposure of private customer, credential, or account data - Deadline ambiguity caused by missing timezone or invalid workback - Treating local prototype routes as connected production features - Doorway documentation that repeats the same approval language without useful operational detail - Accessibility failures in status, validation, keyboard flow, or contrast ## Qualification claim boundary ### Potentially allowed only after the stated evidence - The supplied job record describes a proposed social operating agent named Rebecca. - The proposed workflow includes draft, review, approval, and publication-receipt concepts. - The supplied principal gates are public posts, account connections, paid promotion, and direct-message commitments. - The supplied never-rules prohibit self-authorized publication, invented customer proof, and unapproved account use. - The current app routes can be used as local prototype or indexed surfaces for drafting, review, records, and receipts. ### Still held - Rebecca is deployed or connected to any provider. - Any account is connected, approved, or controlled. - Any customer is indexed or any customer proof is verified. - Any post has been published or scheduled externally. - Any paid promotion has run. - Any direct-message commitment has been sent or fulfilled. - Any database, credential, publication, or production effect exists. - The job has passed qualification or is operational. ## 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:approval-routing` - `job:rebecca:approval-routing` - `Observed native contract: Notebook records, deadlines, PointGuard, and held web boundary` - `App route: /app/notebook/approvals/` - `App route: /app/notebook/messages/` - `App route: /app/notebook/agent-logs/`