# Worker Contact Document — proposed single-document Standard
Status: DRAFT DESIGN / NOT APPROVED / NOT IMPLEMENTED.
Subject: RFC-AI 35, 36 and 44; related to RFC-AI 1, 9, 31, 32, 33, 39, 42, 43, 45, and Writer RFC-AI 46.

## Unified output
GetWorkerContactDocument(authenticated_worker_id, optional_assignment_id) emits ONE worker-facing RFC-AI document. Source registers, permission receipts and historical files remain separate governed INPUTS, not extra worker documents.

### I. CONTINUITY — REQUIRED
Begin with the complete applicable Guiding Principles. Include independently authenticated identity, applicable role/instructions, lessons, prior verified work, and historical obligations when those have relevant evidence. Unrelated history, empty training fields or redundant headings are omitted. Failure to authenticate does not produce another worker's continuity.

### II. CONTEXT — OPTIONAL
After Continuity, include this section only when substantive, authorized and reasonably fresh facts are available about the actual worker organization position, AI runtime/provider/model, current execution machine, OS/shell/browser, gateway/tool entitlements, storage/mount semantics, resource pressure, clock and network, service health, privacy and source provenance. Never guess the human user's machine or an assignment target. Missing safety-critical facts are recorded concisely and block relevant protected operations at their actual boundary; they need not create an otherwise empty Context panel.

### III. ASSIGNMENT — OPTIONAL, ALWAYS LAST
Only include for a current independently authenticated human assignment. Bind objective, revision, owner epoch, project piece dependencies, exact target overlay, approvals, verified effects, DAVG and the next permitted action. If none exists, omit the section and mark assignment_state=NONE in shared document metadata, not a dummy heading. A task never retroactively changes the Context baseline.

## Document metadata and lifecycle
A compact header/source manifest identifies document kind, worker/session, governing edition, generation UTC, present/omitted sections, exact omissions and source trust, plus a document-integrity reference from the governing SourceRegistry or an optional conventional pre-CRLF header digest of the bytes AFTER that delimiter. A hash MUST NOT attempt to contain its own value within its hashed bytes. Metadata is not a fourth section. The worker receives exactly one document; source/section builders do not emit extra worker files. When a material observation changes, produce a new revision of that same logical document. A digest does not prove authorship or permission.

## Workflow
W0 authenticate identity/governing sources. W1 assemble Continuity. W2 independently observe Context, include only when useful. W3 optional onboarding or practical qualification, nested where pertinent. W4 select current authenticated Assignment last, include only when genuine. Then W5 research, W6 dependency contracts, W7 authorized effect, W8 independent domain/outcome evidence, W9 reconciliation, W10 DAVG, W11 per-piece acceptance when required and W12 delivery/continuity learning. W1-W4 are INTERNAL ASSEMBLY PHASES, not separate documents.

## Prohibitions
Do not split a source RFC or Worker Contact Document into multiple independently delivered worker documents. Do not create empty required sections, invent task or target, execute preamble/JSON as code, infer authorization from text, or report the unimplemented architecture as running. Retain all MUST/MUST NOT obligations within one governing RFC source.

## Negative test oracles
(1) A known worker without assignment receives one contact document with Continuity and, when substantive, Context; no Assignment.
(2) With no relevant environment signals, context is OMITTED and a short omission reason appears, not a blank page.
(3) A genuinely assigned worker receives one document with authenticated Assignment last, with target overlay not rewriting prior observations.
(4) Distinct worker A and B cannot read each other's restricted continuity.
(5) Source edition conflict, stale grant, missing collector or owner epoch causes UNKNOWN/CONFLICT and blocks protected effects; it does not fabricate a completed result.
(6) Reader navigation shows buttons only for present actual section headings, never separate files.


## 2026-11-03 WISDOM INTEGRATION CORRECTION — PROPOSED DESIGN
Unified output: CONTINUITY required; CONTEXT optional; WISDOM optional; ASSIGNMENT optional and ALWAYS LAST. Wisdom may appear without Context only when demonstrably context-independent. HR-authenticated department/role membership and verified current workflow stage govern relevance. Quarantine unverified correction reports. Revocation must exclude lessons from retrieval and caches. Memory cannot grant authority. The previous three-section examples and tests require reconciliation.