Research
Research a target note, idea, project, or topic. Preserve external sources as
traceable source records by default; write summaries only when the user asks for
synthesis, assessment, or a concise research brief. Any source used in a summary
keeps a complete immutable copy in raw/processed/YYYY-MM-DD/.
Notes tagged external are treated as clipped/imported external sources and are
eligible for synthesis while preserving the complete source record.
Portent reference: ../references/portent-knowledge-base-spec.md.
Research briefs are type: Note by default. External changes, meetings,
incidents, product launches, or decisions that happened are type: Event. Every
synthesized Note or Event should set belongs_to to its primary Project,
Responsibility, Operation, or Topic when that context is clear.
Parameters
Target can be:
- note filename (
voice-notes-app or voice-notes-app.md)
- relative path (
notes/car-search/prd.md)
- absolute path
Optional flags:
--mode report|apply (default: report)
--output sources|summary|both (default: sources)
Target Resolution
Resolve target in this order:
- exact path
- unique basename match
- if ambiguous, ask one concise disambiguation question and stop
Workflow
- Load the target and extract topic/problem and context.
- Check whether target/source notes carry an
external tag.
- Run three tracks in parallel:
- competitor landscape
- community discussions (Reddit/HN/forums)
- market signals (funding/trends/news)
- Classify each external source by type, relevance, topic, and confidence.
- Classify the output as a Portent
Note or Event and identify the primary
belongs_to relationship when clear.
- Choose output behavior:
sources: create or update source records only
summary: write a concise synthesized research block with citations
both: preserve source records and write a concise synthesis
- In
apply mode, archive every external source used for synthesis to
raw/processed/YYYY-MM-DD/ before writing the synthesis.
- Place working source records in the closest durable location:
projects/active/<project>/research/
ideas/<state>/<idea>/research/
notes/<topic>/
- Merge source records into an existing research/source note when they cover
the same external source or same research thread.
- Assign confidence (
high|medium|low) for key claims.
- If writing a summary, keep it clearly separate from owned notes and link
back to archived complete source records.
- Return what was found, where sources were placed, and what was written.
Copy vs Synthesize Decision
Default to --output sources for untagged material. Notes tagged external may
use summary or both during processing because the tag explicitly marks them
as external clipped sources.
- Use
sources for collecting, categorizing, moving, linking, or preserving
external records without interpretation.
- Use
summary when the user wants an answer or brief and does not need
separate working source notes.
- Use
both when the user wants synthesis and the sources should remain useful
as organized research material.
Never summarize user-authored ideas, project drafts, plans, or notes as part of
research unless the user explicitly asks for that specific note to be
summarized. Link external findings to those owned notes instead.
Evidence Policy
- Prefer primary sources when available.
- Mark uncertain claims explicitly instead of overstating.
- Keep findings actionable and traceable to sources.
- Do not replace, compress, or rewrite owned project ideas or user-authored
notes as a research side effect.
- Treat
external as the source-origin signal for synthesis eligibility.
- Merge duplicate external-source records when URL/source identity matches;
otherwise link related sources instead of collapsing them.
- Cite archived complete source records from
raw/processed/YYYY-MM-DD/ for
every synthesized claim or source summary.
Constraints
- Default behavior is report-only and source-first.
- Summary writing requires
external, --output summary, --output both, or
an explicit user request for synthesis.
- In
apply mode, do not write a summary until complete source records have
been archived.
- If signal quality is weak, report low confidence and preserve sources without
overstating conclusions.
- If target note lacks enough context, ask for clarification before broad
search.
Output
Return:
- target note path
- source records found/created and their destination paths
- archived complete source paths under
raw/processed/YYYY-MM-DD/
- source records merged and canonical destinations
- findings summary if requested
- Portent output type and belongs_to relationship used or proposed
- confidence highlights
- whether source records or target notes were updated
- suggested follow-up actions
1---2name: vault-research3description: Use when a vault note, idea, project, or topic needs external sources, competitor research, discussion evidence, or market signals4---56# Research78Research a target note, idea, project, or topic. Preserve external sources as9traceable source records by default; write summaries only when the user asks for10synthesis, assessment, or a concise research brief. Any source used in a summary11keeps a complete immutable copy in `raw/processed/YYYY-MM-DD/`.1213Notes tagged `external` are treated as clipped/imported external sources and are14eligible for synthesis while preserving the complete source record.1516Portent reference: `../references/portent-knowledge-base-spec.md`.1718Research briefs are `type: Note` by default. External changes, meetings,19incidents, product launches, or decisions that happened are `type: Event`. Every20synthesized Note or Event should set `belongs_to` to its primary Project,21Responsibility, Operation, or Topic when that context is clear.2223## Parameters2425Target can be:2627- note filename (`voice-notes-app` or `voice-notes-app.md`)28- relative path (`notes/car-search/prd.md`)29- absolute path3031Optional flags:3233- `--mode report|apply` (default: `report`)34- `--output sources|summary|both` (default: `sources`)3536## Target Resolution3738Resolve target in this order:39401. exact path412. unique basename match423. if ambiguous, ask one concise disambiguation question and stop4344## Workflow45461. Load the target and extract topic/problem and context.472. Check whether target/source notes carry an `external` tag.483. Run three tracks in parallel:49 - competitor landscape50 - community discussions (Reddit/HN/forums)51 - market signals (funding/trends/news)524. Classify each external source by type, relevance, topic, and confidence.535. Classify the output as a Portent `Note` or `Event` and identify the primary54 `belongs_to` relationship when clear.556. Choose output behavior:56 - `sources`: create or update source records only57 - `summary`: write a concise synthesized research block with citations58 - `both`: preserve source records and write a concise synthesis597. In `apply` mode, archive every external source used for synthesis to60 `raw/processed/YYYY-MM-DD/` before writing the synthesis.618. Place working source records in the closest durable location:62 - `projects/active/<project>/research/`63 - `ideas/<state>/<idea>/research/`64 - `notes/<topic>/`659. Merge source records into an existing research/source note when they cover66 the same external source or same research thread.6710. Assign confidence (`high|medium|low`) for key claims.6811. If writing a summary, keep it clearly separate from owned notes and link69 back to archived complete source records.7012. Return what was found, where sources were placed, and what was written.7172## Copy vs Synthesize Decision7374Default to `--output sources` for untagged material. Notes tagged `external` may75use `summary` or `both` during processing because the tag explicitly marks them76as external clipped sources.7778- Use `sources` for collecting, categorizing, moving, linking, or preserving79 external records without interpretation.80- Use `summary` when the user wants an answer or brief and does not need81 separate working source notes.82- Use `both` when the user wants synthesis and the sources should remain useful83 as organized research material.8485Never summarize user-authored ideas, project drafts, plans, or notes as part of86research unless the user explicitly asks for that specific note to be87summarized. Link external findings to those owned notes instead.8889## Evidence Policy9091- Prefer primary sources when available.92- Mark uncertain claims explicitly instead of overstating.93- Keep findings actionable and traceable to sources.94- Do not replace, compress, or rewrite owned project ideas or user-authored95 notes as a research side effect.96- Treat `external` as the source-origin signal for synthesis eligibility.97- Merge duplicate external-source records when URL/source identity matches;98 otherwise link related sources instead of collapsing them.99- Cite archived complete source records from `raw/processed/YYYY-MM-DD/` for100 every synthesized claim or source summary.101102## Constraints103104- Default behavior is report-only and source-first.105- Summary writing requires `external`, `--output summary`, `--output both`, or106 an explicit user request for synthesis.107- In `apply` mode, do not write a summary until complete source records have108 been archived.109- If signal quality is weak, report low confidence and preserve sources without110 overstating conclusions.111- If target note lacks enough context, ask for clarification before broad112 search.113114## Output115116Return:117118- target note path119- source records found/created and their destination paths120- archived complete source paths under `raw/processed/YYYY-MM-DD/`121- source records merged and canonical destinations122- findings summary if requested123- Portent output type and belongs_to relationship used or proposed124- confidence highlights125- whether source records or target notes were updated126- suggested follow-up actions