Skip to content
AI.info

Kinds of learning

Capstone: Design a Learning System and Defend Every Signal

Apply the path to a city-maintenance scenario and produce an auditable learning-strategy memo that may recommend a model, a hybrid, a pilot, or no deployment.

By the end you can

The scenario: prioritize city infrastructure repairs

A city receives resident reports, inspection records, sensor readings, weather data, repair histories, and contractor notes. Leaders want to identify emerging hazards, prioritize inspections, estimate repair duration, and allocate crews.

The request sounds like one AI project. It is not. Inside it sit prediction, ranking, anomaly detection, resource optimization, selective labeling, and causal policy questions. Your task is to separate them before proposing a system. Every failure this capstone asks you to guard against has already happened to a named city, and the numbers are on the record: a lead-pipe search in Flint, a violence-risk score in Chicago, a fraud system in Michigan, a flu tracker at Google, a court in The Hague.

Example

The same output affects people differently

The capstone begins with stakeholder and consequence mapping. Each row below is a group whose exposure to the same ranked list is different. In several cases the size of that difference has been measured.

  • Residents need hazards addressed without neighborhoods being ignored because reporting rates differ. In the New York City and Chicago report data, incidents in downtown Manhattan were reported at about three times the rate of the same incidents in Queens.
  • Inspectors need prioritized queues that preserve authority and explain the available evidence, because a queue they cannot interrogate is one they can only obey or ignore.
  • Dispatch teams need duration and access estimates rather than only risk categories; a ranking with no time attached cannot be turned into a crew schedule.
  • Budget officers need scenario analysis but should not treat prediction as causal proof of policy benefit — Chicago spent $3.8 million in federal grants across six versions of a risk model whose benefit was never demonstrated.
  • Contractors may change documentation behavior after the system influences payment or scrutiny; in Flint the contractor's own choice of which homes to dig, not the model, is what decided where the replacement money went.
  • Auditors need versioned records of data, models, rules, overrides, and appeals — the Flint record exists in checkable form only because a sworn declaration put the hit rates ward by ward onto a federal docket.

Visual

Decompose the request into learning contracts

Each component receives a different signal and requires a separate claim. Hazard triage is supervised classification or ranking from adjudicated inspection outcomes. Emerging pattern discovery is anomaly detection over sensor and repair signals. Repair duration is regression with intervals and site-specific uncertainty. Inspection selection is active learning under inspector capacity and geographic coverage. Crew allocation is constrained optimization using predictions, skills, travel, and policy. Policy impact is causal evaluation of interventions, not ordinary prediction.

The inspection-selection contract is not an abstraction. A city has already signed it. In 2018 five researchers built an adaptive — that is, active-learning — model over 55,893 Flint properties, to decide which homes to excavate in the search for hazardous service lines. Their paper states what it could do: “we emphasize that our predictive model is empirically accurate for estimating whether a Flint home’s pipes are safe/unsafe, with an AUROC score of nearly 0.92, and a true positive rate of 97%”.

The number that matters for a capstone is not the AUROC. It is what the selection policy bought. Backtested on the 6,505 homes the FAST Start program actually visited, the model cut the rate of unnecessary service-line replacement visits from 18.8% to 2.0%. Across 18,000 planned replacements that is worth roughly $11M — about 2,100 more homes made safe on the same budget. Active learning under capacity is not a technique on a diagram. It is 2,100 households.

FigureHierarchy · 6 levels
  • Hazard triage

    Supervised classification or ranking from adjudicated inspection outcomes.

    • Emerging pattern discovery

      Anomaly detection over sensor and repair signals.

      • Repair duration

        Regression with intervals and site-specific uncertainty.

        • Inspection selection

          Active learning under inspector capacity and geographic coverage.

          • Crew allocation

            Constrained optimization using predictions, skills, travel, and policy.

            • Policy impact

              Causal evaluation of interventions, not ordinary prediction.

Comparison

Three defensible first releases

The capstone rewards a justified scope rather than the largest architecture. A decision-support pilot predicts and ranks cases while inspectors retain final authority: lowest interaction risk, creates reviewed feedback, supports shadow evaluation, may improve workflow slowly. A hybrid operations system combines rules, predictive models, anomaly alerts, and optimization: it addresses several tasks and keeps constraints explicit, but it requires interface testing and both component and system metrics. A research-only phase improves labels, reporting coverage, and causal evidence before deployment: appropriate when targets are weak, it reduces premature automation and can test data interventions, and it requires organizational patience.

The mildest phrase in that first column — may improve workflow slowly — is the one that needs evidence. The same architecture has been measured, and it went the other way. Computer-aided detection for screening mammography is the decision-support pilot in its purest form: the system flags and ranks, the expert keeps final authority. It was FDA-cleared, Medicare-reimbursed and widely adopted. Then Fenton and colleagues published the numbers in the New England Journal of Medicine in 2007. They studied 429,345 mammograms from 222,135 women across 43 facilities. After CAD was introduced, specificity fell from 90.2% to 87.2% and biopsies rose 19.7%.

Eight years later Lehman and colleagues looked again, across 323,973 women, and found no improvement on any performance measure. Sensitivity was actually lower among the radiologists who read both with and without it (odds ratio 0.53, 95% CI 0.29–0.97). Their conclusion in JAMA Internal Medicine was blunt: “Computer-aided detection does not improve diagnostic accuracy of mammography. These results suggest that insurers pay more for CAD with no established benefit to women.”

Two large studies, eight years apart, on a system that left the human in charge throughout. Human authority is not a safety guarantee. A pilot whose evaluation plan cannot return that verdict is not an evaluation plan.

FigureComparison · 3 columns

Decision-support pilot

Predict and rank cases while inspectors retain final authority.

  • Lowest interaction risk
  • Creates reviewed feedback
  • Supports shadow evaluation
  • May improve workflow slowly

Hybrid operations system

Combine rules, predictive models, anomaly alerts, and optimization.

  • Addresses several tasks
  • Keeps constraints explicit
  • Requires interface testing
  • Needs component and system metrics

Research-only phase

Improve labels, reporting coverage, and causal evidence before deployment.

  • Appropriate when targets are weak
  • Reduces premature automation
  • Can test data interventions
  • Requires organizational patience

Key idea

Resident reports are not a neutral map of need

Reporting depends on awareness, language, internet access, trust, time, and past response. A model trained to predict inspection findings from reports may underprioritize the neighborhoods that stay silent.

Use proactive sampling, geographic audits, and alternative data sources. Fairness cannot be repaired solely by removing location from the features.

The size of that gap has been estimated on exactly this kind of data. Three researchers took more than 100,000 reports made to the New York City Department of Parks and Recreation. They added more than 900,000 made to Chicago’s transportation and water departments. They used the rate of duplicate reports about the same incident to infer how quickly each neighborhood reports one at all. Their results appeared in Nature Computational Science in December 2023. Incidents in downtown Manhattan were reported at about three times the rate of the same incidents in Queens. That held even after controlling for incident characteristics. Reporting rate rose with population density, with the share of residents holding college degrees, with median income, and with the share of residents who are white. A queue built from reports inherits all of that.

Observed demand and underlying need are different quantities.

Steps

Produce the final strategy memo

Complete each step and preserve evidence for reviewers. Frame the decisions: define users, prediction moments, actions, and costs for every component. Audit feedback: trace labels, reports, outcomes, demonstrations, and missing counterfactuals. Choose approaches: justify supervised, anomaly, active, optimization, or causal methods separately. Establish baselines: compare current policy, transparent rules, and simple models. Design evaluation: specify protected time and geography splits, queues, intervals, slices, and experiments. Govern deployment: set review authority, fallback, appeal, monitoring, and rollback. State stop conditions: list the evidence that would pause, narrow, or cancel the project.

Steps six and seven are the ones students treat as paperwork. Flint is the reason they are not. In 2018 a new program manager stopped using the model's rankings. The consequence was quantified in a federal court filing rather than a paper. For 1 January–15 August 2018 the city's observed hit rate was 19.7%. A random dig would have produced 31.4%. The city made 163 digs, 4.5% of the total, in Ward 5 — the ward the model ranked highest, where the hit rate was 95.7%. It made 702 digs, 18.6%, in Ward 4, the ward the model ranked lowest, where the hit rate was 2.4%. Eric Schwartz, one of the model's builders, swore to that analysis and summed it up in a sentence: “The results of my analysis show that, at an aggregate level, the City is not conducting excavations at homes that are most likely to have a hazardous (lead or galvanized steel) service line.”

Nothing had gone wrong with the modelling. The handover to a contractor is where the value was lost — step six. And the statistic that exposed it, hit rate by ward compared against predicted rank, is precisely the monitoring metric step seven exists to write down in advance. A memo that specifies that comparison would have caught the failure in weeks instead of a litigation cycle.

FigureProcess · 7 steps
  1. 1. Frame the decisions

    Define users, prediction moments, actions, and costs for every component.

  2. 2. Audit feedback

    Trace labels, reports, outcomes, demonstrations, and missing counterfactuals.

  3. 3. Choose approaches

    Justify supervised, anomaly, active, optimization, or causal methods separately.

  4. 4. Establish baselines

    Compare current policy, transparent rules, and simple models.

  5. 5. Design evaluation

    Specify protected time and geography splits, queues, intervals, slices, and experiments.

  6. 6. Govern deployment

    Set review authority, fallback, appeal, monitoring, and rollback.

  7. 7. State stop conditions

    List evidence that would pause, narrow, or cancel the project.

Case

SyRI: The Hague stops a fraud-detection system whose model was secret

A court has already supplied one stop condition. SyRI linked data held across Dutch government bodies to flag people likely to be committing benefit, tax or labor-law fraud. On 5 February 2020, in NJCM and others v The Netherlands, the District Court of The Hague ruled that the legislation authorizing it was unlawful, in breach of Article 8 of the European Convention on Human Rights. The system could not continue in use.

The court then recorded what it could not inspect. The risk model in use and the risk indicators constituting it are “secret”, and “The SyRI legislation does not provide for an obligation to inform the persons that their data have been processed in SyRI”. No accuracy figure appears in that reasoning, because accuracy was not what the case turned on. Inspectability was. A capstone that cannot show a reviewer its indicators has already failed a test a court has administered.

Analogy

Designing a public transit network

A city plans transit as a whole. Routes, schedules, demand forecasts, safety rules, budgets, and accessibility cannot be reduced to one optimization score. The plan succeeds only when the pieces work together for real neighborhoods.

A learning system has the same systems-level requirement, and one asymmetry the transit plan does not. A transit plan does not change where people need to go. A predictive model reshapes the very data used to judge later demand and performance.

Google Flu Trends is that asymmetry with a count attached. After its 2009 rebuild the system overestimated CDC influenza-like-illness week after week. Lazer and three colleagues put the tally in Science in 2014: “GFT also missed by a very large margin in the 2011–2012 flu season and has missed high for 100 out of 108 weeks starting with August 2011”. An independent epidemiological reassessment in PLOS Computational Biology found more. The system had missed the first wave of the 2009 A/H1N1 pandemic entirely. It had overshot the 2012/2013 A/H3N2 season by a wide margin — about 268% of surveillance ILI nationally.

The diagnosis is the part a capstone must copy. Lazer and colleagues attributed the drift to "algorithm dynamics" — Google's own search changes and users' responses to them — not to a modelling error. The model did not decay. The world that generated its inputs moved, partly because the model was in it.

The capstone is a system design, not a model-selection contest.

Example

What a strong submission contains

A reviewer should be able to reconstruct the reasoning without guessing. Of the items below, the human-roles diagram is the one written last and the one that matters first. There is a measured price for leaving it out.

Michigan's MiDAS unemployment system issued fraud determinations with no human adjudicator. It then terminated benefits, garnished wages and intercepted tax refunds on the strength of them. In 2019, in Cahoo v. SAS Analytics Inc., the U.S. Court of Appeals for the Sixth Circuit set out what a review had found: “this system was deeply flawed; the Michigan Auditor General reviewed over 22,000 of MiDAS’ fraud determinations and found that 93% of them did not actually involve fraud. In other words, 93% of MiDAS’ fraud adjudications were false-positives.” The Michigan Supreme Court repeated the 93% figure in 2022, in Bauserman v. Unemployment Insurance Agency, and held that the claimants had stated a claim on which they may recover money damages for the due-process violation. The authority-and-appeal layer is the difference between a false-positive rate and a constitutional injury.

  • A one-page task map separating prediction, ranking, anomaly, optimization, and causal questions.
  • A feedback inventory with provenance, delay, missingness, bias, and annotation cost.
  • A baseline table comparing current workflow, rules, simple models, and proposed additions — including the random-dig baseline of the Flint kind, which the city's 2018 hit rate of 19.7% fell below.
  • An evaluation plan covering time, geography, rare hazards, uncertainty, and review capacity.
  • A human-roles diagram showing authority, override, escalation, and appeal: the layer MiDAS did not have when 93% of its reviewed determinations turned out to involve no fraud.
  • A deployment sequence with pilot boundaries, monitoring, rollback, and stop conditions, naming the monitoring statistic in advance — hit rate by ward against predicted rank is one that worked.
  • A final recommendation that may be build, pilot, research, redesign, or do not deploy.

The quality bar: make uncertainty actionable

A strong capstone does not hide uncertainty behind a sophisticated method. It names which claims are predictive, causal, exploratory, or policy-driven, and it attaches an appropriate evidence plan to each of them.

Chicago shows how long a system can run while its central claim goes untested. CPD spent $3.8 million in federal grants across six versions of its "party to violence" risk models. As of July 2018, 399,412 individuals held an SSL risk score. As of March 2019, 313,513 held a CVRM risk tier. The causal question — does scoring these people reduce harm to them? — was examined by RAND, in a quasi-experimental evaluation of the 426-person 2013 pilot. It found no effect on victimisation: “Individuals on the SSL are not more or less likely to become a victim of a homicide or shooting than the comparison group, and this is further supported by city-level analysis.” In January 2020 the City of Chicago Office of Inspector General reported that the scores were unreliable and that the program had been decommissioned on 1 November 2019.

Ranking hundreds of thousands of people is a predictive claim. That the ranking helps them is a causal one, and no amount of the first ever becomes the second. If the data cannot support every component, the final recommendation should be narrower than the original request. Responsible scope is a technical achievement.

Case

160 teams, six life outcomes, and predictions barely better than a benchmark

There is a published measurement of how narrow a defensible claim can turn out to be. The Fragile Families Challenge, run by Matthew Salganik and his co-authors, put 160 teams on one task: build predictive models for six life outcomes, among them a child’s grade point average and whether a family would be evicted, on a high-quality birth-cohort study. Reporting in PNAS in 2020, they concluded that “the best predictions were not very accurate and were only slightly better than those from a simple benchmark model”. Prediction error, they found, was “strongly associated with the family being predicted and weakly associated with the technique used to generate the prediction”.

That result is the deliverable. Within each outcome it mattered far more which family was being predicted than which of 160 teams' techniques did the predicting. Some outcomes are not very predictable from the data anyone has. Reporting so is the accurate answer, not a failed project.

Key takeaways