Skip to content
FlowMCP v4

Entry-Point Prompt + Personas Obligation

Conformance language (MUST/SHOULD/MAY) follows BCP 14 [RFC2119]/[RFC8174] as defined in 00-overview.md. The binding source is the FlowMCP Schemas Specification v4.2.0.

Entry-Point Prompt

Section titled “Entry-Point Prompt”

Empty context (see 02-eligibility.md) is a convention — it needs an operational anchor. The entry-point prompt is that anchor: the first prompt after /clear starts every grading run and binds persona, selection/schema, mode, and spec version.

Concept

Section titled “Concept”
TermDefinitionCheckable?
Empty contextConvention: no relevant prior informationNo, trust-based
Entry-point promptFirst prompt after /clear = grading startNo, organisational

The spec requires: the README in the grading repository provides a prompt template. The grader runs /clear, copies the prompt, and fills in persona, selection/single-schema, mode, and the lockSnapshot hash from the selection’s index.json.

Prompt Template

Section titled “Prompt Template”

The binding prompt template is:

You are performing a FlowMCP grading. Instructions:


1. Persona: crypto-trader-2026
2. Selection: crypto-domain-full, lockSnapshot hash: <sha>
3. Mode: Full (initial baseline)
4. Spec version: gradingSpec/2.0.0
5. Pre-condition: all member schemas have gradingStatus: stable
6. Output format: _gradings/<area>--<timestamp>.json

Six numbered lines. For Single-Gradings, line 2 is replaced and line 5 is dropped:

1. Persona: crypto-trader-2026
2. Single-Schema: etherscan.getContractEthereum, area: single-test
3. Mode: Full (initial baseline)
4. Spec version: gradingSpec/2.0.0
6. Output format: _gradings/<area>--<timestamp>.json

(Line 5 is dropped — the pre-condition applies only to aggregated checks, see 21-pre-conditions.md.)

Personas Obligation

Section titled “Personas Obligation”

The personas obligation has two levels — spec obligation and convention. They are complementary (not alternative).

LevelApplies toAnchoring
Spec obligationSelection onlypersonaIds[] is a mandatory field in selection.json (see 16-selection-lockfile.md)
Convention via promptSingle AND SelectionEvery grading run starts with the persona line in the prompt (line 1)

Rationale: Single-Gradings without a persona anchor produce evaluation drift. The spec obligation in selection.json is the formal anchoring; the prompt requirement is the operational one.

Personas-obligation summary:

  • Selection-Gradings: persona MUST be in selection.json AND in the prompt
  • Single-Gradings: persona SHOULD be in the prompt (organisational, not a spec-mandatory field)

Cross-Reference to the README

Section titled “Cross-Reference to the README”

The README in the grading repository contains the ready-to-use prompt with example values. The README section anchors the entry-point prompt and the personas obligation in a single block.

Cross-Refs

Section titled “Cross-Refs”
Section titled “Related”