github-issues

[channels/channel] Author a long-form, multi-chapter book from a research session's surviving findings

[channels/channel] Render a research topic's entire surviving findings corpus into a complete Diátaxis documentation set — a reference page per finding, a per-dimension explanation, how-to, and guided tutorial, plus index pages — every page carrying MIF Level-1 frontmatter and a diataxis_type marker

[channels/channel] Publish a research topic to GitHub Discussions, grounded in the SOURCES (findings + primary citations) — an announcement of completed research, a Q&A thread about methodology, or a non-canonical observation; never from a rendered report

[channels/channel] Produce NotebookLM assets (audio deep-dive, slide deck, infographics, video, mind map) grounded in the SOURCES — the findings' actual cited primary materials are added to the notebook plus a findings digest, never a rendered report

[channels/channel] Produce a styled, print-ready PDF directly from the SOURCES — a topic's surviving findings and their primary-source citations, composed into a comprehensive document and rendered with pandoc, a title page, and Mermaid diagrams; never built from a rendered report

[channels/channel] Render a topic's surviving findings into well-formed JATS (NISO Z39.96) XML directly from the SOURCES — a scholarly article with article metadata, a body of one section per finding, and a back-matter reference list of the primary-source citations; never built from a rendered report

[channels/channel] Render surviving findings (typically a regulatory-disclosure artifact) into an inline XBRL (iXBRL) document directly from the SOURCES — facts tagged with xbrli:context / xbrli:unit and current-taxonomy concepts inside a human-readable XHTML shell; never built from a rendered report

[channels/channel] Package a clinical-submission artifact into the FDA eCTD module structure (M1-M5 + the XML backbone) directly from the SOURCES — a topic's surviving findings and their primary-source citations; lays out the eCTD module tree and writes the backbone; verify-live eCTD v4.0; never built from a rendered report

[market-research/methodology] Use when the user asks to "analyze competitors", "map competitive landscape", "Porter's 5 Forces analysis", "competitor comparison", "competitive positioning", "identify competitors", "competitive intelligence", or needs competitor research

Self-contained, MIF-native AI research harness template — a goal-driven multi-agent engine, adversarial falsification gate, knowledge graph, and research→report/blog pipelines. Instantiate and update-propagate with Copier.