Source: frameworks/gost-enablement/01-gost-enablement-context.md
GOST Participant Enablement — Context & Required Inputs
The Gap Protocol
A gap is any required input not available in the source material.
Procedure:
- Record the gap — what is missing, what it's required for, where it should have come from.
- Stop the build — do not proceed past gap identification.
- Present the gap report to the advisor.
- Wait for resolution — the advisor gathers the missing input or makes a decision.
- Proceed only after the advisor confirms all gaps are resolved.
Prohibitions:
- Never invent GOST content (goals, objectives, strategies) — these must come from the client's actual framework.
- Never use the golden example's client-specific content (the original deployment client's goal, objectives) as a substitute for the current client's data.
- Never assume department strategies — each department's strategy must be confirmed or excluded from the prompt.
- Never skip advisor sign-off on the gap report.
Gap Report Format
GOST ENABLEMENT — GAP REPORT
Client: [client name]
Date: [date]
Source Material Reviewed: [list what was available]
GAP 1
Required for: [which section of the prompt]
What's missing: [specific description]
Resolution needed: [what the advisor must provide or decide]
Status: [ ] Open [ ] Resolved
GAP 2
...
RESOLUTION LOG
Gap 1: [resolution and date]
Gap 2: ...
Required Inputs by Section
Company Goal
| Input | Required | Source | Gap Trigger |
|---|
| Company-wide goal statement (3-year) | Yes | Client's GOST documentation, training deck, or strategy workshop output | No goal statement available — stop |
| Goal timeframe | Yes | Same | Unclear whether goal is 1-year, 3-year, or 5-year — clarify before building |
Company Objectives
| Input | Required | Source | Gap Trigger |
|---|
| Full list of company objectives | Yes | Client's GOST documentation or Individual Tactics Template | Objectives not defined — stop. Cannot build prompt without objectives to anchor tactics. |
| Objective numbers/labels | Yes | Same | If objectives are not numbered or labeled, assign labels (Obj 1, Obj 2, etc.) and confirm with advisor |
| Measurable targets in each objective | Recommended | Same | If objectives are aspirational without numbers, note as gap — the prompt will still work but tactics quality will be lower |
Department Strategies
| Input | Required | Source | Gap Trigger |
|---|
| At least one department strategy example | Recommended | Strategy Cards, training materials, or advisor notes | If no strategies are available, the prompt can still help participants draft strategy-connected tactics, but quality is lower. Note as gap. |
| Strategy Card template (if used) | Optional | Client's GOST toolkit | Not a blocker — the prompt references "your department strategy from your Strategy Card" generically |
Golden Example
| Input | Required | Source | Gap Trigger |
|---|
| A completed tactic example showing what "good" looks like | Yes | Client's training materials, a real completed submission, or the kit's default HR example | If no client-specific example exists, use the kit's default HR example (from Strategy Card & Instructions Template). Not a gap — the default is designed for this. |
| Example includes: tactic statement, end state, KPIs, backward plan | Yes | Same | If the example is incomplete (e.g., tactic statement only, no backward plan), supplement with the kit's default. Note what was supplemented. |
12-Week Tactics Planner Template
| Input | Required | Source | Gap Trigger |
|---|
| The client's 12-Week Tactics Planner template or equivalent | Yes | Client's GOST toolkit | If the client uses a different planning template, the output format in the prompt must be adapted to match. Do not deploy with a mismatched format. |
| Template field names and structure | Yes | Same | If field names differ from the kit's default (e.g., "Action Items" instead of "Tactics"), update the prompt to match the client's language. |
Quarter and Dates
| Input | Required | Source | Gap Trigger |
|---|
| Which quarter the prompt covers | Yes | Advisor | Not a gap — but the prompt must be updated with correct quarter dates before deployment. Default is Q2 2026 (April–June). |
| Quarter start and end dates | Yes | Advisor or client calendar | Same — must match the client's fiscal calendar if it differs from calendar quarters |
| Weekly date ranges in the planner output | Recommended | Derived from quarter dates | Calculate from quarter start date. If not provided, use standard Monday–Friday weeks. |
Submission Details
| Input | Required | Source | Gap Trigger |
|---|
| How participants should submit (email, form, system) | Recommended | Advisor or client-side leader | If unknown, the consultant brief will say "email directly" as default. Not a blocker. |
| Submission deadline | Recommended | Advisor or client-side leader | If unknown, leave as [insert date] in the consultant brief email template. Not a blocker. |
Source Material Types
| Source | Authority | What It Provides |
|---|
| Client's GOST documentation (training decks, Strategy Cards, Individual Tactics Template) | Primary | Goal, objectives, strategies, example tactics, planner template structure |
| Advisor notes / session transcripts | Secondary | Context on participant resistance, what's been tried, who the internal champion might be |
| Client reference data | Required supplement | Correct spelling of company name, leader names, tool names, department names |
| Kit golden example (original deployment) | Structural reference | Prompt structure, output format, participant instructions — never content |
What the Golden Example Provides
Use the golden example (03-gost-enablement-golden-example.md) for:
- Prompt structure and conversational flow
- Participant instruction format and language
- Output template structure
- Consultant brief structure and content
Never use the golden example for:
- The client's goal or objectives (use the client's actual GOST data)
- The client's department strategies
- The client's planner template (if it differs from the default)
- Submission deadlines or logistics