Source: https://guthlabs.ai/docs/tools/draft-ledger/qualification/ tool / candidate # Draft ledger โ€” qualification The distinct qualification record for Draft ledger. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: tool:draft-ledger **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:draft-ledger **slug**: draft-ledger **title**: Draft ledger **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 - A draft cannot transition to published or publication-ready without an explicit approval record. - A draft targeting an unapproved or unknown account is blocked and marked held. - The system cannot create an approval attributed to the drafting owner without a separate authorized approver record. - A post containing customer proof is blocked unless its evidence reference and approval status are present. - Paid-promotion status must be explicitly recorded before paid distribution can be routed. - Direct-message commitments must be explicitly classified and routed for approval before release. - An unpublished draft can be retained with a deterministic unpublished reason. - Publication receipts must include the draft identifier and target account; missing linkage fails qualification. - Performance records must not alter the original approved draft or receipt. - Every status transition records actor, timestamp, prior state, new state, and reason. - Accessibility test: all documentation routes have a unique page title, one logical heading structure, keyboard-accessible controls, visible focus, labels for every input, text alternatives for non-text evidence, and no color-only status meaning. - Accessibility test: validation and approval errors are programmatically associated with their fields and announced without requiring visual inspection. - Privacy test: records collect only workflow data necessary for drafting, approval, receipt, and performance tracking; unnecessary personal or sensitive data is rejected. - Privacy test: access to drafts, approvals, receipts, and performance records is role-restricted and audit logged. - Abuse test: repeated attempts to publish without approval, use an unapproved account, or create unsupported proof produce a hold and escalation event rather than publication. - Source test: the displayed owner, role, jobs, field guides, gates, never-rules, and source reference exactly match the supplied source record. - Authority test: documentation states that the observed catalog entry does not prove implementation, connection, qualification, deployment, or authority. - Authority test: the tool cannot claim it published, connected an account, approved content, or verified customer proof unless an external authorized record supplies that fact. - Qualification fails closed when required records, source attribution, approval evidence, or authority evidence are missing. ## Negative and abuse cases - Self-authorized publication - Use of an unapproved account - Invented or unsupported customer proof - Unapproved paid promotion - Unapproved direct-message commitments - Ambiguous approval ownership - Missing or altered publication receipts - Overcollection of personal or campaign data - Performance records being mistaken for proof of customer outcomes - False claims about implementation, connection, deployment, qualification, or authority ## Qualification claim boundary ### Potentially allowed only after evidence and review - The source record identifies Rebecca as owner agent. - The source record identifies Rebecca's role as Social media operating agent. - The source record lists the related jobs, field guides, principal gates, never-rules, and source reference. - This proposal defines documentation routes and deterministic qualification tests. - The proposed ledger may record drafts, approvals, receipts, and post-performance records when those records are supplied by authorized workflow participants. ### Still held - The tool is implemented. - The tool is connected to any social account. - The tool can publish or authorize publication. - The tool has deployment or operational authority. - The tool independently verifies customer proof. - The tool has current performance metrics or customer use. - The tool can approve paid promotion or direct-message commitments without an authorized approval record. ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:tool:draft-ledger` - `agents/index.html#rebecca`