AI Venture Build · Capstone brief
VEN-08 · Regulatory landmine map
List the rules that could stop your launch — in Virginia schools, in a regulated industry, or in a consumer market — and say which one you would hit first. Not a survey of AI policy: the specific requirements that apply to this venture, this buyer, this year.
The question
List the rules that could stop your launch — in Virginia schools, in a regulated industry, or in a consumer market — and say which one you would hit first. Not a survey of AI policy: the specific requirements that apply to this venture, this buyer, this year.
System / materials
The venture, its buyer, and its data. Whichever regimes actually apply, read at the source rather than summarized from commentary: FERPA and student-privacy requirements where a school is the buyer (https://studentprivacy.ed.gov/), COPPA and advertising-substantiation rules where the user is a child or a consumer (https://www.ftc.gov/business-guidance), sector rules where the venture touches health, finance, or employment, and the division's own procurement and data-privacy requirements where the customer is a public school. Nothing here is legal advice, and the packet says so on its face.
Expected failure modes
Writing a general essay about AI regulation instead of a map of this venture's exposure. Missing procurement entirely — for a school buyer, the purchase process stops more launches than any statute. Confusing "no one has enforced this yet" with "this does not apply." Assuming a terms-of-service checkbox handles a consent requirement for minors. Citing a bill that was never enacted, or an enacted law without checking whether it is in force.
Done looks like
An exposure map: each applicable requirement with what triggers it, what compliance would actually take, and roughly what it costs; the requirements ranked by which you hit first at launch, not by severity; the one that would stop you soonest, with what you would do about it; the open questions a real lawyer would need to answer, stated as questions; and the disclaimer that this is student work and not legal advice.
Five C's
CT: mapping exposure rather than summarizing law. CR: ranking by launch order. CO: a peer plays the district procurement officer and asks the hard question. CM: a map a founder could act on Monday. CZ: who the rule was written to protect, and whether your product respects that intent even where the rule is silent.
Mentor role
A compliance professional, district procurement or privacy officer, or an attorney reviews the map. Standing instruction: reject any packet framed as legal advice or missing the procurement path for a school buyer. School-supervised.
Rubric calibration
R1: one venture, one buyer, one jurisdiction. R2: every requirement cited to a primary source with the date accessed. R3: comparator is launching with no compliance work, and what that risks. R4: the first-hit requirement identified with reasoning. R5: map is actionable. R6: names the open legal questions instead of answering them.
Two ways this goes wrong
(a) A survey of AI policy with no connection to this venture's actual exposure. (b) Statutes analyzed carefully while the procurement process that would really block the sale goes unmentioned.
Credit lane fit
Lane A immediately (entrepreneurship, government, or business law cross-listing). Strong non-technical option. No verified credit claim.