Response triage — tools

The distinct tools record for Response triage. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: job:wick:response-triage
Parent lifecycle: candidate
Page lane: package
Lane lifecycle: proposed
Owner: Wick
Owner role: World posts and outreach agent
Owner status: HELD
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.

Authoritative package lane tools and interfaces

Canonical tools-page assignments

World recorder (record · required) — Preserve the source-linked world-post context, locator, provenance, and revision history.
Outreach queue (interface · required) — Track response items, due dates, priority, review state, and held external actions.
Source lock (skill · required) — Separate verified source facts from unknown, conflicting, or unsupported claims.
Response classifier (skill · required) — Provide a bounded classification of intent, urgency, tone, risks, and proposed next action.
World packets (guide · required) — Supply the applicable source-backed world-posting procedure.
Outreach rules (guide · required) — Constrain drafting, route verification, escalation, and external communication behavior.
Account dossiers (guide · required) — Provide account-specific context without granting account access or asserting unverified facts.
Contact histories (guide · required) — Check relationship history and prevent invented commitments or familiarity.
Notebook Messages (interface · required) — Own local draft preparation and recipient/context review while final send remains held.
Notebook Approvals (interface · required) — Own proposal review, approval, hold state, and receipts.
Notebook Agent Logs (interface · required) — Expose Wick's current work, authority boundaries, evidence, and receipts.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

Canonical tools-page assignments

No verified instrument is assigned to this tools lane.

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

Impersonating Antonio or implying personal authorship without approval.
Sending from an unverified route or treating a route label as proof of connectivity.
Inventing relationship history, account facts, commitments, or customer context.
Turning a local prototype route into a claim of provider connection or external effect.
Publishing world posts or sending outreach without a human gate.
Including unsupported pricing, availability, promises, or legal/commercial commitments.
Using account access, credentials, or protected customer data outside the job boundary.
Losing source provenance, canonical IDs, revisions, or the exact approved draft.
Treating classifier output as authorization rather than bounded assistance.
Creating doorway documentation routes without distinct useful procedural content.

Sources and evidence

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

agents/index.html#wick
source_record:job:wick:response-triage
observed_native_contract:records
observed_native_contract:pointguard
observed_native_contract:deadlines
app_route:/app/notebook/messages/
app_route:/app/notebook/approvals/
app_route:/app/notebook/agent-logs/
app_route:/app/notebook/field-guides/