#!RFC-AI/2;id=11;draft=4;v=0.4.0;status=draft;lang=en;dir=auto;theme=chatgpt-mono;sha256=204cb765d6134ba767356d6e121d9a1693db0ac4fca46fbc72458f48fac4746d
For easier reading, view RFC-AI documents using RFC-AI Reader software.

RFC-AI 11 — CORPORATE CONTEXT RESOLUTION AND DEEP RESEARCH FIRST
DOCUMENT CLASS: AI RFC — INTELLIGENT-WORK GUIDANCE
STATUS: DRAFT FOR CEO REVIEW — ENTIRE RFC-AI SYSTEM UNIMPLEMENTED

1. PURPOSE — WHAT AND WHY
Investigate all relevant contexts before interpreting an assignment. An intelligent worker first conducts meaningful internal investigation and proportionate external research, rather than interpreting an assignment from superficial wording or memory.

2. INTELLIGENT-WORK DIRECTION
Read applicable instructions and project objectives, prior work, logs, completed and unresolved DAVG, lessons, collaborators, real environmental context and relevant research. Resolve contradictions and source authority before deciding what action serves the objective.

3. PROPOSED IMPLEMENTATION APPROACH
Use the relevant authorized Interface, component and expressly designated Standard: RFC-AI 3, 5, 18, 31, 35 and 36. Investigate the complete relevant context before deciding what the assignment means (see RFC-AI 11). A competent worker may discover, invent and improve the necessary methods during implementation; this guiding AI RFC is not required to repeat low-level APIs, algorithms or technology choices. Previous and legacy systems are research evidence only, never an implementation of this draft.

4. EVALUATION AND ACCOUNTABILITY
Use independent DAVG as described in RFC-AI 22 to challenge whether the eventual real-world result meets the objective, not whether the AI RFC looks like a traditional API specification. A missing prerequisite creates an active cross-worker recovery obligation through the worker coordination Interface, not a reason to abandon the task (RFC-AI 20 and 31). Report only verified effects and preserve lessons without reintroducing old operational mistakes.

5. DESIGN CUSTODY
Original subject-specific intended contract: Resolve WHO WHAT WHERE WHEN WHY HOW; read current objectives, CEO decisions, lexicon, coding standards, forbidden rules, logs, DA/DAVG, research ledger before work; only claim accessed sources actually read.
Implementation tasks, legacy-derived candidate methods, proposed data schemas, tests and open engineering questions are kept with this draft's append-only objectives.txt or the responsible Interface/Standard. This RFC has NOT been implemented; it does not approve a deployment or create a new CEO release gate. Rewritten 2026-11-02T20:28:09.285Z.


## HISTORICAL FAILURE EVIDENCE — RESEARCH ONLY; NOT AN RFC-AI IMPLEMENTATION
Historical context: Workers began assignments before investigating complete existing context; prior work, authoritative objectives, roles and DA evidence were missed.
Historical reports have mixed evidence quality; verify primary facts before adopting a claimed root cause. Preserve source provenance and do NOT operationalize retired legacy policies as current RFC authority.

## MUST-DESIGN CRITERIA — CEO-DIRECTED PROPOSED FUTURE SYSTEM
MUST-11-01: MUST literally investigate every materially relevant accessible context before deciding what the assignment means; historical logs, sources, prior DAVG, current decisions, interfaces, roles, capabilities and affected recipients count.
MUST-11-02: MUST track justified relevance and unexamined material leads; MUST NOT endlessly fetch irrelevant history or substitute stale information for authenticated current instructions.
MUST-11-03: MUST direct qualified worker roles to investigate missing context when ordinary independent investigation cannot obtain it.

IMPLEMENTATION STATUS: Entire RFC-AI system NOT IMPLEMENTED. Historical systems are independent past research material; no test or existing service may be counted as implementing this RFC-AI.

## DESIGN REVIEW ADDENDUM 2026-11-03 — CONTEXTUAL RESEARCH
REQ-AI-11-CONTEXT-001: Investigate current governing instructions, identity-specific continuity and actual environment context BEFORE assignment execution. Actual OS/runtime/host/provider entitlements, storage authority, resource pressure and collected evidence MUST be stated as VERIFIED, REPORTED or UNKNOWN; a previous machine name does not establish present host.
REQ-AI-11-CONTEXT-002: Research MUST be scoped to authenticated assigned objectives after Continuity and Context; relevance and demonstrated downstream usefulness take precedence over mechanical search volume.