Source: https://guthlabs.ai/docs/tools/source-lock/

tool / candidate

# Source lock

Proposal-only contract for a source-control gate owned by Wick. It would constrain world-post research, outreach dossiers, message drafts, response triage, and campaign chronology by requiring traceable source records before external sends, relationship commitments, pricing statements, or account access. Implementation, connection, qualification, deployment, and authority are unproven.

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: tool:source-lock

**Parent lifecycle**: candidate

**Page lane**: contract

**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](<https://guthlabs.ai/labs.html#tools>) — 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.

## Bounded contract

Proposal-only contract for a source-control gate owned by Wick. It would constrain world-post research, outreach dossiers, message drafts, response triage, and campaign chronology by requiring traceable source records before external sends, relationship commitments, pricing statements, or account access. Implementation, connection, qualification, deployment, and authority are unproven.

### Owners

- Wick

- World posts and outreach agent

### Inputs

- World-post research

- Outreach dossiers

- Message drafts

- Response triage

- Campaign chronology

- World packets

- Outreach rules

- Account dossiers

- Contact histories

- Proposed external-send content

- Proposed relationship commitments

- Proposed pricing statements

- Proposed account-access requests

### Outputs

- Proposal-only source-lock decision for a gated action

- Source traceability status for supplied outreach material

- List of missing, conflicting, or unsupported records

- Escalation or hold notice when a principal gate cannot be satisfied

## Required or proposed record references

The list defines expected records; it does not assert that any record instance exists.

- Source record for the proposed action

- Applicable world packet

- Applicable outreach rules

- Relevant account dossier

- Relevant contact history

- Route verification record for any external send

- Evidence supporting relationship history

- Evidence supporting pricing statements

- Authorization record for account access

## Route contract

The links below are this site's admitted canonical public records. Source-lane route suggestions are proposals only and are not represented as live or canonical until separately admitted.

[01**overview**/docs/tools/source-lock/](<https://guthlabs.ai/docs/tools/source-lock/>)[02**usage**/docs/tools/source-lock/usage/](<https://guthlabs.ai/docs/tools/source-lock/usage/>)[03**boundaries**/docs/tools/source-lock/boundaries/](<https://guthlabs.ai/docs/tools/source-lock/boundaries/>)[04**qualification**/docs/tools/source-lock/qualification/](<https://guthlabs.ai/docs/tools/source-lock/qualification/>)

### Held source-proposed extensions

- /docs/source-lock/contract: Define the gate inputs, outputs, records, dependencies, and non-authority boundary.

- /docs/source-lock/gates: Describe checks for external sends, relationship commitments, pricing statements, and account access.

- /docs/source-lock/failure-states: Describe missing-source, unverified-route, conflicting-history, and unauthorized-access holds.

- /docs/source-lock/never-rules: Explain prohibitions on impersonation, unverified sending, and invented relationship history.

- /docs/source-lock/overview — scope, proposal-only status, non-authority statement, and supported artifact classes.

- /docs/source-lock/source-record — exact supplied catalog record, owner, jobs, field guides, gates, never-rules, and source reference.

- /docs/source-lock/qualification-model — deterministic pass/fail/unknown rules for claims, identity, route, history, pricing, commitments, and account access.

- /docs/source-lock/pre-send-gates — one gate per principal gate with blocking conditions and required records.

- /docs/source-lock/source-provenance — claim-to-reference mapping, source freshness fields, and unknown handling.

- /docs/source-lock/relationship-history — allowed evidence model and explicit prohibition on invented history.

- /docs/source-lock/privacy-and-data-minimization — data classes, minimization, retention, redaction, and no account-access assumption.

- /docs/source-lock/abuse-and-safety — impersonation, unauthorized sending, coercive outreach, spam, fraud, and escalation handling.

- /docs/source-lock/accessibility — keyboard, focus, labels, headings, error messaging, contrast, and non-color status requirements.

- /docs/source-lock/authority-boundaries — what the supplied record establishes and what remains unproven.

- /docs/source-lock/test-vectors — deterministic fixtures for pass, fail, and unknown outcomes.

- /docs/source-lock/change-log — versioned rule changes and reviewer decisions.

These extension paths are not generated by this record and must not be treated as resolving routes.

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