Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

tool / candidate

Source lock — qualification

The distinct qualification record for Source lock. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
tool:source-lock
Parent lifecycle
candidate
Page lane
docs_qualification
Lane lifecycle
proposed
Owner
Wick
Owner role
World posts and outreach 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.

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:source-lock
slug
source-lock
title
Source lock
owner_agents
Wick
owner_roles
World posts and outreach agent
related_jobs
World-post research; Outreach dossiers; Message drafts; Response triage; Campaign chronology
related_field_guides
World packets; Outreach rules; Account dossiers; Contact histories
principal_gates
Every external send; Relationship commitments; Pricing statements; Account access
never_rules
Impersonate Antonio; Send from an unverified route; Invent relationship history
lifecycle
candidate
source_refs
agents/index.html#wick

Proposed deterministic qualification tests

  • Source-record fidelity: rendered source record exactly contains tool_id tool:source-lock, slug source-lock, title Source lock, owner agent Wick, owner role World posts and outreach agent, all five related jobs, all four related field guides, all four principal gates, all three never-rules, and agents/index.html#wick.
  • Unknown preservation: an artifact with no implementation, connection, deployment, or authority evidence receives unknown for those fields and cannot receive an overall qualified status.
  • Identity gate: any artifact proposing impersonation of Antonio fails immediately and records the matching never-rule.
  • Route gate: any artifact proposing a send from an unverified route fails immediately; absence of route verification is unknown and blocks sending.
  • History gate: any relationship assertion lacking a supplied supporting record is unknown; any assertion contradicting supplied records fails; no history may be inferred from tone or similarity.
  • Source gate: every externally material claim must map to a supplied source reference or be marked unsupported; unsupported claims block external send.
  • Commitment gate: pricing statements or relationship commitments without explicit review evidence fail or remain unknown and block sending.
  • Account-access gate: any account-access request without explicit supplied authority fails; the catalog record alone never grants access.
  • Privacy test: collection of recipient credentials, unnecessary sensitive data, or unrestricted contact-history export fails minimization review; redaction must be available before export.
  • Abuse test: bulk unsolicited outreach, deceptive identity, evasion of opt-out, harassment, fraud, or pressure tactics fails and produces escalation guidance rather than a draft send.
  • Accessibility test: every interactive control is keyboard reachable, has a programmatic name, visible focus, associated error text, and status conveyed without color alone.
  • Accessibility structure test: each documentation route has one clear primary heading, logical heading order, descriptive link names, sufficient text alternatives for non-text content, and no instruction dependent only on visual position.
  • Determinism test: identical artifact, source set, rule version, and inputs produce byte-equivalent qualification results and remediation codes.
  • No-side-effect test: qualification, export, comparison, and remediation routes do not send messages, publish posts, alter chronology, access accounts, or contact recipients.
  • Source integrity test: modifying a supplied artifact changes its reported digest or comparison result; the integrity result must not be described as proof of truth or authority.
  • Disposition test: any fail or unknown on a principal gate yields blocked; only all required gates passing may yield proposal-qualified, never operationally authorized.

Negative and abuse cases

  • Observed catalog presence may be mistaken for implemented or deployed capability.
  • Owner-agent labeling may be mistaken for permission to send, publish, access accounts, or make commitments.
  • A digest or text comparison may be mistaken for source truth or relationship proof.
  • Incomplete records can create false confidence if unknown is collapsed into pass.
  • Personal contact histories and recipient data may be over-collected, exposed, or retained unnecessarily.
  • Qualification tooling could be repurposed for spam, impersonation, coercion, fraud, or route-evasion.
  • Accessibility failures could exclude reviewers or hide blocking statuses.
  • Pricing and relationship commitments can create legal, reputational, or commercial exposure.
  • A source URL alone does not prove currentness, authorship, permission, or authority.

Qualification claim boundary

Potentially allowed only after evidence and review

  • The supplied record identifies tool:source-lock with slug source-lock and title Source lock.
  • The supplied record names Wick as owner agent and World posts and outreach agent as owner role.
  • The supplied record lists the supplied related jobs, field guides, principal gates, never-rules, and source reference.
  • This response proposes documentation routes and deterministic qualification tests.
  • The proposal treats implementation, connection, qualification runtime, deployment, and authority as unproven.
  • A qualification result can describe evidence status and blocking conditions if the required records and deterministic inputs are present.
  • The proposed system must not send, publish, access accounts, impersonate Antonio, invent relationship history, or make commitments without independently supplied authority.

Still held

  • The tool is implemented or connected.
  • The tool is deployed or operational.
  • Wick or any owner role has authority to send external messages or publish world posts.
  • The source reference is reachable, current, authoritative, or sufficient by itself.
  • Any customer, provider, deployment, usage, metric, effect, or workflow outcome exists.
  • The tool can verify identity, source truth, permission, relationship history, pricing, or account access without supplied evidence.
  • A qualification result authorizes an external send or relationship commitment.
  • Any compatible instrument establishes authority, provenance, or truth.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

  • source_record:tool:source-lock
  • agents/index.html#wick