When this helps
Editorial synthesis grounded in the source pattern. Early-stage scholarly, design or entrepreneurial ideas that are not yet stable enough for formal evaluation but need disciplined critique.
Academics often generate promising but incomplete research ideas, arguments or teaching concepts that are difficult to structure, evaluate or fully articulate. Without systematic critique, these ideas may remain underdeveloped, internally inconsistent or insufficiently examined. Access to human interlocutors is limited by time, availability and contextual constraints.
Pattern response
Editorial synthesis grounded in the source response. Externalise the emerging idea and configure a deliberately critical exchange. Probe assumptions, identify evidence gaps, generate alternative framings and test consequences; then preserve the critique, revisions and unresolved issues. Treat GenAI as a structured source of questions and counterpositions, not as a colleague or authority. The author owns the interpretation and decision to proceed.
- A structured critique of an emerging idea, including assumptions, alternatives and evidence gaps.
- A recoverable record of questions, revisions and unresolved issues.
- Author ownership of the interpretation and any decision to proceed.
Workflow at a glance
- 01
Externalise the idea and context
An accountable academic initiates, interprets, or approves this stage; automation remains bounded by the listed modules.
MOD-001 · MOD-040 - 02
Interrogate weaknesses
An accountable academic initiates, interprets, or approves this stage; automation remains bounded by the listed modules.
MOD-031 · MOD-017 · MOD-021 - 03
Reframe through alternatives
An accountable academic initiates, interprets, or approves this stage; automation remains bounded by the listed modules.
MOD-022 · MOD-027 - 04
Iterate and structure
An accountable academic initiates, interprets, or approves this stage; automation remains bounded by the listed modules.
MOD-036 · MOD-009 · MOD-037 - 05
Validate and decide
An accountable academic initiates, interprets, or approves this stage; automation remains bounded by the listed modules.
MOD-042 · MOD-044
Human checkpoints
People define purpose and boundaries, supply or authorise source material, inspect intermediate representations, resolve ambiguity, approve consequential outputs, correct errors, and remain accountable for scholarly, pedagogical, legal, or organisational decisions. A generated recommendation or draft is not an approval decision.
Risks and misuse
Source-stated improvement concerns
- Develop more context specific interaction modes aligned with genres such as funding proposals, journal articles or teaching design, enabling more precise critique.
- Integrate personal knowledge bases, including prior publications and project materials, to ground critique in existing work.
- Introduce validation routines to identify hallucinated content or superficially plausible but weak suggestions.
- Incorporate reflective prompts that assess how ideas have changed through interaction, strengthening independent judgement and reducing over reliance on the system.
Inferred workflow risks
- Inferred: unstated constraints.
- Inferred: scope drift.
- Inferred: ambiguous success conditions.
- Inferred: context drift.
- Inferred: false continuity.
- Inferred: overconfident response.
- Inferred: unauthorised action.
- Inferred: leading questions.
Use this pattern
Begin with the recurring problem and the authorised inputs. Follow the workflow in order, keep intermediate outputs inspectable and retain the named human decisions.
- Minimum viable implementation: a documented human procedure using the ordered modules: Workflow Briefing and Context Definition → Conversational Interaction → Question and Probe Generation → Argument and Concept Analysis → Assumption Identification → Perspective Simulation → Outline and Scaffold Generation → Dialogue and Turn Management → Draft Revision → Record Storage → Output Quality Evaluation → Human Review and Approval.
- Robust implementation: add explicit schemas, source identifiers, access controls, logging, exception queues, independent evaluation, backups, and named approval owners.
- Low-code implementation: use forms and a workflow orchestrator to connect bounded services, with approval gates before external communication or state changes.
- Local or privacy-preserving implementation: keep sensitive artefacts in controlled storage and prefer local extraction, transcription, search, or model execution where capability and governance permit.
- Speculative implementation: more autonomous coordination may be explored only with constrained tools, stop conditions, audit logs, and human authority; it is not implied by the source pattern.
Reusable modules
- MOD-001 Workflow Briefing and Context Definition
- MOD-040 Conversational Interaction
- MOD-031 Question and Probe Generation
- MOD-017 Argument and Concept Analysis
- MOD-021 Assumption Identification
- MOD-022 Perspective Simulation
- MOD-027 Outline and Scaffold Generation
- MOD-036 Dialogue and Turn Management
- MOD-009 Draft Revision
- MOD-037 Record Storage
- MOD-042 Output Quality Evaluation
- MOD-044 Human Review and Approval
Related patterns
Technical and provenance detail
Data and information flow
Inputs may include request, context, constraints, user message, dialogue state, available tools or sources, idea or claim, inquiry stance, dialogue history, idea or text, analysis question, problem framing, argument, plan, issue, perspective definitions, interaction rules, brief, source material, required structure, roles, draft, revision brief, artefact or record, metadata, retention rule, output, criteria, source evidence, candidate output or action, evidence, review criteria. The stage sequence transforms, analyses, enriches, retrieves, generates, coordinates, stores, or outputs information according to each linked module contract. Outputs may include approved workflow brief, response, state update, action or question, questions, follow-up probes, rationale, argument map, conceptual issues, identified tensions, assumption register, support status, test questions, perspective-specific responses, tensions, shared assumptions, outline, scaffold, open questions, ordered dialogue, state updates, termination signal, revised draft, change record, stored object, identifier, storage receipt, evaluation findings, score or decision, required revisions, approval decision, corrections, escalation. Source identity, permission state, uncertainty, retention, and human decisions should travel with records rather than being discarded between stages.
Source provenance
- Pattern ID: DP-020
- Original title: Pattern 19: AI as a Critical Friend for Half-Formed Ideas
- Source location:
SRC-001:P0486–P0513; page number unknown. - Source status: explicit.
- Extraction notes: Canonical ID follows manuscript order. Legacy numbers are not used as publication identifiers; any numbered source heading is retained only for provenance and source fidelity.
- Editorial interventions: The public title, summary, context, response and intended outcomes are concise editorial syntheses grounded in the source pattern. Original source prose is preserved below; workflows and modules remain separated and provenance-labelled.
Open questions
- Which elements of this pattern require empirical or practice-based evaluation in the intended setting?
- Which implementation examples remain current, authorised and proportionate to the setting at the time of use?