Web blocks¶

BlockSpec¶

Registered in web/blocks/registry.py. Each block has id, group, description, optional module_deps / artifact_patterns, and a render(ctx, placement) function.

BlockPlacement¶

Layout YAML uses placement_id (unique instance) and block_id (reusable type).

Adding a block¶

Implement render_* in web/blocks/implementations/ — adapt an existing page renderer; do not duplicate ArtifactService logic.
Register in web/blocks/builtin.py.
Add placement to a curated preset under web/layouts/presets/ (the built-in all layout picks up new blocks automatically).
Add a smoke test under tests/web/blocks/.

Insights blocks for new analysis modules¶

Block id	Module	Layouts
`llm_summary_block`	`llm_summary` / `narrative_summary` (parametric)	`default`
`llm_speaker_summary_block`	`llm_speaker_summary` (group runs: synthesised index via resolver)	`default`
`llm_action_items_block`	`llm_action_items`	`default`, `executive`
`llm_custom_qa_block`	`llm_custom_qa`	presentation helpers under summary/speakers (Actions placement removed)
`lexical_diversity_block`	`lexical_diversity`	`default`
`insights_contract`	`insights`	`default`
`highlights`	`highlights`	`default`, `executive`
`executive_summary` / `commitments_table`	`summary`	`default`, `executive`

Group runs (dual presentation)¶

Group analysis already executes selected modules on each member transcript, then finalizes aggregates. Insights/Overview blocks must not assume only single-transcript stems under the group run root.

Shared helpers: web/blocks/group_content.py. Loader: ArtifactContentLoader resolves via storage_root (member run dirs).

On group runs, content blocks show:

Group rollup — aggregate *_rows.json / blobs / group LLM synthesis
Per session — session picker loads that member’s single-transcript contract (_insights.json, _highlights.json, etc.)

Surface	Group rollup source	Per-session source
Highlights	`highlights/highlight_rows.json`	member `_highlights.json`
Insights contract	`insights/insight_rows.json`	member `_insights.json`
Action items	`llm_action_items/action_item_rows.json`	member `_llm_action_items.json`
Custom questions	`llm_custom_qa/qa_answer_rows.json` (+ `qa_member_failures.json`)	member `_llm_custom_qa.json`
Executive summary / commitments	blob `summary/summary.json`	member `_summary.json`
LLM summary (block)	synthesis / collect blob	member `_llm_summary`
LLM speaker summaries	synthesis index	member speaker index + files
Lexical diversity	`session_rows` / `speaker_rows`	member `_lexical_diversity.json`

transcript_summary_hero / resolve_primary_summary still prefer committed cross-session synthesis as the primary prose hero (no member _llm_summary primary fallback). Member summaries remain available under Per session on Insights LLM blocks.

Overview module metrics use summary extractors under web/summary_extractors/. Zip export summaries for LLM prose/list modules are resolved in transcriptx.export.resolve.

Layout preset catalog¶

Built-in YAML lives under web/layouts/presets/. The generated all layout is not a YAML file.

Id	Title	Intent
`default`	Standard	Everyday curated Overview + sectioned Insights (product default)
`executive`	Executive	Metrics / health / export Overview; summary + actions + highlights
`meeting_followup`	Meeting follow-up	Post-meeting extracts, commitments, highlights
`speaker_focus`	Speakers	Speaker cards + linguistic Insights stack
`minimal`	Minimal	Hero + glance + status; lean Insights (summary + highlights)
`developer_debug`	Developer debug	Inspection / layout testing
`all`	All	Every registered block, alphabetical (generated)

Curated Insights placements should set section: (summary | speakers | actions | highlights) so Insights local navigation stays coherent. Public envelope is schema_version 1 only.

Adding a layout¶

Copy presets/default.yaml (or another curated preset) to {config_dir}/profiles/ui_layouts/my_layout.yaml (runtime PROFILES_DIR/ui_layouts/; not repo data/profiles/), or add a new built-in under presets/ and register the id in BUILTIN_LAYOUT_IDS + layout picker labels.
Validate via Dashboard Builder Schema mode or LayoutProfileStore.validate_layout_dict / validate_layout.
Set active_layout_profile_id in session state or use the Dashboard Builder selector.
Prefer Save as custom layout in Dashboard Builder for user clones (overwrite confirmation + delete support).

See dashboard_builder.md for Schema / Preview / save / delete workflows.

BlockContext¶

Built by build_context_from_session() — blocks never receive raw st.session_state.