Source: https://guthlabs.ai/docs/jobs/rebecca-approval-routing/field-guides/

job / candidate

# Approval routing — field guides

The distinct field guides 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**: docs_urls

**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](<https://guthlabs.ai/guth.html#builder>) — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Related field-guide records

- /app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

## Operating sequence

- Create or open the Rebecca job record and PointGuard context room.

- Capture the communication brief and link source-labelled notes, files, campaign packets, brand voice, and channel rules.

- Create a draft with an explicit target channel, account, audience, and requested publish window.

- Check the draft for unsupported customer proof, unapproved accounts, paid-promotion implications, and direct-message commitments.

- Place the draft in the local approval queue with every principal gate marked Needs review, Approved, or Held.

- Create deadline to-dos using a backward plan from the requested publish window; preserve timezone and dependencies.

- Route the approval request to the designated human approver and retain the source context.

- Revise only through a new draft revision when review changes the content, claims, channel, account, or timing.

- Require explicit human approval for every public post before any publication activity is considered.

- Require separate human review for account connections, paid promotion, and direct-message commitments.

- Record a publication receipt only from supplied human or source-labelled evidence; otherwise leave publication Held.

- Write an agent log receipt covering actions taken, authority boundaries, unresolved blockers, and next owner.

## Handoff boundary

- Self-authorized publication

- Invented customer proof or unsupported public claims

- Use of an unapproved account

- Treating a local prototype route as a connected social provider

- Confusing draft approval with account connection approval

- Paid promotion proceeding without separate review

- Direct-message commitments being treated as ordinary posts

- Silent deadline or timezone errors

- Publication receipts being inferred without evidence

- Private or customer information being exposed in public drafts

- Duplicate or stale revisions being approved

- Accessibility failures in gate status, forms, or approval actions

## 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`

- `Observed native contract: Notebook collection lifecycle and membership ordering`

- `Observed native contract: Notebook deadlines and to-dos`

- `Observed native contract: canonical record provenance and revisions`

- `Observed native contract: PointGuard context boundary`

- `Observed app routes: /app/notebook/approvals/`

- `Observed app routes: /app/notebook/agent-logs/`

- `Observed app routes: /app/notebook/field-guides/`

- `Observed app routes: /app/notebook/messages/`

- `Observed app routes: /app/notebook/projects/`

- `Observed app routes: /app/notebook/to-dos/`

- `Observed app routes: /app/notebook/agenda/`

- `Observed app routes: /app/pointguard/`

- `job:rebecca:approval-routing`

- `Observed native contract: PointGuard is a persistent cross-app context surface; specialist apps remain execution and canonical-record owners.`

- `Observed native contract: Current GuthHub app routes are local prototypes or indexes; provider, credential, database, customer, publication, and production effects are held.`
