Message drafts — forms

The distinct forms record for Message drafts. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: job:wick:message-drafts
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.

Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

Draft brief

Define the communication task and intended audience without authorizing external action.

draft title
communication type: world post, outreach, reply, follow-up, or other
objective
audience or recipient description
desired outcome
owner
priority
requested due date
tags

Source lock

Bind claims and relationship context to inspectable source records.

source record IDs
source locators
source SHA-256 values
provenance notes
claim-by-claim evidence links
relationship history source
unknown or unverified context flags

Message content

Prepare a clear, accessible draft that does not impersonate Antonio or imply unsupported commitments.

draft body
subject or post heading
call to action
pricing language, if any
sender identity and role
attachments or links
accessibility text
tone notes
claims requiring approval

Destination and route check

Record the intended channel and prevent sending from an unverified route.

destination name
channel
route locator
route verification status
recipient identity
account owner
route-specific constraints
send status: held, ready for review, or rejected

Review and receipt

Capture human review, classification, and disposition without performing the external effect.

reviewer
review decision: needs review, approved, or held
decision timestamp
approval scope
rejection or hold reason
response classification
follow-up due date
receipt reference

Accessible state contract

Every field requires a visible and programmatic label.
Required and optional fields must be stated in text.
Invalid entries require an actionable message linked to the field.
Blocked and Held states remain visible without relying on color alone.

Supporting documentation fields

These fields come from the docs_urls lane and remain separate from the primary operating form.

Request and intended channel

Capture what communication is being prepared without implying that a route is verified or that any external action will occur.

request title
communication type: world post or outreach
intended channel or route
recipient or audience description
requested completion date and time zone
operator or requesting person
purpose and desired outcome

Source context

Bind the draft to supplied source material and make unsupported relationship claims visible before drafting.

source record IDs or locators
source summary
source SHA-256 when available
source lock status
relevant account dossier
relevant contact history
claims permitted by source
claims requiring review
missing context

Draft content

Prepare a reviewable communication with explicit authorship, tone, and commitment boundaries.

subject or post title
message body
call to action
tone
pricing statement present: yes or no
relationship commitment present: yes or no
attachments or links
sender identity and route status
draft revision note

Human review and disposition

Record the gate outcome and preserve a receipt for every proposed external effect.

reviewer
review status: Needs review, Approved, or Held
review comments
required changes
approval timestamp
final disposition
reason for hold or rejection

Required or proposed record references

No record existence is asserted by this documentation page.

Canonical message-draft record with ID, owner, origin, source locator, source SHA-256, provenance, revision, lifecycle, tags, links, and attachments.
Source record or source-labelled note supporting each factual statement.
Recipient or destination record with route verification state; no account access is implied.
Approval receipt for every proposed external send or publication.
Response-classification record for any received response, linked to the originating draft.
Contact history or account dossier when relationship context is used; unsupported history must be marked unknown.
source-linked communication brief
draft message or world-post record
source lock record
outreach queue item
account dossier or contact history when applicable
response classification record
approval receipt

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/