Resolved: The United States federal government should substantially increase the regulation of large-language-model artificial intelligence systems.
A broad policy stem. The resolution is the topic area, not the plan, so the affirmative is whatever plan text you can defend as topical.
Nothing on its own. This is a topic stem: the aff writes a plan inside it. "Substantially increase" and "regulation" are the words the negative will run topicality on.
Aff needs a plan text, a solvency advocate, and inherency. Neg gets topicality, disads, counterplans, and kritiks. Neither side is arguing the resolution in the abstract.
Standard aff areas: pre-deployment evaluation mandates, compute-threshold licensing, training-data disclosure, liability for model outputs, and biosecurity screening on model capability. Each has a distinct disad profile, so pick one and build the block around its specific link turns.
The capability curve is outrunning the evaluation regime, and only a federal mandate creates a pre-deployment check.
The plan trades off with the innovation and the state capacity it needs to work, and there is a counterplan that captures the offense without the link.
Does federal regulation solve the capability risk, or does the states counterplan capture it while the DA turns the case?
- Running the resolution as the plan. You need a plan text; "regulate AI" is not one and topicality will be the whole 1NC.
- Reading bioweapon uplift without impact calculus. Magnitude claims need probability and timeframe work or they lose to a smaller but cleaner DA.
- Going for topicality and the case in the 2NR. Pick one and develop it.
- Reading a generic innovation DA with no specific internal link. The aff link turn writes itself if you cannot name the capability.