Research Introduction Architect
by @quochungto
Draft a complete research introduction and matching conclusion using the Context→Problem→Response architecture. Use this skill when the user has a framed res...
Example 1 — Humanities paper (point-last, full context)
Input:
Introduction draft:
> In almost every episode of *Star Trek: The Next Generation*, the android Data wonders what makes a person a person. In the original *Star Trek*, similar questions were raised by the half-Vulcan Mr. Spock, whose status as a person was undermined by his machine-like logic and lack of emotion. Data and Spock are only the most recent "quasi-persons" in American popular fiction who have explored the nature of humanity — a lineage that runs from Frankenstein's monster to the Terminator. But the real question is not whether these characters achieve personhood. It is why these quasi-persons who struggle to be persons are almost always white and male. As cultural interpreters, do they tacitly reinforce destructive stereotypes about what it means to be "normal"? This article argues that the model person in American science fiction is consistently defined by Western, male criteria — a definition that, taken seriously, excludes most of the people in the world.
Why this works:
Example 2 — Professional report (point-first, fast pace, no explicit consequence)
Input:
Introduction draft:
> As part of its Continuous Quality Improvement program, Motodyne plans to redesign the user interface for its Unidyne online help system — specifically, the icons that should be self-explanatory without verbal labels. Motodyne has three years of experience with its current icon set, but it has no data showing which icons users actually understand without labels. Lacking such data, we cannot determine which icons to redesign. This report provides data for eleven icons and shows that five of them are not self-explanatory.
Why this works:
Example 3 — Academic paper with conclusion (legal history)
Input:
Introduction draft:
> In today's society, would Major John André — a British spy captured behind American lines in 1780 — be hanged? Though considered a noble patriot by the British, he suffered the punishment mandated by military law. Over time our traditions of punishment have changed, but the punishment for spying has not: it is the only offense that still mandates death. Recently, however, the Supreme Court has rejected mandatory death sentences in civilian cases, creating an ambiguity in their application to military law. If those decisions apply to the military, Congress may have to revise the Uniform Code of Military Justice. This article concludes that it will.
Conclusion draft:
> In light of recent Supreme Court decisions rejecting mandatory capital punishment, the mandatory death penalty for espionage is apparently unconstitutional and must be revised by Congress. More significantly, if the Uniform Code of Military Justice is changed, it will challenge the fundamental value of military culture that ultimate betrayal requires the ultimate penalty. Congress will then have to deal not just with a legal inconsistency, but with the military's deeply held sense of what justice demands — a question that extends well beyond the narrow issue of one penalty's constitutionality. Future research should examine how military culture has historically adapted its core values when external legal constraints required change, and whether those adaptations were perceived as legitimate by the communities they governed.
Why this works:
clawhub install bookforge-research-introduction-architect