Reference index

This index organises the descriptive tokens and templates used across the fekonkocur reference. Each block presents a compact definition, annotation tokens, and an analytical example. The material is neutral and editorial, intended to support reading and labelling of managerial messages. The goal is to create consistent, easily comparable descriptions of communicative acts so that readers can map tone, intent, anchors, and continuity markers without conflating interpretation with recommendation. The following sections provide detailed explanatory text, example tokens, and short templates that can be adapted into annotation headers or metadata blocks.

Intent tokens and framing

Intent tokens provide a concise label for the communicative purpose of a message. Tokens are intended to be neutral descriptors, not evaluative judgments. Typical categories include informational, directive, consultative, and reflective. An informational token signals presentation of facts or status and is paired with provenance markers. A directive token identifies a request or decision path and is paired with scope and response expectations. Consultative tokens mark invitations to comment, with boundary markers that indicate the type of input sought. Reflective tokens summarise interpretation or implication and are suitable for synthesis statements. For practical annotation, present the token in a short header block followed by a clarifying phrase. Example header template: [Intent: informational] [Scope: Q2 operations] [Response: none expected]. This format helps readers identify the opening frame and anticipate the type of continuity markers that may appear in later messages. Intent framing increases clarity when messages circulate across organisational boundaries.

Token example

[Intent: consultative] [Scope: product roadmap] [Reply: requested]

Use guidance

Place token at the header; keep phrasing factual and concise.

Context anchors and provenance

Anchors identify the factual or documentary basis that situates a statement in context. They can be primary sources such as data extracts, meeting minutes, or policy excerpts, or secondary sources such as summaries and interpretive notes. A reliable anchor entry includes a short descriptor, a provenance tag, and temporal constraints where relevant. Example anchor template: [Anchor: Q1 sales table] [Source: Sales report v3, 2026-01-10] [Scope: regional totals only]. Distinguish anchors that are direct quotations from those that are interpretive paraphrases. Where possible include a provenance token that allows readers to locate the source document or dataset. Well-formed anchors reduce ambiguity when messages pass between teams with differing background knowledge. They also enable later reconciliation when continuity markers are used to compare iterations. This section describes minimal anchor constructs and offers sample phrasing that preserves clarity while remaining brief.

Alignment cues and metadata

Alignment cues link a message to internal categories such as strategic domains, cadence bands, or governance checkpoints. These cues function as metadata that readers use to prioritise or filter content. Typical cue types include strategic mapping, temporal banding, and governance notes. A strategic mapping cue might read: [Alignment: customer experience], while a temporal band could be: [Cadence: quarterly review]. Governance notes indicate review or compliance expectations. Cues should be neutral descriptors and should not include evaluative content. They are intended to signal context, not to assign judgement. Use short, standardised tokens and maintain a glossary of accepted cue values to ensure consistent application across messages. This facilitates clear sorting and search in later analysis and supports consistent interpretation by readers at different organisational levels.

Strategic mapping

Use fixed vocabulary such as customer experience, operations, risk, or strategy.
Temporal band

Mark cadence explicitly: daily, weekly, quarterly, or ad hoc.
Governance note

Indicate review expectations or compliance mapping where relevant.

Continuity markers and lineage

Continuity markers maintain the trace of a message as it evolves. Markers can include an originating intent token, a version label, a reference identifier, and a short change summary. Together these elements create a compact lineage block that helps readers follow how intent and content shift across iterations. Example continuity template: [Origin: Intent-2026-007] [Version: v1.2] [Ref: MSG-2026-007-A] [Change: adjusted scope to regional totals]. Use concise change summaries that note substantive differences without extended narrative. Where multiple documents or threads are related, include cross-reference identifiers to enable programmatic linking and manual reconciliation. Continuity markers are designed to preserve readability while enabling audit and comparison tasks for later analysis. They are minimal by design to avoid burdening standard communication while providing enough structure for traceability.

Lineage tokens

Short stable identifiers help link related messages.

Change summary

Keep summaries factual and minimal to preserve readability.

Templates and glossary

A compact set of templates and a glossary of accepted tokens are available in the guidelines section. Templates show how to present tokens, anchors, cues, and markers in a header or metadata block. The glossary lists standard values and short definitions to promote consistent usage. Use the guidelines to adapt templates into your own annotation workflow while keeping the descriptive, non-prescriptive orientation of this reference. For detailed examples and a searchable list of tokens, open the guidelines area or consult the analysis articles for annotated case studies.

View templates and glossary About the approach