Session Chronicle

View saved version →

---
name: session-chronicle
description: Reconstruct a conference, symposium, seminar, workshop, panel, forum, roundtable, presentation, or Q&A transcript as a faithful professional narrative. Use by default when a transcript is supplied without another requested output, and for CHRONICLE, OUTLINE, or HELP commands.
---

# Session Chronicle

Turn the supplied transcript into a readable, source-grounded record. Do not ask intake questions unless the source is genuinely unusable; make cautious editorial decisions and state material uncertainty.

## Routing

- A transcript with no further instruction means `CHRONICLE`.
- `OUTLINE` produces a structured plan rather than full prose.
- `HELP` briefly lists supported outcomes and routes the user's next request. Preserve slash-prefixed or plain command aliases, case-insensitively.
- Route EXPAND, SUMMARISE/SUMMARIZE, PUBLISH, and HIGHLIGHTS to `session-publish`; multi-session comparison to `session-compare`; INFOGRAPHIC and other visual requests to `session-visuals`.

## Workflow

1. Assess transcript quality and boundaries. Read [transcript quality guidance](../../references/transcript-quality-guidance.md) when the source is noisy, incomplete, or poorly labeled.
2. Detect the session format: presentation, interview, panel, roundtable, moderated Q&A, workshop, or mixed. Identify speakers only to the degree supported by the source.
3. Map chronology, themes, transitions, questions, responses, agreements, disagreements, examples, and conclusions.
4. Draft in professional prose using the fitting pattern in [narrative patterns](../../references/narrative-patterns.md). Prefer thematic organization within the actual progression of the session.
5. Apply [attribution guidance](../../references/attribution-guidance.md), then check every substantive claim against the source.

## Fidelity rules

- Preserve meaning, nuance, speaker intent, material distinctions, and the sequence needed to understand the discussion.
- Improve grammar and flow without silently strengthening claims or resolving ambiguity.
- Never invent names, roles, motives, quotations, consensus, conclusions, context, or facts.
- Paraphrase by default. Use direct quotations only when wording is clear and worth preserving.
- Mark uncertainty locally and proportionately. Do not let minor transcript noise dominate the narrative.
- Add external context only when the user requests it or it is necessary to identify a clearly referenced item; label it separately and cite its source.

For `OUTLINE`, follow the relevant session shape, listing proposed sections, principal points, supported speaker attribution, and unresolved ambiguities. Do not draft the full chronicle.

View saved version →

---
name: session-compare
description: Compare two or more conference or session transcripts, chronicles, or summaries across themes, speaker positions, convergence, divergence, evidence, and implications. Use for cross-session synthesis and comparison; do not use for a single-session recap.
---

# Session Compare

Build an evidence-grounded synthesis across supplied sessions. Do not manufacture symmetry, conflict, or consensus merely to complete a comparison framework.

## Workflow

1. Confirm that at least two distinguishable source units are available; identify their titles or neutral labels.
2. Assess comparability: topic, purpose, participants, format, date, and level of detail. State material limitations.
3. Create an evidence map for recurring themes and session-specific concerns. Keep absence of discussion distinct from disagreement.
4. Compare positions with cautious attribution using [attribution guidance](../../references/attribution-guidance.md).
5. Report supported convergence, divergence, complementary emphasis, and unresolved questions.
6. Derive implications only when warranted, labeling interpretations as synthesis rather than source claims.

Use a narrative, matrix, or hybrid structure according to the number and complexity of sessions. Cite or point to transcript evidence precisely enough that the comparison can be checked. Preserve meaningful outliers rather than forcing a majority story.

View saved version →

---
name: session-publish
description: Expand, summarise, or turn a supplied session transcript or chronicle into publication-ready prose or highlights. Use for EXPAND, SUMMARISE/SUMMARIZE, PUBLISH, HIGHLIGHTS, executive-summary, article, newsletter, or concise recap requests.
---

# Session Publish

Produce the requested derivative without adding unsupported substance. Read [output modes](../../references/output-modes.md) for the selected mode and [attribution guidance](../../references/attribution-guidance.md) when speaker identity or quotation is uncertain.

## Workflow

1. Identify the source artifact and requested mode. Plain or slash-prefixed commands are case-insensitive.
2. Preserve the source's factual boundaries, speaker positions, qualifications, and uncertainty.
3. Select information by importance to the requested audience and length; do not equate brevity with flattening nuance.
4. Draft in a self-contained form suited to the mode and user-specified audience, channel, tone, and length.
5. Verify that headlines, leads, highlights, and conclusions do not overclaim.

If no audience or length is given, choose a broadly professional audience and a proportionate length without asking. If the input is a raw transcript, first reconstruct enough structure to publish it faithfully.

View saved version →

---
name: session-visuals
description: Plan or generate source-grounded conference infographics, social carousels, visual summaries, quote cards, or slide-like visual records from a supplied transcript, session account, presentation, or approved chronicle. Use for INFOGRAPHIC and other requests to visualize a conference, panel, seminar, workshop, forum, roundtable, or session.
---

# Session Visuals

Translate the session into a coherent visual chronicle while keeping every factual element traceable to the supplied source.

## Visual modes

- `INFOGRAPHIC` or `EDITORIAL INFOGRAPHIC`: a professional visual chronicle whose structure reflects the session type and verified content. Read [editorial infographic patterns](../../references/editorial-infographic-patterns.md) before planning or generating it.
- `CAROUSEL`: a sequence with one principal message per card.
- `QUOTE CARD`: one verified quotation with restrained context.
- `VISUAL SUMMARY`: a lighter overview built around a small number of themes.
- `VISUAL BRIEF`: approved copy and production instructions without rendering.

Infer the mode from the request and supplied references. When the user supplies a visual reference, derive its hierarchy, density, section rhythm, palette logic, and image treatment without copying protected branding or proprietary graphics.

## Workflow

1. Identify the mode, audience, platform, dimensions, and panel count when provided. Otherwise choose a restrained, readable default without intake questions.
2. Classify the session as a leadership/keynote speech, government/policy address, technical presentation, panel discussion, roundtable, or another source-supported format.
3. Build a source ledger containing the session title or theme; speaker name, role, and organization; central message; major themes and arguments; figures; initiatives and frameworks; examples and case studies; timelines; agreements and disagreements; implications; future priorities; and quotation candidates. Mark each item as exact, paraphrased, uncertain, or externally supplied. Omit unclear details or disclose the uncertainty.
4. Establish the information hierarchy before choosing imagery. Make the session, speaker, and central message immediately legible; feature roughly four to seven principal insights when the source supports them; place statistics, examples, milestones, initiatives, and short quotations at the supporting level.
5. Convert narrative into visual language: concise headings, icons, timelines, process arrows, pillars, numbered frameworks, comparison panels, statistic blocks, callouts, quote panels, and takeaway banners. Do not put the prose chronicle into decorative boxes.
6. Choose the production method. Use deterministic layout for text-heavy designs; use image generation for supporting illustrations, backgrounds, or authorized visual assets. If a generative tool is used for a complete visual, keep exact text independently controlled or verify every rendered word. If suitable rendering tools are unavailable, deliver a production-ready brief and approved copy.
7. Apply user-supplied branding and authorized assets. Use a restrained professional conference system—navy, teal, green, white, light neutrals, clean sans-serif type, and consistent iconography—when no brand direction is supplied.
8. Proofread every visible name, role, organization, date, number, acronym, program name, label, and quotation against the source. Inspect the result at full size and thumbnail size for hierarchy, clipping, contrast, and legibility.

## INFOGRAPHIC default behavior

When a user supplies source material and simply asks to create an infographic:

1. Analyze the source and classify the session.
2. Extract and verify the source ledger.
3. Select the strongest source-responsive visual narrative.
4. Condense prose into infographic-ready language without losing important qualifications.
5. Construct a production or image-generation prompt containing the purpose, title, supported s

Preview of the first 4,000 characters. Read full instructions →