Message drafts — field guides

Record status

Record ID

job:wick:message-drafts

Parent lifecycle

candidate

Page lane

docs_urls

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.

Related field-guide records

No separate guide route is admitted for this project or job.

Source-proposed guide paths are references, not proof that those paths resolve.

Operating sequence

1. Create a local draft brief and assign Wick as the preparing owner.
2. Collect and lock source records before writing factual claims or relationship context.
3. Record each material claim with its source locator and provenance; mark unsupported claims unknown.
4. Draft the message with sender identity, recipient, destination, and accessibility text visible.
5. Check that the route is verified and that the draft does not impersonate Antonio, invent relationship history, or make an unapproved pricing or relationship commitment.
6. Save the draft as a revisioned, source-linked message record with external action held.
7. Create an approval item for every proposed send or publication and preserve the reviewer receipt.
8. If a response is supplied, classify it and create a linked contact-history or follow-up record only from supported content.
9. Track the human-approved next action as a local to-do; do not send, publish, access accounts, or represent Guth autonomously.

Handoff boundary

• External send or publication may occur without explicit human approval.
• A draft may impersonate Antonio or imply Guth representation beyond Wick's bounded role.
• Unverified routes or account access may expose information or create unauthorized commitments.
• Relationship history, pricing, recipient identity, or source claims may be invented or stale.
• A response classifier may be mistaken; classification must remain reviewable and non-authoritative.
• Prototype app routes may be mistaken for connected communication infrastructure.
• Attachments or source references may expose private material without a visibility review.
• Deadlines may be treated as authorization; deadlines organize review only.
• Accessibility failures may hide held, rejected, overdue, or approved states.

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:message-drafts
• Observed native contract: Notebook records preserve canonical IDs, provenance, revisions, lifecycle, links, and attachments.
• Observed native contract: Notebook todo payload supports due dates, priority, completion state, tags, revisions, and deadline views.
• Observed native contract: final send remains human-held on Notebook Messages and Business Messages.
• Observed native contract: PointGuard is a persistent cross-app context surface; specialist apps remain execution and canonical-record owners.
• Observed app routes: /app/notebook/messages/
• Observed app routes: /app/notebook/approvals/
• Observed app routes: /app/notebook/agent-logs/
• Observed app routes: /app/business/messages/
• Observed app routes: /app/pointguard/
• job:wick:message-drafts
• Observed native contract: current GuthHub app routes are local prototypes or indexes and provider, credential, database, customer, publication, and production effects are held.
• Observed app route: /app/business/messages/
• Observed app route: /app/notebook/messages/
• Observed app route: /app/notebook/approvals/
• Observed app route: /app/notebook/agent-logs/
• Observed app route: /app/pointguard/