--- name: consult-framing description: Prepare or adopt exact engagement framing from an accepted promise, readable agreed framing, or bounded internal authority, preserving scope, criteria, ownership and unresolved limits. metadata: version: 0.1.1 --- Read [working instructions](references/governing.md) before applying this method. # Take over the promise and frame the work Read and apply the [common working instructions](references/source/implementation/working-character/instructions.md) and the [domain requirements](references/source/implementation/runtime/requirements.md#selected-domain-requirements) selected for this task. Verify tool access and storage operations in the current environment; do not infer either from this skill's availability. Missing required instructions or access block only dependent operations; continue permitted work from supplied material. Return one useful brief with identifiable Engagement, Baseline, Handoff, Stakeholder and expected Outcome sections where applicable. Preparation records no actual adoption, start, retention, release or acceptance. People retain those decisions. Read the [output contract](references/source/implementation/skills/consult-framing/references/output-contract.md), [operational requirements](references/source/implementation/skills/consult-framing/references/source-map.md), [entity lineage](references/source/implementation/runtime/entity-lineage.md), [binding contract](references/source/implementation/workspace-bindings/contract.md) and this method's entity-home/method-settings roles in the [binding catalog](references/source/implementation/runtime/binding-catalog.json). Resolve each needed operation against the actual authorized home and available tools. Reuse current valid target choices, authority, answered questions and standing effort limits. No full firm setup is required. For project creation or revised framing, apply [project record maintenance](references/source/implementation/workspace-bindings/contract.md#project-record-maintenance). Inspect existing framing, partial plan and human notes first; propose only missing sections/references. Reuse contextual Party/Stakeholder and `baseline.stakeholders`, with exact permitted Sales references and unknown sponsor/authority kept unknown. Return the relevant originals/states and maintenance handoff; a table suffices and only consequential unresolved decisions need confirmation. 1. Identify the ordinary request, purpose, intended readers, exact engagement and current home. Use the smallest sufficient readable input. Preserve original wording, notes/dissent, source revisions, passages, read coverage and rights. Synthetic/sanitized work needs no real-client setup. Before admitting real material, establish authorized assistance/context/audience and applicable policy. Access, information use, operational acceptance and work authority are separate. Unread/private/restricted items stay excluded from text, links, metadata and receipts. 2. Choose the compatible entry: - **sale-handover:** inspect the exact accepted proposal when present, submission and acceptance evidence, current order/call-off and handoff. Carry question, promises, scope/exclusions, staffing/price assumptions, stakeholders and risks with their existing qualifications. Delivery lead accepts or names gaps. When seller is lead, an attributable acknowledgement suffices: reference rather than retype the promise. Adopt criteria already agreed without redundant approval. A direct award has no invented proposal; the actual call-off supplies its promise. - **existing-framing:** adopt the readable exact agreed question/scope/criteria and decision references. No sale, pursuit or handoff is forced. Preserve stable baseline identity and revision rather than create a competing current baseline. A delivery lead adopting existing framing is not thereby a seller or a receiver acknowledging a sale handoff; attribute only the roles evidenced in this context. - **internal-work:** inspect the bounded internal/investment/pro-bono decision, sponsor, purpose, scope, caps/expiry and criteria. No buyer, proposal or order is invented. A workshop's criterion can be observable participation/result rather than a fabricated rendered file. 3. Check the authority at the requested work assessment, against whole original context, actual role/subject and current limits/consumption. An accepted proposal, buyer yes, framework or NDA alone authorizes no paid work. One effective primary basis covers permitted work: concluded order with concluded amendments, or internal decision. Preserve earlier authority and supersession dates without backdating; separately bound any own-risk supplement. A historical concluded order remains historical even if present work coverage is unproved. For bounded sources apply the current [time/authority procedure](references/source/implementation/skills/sales-pursuit-event/references/time-authority-model-0.1.15.md). A responsible usage report neither grants nor extends authority; unknown balance, expiry, revocation, suspension/cancellation or exhausted caps blocks dependent work. 4. Separate agreed framing from proposals and gaps. Identify question/optional structure, in/out/adjacent scope, dates, success criteria, accepting party/procedure and exact version to be reviewed. Record expected outcomes only when named, with supplied measure/target/baseline, data owner and later assessment date or unknown. Delivery acceptance is distinct from measured business effect. Missing criteria, method or unsupported extra scope stays unresolved with owner/settling evidence; do not invent a business/legal decision to complete a template. Carry agreement status through the wording inside every section: a proposed acceptance procedure/home remains proposed. An assessment timestamp is not a work start date or bounded authority interval when no such authority is supplied. 5. Identify effective method/settings versions and their content evidence, applicability and attributable choice. Missing required methods block their tailored lane; common framing continues. Preserve supplied definitions, organizational levels, populations, units, periods and exceptions; apply domain vocabulary and evidence requirements only from applicable configuration or supplied evidence. Labels establish no legal mandate, adopted standard or savings. Method adoption changes no notes, issued promises, authority or wiki content. 6. Reference agreed home/category/context, information owner, lead, permitted participants, continuity owner and exit recipient/retention/export/access terms. Reuse valid arrangements. Durable client work or colleague reuse needs those terms and demonstrated operations/access; missing proof blocks that operation, not a permitted unretained brief. No quiet destination fallback or automatic firm reuse. 7. Lead with what can be adopted/prepared and what cannot proceed. Keep material exclusions, competing views and decision-changing unknowns beside their claims. Give planning the baseline commitments, result criteria and client-input needs with owners/dates or unknown and consequences; do not fabricate assignments or invoke planning/analysis. Return exact source links/qualifications and proposed next settling questions. Readable sections and structured evaluation agree. 8. Self-check wording against whole evidence, including summary claims and numbers. Check source/version/passage links separately from semantic support and actual intended-reader wiki navigation. Record reader misunderstandings honestly: simulated author checks are neither human usefulness nor independent review. Changed bytes invalidate affected checks; identify all readable affected dependencies and unknown coverage. Preserve prior outputs, human originals and authority history. On resumption reconcile exact inputs/configuration/current record and uncertain effects before retry; create no replacement record. Stop at the selected scope for independent review.