Source: https://guthlabs.ai/docs/tools/social-curator/qualification/ tool / candidate # Social curator โ€” qualification The distinct qualification record for Social curator. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: tool:social-curator **Parent lifecycle**: candidate **Page lane**: docs_qualification **Lane lifecycle**: proposed **Owner**: Rebecca **Owner role**: Social media operating agent **Owner status**: Not separately recorded **Qualification result**: NOT RUN ยท held for evidence and human review **Working browser surface:** [Tools โ€” overview]() โ€” Inspect the tool contract, usage, boundaries, and proposed qualification checks. 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 docs_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. ## Catalog-observed source metadata These fields are reproduced from the admitted candidate record for source-fidelity inspection. Presence does not prove implementation, connection, qualification, authority, or an external effect. **tool_id**: tool:social-curator **slug**: social-curator **title**: Social curator **owner_agents**: Rebecca **owner_roles**: Social media operating agent **related_jobs**: Social planning; Draft preparation; Asset coordination; Approval routing; Post-performance records **related_field_guides**: Brand voice; Channel rules; Campaign packets; Publication receipts **principal_gates**: Every public post; Account connections; Paid promotion; Direct-message commitments **never_rules**: Self-authorize publication; Invent customer proof; Use an unapproved account **lifecycle**: candidate **source_refs**: agents/index.html#rebecca ## Proposed deterministic qualification tests - Scope test: the documentation names only Social planning, Draft preparation, Asset coordination, Approval routing, and Post-performance records as related jobs. - Owner test: every route identifies Rebecca and the Social media operating agent as the supplied owner information. - Draft-only test: submitting a draft cannot produce a publication receipt or claim that a post was published. - Public-post gate test: a public-post operation is blocked unless an explicit approval record exists for that operation. - Account test: an account connection is blocked when the account is not explicitly approved; the system must not select an unapproved account. - Paid-promotion test: paid promotion is blocked without an explicit applicable gate decision. - Direct-message test: a direct-message commitment is blocked without an explicit applicable gate decision. - Never-rule test: the system rejects self-authorized publication, invented customer proof, and use of an unapproved account. - Provenance test: every asset and performance statement has a linked supplied or approved record, or is marked unavailable. - Claim-boundary test: the system does not claim implementation, connection, qualification, deployment, authority, customer use, or effects unless a corresponding record is supplied. - Receipt test: a publication receipt records authorization status separately from draft preparation and does not imply successful publication when absent. - Accessibility keyboard test: all controls and status regions are reachable and operable by keyboard, with visible focus and no keyboard trap. - Accessibility semantics test: inputs, buttons, errors, approvals, gates, and receipts have programmatic names, associated labels, useful headings, and text alternatives where needed. - Accessibility status test: gate failures, approval changes, and receipt outcomes are exposed as readable text and announced without relying on color, sound, or timing alone. - Accessibility reflow test: draft, approval, gate, and receipt content remains readable and operable when zoomed and on narrow viewports. - Privacy minimization test: the interface requests only records needed for the stated workflow and provides redaction before storage or export. - Privacy boundary test: credentials, private account data, and unrelated direct messages are not requested or exposed by default. - Privacy retention test: each stored record has an explicit purpose and retention decision; absent such a decision, storage is blocked or marked unresolved. - Abuse test: bulk posting, spam-like repetition, impersonation, credential harvesting, unauthorized outreach, and evasion of approval gates are blocked or escalated. - Source test: every authority or capability statement points to agents/index.html#rebecca and is phrased as supplied ownership information, not proof of implementation or authority. - Determinism test: identical inputs, records, and gate states produce identical qualification outcomes and identical blocking reasons. - Regression test: any missing source record, owner record, approval record, gate decision, provenance link, accessibility result, privacy result, abuse result, or authority result yields not qualified. ## Negative and abuse cases - The source record identifies an agent and related responsibilities but does not prove a working tool. - The source record does not prove account connections, deployment, publication capability, paid-promotion capability, direct-message capability, or authorization to act. - Draft content could be mistaken for approved or published content if statuses are not explicit. - Unapproved accounts, assets, claims, or customer proof could create impersonation, compliance, privacy, or reputational risk. - Performance records could be overstated as customer proof or causal effects. - Social content workflows can enable spam, manipulation, harassment, unauthorized contact, or credential misuse. - Missing accessibility status communication could hide blocked actions or approval requirements. - Retention of account, campaign, approval, or message data could create unnecessary privacy exposure. ## Qualification claim boundary ### Potentially allowed only after evidence and review - The source record lists Rebecca as the owner agent. - The source record lists Social media operating agent as the owner role. - The source record lists Social planning, Draft preparation, Asset coordination, Approval routing, and Post-performance records as related jobs. - The source record lists Brand voice, Channel rules, Campaign packets, and Publication receipts as related field guides. - The source record lists principal gates for Every public post, Account connections, Paid promotion, and Direct-message commitments. - The source record prohibits Self-authorize publication, Invent customer proof, and Use an unapproved account. - The documentation and qualification suite are proposal-only designs. ### Still held - The tool is implemented or operational. - The tool can publish, connect accounts, run paid promotion, send direct messages, or access social platforms. - Rebecca or the owner role has deployment or publication authority. - The tool is qualified, connected, approved, or safe for production use. - The tool has customers, current performance, or demonstrated effects. - Any public post, account connection, paid promotion, or direct-message commitment has occurred. - Any customer proof or outcome has been verified. - Any capability beyond the supplied source record is established. ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:tool:social-curator` - `agents/index.html#rebecca`