Source: https://guthlabs.ai/docs/jobs/rebecca-approval-routing/forms/ job / candidate # Approval routing โ€” forms The distinct forms 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**: package **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. ## Proposed form sections Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth. ### Communication brief Define the proposed public communication and its source-backed intent. - communication title - business page or channel name - communication objective - audience - campaign or initiative - requested publish window - source records and locators - attachments or referenced files ### Draft and channel fit Capture the draft and the rules used to review it before approval. - draft text - media or attachment references - channel format - brand voice reference - channel rules reference - claims requiring evidence - customer proof included - customer proof source - account selected - account approval status ### Principal gates Make each consequential gate explicit rather than implicit. - public-post gate status - account-connection gate status - paid-promotion gate status - direct-message commitment gate status - required approver - review notes - blocking reason - held decision reason ### Deadline and workback Track timing without implying an external calendar write or publication. - requested publish date and time - timezone - draft-ready deadline - review deadline - approval deadline - final human confirmation deadline - conflict or dependency notes - to-do priority - recurrence candidate ### Approval and publication receipt Preserve a local evidence trail for decisions and any later human-reported result. - approval state - approver identity - approval timestamp - approval scope - human publication confirmation - publication timestamp if supplied - publication locator if supplied - receipt source - revision identifier - follow-up owner ### Accessible state contract - Every field requires a visible and programmatic label. - Required and optional fields must be stated in text. - Invalid entries require an actionable message linked to the field. - Blocked and Held states remain visible without relying on color alone. ## Supporting documentation fields These fields come from the docs_urls lane and remain separate from the primary operating form. ### Draft brief Capture the communication request and its accountable owner. - request title - requester - business page or communication context - objective - audience - channel - proposed account - draft text - call to action - requested publish window - priority - source references - campaign packet reference ### Evidence and claims Separate supported source material from proposed language and identify claims requiring review. - supporting record IDs - customer-proof references - claim inventory - claim status: supported, needs review, or prohibited - attachment references - source locator - source SHA-256 when applicable - provenance note ### Principal gates Require explicit handling for publication, account use, paid promotion, and direct-message commitments. - public-post gate decision - account-connection gate decision - paid-promotion gate decision - direct-message commitment gate decision - unapproved-account check - self-authorization check - human approver ### Approval decision Record the exact revision and decision outcome. - approval status: needs review, approved, or held - approver identity - decision timestamp - revision reviewed - decision rationale - required changes - expiry or re-review condition - receipt reference ## Required or proposed record references No record existence is asserted by this documentation page. - Job record for Rebecca approval routing - Draft record with canonical ID, origin, source locator, source SHA-256, provenance, revision, lifecycle, tags, links, and attachments - Content calendar record - Approval queue record - Campaign packet record - Brand voice record - Channel rules record - Publication receipt record - Account connection review record - Paid promotion review record - Direct-message commitment review record - To-do records for deadlines and workback steps - Agent log record preserving work, receipts, authority, and current state - Draft record with canonical ID, owner, source reference, channel, proposed account, content, attachments, tags, revision, and lifecycle - Approval record with approver, decision, decision time, revision reviewed, rationale, and receipt link - Content-calendar item with proposed publish time, priority, deadline, and current state - Channel and account declaration identifying the intended account without implying an active connection - Brand-voice and channel-rules references - Campaign packet reference when the draft belongs to a campaign - Publication receipt record, held unless publication is separately performed and verified by a human ## 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.`