business-e2e-context

Kind context with a declared write scope (agentic-qa-core/references/skill-composition-strategy.md §2b). Delivered once by upstream as a placeholder, then owned by the project: the map inside is this project's synthesis. Procedure: agentic-qa-core/references/business-context-maps.md.

Compact Rules

DO: read the map through bun run context:map business-e2e-context (or --section <id> for one journey or feature). NEVER read references/business-e2e-map.html raw: its SVG is most of the bytes and none of the facts.
DO: treat a placeholder map as "no map". Say so and hand the user project-context mode e2e; never plan E2E coverage as if the product had no journeys.
DO: start from the journey, then the feature. A story is tested inside the journey that reaches it; the feature catalog answers "what exists", the journeys answer "what a user does and where it breaks".
WHEN a session observes something that contradicts a section (a step, a branch, a state the UI shows): PROPOSE the one-section edit with its evidence to the user (or to the conductor when you are a supervised worker), apply it only on approval. Procedure: references/refresh.md.
DO NOT: write anywhere but this skill's own references/. No Jira, no .context/, no other skill, no test code, no product code.
DO NOT: copy map content into this SKILL.md. Judgment goes in ## Rules or references/gotchas.md, dated and measured.
Before a step that uses diagrams (redrawing a figure), run the point-of-use check in agentic-qa-core/references/preflight-gate.md §8.

Read full SKILL.md when: building a briefing for a UI or E2E dispatch, scoping a smoke or regression run, deciding whether a section is stale, or proposing an edit to the map.

What this skill knows

One aspect of the system under test: its use, end to end. Who the users are, which journeys they take and where each one can fail, which features exist and which journeys cross them, and the flows that only make sense across several features. Loading it changes what the agent KNOWS; the only thing it ever does is propose an edit to its own map.

Sources of truth (cited, never copied)

Source	What lives there	Role
`references/business-e2e-map.html`	the synthesis: a `<section>` per journey first, then per feature, plus `discovery-gaps`	this skill's map (read via `bun run context:map`)
the frontend repo (`{{FRONTEND_REPO}}`)	routes, pages, forms, guards	wins over the map on any conflict
the running app of the active environment	what a user really sees	wins for behaviour
`business-data-context`, `business-api-context`	the data and API behind each step	cited per step, never restated
`project-context` mode `e2e`	the generator that CREATEs the map and UPDATEs its stale sections	owns regeneration

Rules (judgment, dated)

(none yet: each rule carries YYYY-MM-DD · rule · measured: how)

Not here

Entities, triggers and state machines → business-data-context.
Endpoint groups, auth and error semantics → business-api-context.
Selectors, page objects and test code → tests/components/ (KATA), owned by /test-automation.
Jira stories and their ACs → .context/PBI/ (synced cache).

References

references/business-e2e-map.html — the map (generated; read through the reader).
references/refresh.md — the self-update procedure and this aspect's staleness signals.
references/gotchas.md — measured traps in reading this project's journeys.

Refinements

Lessons land as proposals per agentic-qa-core/references/skill-refinement-protocol.md, never as direct edits.