LOOM.
PUBLIC RESEARCH DOCUMENT · PL-001

Loom Research Charter / Core Specification

The foundational specification governing the Loom research system, its purpose, structure, epistemic discipline, and research governance.

Source: PL-001_Spec PL-001.mdRendered from the current repository document
I need to recreate the case studies for my project which is called Loom, During a transfer a significant amount of documentation was lost. Let me know if you are able to recreate all case files with a complete loom analysis from the data dump that I provide. I need a full rewrite of all case studies and nothing more preferably in markdown format

Project Loom --- Case Study Recovery ManifestRecovered from saved Project Loom materials on 2026-09-06.## Canonical case-study IDs- PL-402 --- Case Study #001: Student Loan Forgiveness- PL-403 --- Case Study #002: Healthcare.gov Launch- PL-404 --- Case Study #003: Cash for Clunkers- PL-405 --- Case Study #004: Acid Rain Program- PL-406 --- Case Study #005: Operation Warp Speed## Recovery status### Fully recovered from saved source material- PL-404 --- Cash for Clunkers- PL-406 --- Operation Warp Speed- PL-006 --- Flint Water Crisis (later numbering used in the expanded vault)### Registered but full body not present in the located canonical registry artifact- PL-402 --- Student Loan Forgiveness- PL-403 --- Healthcare.gov Launch- PL-405 --- Acid Rain ProgramThe registry confirms these artifacts existed and records their titles,versions, purposes, and analytical roles, but the located registrycontains the placeholder "[Full case study text as previouslymemorialized]" rather than their full bodies. Those three should NOT bereconstructed from memory or newly written as if they were the originaldrafts.## Important numbering noteThe earlier canonical registry used PL-402--PL-406 for cases #001--#005.A later Obsidian setup document uses a separate local case numberingconvention (PL-001--PL-008). Flint is therefore preserved here as PL-006while retaining the later case-study identity.## Known analytical sequence#001 Student Loan Forgiveness --- veto fragility #002 Healthcare.gov ---execution fragility #003 Cash for Clunkers --- design adequacy #004 AcidRain Program --- durable success / accumulated capacity #005 OperationWarp Speed --- crisis success / assembled capacity #006 Flint WaterCrisis --- information-flow and self-correction failureCase Study #003: Cash for Clunkers (2009) The Car Allowance RebateSystem (CARS) is the right next test. It isolates thedesign-versus-implementation distinction cleanly: the system wasimplemented with remarkable speed and operational competence, the publicparticipated at scale, the statutory authority was clear, the fundingwas exhausted rapidly---and yet the long-term policy impact remainsdebated. This is not a failure case. It's an adequacy case.What it tests: Can Loom distinguish between "the governance systemworked as designed" and "the design was insufficient to achieve thestated policy goals"?Case Study #003: Cash for Clunkers (2009) When Implementation Succeedsbut Outcomes Disappoint Status: Working Date: July 2026 OntologyVersion: v0.3 Protocol Version: v1.0Stage 0: Case Definition Field Entry Case Name Car Allowance RebateSystem (CARS) --- "Cash for Clunkers" Date Range June--August 2009(program active July 1 -- August 24, 2009) Policy Domain Economicstimulus, environmental policy, industrial policy Governance LevelFederal Policy Type Legislative (authorized by Consumer Assistance toRecycle and Save Act of 2009) Intended Outcome Stimulate economicactivity, reduce greenhouse gas emissions, improve vehicle fuelefficiency, support domestic auto industry Actual Outcome \$3 billion inrebates exhausted in weeks; \~690,000 vehicle transactions; short-termeconomic stimulus achieved; environmental benefits modest relative tocost; program expired after exhausting funds Gap Description Programachieved immediate operational targets but long-term environmental andeconomic additionality remains contested Levels of Analysis Engaged:Policy, Institution, Governance System, EnvironmentStage 1: Policy Diagnosis Core Question: Was the policy objectivesufficiently defined and matched to the mechanism chosen?Dimension Assessment Evidence Level Objective clarity Multipleobjectives stated: stimulus, environmental improvement, industrysupport. These objectives can conflict (e.g., maximizing participationvs. maximizing emissions reduction). A (statutory text) Scope Bounded:\$3 billion in appropriations, specific vehicle eligibility criteria,defined time window. A Mechanism fit Rebate on trade-in of older, lessfuel-efficient vehicles for new, more fuel-efficient ones. Mechanismdirectly incentivizes the desired behavior (vehicle replacement). ACompleteness Statutory authority clear. Funding appropriated. Agency(NHTSA) designated. Implementation timeline specified. Rulemakingcompleted within weeks of enactment. A Assumptions That consumers wouldrespond to incentives; that dealers could process transactionsefficiently; that displaced vehicles would not simply be replaced byadditional household vehicles; that emissions reductions would exceedwhat would have occurred through normal fleet turnover. C Policy DesignAssessment: Adequate. Objectives were multiple and partially in tension,but the mechanism was well-matched to the primary behavioral goal(incentivizing vehicle replacement). The key vulnerability was in theassumptions about additionality---whether the program causedtransactions that would not have occurred otherwise.Level of Analysis: PolicyStage 2: Governance Architecture Mapping Core Question: Who wasresponsible, who had authority, and how were responsibilitiesdistributed?Actor Inventory Actor Formal Authority Actual Role Critical? CongressStatutory authorization, appropriations Enacted CARS Act; appropriated\$1 billion initially, later supplemented to \$3 billion Yes NationalHighway Traffic Safety Administration (NHTSA) Rulemaking, programadministration Issued final rule (July 24, 2009); managed programoperations; processed dealer reimbursement claims Yes Department ofTransportation Oversight Parent department of NHTSA No Office ofManagement and Budget Budget oversight Reviewed rule; monitoredexpenditure No Automobile dealers Transaction processing Acceptedtrade-ins; submitted reimbursement claims; facilitated consumerpurchases Yes Consumers Participation Traded in eligible vehicles;purchased new vehicles Yes Automobile manufacturers Supply Producedeligible new vehicles; did not directly participate in programadministration No Disposal facilities Vehicle destruction Receivedtrade-in vehicles for engine destruction and recycling Yes AuthorityAnalysis Authority Type Actor Holding Authority Adequate? Legalauthority Congress (statutory); NHTSA (regulatory) Yes --- clearstatutory mandate Administrative authority NHTSA Yes --- designatedimplementing agency Budget authority Congress (appropriations); NHTSA(disbursement) Yes --- funds appropriated and available Enforcementauthority NHTSA Adequate --- dealer compliance mechanisms establishedOversight authority DOT, OMB, GAO Adequate Authority AlignmentAssessment Aligned. NHTSA had the formal authority required to designand administer the program. No authority gap existed betweenimplementation responsibility and legal empowerment.Level of Analysis: Governance SystemStage 3: Dependency Chain Analysis Core Question: What conditions,actors, and systems had to remain intact for implementation to succeed?Dependency Mapping Dependency Owner/Controller Within NHTSA Control?Failure Impact Redundancy? Statutory authority Congress No --- butsettled Program could not exist No (statutory required) AppropriationsCongress No --- but provided Program would exhaust funds No(appropriations required) Rulemaking completion NHTSA Yes Program couldnot launch No (required) Dealer participation \~20,000 auto dealers No--- voluntary Insufficient transaction volume Yes (many dealers)Consumer participation Public No --- voluntary Insufficient transactionvolume Yes (millions of potential participants) Claims processing systemNHTSA / contractors Partial --- system development Administrativebottleneck Limited Vehicle disposal infrastructure Disposal facilitiesNo --- existing market Program integrity risk Yes (many facilities)Manufacturer vehicle supply Automakers No --- existing productionInsufficient eligible vehicles Yes (multiple manufacturers) DependencyConcentration Assessment Low concentration. The program architecturecontained redundancies at most nodes. Dealer participation wasdistributed across thousands of independent businesses. Consumerparticipation was distributed across millions of households. No singledealer, consumer, manufacturer, or disposal facility could determineprogram success or failure. The only concentrated dependencies werestatutory authority and appropriations---standard for any federalprogram---and both were settled before launch.Level of Analysis: Governance SystemStage 4: Capacity Assessment Core Question: Did the implementing systempossess the specific capacities required for this policy?Capacity Domain Assessment Rating Evidence Policy capacity NHTSA hadexperience with vehicle safety regulation and consumer-facing programs,though not rebate programs of this scale. Rulemaking completed rapidly.Adequate C (rule promulgated within weeks of enactment) Legal capacityStatutory authority clear. No significant legal challenge emerged.Strong A (statute, final rule unchallenged) Administrative capacityNHTSA managed a high-volume claims processing operation. Initialprocessing delays occurred but were resolved. Adequate to Strong C (GAOreports, agency data) Technical capacity Claims processing systemdeveloped and deployed rapidly. Crashed under initial volume butstabilized. Adequate (after initial stress) C Contractor managementLimited contractor dependency relative to Healthcare.gov. Primaryoperational functions retained within agency or distributed acrossdealers. Adequate C Financial capacity \$3 billion appropriated andavailable. Reimbursement mechanism functioned. Funds exhausted bydesign. Strong A Political capacity Program had bipartisan congressionalsupport at enactment. Public participation was high. Politicalopposition emerged around program cost and effectiveness but did notdisrupt implementation. Strong C Adaptive capacity NHTSA responded toinitial claims processing surge by adding staff and extending processinghours. Program adjusted to demand. Adequate C Key finding: UnlikeHealthcare.gov, NHTSA possessed adequate-to-strong capacity across allrelevant domains for the program's operational requirements. No capacitydomain was critically weak. The program's challenges were operationalscaling issues (initial claims processing surge), not fundamentalcapacity gaps. These were resolved without structural intervention.Level of Analysis: InstitutionStage 5: Implementation Debt Assessment Core Question: What accumulatedweaknesses existed before the program launched?Debt Type Assessment Evidence Institutional debt NHTSA had no priorexperience with large-scale consumer rebate programs. However, theprogram design was relatively simple (dealer-submitted claims forqualifying transactions), and the agency had relevant regulatory andadministrative experience. Debt was low. C Legal debt None. Statutoryauthority was new and clear. No unresolved legal questions accumulatedfrom prior programs. A Procurement debt Low. The program did not dependon a complex contractor ecosystem. Primary operational functions wereperformed by dealers (market actors with existing capacity) and NHTSA(direct administration). C Technical debt Moderate. Claims processingsystem was newly built for the program and had not been tested at scale.Initial volume exceeded system capacity. This is normal first-usetechnical debt, not accumulated structural debt. C Timeline debtSignificant. The program was authorized in June 2009, rules werefinalized in July 2009, and transactions began immediately. Thecompressed timeline between authorization and operation was deliberate(stimulus urgency) and created limited margin for system testing anddealer education. A Data debt Low. Vehicle specifications, dealerregistrations, and consumer eligibility criteria were based on existingdata sources (EPA fuel economy ratings, state vehicle registrations,dealer licensing). C Key finding: Implementation debt was low tomoderate. The most significant debt was timeline compression---adeliberate choice reflecting stimulus urgency, not accumulatedstructural weakness. Unlike Healthcare.gov, where procurement, testing,and oversight debt had accumulated silently, Cash for Clunkers carriedrelatively little pre-existing institutional burden. The program wasbuilt quickly on a relatively clean institutional foundation.Level of Analysis: Institution, Governance SystemStage 6: Fragility Diagnosis Core Question: What type of fragilitydetermined the outcome?Veto Fragility Assessment External Veto Actor Could Actor TerminatePathway? Did Actor Terminate Pathway? Congress Yes (could have repealedor defunded) No Courts Yes (could have enjoined program) No OMB Limited(review authority only) No Veto Fragility Level: Low. No external actorpossessed the ability to terminate the program, and none attempted to doso during its operational period.Execution Fragility Assessment External Dependency Could Failure PreventDelivery? Did Failure Occur? Dealer participation Low risk --- thousandsof independent dealers, high incentive to participate (reimbursement) No--- participation was robust Consumer participation Low risk ---millions of potential participants, strong incentive (rebate) No ---participation exceeded expectations Claims processing system Moderaterisk --- newly built, untested at scale Initial stress resolved withoutstructural failure Vehicle disposal infrastructure Low risk --- existingmarket, simple requirements (engine destruction) No Manufacturer vehiclesupply Low risk --- multiple manufacturers, existing production NoExecution Fragility Level: Low. The program architecture distributedcritical functions across thousands of independent actors (dealers,consumers, manufacturers) with strong incentives to participate. Theonly concentrated operational dependency was the claims processingsystem, which experienced stress but did not fail.Fragility Summary Fragility Type Level Evidence Veto fragility Low Noexternal veto actor; program operated with clear authority throughoutExecution fragility Low Distributed dependencies with strong participantincentives; no single point of operational failure Key finding: UnlikeStudent Loan Forgiveness (high veto fragility) and Healthcare.gov (highexecution fragility), Cash for Clunkers exhibited low fragility acrossboth dimensions. The governance architecture was structurally resilient.The program was not vulnerable to disruption by external actors oroperational dependency failure.Level of Analysis: Governance SystemStage 7: Outcome Analysis Core Question: What actually happened, and howdoes the outcome relate to the governance architecture?Implementation Completion Status Stage Status Notes Statutoryauthorization Complete June 2009 Rulemaking Complete July 24, 2009(final rule) Dealer registration Complete \~20,000 dealers registeredProgram launch Complete July 1, 2009 (initial); July 24, 2009 (full)Consumer transactions Complete \~690,000 transactions processed Claimsprocessing Complete Initial surge stress; resolved with staffingincreases Fund exhaustion Complete August 24, 2009 (\$3 billionexhausted) Vehicle disposal Complete Required engine destructioncompleted Economic stimulus Partial Short-term economic activitygenerated; additionality contested Emissions reduction Partial Modestimprovements over baseline fleet turnover; cost-effectiveness debatedIndustry support Partial Supported auto industry during crisis period;temporary effect Outcome Classification Classification Applies? BasisSuccess No Objectives partially achieved; long-term impact contestedPartial success Yes Program achieved immediate operational targets;long-term policy impact was modest relative to cost and ambitionImplementation failure No The governance system executed competentlyDesign failure Partial The mechanism produced transactions but may havebeen an inefficient instrument for the stated environmental and economicobjectives Governance failure No Authority, capacity, dependencies, andfragility were all adequate Recovery Not applicable No initial failureoccurred Key finding: Cash for Clunkers was an implementation successand a policy design question. The governance system performed asintended. The debate about the program's value is not about whether thegovernment could execute---it clearly could---but about whether thechosen mechanism was the most effective way to achieve the statedobjectives given the cost.Level of Analysis: Policy, EnvironmentStage 8: Diagnostic Synthesis Core Question: What is the primaryexplanation for the governance outcome?Primary Diagnosis Cash for Clunkers represents a case where governancearchitecture was adequate but policy design ambition exceeded mechanismeffectiveness. The implementing institution possessed clear authority,adequate capacity, low implementation debt, and a structurally resilientdependency architecture. The program achieved its operational targets.The gap between intended and actual outcomes is not attributable togovernance failure---it is attributable to the inherent limitations ofthe policy mechanism in producing lasting environmental and economicchange through a temporary consumer incentive program.Secondary Factors Multiple objectives in tension. The program sought tostimulate the economy, reduce emissions, and support the auto industrysimultaneously. Maximizing participation (stimulus) could conflict withmaximizing emissions reduction per dollar (environmental effectiveness).The mechanism served the participation goal better than theenvironmental goal.Additionality assumptions. The program's environmental and economicimpact depended on causing transactions that would not have occurredotherwise. Research suggests significant non-additionality: manyparticipants would have purchased vehicles in the near term without theprogram, reducing the net impact.Timeline compression by design. The program was intentionallyshort-duration stimulus. This limited the depth of environmental impact(one-time fleet improvement rather than sustained transformation) butwas inherent to the policy concept, not an implementation failure.Interaction Effects The combination of low fragility, adequate capacity,and clear authority meant that implementation did not impede the policy.This distinguishes Cash for Clunkers sharply from Student LoanForgiveness and Healthcare.gov. In those cases, governance architecturedetermined the outcome. In this case, governance architecture enabledthe outcome---and the outcome's limitations are attributable to thepolicy design itself.Diagnostic Classification Policy design failure --- the mechanism couldnot produce the objective (partial: produced transactions but was aninefficient instrument for environmental and economic goals)Authority failureCapacity failureDependency failureFragility failureDebt revelationAdaptive failurePrimary classification: Design adequacy question. The governance systemperformed. The remaining question is whether the policy design wassufficient to achieve the stated objectives, which is a policy analysisquestion beyond the scope of governance mechanism diagnosis.Level of Analysis: Policy (primary); Institution and Governance System(secondary --- both performed adequately)Stage 9: Intervention Design Core Question: What would improve theprobability of achieving the intended outcomes?Authority Recommendations None. Authority was clear and adequate.Capacity Recommendations Modest. NHTSA could have benefited frompre-launch load testing of the claims processing system to reduceinitial surge stress, but this was an operational scaling issue, not acapacity failure.Dependency Recommendations None. Dependency architecture wasappropriately distributed.Sequencing Recommendations A longer program duration with phasedincentive structures could have improved environmental additionality byreducing the substitution effect (consumers accelerating already-plannedpurchases). However, this would have conflicted with the stimulusobjective of rapid economic injection. This is a design tradeoff, not agovernance flaw.Fragility Recommendations None. Fragility was low across bothdimensions.Design Recommendations (Beyond Governance Diagnosis) If the primaryobjective was environmental improvement rather than economic stimulus, adifferent mechanism---such as a fee-and-rebate structure calibrated toemissions reductions per dollar, or a sustained incentive program ratherthan a temporary one---would have produced greater environmental impactper dollar of public expenditure. This is a policy design observation,not a governance diagnosis, but the governance architecture would havesupported such a design had it been chosen.Protocol Metadata Field Entry Protocol Version v1.0 Ontology Versionv0.3 Case Study #003 Analyst Project Loom Date of Analysis July 2026Review Status Working Cross-Case Comparison Matrix (Initial) Variable#001: Student Loans #002: Healthcare.gov #003: Cash for Clunkers Policydesign Adequate Adequate Adequate (multi-objective tension) Authorityalignment Misaligned (legal contested) Aligned Aligned Dependencyconcentration High (judicial node) High (integration node) LowImplementation debt High (legal, data, institutional) High (procurement,testing, oversight, timeline) Low to moderate (timeline only) Vetofragility High Low Low Execution fragility Low High Low Adaptivecapacity Not tested (pathway terminated) Initially absent; demonstratedin recovery Adequate (operational scaling response) Primary outcomeclassification Implementation failure (blocked) Implementation failure →Recovery Partial success Primary diagnostic classification Fragilityfailure (veto) Capacity failure + Fragility failure (execution) Designadequacy question Emerging Patterns (Preliminary, 3 Cases) Fragilitytype predicts failure mode. Veto fragility (#001) and executionfragility (#002) produced different failure mechanisms. Low fragility inboth dimensions (#003) correlated with implementation success.Dependency concentration amplifies fragility. High concentration (#001legal, #002 operational) created single points of failure. Lowconcentration (#003) distributed risk across redundant nodes.Capacity domains enable differentiation. Aggregated "capacity" ratingswould have obscured the distinction between #002 (specific domainweaknesses) and #003 (broadly adequate capacity). Domain-level analysiswas necessary for diagnostic precision.Implementation debt is a pre-existing condition, not a post-hoc label.In #001 and #002, debt predated the stress event. In #003, lowpre-existing debt correlated with smoother implementation.The ontology can distinguish implementation failure from designlimitation. Case #003 demonstrates that Loom does not default to findinggovernance failure. When the governance system performs adequately, thediagnosis identifies this and directs attention to the policy designlevel.Protocol Refinements for v1.1 (From This Case) Level of Analysis ---Validated. The explicit identification of analytical level prevented theerror of attributing design limitations to governance failure. Cash forClunkers was an implementation success; its limitations were at thepolicy design and environmental levels.Evidence Standards --- Validated. The discipline of rating evidencequality exposed areas where claims about program impact rely oncontested economic analysis (Level C) rather than direct documentaryevidence (Level A).Design Adequacy Question --- The protocol currently classifies outcomesacross success, partial success, and various failure types. Case #003suggests adding a formal "Design Adequacy" classification for caseswhere governance performed adequately but the mechanism's inherentlimitations produced disappointing outcomes. This prevents the frameworkfrom implying that all disappointing outcomes are governance failures.Case Study Status: Working Next Review: After protocol v1.1 refinementsThe case study validates the core proposition: Loom can distinguishbetween governance failure and policy design limitation. The protocol isnow tested across three distinct configurations---external veto,internal capacity collapse, and adequate implementation with designquestions.Case Study #005: Operation Warp Speed (2020--2021) Crisis GovernanceUnder Extreme Time Pressure text Project: Project Loom Artifact ID:PL-406 Title: Case Study #005 --- Operation Warp Speed (2020--2021):Crisis Governance Under Extreme Time Pressure Version: v1.0 Status:Working Analytical Role: Crisis Success Case --- Parallel Processing /Adaptive Capacity Layer: Validation Owner: Project Loom Created:2026-07-13 Last Updated: 2026-07-13 Depends On: PL-201 (v1.1), PL-101(v0.3) Supersedes: None Superseded By: None Related: PL-501 Stage 0:Case Definition Field Entry Case Name Operation Warp Speed (OWS) DateRange May 2020 -- February 2021 (primary operation); vaccine developmentcontinued through 2021 Policy Domain Public health, industrial policy,interagency coordination, public-private partnership Governance LevelFederal Policy Type Executive initiative with congressional funding;public-private partnership model Intended Outcome Develop, manufacture,and distribute 300 million doses of safe and effective COVID-19 vaccinesby January 2021 Actual Outcome Two vaccines (Pfizer-BioNTech, Moderna)received Emergency Use Authorization in December 2020; third (Johnson &Johnson) in February 2021; over 300 million doses distributed bymid-2021; vaccine development timeline compressed from typical 10--15years to approximately 11 months Gap Description The programdramatically exceeded typical vaccine development timelines whilemaintaining safety standards. This is a governance success under extremeconstraints. Pre-Analysis Hypothesis:Operation Warp Speed will demonstrate that high governance capacity cancompensate for compressed timelines by replacing sequential dependencychains with parallel execution while maintaining sufficientcoordination. The case will stress Governance Capacity (especiallyadaptive capacity and public-private coordination), Dependency Chains(parallel vs. sequential), and Implementation Debt (specifically,whether low initial debt enabled rapid mobilization).Levels of Analysis Engaged: Policy, Institution, Governance System,EnvironmentStage 1: Policy Diagnosis Dimension Assessment Evidence Level Objectiveclarity Specific: 300 million doses; safe and effective; January 2021target. Quantitative and time-bound. A (HHS/DOD announcements,contracts) Scope Massive: entire U.S. population; multiple vaccinecandidates; manufacturing at risk before efficacy data. A Mechanism fitPublic-private partnership with government funding (BARDA, DOD),manufacturing support, regulatory coordination (FDA), and distributionlogistics (DOD). Unprecedented mechanism for the objective. ACompleteness The initiative combined funding, manufacturing, regulatorycoordination, and logistics into a single operational framework. Unusualintegration of functions typically handled sequentially or by separateagencies. A Assumptions That mRNA technology would prove viable; thatmanufacturing could scale before efficacy was proven; that FDA couldreview at speed; that distribution infrastructure existed or could bebuilt. Most assumptions proved valid; mRNA was the critical enablingcondition that OWS did not control but bet on correctly. B Policy DesignAssessment: Strong. The mechanism directly addressed the corechallenge---timeline compression---by restructuring the standard vaccinedevelopment sequence. The key design choice was overlapping phases thatare traditionally sequential: manufacturing began before efficacy data;distribution planning began before authorization. This was not merelyaccelerating the existing process; it was redesigning the processarchitecture.Level of Analysis: PolicyStage 2: Governance Architecture Mapping Actor Inventory Actor FormalAuthority Actual Role Critical? White House / HHS / DOD Executivecoordination OWS leadership: Moncef Slaoui (Chief Advisor), GeneralGustave Perna (COO) Yes HHS (BARDA) Funding, manufacturing contractsProvided advance purchase agreements and manufacturing support YesDepartment of Defense Logistics, distribution planning Managed supplychain, distribution infrastructure Yes FDA Regulatory review, EmergencyUse Authorization Reviewed safety and efficacy data; issued EUAs Yes CDCImmunization guidelines, distribution recommendations Advisory Committeeon Immunization Practices (ACIP) recommendations SupportingPfizer-BioNTech Vaccine development, manufacturing Developed mRNAvaccine; did not accept OWS funding for development Yes Moderna Vaccinedevelopment, manufacturing Developed mRNA vaccine with OWS funding andsupport Yes Johnson & Johnson Vaccine development Developed adenovirusvector vaccine Yes AstraZeneca / Oxford Vaccine development Developedadenovirus vector vaccine (later authorized outside U.S.) SupportingState governments Distribution, administration Received federalallocations; managed state-level distribution Yes Private sector(logistics) Distribution McKesson, FedEx, UPS, CVS, Walgreens SupportingAuthority Analysis Authority Type Actor Adequate? Legal authority HHS,DOD, FDA (via statutory authority; emergency powers) Yes Administrativeauthority OWS leadership (coordinated across agencies) Yes Budgetauthority Congress (CARES Act and subsequent appropriations); HHS(BARDA) Yes --- approximately \$18 billion Regulatory authority FDA (EUApathway) Yes Distribution authority DOD, states Yes --- coordinatedfederal-state distribution Authority Alignment Assessment Aligned andintentionally restructured. OWS was not a standing agency but atemporary coordination structure layered across existing institutions.Authority was drawn from multiple sources (HHS, DOD, FDA) andcoordinated through a dedicated leadership team. This avoided thetypical problem of interagency coordination without formal authority bycreating a temporary authority structure with White House backing.Level of Analysis: Governance SystemStage 3: Dependency Chain Analysis The Standard Vaccine DevelopmentChain (Sequential) text Basic Research → Preclinical → Phase I → PhaseII → Phase III → Regulatory Review → Manufacturing → Distribution →Administration (sequential, 10--15 years) The OWS Restructured Chain(Parallel) text Basic Research (already complete for mRNA) │ ├── Phase I──┐ ├── Phase II ──┼── Phase III ── Regulatory Review (FDA, rolling) ├──Manufacturing (at risk, concurrent with trials) ├── DistributionPlanning (DOD, concurrent) └── Administration Planning (CDC, states,concurrent) (parallel, 11 months) Dependency Mapping DependencyOwner/Controller Within OWS Control? Failure Impact Redundancy? mRNAtechnology viability Pfizer, Moderna (prior research) No --- technologyexisted before OWS No vaccines if mRNA failed Yes --- multiple vaccineplatforms funded Phase III trial results Pfizer, Moderna, independentDSMBs Partial --- OWS funded but did not control trials No EUA withoutefficacy data Yes (multiple candidates) FDA regulatory review FDA No ---independent regulator No authorization No (regulatory required)Manufacturing at scale Pfizer, Moderna, subcontractors Partial --- OWSfunded and supported via DPA No doses without manufacturing Yes(multiple manufacturers) Raw materials / supply chain Global suppliers;DPA authority Partial --- DPA could prioritize Manufacturing delaysLimited Cold chain distribution DOD, McKesson, FedEx, UPS Yes --- DODmanaged logistics Spoiled doses; delivery failure Partial Stateadministration State governments No --- federal system Doses distributedbut not administered Yes (50 states) Public acceptance Public No Lowuptake despite availability No (trust-dependent) DependencyConcentration Assessment Deliberately low concentration. OWS's definingstructural innovation was eliminating concentrated dependencies throughredundancy and parallel processing. Multiple vaccine candidates (mRNA,adenovirus vector, protein subunit) ensured that failure of any oneplatform did not terminate the program. Manufacturing was funded at riskacross multiple facilities. The DOD distribution system providedlogistics capacity that did not depend on any single contractor.The remaining concentrated dependencies were: FDA regulatory review(non-redundant by design---regulatory independence was a feature, not aflaw), raw material supply chains (partially addressed through DPA), andpublic acceptance (addressed through transparency measures andcommunication).Level of Analysis: Governance SystemStage 4: Capacity Assessment Capacity Domain Rating Evidence EvidenceLevel Policy capacity Strong OWS leadership included experiencedpharmaceutical industry and military logistics expertise. Designexplicitly targeted timeline compression through parallel processing. ALegal capacity Strong EUA pathway existed in statute; FDA had clearauthority. Contracts structured under existing BARDA authority. AAdministrative capacity Strong OWS created a dedicated coordinationstructure rather than relying on existing interagency processes. BTechnical capacity Strong mRNA technology was de-risked by priorresearch (NIH, DARPA, private sector). Manufacturing science was mature.A Public-private coordination Strong BARDA had experience with advancepurchase agreements. OWS used flexible contracting and manufacturingsupport. B Financial capacity Strong Approximately \$18 billionappropriated. Funding was not a constraint. A Political capacity StrongBipartisan support for vaccine development. Operation continued acrossadministration change (Trump to Biden). A Adaptive capacity Strong OWSadjusted as candidates succeeded or failed. Manufacturing reallocated.Distribution adapted to state-level variation. B Key finding: OWSdemonstrated strong capacity across all relevant domains. Critically,the capacity was assembled---the initiative brought together expertisefrom pharmaceutical industry, military logistics, and public healthagencies into a temporary structure designed for speed. This was notinstitutional capacity accumulated over decades (as in the Acid RainProgram). It was capacity intentionally assembled for a specificmission.Level of Analysis: InstitutionStage 5: Implementation Debt Assessment Debt Type Assessment EvidenceEvidence Level Institutional debt Low. OWS was a new structure. It didnot inherit legacy coordination failures because it was not an existinginstitution. A\Legal debt Low. EUA pathway was established in statute. Contractingauthority was clear. A\Technical debt Low. mRNA technology was developed but not previouslymanufactured at billion-dose scale. The technology risk was real but not"debt"---it was a known uncertainty, not accumulated weakness. B\Procurement debt Low. OWS used flexible contracting mechanisms (advancepurchase agreements, manufacturing support) rather than traditionalprocurement that would have imposed sequential timelines. B\Timeline debt None. The compressed timeline was the constraint to besolved, not accumulated weakness. OWS was designed specifically tooperate under compression. A\Data debt Low. Clinical trial data was generated in real time. FDA usedrolling review rather than waiting for completed submissions. A\Coordination debt Intentionally avoided. OWS replaced sequentialinteragency coordination with parallel processing under unifiedleadership. A\Key finding: Operation Warp Speed carried remarkably low implementationdebt. This was not accidental---it was structural. By creating atemporary organization rather than operating through existinginstitutional arrangements, OWS avoided inheriting the coordinationdebt, procurement rigidity, and sequential processing norms thatcharacterize standard government operations. This aligns with thepattern observed across Loom cases: low implementation debt isassociated with implementation success. But OWS achieved low debtthrough a different mechanism than the Acid Rain Program---not throughdecades of accumulated capacity, but through intentional organizationaldesign that bypassed existing debt.Level of Analysis: Institution, Governance SystemStage 6: Fragility Diagnosis Veto Fragility Assessment External VetoActor Could Actor Terminate Pathway? Did Actor Terminate Pathway?Congress Yes (could defund) No --- continued funding FDA Yes (could denyEUA) No --- authorized vaccines based on data Courts Yes (could enjoin)No --- limited legal challenges; none successful Administration changeYes (could deprioritize) No --- Biden administration continued andexpanded OWS Veto Fragility Level: Low. The program had bipartisansupport and survived administration change. FDA maintained independentreview but acted on compressed timelines. No external veto wasexercised.Execution Fragility Assessment External Dependency Could Failure PreventDelivery? Did Failure Occur? mRNA efficacy Yes --- if mRNA vaccines hadfailed, timeline would have extended No --- both mRNA vaccines showed\~95% efficacy Manufacturing scale-up Yes No --- manufacturingsucceeded, though with early bottlenecks Raw material supply Yes Partial--- some shortages; DPA mitigated State distribution Yes --- butredundant across 50 states Partial --- state-level variation in speedPublic acceptance Yes Partial --- uptake was high initially butplateaued Execution Fragility Level: Moderate to Low. Themultiple-candidate strategy provided redundancy against platformfailure. Manufacturing, supply chain, and distribution dependencies wereactively managed. The most significant remaining fragility was publicacceptance---outside OWS's direct control.Fragility Summary Fragility Type Level Evidence Veto fragility LowBipartisan support; survived administration change; FDA acted onevidence Execution fragility Moderate to Low Redundancy across vaccineplatforms; active dependency management; public acceptance residual riskLevel of Analysis: Governance SystemStage 7: Outcome Analysis Implementation Completion Status Stage StatusNotes Funding and organization Complete May 2020 Vaccine candidateselection Complete Multiple platforms funded Clinical trials (PhaseI--III) Complete Compressed timeline; rolling data submissionManufacturing at risk Complete Began before efficacy data FDA EmergencyUse Authorization Complete Pfizer: December 11, 2020; Moderna: December18, 2020 Distribution infrastructure Complete DOD-managed logisticsDoses distributed Complete --- exceeded Over 300 million doses bymid-2021 Doses administered Complete --- variable U.S. achieved highinitial coverage; boosters ongoing Safety monitoring Complete ---ongoing Post-market surveillance continued Outcome ClassificationClassification Applies? Basis Success Yes 300 million dose targetachieved; timeline compressed from 10--15 years to 11 months; safetymaintained Partial success No Primary objectives achieved Implementationfailure No System executed as designed Design failure No Parallelprocessing architecture functioned Level of Analysis: All levelsperformed adequately or strongly.Stage 8: Diagnostic Synthesis Primary Diagnosis Operation Warp Speedsucceeded because a temporary governance structure intentionallydesigned for speed replaced sequential dependency chains with parallelprocessing, supported by strong assembled capacity, low inheritedimplementation debt, and redundancy across critical dependencies.The program's defining governance innovation was the deliberaterestructuring of the implementation architecture. Standard vaccinedevelopment proceeds sequentially---research, then trials, thenmanufacturing, then distribution---because each stage's initiationdepends on the previous stage's success. OWS funded all stagessimultaneously, accepting the financial risk of manufacturing failure inexchange for the time savings of parallel execution. This was not merelyaccelerating the existing process; it was redesigning the processarchitecture to operate under a different dependency logic.Secondary Factors Prior mRNA research. The technology was not inventedby OWS. Decades of NIH, DARPA, and private sector research had de-riskedthe mRNA platform. OWS bet on a mature technology, not an experimentalone.Financial risk absorption. The government absorbed the financial risk ofat-risk manufacturing. Private companies would not have manufactured atscale before efficacy data without government guarantees. This riskabsorption was a critical enabling condition.Temporary organizational design. OWS was a mission-specific structure,not a permanent agency. This allowed it to bypass standard procurementtimelines, interagency coordination norms, and sequentialdecision-making processes that would have imposed implementation debt.Redundancy across platforms. Funding multiple vaccine candidates (mRNA,adenovirus vector, protein subunit) created redundancy that reducedfragility. The failure of any one candidate did not threaten the overallmission.Feedback Architecture Feedback Mechanism Function Clinical trial data(rolling) Real-time safety and efficacy information; enabled FDA rollingreview Manufacturing yield data Production adjustment; raw materialallocation Distribution tracking (Tiberius) Real-time allocation anddelivery monitoring State-level administration data Identifiedbottlenecks; enabled federal support Adverse event monitoring (VAERS)Post-market safety surveillance Interaction Effects The combination ofparallel processing, redundant candidates, and government riskabsorption was mutually reinforcing. Parallel processing requiredfinancial risk absorption (government funded manufacturing beforeefficacy was proven). Financial risk absorption enabled redundancy(multiple candidates could be funded simultaneously). Redundancy reducedfragility (failure of any single candidate did not terminate theprogram). Reduced fragility allowed FDA to maintain independent reviewwithout political pressure to lower standards---a virtuous cycle thatpreserved both speed and safety.Diagnostic Classification Success --- Objectives achieved. The frameworkidentifies specific governance design features that enabled success.Level of Analysis: Policy (strong design---parallel processingarchitecture), Institution (strong assembled capacity), GovernanceSystem (low fragility through redundancy; low inherited debt throughtemporary structure), Environment (prior mRNA research enabled theapproach; crisis context motivated investment and public acceptance)Stage 9: Intervention Design The program succeeded. Intervention designidentifies the features most responsible for success and the conditionsunder which they might be replicated.Features Most Responsible for Success Parallel processing architecture.Manufacturing, trials, and distribution planning occurred simultaneouslyrather than sequentially. This was the single most important designchoice.Government risk absorption. Advance purchase agreements and at-riskmanufacturing funding removed the financial barrier to parallelprocessing.Redundancy across candidates. Multiple vaccine platforms reduced therisk that any single failure would terminate the program.Temporary organizational structure. OWS was not constrained by existingagency processes, procurement timelines, or interagency coordinationnorms.Assembled expertise. Leadership combined pharmaceutical industryknowledge with military logistics capability.Counterfactual Stress Test Condition Removed Expected Effect No parallelprocessing Timeline extends to 3--5+ years; sequential dependency chainsimpose standard vaccine development duration No government riskabsorption Manufacturers wait for efficacy data before scalingproduction; timeline extends by years Single vaccine candidate Platformfailure terminates the program; no redundancy Standard agencycoordination (no OWS) Interagency friction imposes delays; procurementtimelines extend; sequential processing norms dominate mRNA technologynot mature Parallel processing still possible but timeline extends dueto technology development requirements Conclusion: The program's successdepended on the interaction of parallel processing architecture,government risk absorption, and technological maturity. The governancedesign was necessary but not sufficient---without mature mRNAtechnology, the timeline would have been longer regardless of governancedesign.Replicability Conditions The features most responsible for success arereplicable in other crisis contexts but require:Pre-existing technological maturity (parallel processing cannot createtechnology that does not exist)Willingness to absorb financial risk (politically contingent)Ability to create temporary structures that bypass standard processes(may face institutional resistance in non-crisis contexts)Redundancy across multiple independent pathways (requires resources andcoordination)Stage 10: Framework Reflection Question Response Which ontology conceptswere essential? Dependency Chains (parallel vs. sequential processingwas the core analytical insight), Governance Capacity (assembledcapacity distinct from accumulated capacity), Implementation Debt (lowinherited debt through temporary structure), Dependency Concentration(deliberately low), Governance Fragility (redundancy reduced fragility).Which concepts were unused? Formal vs. Effective Authority was aligned.Policy Completeness was not an issue. Did this case expose a gap? Thecase reveals that Institutional Maturation (identified as a candidate inCase #004) has a counterpart: Assembled Capacity---capacityintentionally created for a specific mission rather than accumulatedover time. The Acid Rain Program succeeded through accumulated capacity;OWS succeeded through assembled capacity. Both achieved lowimplementation debt, but through different mechanisms. This suggeststhat Implementation Debt can be avoided either by building capacitygradually (maturation) or by creating temporary structures that bypassinherited debt (assembly). Did any concepts overlap? No. Should anyconcept be added, refined, or deprecated? The distinction betweenaccumulated and assembled capacity should be tracked. If it persistsacross additional cases, it may warrant formalization. The currentGovernance Capacity framework accommodates both but does not explicitlydistinguish between them. Confidence in diagnosis? High. The causalmechanisms are well-documented. What would increase confidence? Acomparison case where a temporary governance structure failed---testingwhether assembly alone is sufficient or whether specific design features(parallel processing, redundancy) are necessary. Ontology EvolutionCandidates Two candidates are now being tracked:Institutional Maturation (from Case #004): Accumulation of institutionalknowledge and capability over time.Assembled Capacity (from Case #005): Capacity intentionally created fora specific mission through temporary organizational design.Both produce low implementation debt but through different mechanisms.This distinction may become important as the case library grows.Hypothesis Assessment Original Hypothesis: Operation Warp Speed willdemonstrate that high governance capacity can compensate for compressedtimelines by replacing sequential dependency chains with parallelexecution while maintaining sufficient coordination.Assessment: Supported. The case confirmed the central mechanism. Theontology captured the critical governance innovation (parallelprocessing architecture) and the enabling conditions (government riskabsorption, redundancy, temporary organizational design). The case alsorevealed an unexpected dimension: the distinction between accumulatedcapacity (#004) and assembled capacity (#005) as alternative pathways tolow implementation debt.Unexpected findings: The importance of technological maturity as aprecondition. Governance design could not have succeeded without priormRNA research. This is a reminder that governance capacity operateswithin environmental constraints---the best-designed implementationarchitecture cannot substitute for absent technology.Ontology modifications required: None immediately. Theaccumulated/assembled capacity distinction is noted for tracking. If itpersists across additional cases, it may warrant formalization in afuture ontology version.Cross-Case Reference [[PL-402 Case Study 001]] --- Student LoanForgiveness (veto fragility failure)[[PL-403 Case Study 002]] --- Healthcare.gov (execution fragilityfailure)[[PL-404 Case Study 003]] --- Cash for Clunkers (design adequacyquestion)[[PL-405 Case Study 004]] --- Acid Rain Program (durable successthrough accumulated capacity)[[PL-501 Cross-Case Comparison Matrix]]Change Log Version Date Changes Rationale v1.0 2026-07-13 Initial casestudy Fifth validation case; first crisis success case; first explicithypothesis test# PL-000: Project Loom Master Index## Complete System Library and Cross-Reference Guide---## 1. SYSTEM OVERVIEW| Field | Value ||-------|-------|| Framework Name | Project Loom || Purpose | Governance analysis framework for documenting how systems fail, exclude, and harm populations they claim to serve || Core Method | Three diagnostic questions applied to governance cases: What does the system claim to do? Who is the user for whom that promise breaks? What assumption makes that exclusion invisible? || Origin | Built from lived experience with healthcare system failure, expanded through comparative case analysis || Status | Active development — transitioning from retrospective case analysis to prospective policy analysis || Current Version | v0.5 (post-Case #009, post-Pattern Report #001) || Total Cases | 9 completed, 3 prioritized for next phase || Total Concepts Tracked | 22 (6 stable, 3 working, 3 supported, 8 candidate, 2 observation) |---## 2. PROJECT LOOM ONTOLOGY### 2.1 Concept Status Definitions| Status | Definition | Threshold for Promotion ||--------|------------|------------------------|| Observation | Noted in 1 case as potentially significant | Requires clear mechanism identification || Candidate | Observed in 1 case with clear mechanism | Requires 2–3 additional cases for validation || Supported | Observed in 3+ structurally different cases or 2 cases with strong cross-case validation | Requires 5+ cases across diverse domains || Working | Actively used in analysis but not yet formalized | Requires formal definition and case testing || Stable | Canonical concept, survives 5+ cases, no falsifying cases | Final status |### 2.2 Current Concept Inventory#### STABLE CONCEPTS (6)| Concept | Definition | Origin Case | Defining Characteristics ||---------|------------|-------------|-------------------------|| Governance | The system of rules, practices, and processes by which decisions are made and implemented | All cases | Foundational concept || Policy | A deliberate system of principles to guide decisions and achieve rational outcomes | All cases | Foundational concept || Implementation | The process of putting a policy or decision into effect | All cases | Foundational concept || Governance Capacity | The ability of a system to detect, diagnose, and act on problems within its domain | All cases | Multidimensional — accumulated, assembled, sustaining || Dependency Chains | The networked relationships where system operations depend on conditions set elsewhere | All cases | Chain ends far from where bodies fall || Implementation Debt | Structural weaknesses that exist before implementation begins; revealed, not created, by failure | #001–#008 | Causal predictor of governance outcomes |#### WORKING CONCEPTS (3)| Concept | Definition | Current Use ||---------|------------|-------------|| Veto Fragility | Vulnerability to external actors terminating a governance pathway | Stable in practice, awaiting formal consolidation || Execution Fragility | Vulnerability to operational dependencies failing | Stable in practice, awaiting formal consolidation || Stakeholder Alignment | Degree to which affected parties support or oppose a policy | Used across all cases, not yet formalized |#### SUPPORTED CONCEPTS (3)| Concept | Definition | Evidence Base | Promotion Date ||---------|------------|---------------|----------------|| Institutional Maturation | Long-term institutional learning that reduces implementation debt | Case #004 Acid Rain | Post-Pattern Report #001 || Assembled Capacity | Capacity intentionally created for specific missions, temporary or permanent | Cases #005, #009 | Post-Pattern Report #001 || Mechanism-Purpose Alignment | Relationship between enforceable architecture and stated objectives | Cases #003, #004, #007 | Post-Pattern Report #001 || Self-Correction Fragility | Inability of a system to recognize and correct its own failures | Cases #006, #009 | Post-Case #009 |#### CANDIDATE CONCEPTS (8)| Concept | Definition | Origin Case | Validation Needed ||---------|------------|-------------|-------------------|| Governance Epistemology | How governance systems determine what they know and convert knowledge into action | #006 Flint | Additional knowledge/action cases || Information Flow | Movement of data through governance systems | #006 Flint | Subsumed under Governance Epistemology || Design Fragility | Vulnerability created by architecture itself | #007 MSA | Second architecture failure case || Temporal Fragility | Vulnerability when implementation horizons exceed stability of enabling conditions | #008 CAHSR | Second long-horizon case || Sustaining Capacity | Ability to maintain resources, legitimacy, and coordination over long periods | #008 CAHSR | Successful long-horizon comparison || Objective Layer Separation | Distinction between stated and actual objectives | #007 MSA | More design cases || Chronic Partial Implementation | System continues operating but cannot achieve original objective | #008 CAHSR | Multiple long-duration cases || Adaptive Capacity | Ability to restructure when failure is acknowledged | #009 USDS | Distinguish from Self-Correction |#### OBSERVATION CONCEPTS (2)| Concept | Definition | Evidence | Status ||---------|------------|----------|--------|| Environmental Justice Debt | Cross-cutting debt dimension affecting marginalized communities | #006 Flint | Awaiting further evidence || Commitment Gap Debt | Parent category for funding, authority, and capacity gaps | #008 CAHSR | Awaiting parent category confirmation |---## 3. CASE STUDY LIBRARY### 3.1 Completed Cases (9)| ID | Case Name | Period | Domain | Analytical Role | Primary Finding | Concepts Tested | Document Status ||----|-----------|--------|--------|-----------------|-----------------|-----------------|-----------------|| #001 | Student Loan Forgiveness | 2022–2023 | Education Policy | External Constraint Failure | Legal pathway invalidated by Supreme Court | Veto Fragility | Summary only || #002 | Healthcare.gov Launch | 2013 | Health IT | Execution Failure | Capacity deficit caused operational collapse | Execution Fragility, Capacity Domains | Summary only || #003 | Cash for Clunkers | 2009 | Economic Stimulus | Partial Success | Operational success, modest policy impact | Implementation vs. Policy Quality | Summary only || #004 | Acid Rain Program | 1990–2010 | Environmental | Durable Success | Market mechanism with accumulated capacity succeeded | Institutional Maturation, Mechanism-Purpose Alignment | Summary only || #005 | Operation Warp Speed | 2020–2021 | Public Health | Crisis Success | Temporary capacity assembly accelerated vaccine development | Assembled Capacity | Summary only || #006 | Flint Water Crisis | 2014–2016 | Public Health | Self-Correction Failure | Information suppressed, no corrective mechanism existed | Self-Correction Fragility, Governance Epistemology | Summary only || #007 | Tobacco MSA | 1998–Present | Public Health | Mixed Outcome | Financial architecture succeeded, health goals failed | Mechanism-Purpose Alignment, Design Fragility | Summary only || #008 | California High-Speed Rail | 2008–Present | Infrastructure | Chronic Partial Implementation | Timeline exceeded stability of enabling conditions | Temporal Fragility, Sustaining Capacity | Summary only || #009 | United States Digital Service | 2014–Present | Government Tech | Self-Correction Success | Durable corrective mechanism created after recognized failure | Self-Correction Fragility, Assembled Capacity, Governance Epistemology | Full document (PL-410) |### 3.2 Prioritized Next Cases (3)| Priority | Case | Tests | Rationale ||----------|------|-------|-----------|| #010 | Southwest Airlines Holiday Collapse (2022) | Coordination Debt, Execution Fragility | Private sector comparison; coordination failure; rapid collapse || #011 | Opioid Settlement Implementation | Design Fragility, Mechanism-Purpose Alignment | Tests whether MSA pattern repeats || #012 | Crossrail (London) | Temporal Fragility, Sustaining Capacity | Long-horizon success comparison to CAHSR |---## 4. ARTIFACT LIBRARY### 4.1 Core Framework Documents| Artifact ID | Title | Description | Status ||-------------|-------|-------------|--------|| PL-000 | Master Index | This document | Created || PL-101 | Project Loom Ontology | Core concept definitions and relationships | Needs updating post-Case #009 || PL-105 | Ontology Evolution Log | Status changes and promotion history | Updated through Case #009 || PL-201 | Loom Analysis Protocol | Ten-stage case study methodology | Referenced, not fully drafted || PL-501 | Cross-Case Comparison Matrix | Comparative analysis across all cases | Needs updating post-Case #009 || PL-502 | Pattern Report #001 | Concept consolidation after eight cases | Completed || PL-601 | Project Loom Canon | Intellectual scaffolding and bibliography | Created |### 4.2 Case Study Documents| Artifact ID | Case | Status | Location ||-------------|------|--------|----------|| PL-401 | Case Study #001 — Student Loan Forgiveness | Summary only | Section 3.1 || PL-402 | Case Study #002 — Healthcare.gov | Summary only | Section 3.1 || PL-403 | Case Study #003 — Cash for Clunkers | Summary only | Section 3.1 || PL-404 | Case Study #004 — Acid Rain Program | Summary only | Section 3.1 || PL-405 | Case Study #005 — Operation Warp Speed | Summary only | Section 3.1 || PL-406 | Case Study #006 — Flint Water Crisis | Summary only | Section 3.1 || PL-407 | Case Study #007 — Tobacco MSA | Summary only | Section 3.1 || PL-408 | Case Study #008 — California High-Speed Rail | Summary only | Section 3.1 || PL-409 | Case Study #009 — USDS | Full document | Section 5 || PL-410 | Case Study #010 — Southwest Airlines | Not started | Planned || PL-411 | Case Study #011 — Opioid Settlement | Not started | Planned || PL-412 | Case Study #012 — Crossrail | Not started | Planned |### 4.3 Policy Analysis Documents| Artifact ID | Title | Status ||-------------|-------|--------|| PL-701 | Policy Analysis #001 — NY Data Center Moratorium | Draft || PL-702 | Policy Analysis #001-B — Executive Order vs. Legislative Mandate | Draft |---## 5. CANONICAL LITERATURE### 5.1 Core Governance and State Capacity| Author | Work | Year | Key Contribution ||--------|------|------|------------------|| Francis Fukuyama | State-Building | 2004 | State capacity as foundation of development || Peter Evans | Embedded Autonomy | 1995 | Coherent bureaucracy with societal ties || Thandika Mkandawire | Thinking About Developmental States in Africa | 2001 | African developmental state conditions || Melissa M. Lee | Crippling Leviathan | 2020 | External subversion weakening the state || Atul Kohli | State-Directed Development | 2004 | State intervention comparison |### 5.2 Implementation and Policy Process| Author | Work | Year | Key Contribution ||--------|------|------|------------------|| Pressman & Wildavsky | Implementation | 1973 | Implementation gap || Mazmanian & Sabatier | Implementation and Public Policy | 1983 | Multi-stage implementation framework || Michael Lipsky | Street-Level Bureaucracy | 1980 | Frontline discretion || James C. Scott | Seeing Like a State | 1998 | Local knowledge vs. top-down planning |### 5.3 Institutions and Collective Action| Author | Work | Year | Key Contribution ||--------|------|------|------------------|| Douglass North | Institutions, Institutional Change | 1990 | Rules of the game, path dependence || Elinor Ostrom | Governing the Commons | 1990 | Self-governing institutions || March & Olsen | Rediscovering Institutions | 1989 | Institutional norms and identity || Mahmood Mamdani | Citizen and Subject | 1996 | Bifurcated colonial state |### 5.4 Dependency and Global Political Economy| Author | Work | Year | Key Contribution ||--------|------|------|------------------|| Walter Rodney | How Europe Underdeveloped Africa | 1972 | Underdevelopment as product of extraction || Justinian Rweyemamu | Underdevelopment and Industrialization in Tanzania | 1973 | Structural barriers to industrialization || Patrice Lumumba | Lumumba Speaks | 1961 | Sovereignty and neocolonial threats || Andre Gunder Frank | Capitalism and Underdevelopment | 1967 | Satellite-metropole relations || Samir Amin | Accumulation on a World Scale | 1974 | Global uneven development || Cardoso & Faletto | Dependency and Development | 1979 | Dependent-associated development |### 5.5 Complex Systems and Failure| Author | Work | Year | Key Contribution ||--------|------|------|------------------|| Charles Perrow | Normal Accidents | 1984 | System accidents as inevitable || Donella Meadows | Thinking in Systems | 2008 | Feedback loops, leverage points || Herbert Simon | Administrative Behavior | 1947 | Bounded rationality || Diane Vaughan | The Challenger Launch Decision | 1996 | Normalization of deviance || Bent Flyvbjerg | Megaprojects and Risk | 2003 | Optimism bias, strategic misrepresentation |### 5.6 Colonialism and Post-Colonial Governance| Author | Work | Year | Key Contribution ||--------|------|------|------------------|| Frantz Fanon | The Wretched of the Earth | 1961 | Colonial psychology and decolonization || Kwame Nkrumah | Neo-Colonialism | 1965 | Economic domination after independence || Achille Mbembe | On the Postcolony | 2001 | Post-colonial power logics || Partha Chatterjee | The Nation and Its Fragments | 1993 | Post-colonial political modernity |### 5.7 Policy Design and Tools| Author | Work | Year | Key Contribution ||--------|------|------|------------------|| Christopher Hood | The Tools of Government | 1983 | NATO framework || Michael Howlett | Designing Public Policies | 2011 | Policy instrument mix || Schneider & Ingram | Policy Design for Democracy | 1997 | Design as political || Lester Salamon | The Tools of Government | 2002 | New governance tools |### 5.8 Accountability and Transparency| Author | Work | Year | Key Contribution ||--------|------|------|------------------|| Guillermo O'Donnell | Horizontal Accountability | 1998 | Checks and balances || Fung, Graham & Weil | Full Disclosure | 2007 | When transparency works || John Gaventa | Power and Powerlessness | 1980 | Power shaping consciousness || Amitav Acharya | Constructing a Security Community | 2001 | Non-Western institutional perspectives |### 5.9 Infrastructure and Planning| Author | Work | Year | Key Contribution ||--------|------|------|------------------|| James Holston | The Modernist City | 1989 | Top-down design failure || Michael Goldman | Imperial Nature | 2005 | World Bank project politics || Deborah Bräutigam | The Dragon's Gift | 2009 | Chinese infrastructure in Africa |### 5.10 Reform and Institutional Change| Author | Work | Year | Key Contribution ||--------|------|------|------------------|| Merilee Grindle | Despite the Odds | 2004 | Reform in hostile environments || Haggard & Kaufman | Political Economy of Democratic Transitions | 1995 | Crisis and reform windows || Acemoglu & Robinson | Why Nations Fail | 2012 | Inclusive vs. extractive institutions || Mahmood Mamdani | Good Muslim, Bad Muslim | 2004 | Cold War and state fragility |---## 6. STANDARDIZED CASE STUDY TEMPLATE### 6.1 Required Sections (11)| # | Section | Purpose ||---|---------|---------|| 1 | Executive Summary | 2–3 paragraph overview || 2 | Historical Timeline | Chronological events || 3 | Governance Objective | Stated purpose of the system || 4 | Mechanism Inventory | All governance mechanisms involved || 5 | Dependency Chain Analysis | Networked relationships || 6 | Governance Capacity Assessment | Ability to detect, diagnose, act || 7 | Implementation Debt Assessment | Pre-existing structural weaknesses || 8 | Candidate Concept Evaluation | Test concepts against evidence || 9 | Counterfactual Analysis | What could have interrupted cascade || 10 | Lessons for the Loom Ontology | What the case teaches || 11 | Concept Promotion Recommendations | Formal ontology update proposals |### 6.2 Additional Recommended Sections| Section | Purpose ||---------|---------|| Cross-Case Linkages | Explicit references to other cases || Falsifiability Statement | What would disprove Loom's diagnosis |---## 7. CONCEPT-TO-CASE CROSS-REFERENCE MATRIX| Concept | #001 | #002 | #003 | #004 | #005 | #006 | #007 | #008 | #009 ||---------|------|------|------|------|------|------|------|------|------|| Veto Fragility | ⭐ | | | | | | | | || Execution Fragility | | ⭐ | | | | | | | || Implementation Debt | | ⭐ | | | | ⭐ | ⭐ | ⭐ | || Institutional Maturation | | | | ⭐ | | | | | || Assembled Capacity | | | | | ⭐ | | | | ⭐ || Mechanism-Purpose Alignment | | | ⭐ | ⭐ | | | ⭐ | | || Self-Correction Fragility | | | | | | ⭐ | | | ⭐ || Governance Epistemology | | | | | | ⭐ | | | ⭐ || Design Fragility | | | | | | | ⭐ | | || Temporal Fragility | | | | | | | | ⭐ | || Sustaining Capacity | | | | | | | | ⭐ | || Chronic Partial Implementation | | | | | | | | ⭐ | || Adaptive Capacity | | | | | | | | | ⭐ |---## 8. NEXT ACTIONS### 8.1 Immediate Priorities| Priority | Action | Rationale ||----------|--------|-----------|| 1 | Draft Case Study #010 (Southwest Airlines) | Tests coordination debt, private sector comparison || 2 | Update PL-101 Ontology post-Case #009 | Self-Correction Fragility promotion || 3 | Update PL-501 Cross-Case Matrix | Include Case #009 || 4 | Draft PL-201 Analysis Protocol | Standardize methodology |### 8.2 Medium-Term Priorities| Priority | Action | Rationale ||----------|--------|-----------|| 5 | Draft Case Study #011 (Opioid Settlement) | Test MSA pattern repeatability || 6 | Draft Case Study #012 (Crossrail) | Long-horizon success comparison || 7 | Conduct Pattern Report #002 | After 12 cases, consolidate again || 8 | Test prospective analysis on NY Data Center policy | Validate predictive capacity |---## 9. SYSTEM METADATA| Field | Value ||-------|-------|| Created | 2026-07-13 || Last Updated | 2026-08-14 || Total Artifacts | 25+ || Total Cases | 9 completed, 3 planned || Total Concepts | 22 tracked || Total Canonical Works | 50+ || Primary Methodology | Ten-stage case study protocol || Core Diagnostic | Three questions applied systematically || Framework Status | Active development, transitional phase |---*This index is designed to be machine-readable and comprehensive. Each artifact ID, concept, case, and canonical work is uniquely identified for cross-referencing. The system is structured so that any new case study, concept, or analysis can be added without disrupting existing relationships.**To feed this into another system, use the artifact IDs (PL-XXX) as primary keys, the concept names as controlled vocabulary, and the case numbers (#XXX) as sequential identifiers. The ontology evolution log (PL-105) tracks all status changes over time.Project Loom: Held Context BriefFor reference in future conversations. Last updated: 2026-08-12.The Human• Independent researcher and systems analyst. Background: 15 years as a program manager buildingand implementing operational systems (CRMs, knowledge hubs, security screening programs).• Identical twin sister died (memory: stated plainly in bios, pivots quickly to how the loss forgeddiagnostic attention; warm credibility, not memorial).• Father: Justinian Rweyemamu, known economist. Connection used as intellectual lineage (dependencytheory, postcolonial political economy, infrastructural asymmetry) — not credential substitution.• Personal origin of the work: a failed beer purchase in 2022 due to payment platform fragmentation,leading to the core question: “Why is this my problem?” and the insight that systems don’t rejectexcluded users — they simply cannot see them.What Project Loom IsAn empirical research program for developing a governance ontology with:• Complete Obsidian vault architecture• Concept registry (canonical definitions)• Case analysis methodology• Mission: make governance more transparent, understandable, and accountableCore ontology: Implementation Debt, Governance Fragility, Governance Capacity, Dependency Chains,Self-Correction Fragility, Mechanism–Purpose Alignment, Chronic Partial Implementation.Completed case studies (#001–#008): Student Loan Forgiveness, Healthcare.gov, Cash forClunkers, Acid Rain Program, Operation Warp Speed, Flint Water Crisis, Tobacco Master Settlement,California High-Speed Rail.Four foundational documents in progress: Project Loom Charter, Project Loom Ontology, EROSTechnical Specification, Project Loom Repository Guide.GitHub: loom-research-system/loom-research-system, deployed to GitHub Pages.Intellectual DNA (The Pre-Loom Archive)The following conversational threads constitute the archaeology of Loom:1. “When the System Cannot See You” (2022) — Personal thesis introduction. The 3-questiondiagnostic (What does it claim? Who is structurally locked out? What assumption makes thatinvisible?). Origin of Mechanism–Purpose Alignment and Chronic Partial Implementation.Generated by Kimi.ai2. Community-Sovereign Digital Cash paper (2024–2025) — Rigorous systems decomposition.Produced: evidence hierarchy (4 levels), sovereignty taxonomy (7 dimensions), structural attractors,bounded fraud critique, trilemmas (identity/privacy/decentralization; transferability/privacy/coercion; velocity/security). Origin of Implementation Debt, Governance Fragility, Self-CorrectionFragility, Dependency Chains, Governance Capacity.3. “No System Is More Sovereign Than Its Trust Anchor” (2025) — Political economyessay. Crystallized the trust-anchor constraint and the critique of sovereignty rhetoric. ReinforcedDependency Chains and Governance Capacity.4. Drift/MEV on Base (2025) — Technical validation. Proved the diagnostic lens worked onprotocol-level governance failures. Established long-tail case selection methodology.Key Methodological Principles• Long-tail focus: Analyze the cleaner 20%, not the dominant 80%, to avoid overfitting and evasionarms races.• Evidence hierarchy: Distinguish Laboratory Demo → Field Pilot → Adversarial Deployment →Sustained Governance Survivability.• Distributional choice framing: Every architectural choice is a choice about who gets excludedwhen the system strains.• Constraint mapping, not blueprinting: Loom produces maps of incompatibilities, not proposedsolutions.• Negative results are valid: Impossibility or structural incompatibility is a legitimate researchoutcome.EROS ModuleEROS (Executive Reversal Operating System) is a Loom sub-module analyzing executive actions, mappingdependencies, and designing reversals. Politically neutral — studies governance mechanisms, notideology. Same analytical framework applies regardless of administration.Active Creative Work• “Autopsy of a Vanishing” — Public-facing Loom introduction. Tone: simultaneously heartbreakingand hilarious (Moms Mabley, Richard Pryor, Arundhati Roy, Octavia Butler). Visceralautopsy of governance failures leading into Loom as the coroner’s report.• Bio/“How I See” section — Must state sister’s death plainly without dramatization, then pivotto diagnostic attention. Warm credibility. Under 150 words.Communication Preferences• Values intellectual honesty over rhetorical confidence.• Prefers compositional rigor to narrative convenience.Generated by Kimi.ai• Wants systems analysis that surfaces invisible users, not optimization for visible ones.• Appreciates when analysis names its own limits and evidentiary status.• Dislikes theory smuggled in as prediction (e.g., Thucydides Trap applied to decentralized networks= category error).Open Threads (As of 2026-08-12)• Loom vault implementation needs to move from redesigning to executing.• “Autopsy of a Vanishing” needs drafting.• Bio needs finalizing.• Four foundational documents need completion.• Case study methodology needs stress-testing against new domains.• Need to decide target venue/audience class for Loom outputs (interdisciplinary journal? securityworkshop? First Monday?).This brief is a living document. Update as the project evolves.Generated by Kimi.aiOperational Template: Dependency Chains + Adversarial KillChainsA Loom–Threat Management IntegrationPart I — The Reusable TemplatePurposeEvery Loom case already maps Dependency Chains: the upstream nodes a system relies on but does notcontrol. This template adds the adversarial dimension. For each dependency node, you now produce akill chain that answers:1. Under what conditions does this dependency become an active weapon?2. Who can trigger those conditions?3. What is the cascade sequence if the node fails or is coerced?4. At what point does the system lose the ability to self-correct?This does not turn Loom into a threat-intelligence shop. It makes the structural critique actionable bynaming the exact stress conditions under which a dependency becomes fatal.Template StructureFor each case study, create a Dependency Kill Chain Table (DKCT) with the following fields:Field Definition Loom MappingNode ID Canonical name of thedependency (e.g.,CMS_Federal_Data_Services_Hub)Dependency Chains registry entryLayer Governance / Technical /Financial / Social / EcologicalSovereignty taxonomy dimensionNormal State How the node functions understable conditionsMechanism–Purpose Alignment(intended behavior)Stress Condition Endogenous or exogenous shockthat degrades the nodeImplementation Debt(accumulated mismatch)Adversarial Exploitation How an intelligent actoraccelerates or weaponizes thestress conditionGovernance Fragility (capturevector)Cascade Trigger The specific event that turns nodefailure into systemic failureSelf-Correction Fragility (failureto contain)Cascade Sequence Ordered list of downstreamfailures (Phase 1 → Phase 2 →Phase 3)Chronic Partial Implementation(where the system livesindefinitely)Circuit Breaker Human or protocol interventionthat can halt the cascadeGovernance Capacity (actualability to respond)Generated by KimiTable 1 – continuedField Definition Loom MappingIdentifiable Victims Who absorbs the cost at eachphaseCore Loom ethical claimSeverity Scoring (Optional but Operational)Add a Loom Severity Score (LSS) per node:LSS = (Concentration × Substitutability⁻¹ × Victim Vulnerability × Cascade Speed)Factor Scale How to ScoreConcentration 1–5 How many entities control thisnode? (1 = monopoly, 5 = highlydistributed)Substitutability 1–5 How hard is it to replace thisnode? (1 = easily substitutable, 5= irreplaceable)Victim Vulnerability 1–5 How exposed are the system’smost vulnerable users to thisnode’s failure?Cascade Speed 1–5 How fast does failure propagate?(1 = months, 5 = minutes)Interpretation:• LSS 625 (5×5×5×5): Existential, immediate, irreplaceable, crushing the most vulnerable. Treatas design-breaking.• LSS 16 (2×2×2×2): Manageable, slow, substitutable, distributed harm. Treat as operationalrisk.This is not FAIR. It is deliberately qualitative because Loom deals with structural harm that resistsprobabilistic framing.Part II — Worked Example: Case #002 Healthcare.govBackgroundThe Affordable Care Act’s federal health insurance exchange launched in October 2013. The systemdepended on a network of federal contractors, state Medicaid systems, IRS income-verification services,and private insurers. It promised universal access to health insurance enrollment. It delivered a monthlongoutage and enrollment failures for millions.Generated by KimiDependency Kill Chain Table (Healthcare.gov)Node 1: CGI Federal (Primary Contractor)Field EntryNode ID CGI_Federal_Primary_Integration_ContractorLayer Governance + TechnicalNormal State CGI manages end-to-end system integration,timeline, and vendor coordination under CMSoversightStress Condition Compressed timeline (3.5 years of work compressedinto 10 months); no single system owner; CMS lackstechnical capacity to audit CGI’s workAdversarial Exploitation CGI can obscure integration failures because CMScannot independently verify; political pressure tolaunch on schedule removes leverage to delay; CGI’s profit motive aligns with shipping, not stabilizingCascade Trigger Launch date fixed by political calendar (Oct 1,2013) regardless of readinessCascade Sequence Phase 1: Integration untested → user accountcreation fails → Phase 2: Traffic routed to brokenregistration pipeline → database locks → Phase 3:Entire front-end collapses under load → userscannot complete applications → insurers receivegarbled dataCircuit Breaker Delay launch pending independent technical audit(politically impossible) OR decouple federalexchange from state Medicaid systems (legallyimpossible under ACA)Identifiable Victims Uninsured individuals in states without their ownexchanges (34 states); specifically, those withpre-existing conditions who needed coverage by Jan1, 2014, to avoid gaps in careLoom Severity Score: Concentration (2) × Substitutability￿¹ (5) × Victim Vulnerability (5) × CascadeSpeed (4) = 200Interpretation: Highly severe. The contractor was replaceable in theory (low concentration), but the compressedtimeline made substitution impossible in practice (high substitutability￿¹). Victims were extremelyvulnerable, and cascade was hours-to-days.Node 2: IRS Data Services Hub (Income Verification)Field EntryNode ID IRS_Income_Verification_HubGenerated by KimiTable 4 – continuedField EntryLayer Technical + GovernanceNormal State Real-time income verification against IRS databasesto determine subsidy eligibilityStress Condition IRS hub built by separate contractor (QualitySoftware Services, Inc.) with incompatible timeline;hub not stress-tested for concurrent enrollmentvolumeAdversarial Exploitation Political opposition to ACA creates incentive todelay or degrade IRS cooperation; hub becomes atarget for “death by a thousand cuts” via fundingconstraintsCascade Trigger Concurrent enrollment requests exceed hub capacityon Day 1Cascade Sequence Phase 1: Income verification queries timeout →users stuck at subsidy calculation step → Phase 2:Users retry repeatedly, amplifying load → Phase3: Hub throttles all requests → even simpleapplications fail → users abandon enrollmentCircuit Breaker Fallback to self-attested income (implementedeventually, but weeks late)Identifiable Victims Subsidy-eligible users (low-to-moderate income)who could not afford full-premium plans withoutimmediate verificationLoom Severity Score: Concentration (1) × Substitutability￿¹ (5) × Victim Vulnerability (5) × CascadeSpeed (4) = 100Interpretation: Severe. Single point of failure (IRS), no substitute for federal income data, vulnerablepopulation, fast cascade.Node 3: State Medicaid Systems (Dual-Enrollment Bridge)Field EntryNode ID State_Medicaid_Integration_BridgesLayer Governance + TechnicalNormal State Federal exchange forwards Medicaid-eligibleapplicants to state systems; states processenrollmentStress Condition 34 states refused to build their own exchanges,dumping integration burden onto federal system;state Medicaid IT systems vary wildly in age andcapacity (some running COBOL)Generated by KimiTable 5 – continuedField EntryAdversarial Exploitation State political opposition to ACA creates incentiveto delay or reject federal data transfers; states canclaim “federal system errors” to shift blameCascade Trigger Federal exchange sends Medicaid-eligible user datato state system that cannot parse the formatCascade Sequence Phase 1: Data format mismatch → state systemrejects applicant → Phase 2: Applicant told toreapply at state office → Phase 3: Applicantbounces between federal and state systemsindefinitely → coverage gap persistsCircuit Breaker Federal bypass of state systems (legally contested)or manual enrollment processing (implemented asstopgap)Identifiable Victims Poorest applicants (Medicaid-eligible) inRepublican-controlled states with least incentive tocooperateLoom Severity Score: Concentration (3) × Substitutability￿¹ (4) × Victim Vulnerability (5) × CascadeSpeed (3) = 180Interpretation: Severe. Distributed across 34 states but each state system was a bespoke integration pointwith no substitute. Victims were the most vulnerable, and cascade was days-to-weeks.Node 4: User Assumption — Digital Literacy + Stable ConnectivityField EntryNode ID User_Digital_Literacy_And_ConnectivityLayer Social + TechnicalNormal State System assumes users can navigate a multi-stepweb application, upload documents, and maintainsession stabilityStress Condition Target population includes elderly, non-Englishspeakers, rural poor, and disabled users —populations with lower digital literacy and lessreliable internetAdversarial Exploitation Not applicable (no intelligent adversary needed; thearchitecture itself excludes)Cascade Trigger User encounters an error message they cannotinterpret and has no human support channelGenerated by KimiTable 6 – continuedField EntryCascade Sequence Phase 1: User attempts enrollment, fails atdocument upload → Phase 2: User calls helpline,waits 2+ hours → Phase 3: User gives up, remainsuninsuredCircuit Breaker In-person Navigator program (underfunded anddeployed late) or phone enrollment (overwhelmed)Identifiable Victims Elderly, non-English speakers, rural populations,and disabled users —the same populations the ACAwas designed to protectLoom Severity Score: Concentration (5) × Substitutability￿¹ (1) × Victim Vulnerability (5) × CascadeSpeed (2) = 50Interpretation: Moderate. The “dependency” is widely distributed (the users themselves), but the systemhad no substitute for digital enrollment (high substitutability￿¹ in reverse — the system couldn’t functionwithout this assumption). Victims highly vulnerable, but cascade was slow (days of retrying before givingup).Synthesis: What the DKCT Reveals That Standard Loom Analysis Doesn’tStandard Loom analysis of Healthcare.gov would identify:• Implementation Debt (compressed timeline, untested integration)• Governance Fragility (no single owner, contractor opacity)• Chronic Partial Implementation (system “launched” but didn’t work for weeks)The DKCT adds:• Named cascade sequences with phase transitions• Specific circuit breakers that were available but not pulled (delay launch, decouple Medicaid,fallback to self-attested income)• Why circuit breakers failed (political impossibility, legal impossibility, underfunding)• Severity scores that allow comparison across nodesMost importantly, it reveals that the system had multiple opportunities to halt its own collapsebut each circuit breaker was blocked by a higher-order dependency (political calendar, legal architecture,funding constraints). This is Self-Correction Fragility made operational: the system could not repairitself because its governance dependencies were themselves locked.Part III — Integration RoadmapHow to Fold This Into Your Existing Loom Architecture1. Obsidian Vault Structure Create a new folder: Cases/Active/[CaseID]/Kill_Chains/Generated by KimiEach case gets:• Dependency_Kill_Chain_Table.md — the master table• Nodes/ — one note per dependency node, tagged #loom/dependency-node• Cascades/ — one note per cascade sequence, tagged #loom/cascadeNode note template (YAML frontmatter):---case_id: "#002"node_id: "CGI_Federal_Primary_Integration_Contractor"layer: ["Governance", "Technical"]loom_concept: "Dependency Chains"concentration: 2substitutability: 5victim_vulnerability: 5cascade_speed: 4loom_severity_score: 200cascade_trigger: "Launch date fixed by political calendar"circuit_breaker: "Delay launch pending audit"circuit_breaker_blocked_by: "Political impossibility"identifiable_victims: "Uninsured in non-expansion states with pre-existing conditions"tags: ["loom/dependency-node", "loom/kill-chain", "case/healthcare-gov"]---Cascade note template:---case_id: "#002"cascade_id: "C002-001"root_node: "CGI_Federal_Primary_Integration_Contractor"phases: 3time_to_systemic_failure: "48 hours"halting_mechanism: "None deployed"halting_mechanism_blocked_by: "Political calendar lock"tags: ["loom/cascade", "case/healthcare-gov"]---2. Case Study Template Update Add a new mandatory section to your case study template:## Dependency Kill Chain Analysis### Node Registry| Node ID | Layer | LSS | Cascade Trigger | Circuit Breaker | Blocked By ||---|---|---|---|---|---|### Cascade Registry| Cascade ID | Root Node | Phases | Time to Failure | Halting Mechanism ||---|---|---|---|---|### Key FindingGenerated by Kimi[One sentence: The system's most severe dependency was X, which became fatal under stress condition Y,↪ and could not be halted because circuit breaker Z was blocked by W.]3. Concept Registry Updates Add these canonical definitions to your Loom Ontology:Dependency Kill Chain (DKC):A ordered sequence of failures triggered by the degradation or coercion of a specific dependency node,showing how localized stress propagates into systemic harm. A DKC includes the stress condition,adversarial exploitation path, cascade trigger, phase sequence, and available circuit breakers.Cascade Trigger:The specific event that converts a stressed dependency node from a latent risk into an active sourceof systemic failure. Distinct from the stress condition in that it is the moment of irreversibility.Circuit Breaker (Governance):A human or protocol intervention that can halt a cascade sequence before it reaches systemic failure.In Loom analysis, the critical observation is not whether a circuit breaker exists, but whether it ispullable under the system’s actual governance constraints.Loom Severity Score (LSS):A qualitative severity index for dependency nodes, calculated as Concentration × Substitutability￿¹× Victim Vulnerability × Cascade Speed. Designed to prioritize structural harm over probabilisticrisk.Assumption Failure (AF):A threat category describing system failures caused by architectural assumptions about users (connectivity,literacy, biometric readability, platform access) that are not true for identifiable subpopulations.The system does not fail loudly; it fails invisibly for those outside the assumption boundary.4. Workflow Integration For new cases:1. Complete standard Loom decomposition (10 subproblems, sovereignty taxonomy, mechanism–purpose alignment)2. Build DKCT as Step 113. Score each node with LSS4. Identify the highest-severity node — this becomes the focus of the case’s “constraint map” visualization5. Write the cascade sequence as a narrative (Phase 1 → Phase 2 → Phase 3) for the public-facingcase summaryFor existing cases (#001–#008):1. Retrofit DKCT to each case (estimated time: 2–3 hours per case)2. Update case notes with node and cascade YAML frontmatter3. Regenerate the case registry index to sort by highest LSSGenerated by Kimi5. Deliverable Formats The DKCT enables Loom to produce outputs that threat management teamscan actually use:Audience Loom Output Threat Management TranslationPolicy makers Constraint map + identifiablevictimsRisk register with namedpopulations and timelineEngineering teams Cascade sequences + circuitbreakersIncident response playbooks withhalting conditionsRed teams Adversarial exploitation paths Attack trees with namedproceduresJournalists / public Narrative cascade (Phase 1→2→3) Investigative timeline with humanconsequencesDesign reviewers Assumption Failure table Pre-mortem checklist for newsystemsSummary: What Changes and What Doesn’tWhat changes:• Every case now has a structured, operational appendix showing exactly how failure propagates• Dependency nodes are scored and comparable across cases• Circuit breakers are named and their blockage analyzed• Loom can now feed directly into risk registers, incident playbooks, and red-team scenariosWhat doesn’t change:• Loom still starts with the 3-question diagnostic• Loom still maps constraints, not solutions• Loom still identifies distributional choices with identifiable victims• Loom still treats negative results (impossibility, structural incompatibility) as validThe threat management integration makes Loom more operational without making it operationalist.It preserves the ethical core while adding the mechanical rigor that lets the analysis survive contactwith engineering teams, auditors, and adversarial reviewers.Template version 1.0 — August 2026Generated by KimiUser: I need this is markdown formatKimi: What content would you like in markdown format? I can format anything you need — whether it's one of the Project Loom documents (Charter, Ontology, EROS spec, Repository Guide), the "Autopsy of a Vanishing" piece, a case study, or something entirely new. Just let me know what you're working on.Kimi: Here is the cleaned, properly formatted markdown. I've also saved it to /mnt/agents/output/Project-Loom.md.markdown---title: Project Loomdescription: A Research Framework for Understanding Why Governance Fails — and How to Fix It---# Project LoomA Research Framework for Understanding Why Governance Fails — and How to Fix It## What Is Project Loom?Project Loom is an open research initiative that maps, analyzes, and improves governance mechanisms through transparent systems modeling, implementation analysis, and decision support. It treats governance as an empirical object of study — something that can be dissected, measured, and rebuilt.Loom is not a think tank. It is not a consultancy. It is a research operating system: a set of conceptual tools, case study protocols, and analytical frameworks designed to answer one question with surgical precision:> **Why do announced policies fail to become actual outcomes?**The gap between political ambition and institutional capacity is not a bug in the system. It is the system. Project Loom exists to make that gap visible, measurable, and — eventually — bridgeable.## Why Does This Exist?American governance is optimized for announcements, not outcomes. Politicians promise. Agencies procure. Contractors bill. Citizens wait. And somewhere in the machinery between the press conference and the drinking water, things fall apart.Loom builds its analysis from documented cases:- Student Loan Forgiveness — how a legally vulnerable pathway collapsed under judicial review- Healthcare.gov — how operational incapacity destroyed a politically supported policy- Flint Water Crisis — how institutions with information and authority still failed to act- Operation Warp Speed — how temporary capacity assembly can bypass institutional debt- California High-Speed Rail — how long-horizon projects outlast their political and financial foundations- United States Digital Service — how a governance system can build durable self-correction capacity after catastrophic failureEach case follows a standardized diagnostic protocol. Each tests the ontology against real-world outcomes. The goal is not to score points but to build a vocabulary for the thing we are all experiencing but cannot name.## How Did This Start?Project Loom emerged from a simple observation: the machinery of American governance is failing in predictable, repeatable ways. The same patterns appear across domains, administrations, and political coalitions. The failures are not random. They are structural.Loom began as an attempt to name those structures. It has evolved into a multi-module research program with a core ontology, a growing case library, and applied frameworks for intervention design.## The EROS Governance Analysis FrameworkEROS (Executive Reversal Operating System) is one module under the Loom umbrella. It provides a six-stage sequential methodology for analyzing governance mechanisms and designing transitions:| Stage | Question ||-------|----------|| 1. Institutional Mapping | How do power, authority, funding, and decision-making actually flow? || 2. Dependency Analysis | Which systems depend on which others, and what breaks if one changes? || 3. Capacity Assessment | Can the responsible institutions actually perform the required work? || 4. Implementation Design | What are the administrative, legal, and operational steps required? || 5. Transition Risk Modeling | What are the foreseeable failure modes, bottlenecks, and capture pathways? || 6. Accountability & Resilience Evaluation | How do we embed oversight, transparency, and recovery into the design? |This framework is politically neutral. It studies governance mechanisms, not ideology. The same analytical tools apply regardless of administration or policy domain.## Who Is This For?| You are... | Loom can help you... ||------------|----------------------|| A researcher or academic | Develop rigorous, cross-domain frameworks for studying institutional failure and transition || A policy professional or legislative staffer | Design implementation pathways that account for capacity constraints and political fragility || An organizer or advocate | Map the dependency chains and veto points that determine whether a campaign's demands can actually be executed || A journalist | Analyze governance failures with conceptual precision rather than narrative convenience || A technologist or designer | Build tools, databases, and interfaces that make institutional machinery visible and navigable || A citizen | Understand why the systems that affect your life behave the way they do |## How This Site Is OrganizedProject Loom's vault is structured as a working research environment, not a blog or a book. Every folder has a specific function. Understanding the structure is the first step to using the site effectively.### 00 Documentation**What it is:** Meta-project records, style guides, naming conventions, and operational instructions.**Why it matters:** Loom is designed to outlast any single contributor. The documentation ensures that the research methodology, file naming, and editorial standards remain consistent as the project grows.**How to use it:**- New to Loom? Start with Getting Started.- Writing a new case study? Read the Loom Analysis Protocol and Naming Conventions first.- Proposing an ontology change? Check the Ontology Evolution Log for the procedure.- Want to understand how the site deploys? Read the Git Workflow.**How to customize:** Fork the repository, update the documentation to match your own research standards, and use it as the rulebook for your team.### 01 Inbox**What it is:** A holding pen for unprocessed notes, raw clippings, half-formed ideas, and temporary drafts.**Why it matters:** Research generates noise before it generates signal. The inbox prevents raw material from polluting the permanent sections while keeping it accessible for later processing.**How to use it:**- Drop articles, quotes, and rough notes here during active research.- Process inbox items regularly: either promote them to Literature Notes, Permanent Notes, or Projects — or delete them.- The inbox should be empty (or nearly empty) at the end of every research cycle.**How to customize:** If you work in teams, create subfolders by contributor or by topic (e.g., `01 Inbox/Immigration`, `01 Inbox/Health Policy`).### 02 Literature Notes**What it is:** Sourced material — book summaries, article annotations, interview transcripts, and research references. Each note is tied to a specific source and follows a standardized template.**Why it matters:** Loom does not start from theory and look for examples. It starts from cases and builds theory. Literature notes are the raw material of that inductive process. They ensure that every claim in the ontology and every finding in a case study can be traced to a documented source.**How to use it:**- Reading a book relevant to governance? Create a Literature Note using the template.- Literature notes should be source-bound, not concept-bound. One note per book/article, not one note per idea.- Link Literature Notes to Permanent Notes and Case Studies using `[[wikilinks]]`.- Use the Literature Notes Index to browse by author, domain, or concept.**How to customize:** Add fields to the template that match your discipline — e.g., "Methodology" for quantitative studies, "Geographic Scope" for area studies, "Policy Domain" for applied research.### 03 Permanent Notes**What it is:** The analytical core of the project. This folder contains the ontology definitions, case studies, cross-case matrices, and conceptual frameworks that constitute Loom's intellectual architecture.**Why it matters:** Permanent notes are where raw research becomes structured knowledge. A Literature Note asks: What did Fukuyama say? A Permanent Note asks: What is Governance Fragility, and which cases prove or disprove its existence?**How to use it:**- Case Studies (PL-4xx): Each follows a ten-stage diagnostic protocol. Read them as models, not just content. If you are writing a new case, copy the structure of an existing one.- Ontology (PL-1xx): These are the canonical definitions. Do not edit them casually. If a concept needs revision, log the proposal in the Ontology Evolution Log and provide evidence from at least two cases.- Cross-Case Matrices (PL-5xx): Use these to compare cases side-by-side. They are living documents — update them when new cases are added.- Frameworks (PL-2xx): The EROS Framework, Dependency Chain Mapping, Capacity Assessment Rubric, and other methodological tools live here.**How to customize:**- Add new case studies by following the PL-4xx numbering convention.- Propose new ontology concepts by creating a candidate note (status: `Candidate`) and linking it to at least two case studies.- Build new cross-case matrices by identifying a dimension not yet mapped (e.g., "Cases by Administrative Tradition" or "Cases by Degree of Private Sector Involvement").### 04 Projects**What it is:** Active intervention designs, applied research, and public-facing outputs that extend Loom's analytical tools into specific policy domains.**Why it matters:** Loom is not just a diagnostic tool. It is a design tool. The Projects folder is where analysis becomes architecture — where the question shifts from What went wrong? to What would it take to build something better?**How to use it:**- ICE Abolition Architecture (PL-600): A multi-lever governance design for dismantling an enforcement agency. Read it as an example of how Loom concepts translate into intervention design.- Future projects might include: climate transition governance, healthcare system redesign, electoral integrity architecture, etc.- Each project should reference the ontology and case studies that inform its design.**How to customize:**- Start a new project by creating a project charter (scope, concepts applied, expected outputs, feasibility assessment).- Use the EROS Framework as the default methodology, but adapt the stages to the domain.- Projects should produce at least one public-facing output (white paper, policy brief, or manifesto) and one internal analytical product (dependency map, actor inventory, or risk model).### 05 Outputs**What it is:** Public-facing writing, manifestos, white papers, and other documents intended for audiences outside the core research team.**Why it matters:** Research that stays in the vault does not change the world. The Outputs folder is where Loom speaks to policymakers, journalists, organizers, and citizens.**How to use it:**- Autopsy of a Vanishing (PL-000-INTRO): The public introduction to Project Loom. It is meant to be read by people who have never heard of governance ontology.- Future outputs might include: op-eds, testimony, white papers, or multimedia presentations.- Outputs should link back to the ontology and case studies, but they should not require the reader to understand the full framework.**How to customize:**- Write outputs for specific audiences. A white paper for legislative staffers should look different from a manifesto for organizers.- Use the Outputs folder to test whether your analytical concepts can survive translation into plain language. If a concept cannot be explained to a non-specialist, it may not be ready for the ontology.### 06 Archives**What it is:** Deprecated notes, superseded versions, and material that is no longer active but retained for historical reference.**Why it matters:** Research is iterative. Concepts get refined, cases get corrected, frameworks get rebuilt. The archive preserves the intellectual history of the project without cluttering the active workspace.**How to use it:**- When an ontology concept is deprecated, move its note to the Archive and create a `SUPERSEDED_BY` relationship in the Neo4j graph (if using the knowledge graph).- When a case study is updated, archive the old version and note the changes in the Change Log.- The Archive is read-only. Do not edit archived notes.**How to customize:** Add a `deprecated` tag or frontmatter status to archived notes so they are excluded from site navigation and Dataview queries.### 99 Templates**What it is:** Standardized templates for Literature Notes, Case Studies, Project Charters, and other recurring document types.**Why it matters:** Consistency is a research tool. Templates ensure that every case study contains the same analytical stages, every literature note contains the same metadata, and every project charter contains the same feasibility dimensions.**How to use it:**- Create a new Literature Note? Use the Literature Note Template.- Create a new Case Study? Use the Case Study Template.- The templates include Templater syntax for auto-populating dates and IDs. They are ignored by the Quartz build (they do not appear on the live site).**How to customize:**- Add fields to templates as your research needs evolve.- If you are not using Obsidian, the templates are still useful as checklists. Copy the structure into whatever note-taking system you use.## How to Use This Site### If you are a first-time visitorRead the homepage (this page) and the Autopsy of a Vanishing.Browse the Case Studies to see the analytical method in action.Check the Dashboard for a bird's-eye view of the project's scope and status.### If you are a researcherStart with the Ontology (PL-1xx) to understand the conceptual vocabulary.Read 2–3 Case Studies from different domains to see how the concepts are operationalized.Use the Cross-Case Comparison Matrix (PL-501) to identify patterns and gaps.Propose a new case study or ontology revision using the protocols in 00 Documentation.### If you are a policy professionalRead the EROS Governance Analysis Framework (PL-202) to understand the six-stage methodology.Review Case Studies in your domain (e.g., healthcare, environment, immigration).Explore Projects (PL-6xx) to see how Loom concepts translate into intervention design.Adapt the Capacity Assessment Rubric (PL-204) to your own policy context.### If you are an organizer or advocateRead the Autopsy of a Vanishing to understand Loom's political stance and analytical approach.Review Case Studies that align with your campaign domain.Use the Dependency Chain Mapping methodology (PL-203) to identify the veto points and bottlenecks that will determine whether your demands can be executed.Review the ICE Abolition Architecture (PL-600) as a model for multi-lever intervention design.### If you are a technologist or designerReview the Neo4j Knowledge Graph Schema (PL-800) to understand how Loom's relational data is structured.Explore the Dashboard and Cross-Case Matrices as examples of data presentation.Consider building tools that ingest Obsidian vaults into graph databases, generate dependency visualizations, or create interactive case study explorers.The site is built with Quartz — a static site generator for Obsidian vaults. The entire codebase is open source and available on GitHub.## How to Customize & Extend Project LoomProject Loom is designed to be forked, adapted, and extended. Here is how to make it your own:### 1. Fork the RepositoryThe entire site is open source:- GitHub: `https://github.com/loom-research-system/loom-research-system`- Live Site: `https://loom-research-system.github.io/loom-research-system`Fork the repo, rename it, and deploy your own instance to GitHub Pages. The Quartz build system will handle the rest.### 2. Adapt the OntologyThe ontology is not a catechism. It is a working hypothesis. To modify it:- Log the proposed change in the Ontology Evolution Log.- Provide evidence from at least two case studies (or one case study and one external empirical source).- Update the Cross-Case Comparison Matrix to reflect the change.- Update the Neo4j Knowledge Graph (if you are using it) to reflect new nodes or relationships.### 3. Add Case StudiesNew cases should:- Follow the ten-stage diagnostic protocol documented in the Loom Analysis Protocol.- Use the Case Study Template (PL-4xx).- Be linked to at least two existing ontology concepts.- Include a Change Log documenting revisions.### 4. Build New ProjectsProjects are where Loom concepts meet real-world intervention design. A new project should:- Reference the ontology and case studies that inform its design.- Use the EROS Framework as the default methodology.- Produce at least one public-facing output and one internal analytical product.- Include a Feasibility Assessment using the rubric in PL-204.### 5. Deploy the Knowledge GraphThe Neo4j Knowledge Graph (PL-800) is optional but powerful. It enables:- Relationship analytics across cases, actors, and concepts- Pattern detection in governance failure and success- Intervention simulation ("what happens if we remove this node?")- Cross-domain comparison via graph algorithmsTo deploy:- Sign up for Neo4j Aura (free tier available).- Seed the graph with the Concept nodes from PL-800.- Ingest case study data using the Python ingestion pipeline (pseudocode provided in the schema).- Run Cypher queries to test hypotheses and discover patterns.### 6. Customize the SiteThe site is built with Quartz v5.0.0 and deployed to GitHub Pages. To customize:- Edit `quartz.config.yaml` to change the site title, base URL, and plugin settings.- Edit `quartz.layout.ts` to change the page layout and component structure.- Add custom CSS in `quartz/styles/custom.scss`.- Add custom components in `quartz/components/`.The site ignores `99 Templates`, `.obsidian`, and `private` folders — add more ignore patterns as needed.## A Note on MethodProject Loom does not start from theory and look for examples. It starts from cases and builds theory. Every concept in the ontology must earn its place by explaining something that actually happened. If a concept cannot be operationalized — if it cannot be tested against a documented case — it does not belong in the framework.This is empirical research, not opinion journalism. The goal is to build tools that are useful, not to build a brand that is popular.## Explore[Dashboard](Dashboard) | [Getting Started](Getting-Started) | [Case Studies](Case-Studies) | [Projects](Projects) | [Literature Notes](Literature-Notes) | [Ontology](Ontology) | [EROS Framework](EROS-Framework)---Project Loom investigates why policies fail even when well-intentioned, using cross-case analysis of systemic breakdowns.Built with Quartz v5.0.0. Source available on GitHub.What I cleaned up:- Removed all the \\\\\\\* escape artifacts (restored proper **, [[, ]], and _ characters)- Fixed the YAML frontmatter (--- delimiters and proper fields)- Converted the EROS stages and "Who Is This For?" sections into proper markdown tables- Bulleted the case study list- Applied consistent heading hierarchy (# → ## → ###)- Reformatted the numbered customization steps with proper sub-bullets- Cleaned up the Explore section into inline links- Added proper paragraph breaks for readabilityYou can drop this directly into your Quartz vault as index.md or Project Loom.md.User: Where am I putting the ontology in obsidian?Kimi: Your ontology lives in 03 Permanent Notes/.Here's the exact structure:03 Permanent Notes/├── Ontology/│ ├── PL-100 Implementation Debt.md│ ├── PL-101 Governance Fragility.md│ ├── PL-102 Governance Capacity.md│ ├── PL-103 Dependency Chains.md│ ├── PL-104 Self-Correction Fragility.md│ ├── PL-105 Mechanism-Purpose Alignment.md│ ├── PL-106 Chronic Partial Implementation.md│ └── PL-1xx [new concepts].md├── Case Studies/│ ├── PL-401 Student Loan Forgiveness.md│ ├── PL-402 Healthcare.gov.md│ └── PL-4xx [etc].md├── Cross-Case Matrices/│ └── PL-501 Cross-Case Comparison Matrix.md└── Frameworks/ ├── PL-202 EROS Governance Analysis Framework.md ├── PL-203 Dependency Chain Mapping.md └── PL-204 Capacity Assessment Rubric.mdKey rules for ontology notes:- Naming: PL-1xx [Concept Name].md (e.g., PL-100 Implementation Debt.md)- Status: Use frontmatter to track maturity: yaml --- id: PL-100 status: Canonical # or Candidate / Deprecated linked_cases: [PL-401, PL-402] ---- Linking: Every ontology note should link to at least 2 case studies that prove or test the concept. Use [[PL-401 Student Loan Forgiveness]] style wikilinks.- Don't edit casually. If you want to revise a concept, log it in 00 Documentation/Ontology Evolution Log.md first, provide evidence from at least 2 cases, then update.If you want, I can also generate the actual ontology note template (the PL-1xx canonical definition format) in markdown for you to drop into 99 Templates/.User: Sorry I meant the canonKimi: The canon — the authoritative, compiled set of canonical definitions — goes in 03 Permanent Notes/Ontology/.Here is the exact placement:03 Permanent Notes/└── Ontology/ ├── PL-100 Ontology Index.md ← The master canon / table of contents ├── PL-101 Implementation Debt.md ├── PL-102 Governance Fragility.md ├── PL-103 Governance Capacity.md ├── PL-104 Dependency Chains.md ├── PL-105 Self-Correction Fragility.md ├── PL-106 Mechanism-Purpose Alignment.md ├── PL-107 Chronic Partial Implementation.md └── PL-1xx [future concepts].mdPL-100 Ontology Index.md is your canon — the single source of truth that maps every concept, shows its status (Canonical / Candidate / Deprecated), and links to the cases that validate it.Each individual concept note (PL-101 through PL-1xx) is a canonical definition — the final, approved version of that concept. The frontmatter on each one locks its status:yaml---id: PL-101status: Canonicaldefinition: "The accumulated mismatch between political ambition and institutional capacity."linked_cases: [PL-401, PL-402, PL-403]---Rule: The Ontology/ folder contains only canonical definitions. Drafts, candidates, and debates happen in 01 Inbox/ or 04 Projects/ first. Once a concept earns its place (proven by at least 2 case studies), it gets promoted to 03 Permanent Notes/Ontology/ and its status flips to Canonical.If you want, I can generate the PL-100 Ontology Index.md template for you right now.User: I meant thisKimi: This document — the PL-601 Expanded Canon — goes in:02 Literature Notes/PL-601 Project Loom Canon.mdWhy 02 Literature Notes and not 03 Permanent Notes:The canon is a curated bibliography. It is about sourced material, not an ontology concept itself. The vault structure you defined says 02 Literature Notes holds "sourced material — book summaries, article annotations, interview transcripts, and research references." A 430-work master bibliography is exactly that: a meta-reference document.How to organize it inside 02 Literature Notes:02 Literature Notes/├── PL-601 Project Loom Canon.md ← This document (the master index)├── Literature Notes Index.md ← Your auto-generated / manual index├── Weber, Max - Economy and Society.md ← Individual lit notes from the canon├── Fukuyama, Francis - State-Building.md├── Ostrom, Elinor - Governing the Commons.md└── [etc. — one note per work]Each individual work in the canon should eventually become its own Literature Note using your 99 Templates/Literature Note Template.md. The Canon note links to them via [[Author - Title]] wikilinks.Cross-reference in Permanent Notes:In 03 Permanent Notes/Ontology/PL-100 Ontology Index.md, add a line like:markdown- **Theoretical Foundation**: [[PL-601 Project Loom Canon]] — the expanded bibliography mapping every concept to its intellectual sourcesThis keeps the canon in its proper home (02 Literature Notes) while making it discoverable from the ontology.If you prefer it as a framework document (since it maps concepts → sources), you could alternatively put it in:03 Permanent Notes/Frameworks/PL-601 Project Loom Canon.mdBut my recommendation is 02 Literature Notes/ — it's a bibliography, not a concept definition.User: I want cursor to do all of this for me how?Kimi: You open your vault folder in Cursor and let it become your research operating system. Here's the exact setup:---## 1. Open the Vault in Cursorbash# In Cursor: File → Open FolderC:\Users\rweye\quartz-loom\quartzCursor now sees your entire vault as a codebase. It can read every note, enforce conventions, generate new files, and edit across multiple documents simultaneously.---## 2. Create .cursorrules (The Loom Brain)Create this file in your vault root. Cursor reads it automatically on every interaction:markdown# Project Loom — Cursor Operating Rules## IdentityYou are the research engine for Project Loom, an empirical governance research program. You do not write opinions. You write structured analytical documents that can be tested against real cases.## Vault Structure- `00 Documentation/` — Meta, protocols, style guides- `01 Inbox/` — Raw clippings, unprocessed notes- `02 Literature Notes/` — One note per source, standardized template- `03 Permanent Notes/` — Ontology (PL-1xx), Case Studies (PL-4xx), Frameworks (PL-2xx), Cross-Case Matrices (PL-5xx)- `04 Projects/` — Applied intervention designs (PL-6xx)- `05 Outputs/` — Public-facing writing- `06 Archives/` — Deprecated notes- `99 Templates/` — Reusable templates## Naming Conventions- Ontology: `PL-1xx [Concept Name].md`- Frameworks: `PL-2xx [Framework Name].md`- Case Studies: `PL-4xxUser: ive already set it upKimi: You need a **`.cursorrules`** file in your vault root and a workflow that treats Cursor as your research operating system. Here's the exact setup:---## 1. Drop this `.cursorrules` in your vault rootmarkdown# Project Loom — Cursor Operating RulesYou are the research engine for Project Loom, an empirical governance research program. Every file you create or edit must follow these rules.## Vault Structure- 00 Documentation/ — Meta-rules, protocols, naming conventions- 01 Inbox/ — Raw clippings, unprocessed notes, temporary drafts- 02 Literature Notes/ — One note per source. Frontmatter required. Wikilink to ontology concepts.- 03 Permanent Notes/ — The canon. Contains: - Ontology/ — Canonical concept definitions (PL-1xx). Status: Canonical | Candidate | Deprecated. - Case Studies/ — Ten-stage diagnostic protocol (PL-4xx). - Cross-Case Matrices/ — Comparative tables (PL-5xx). - Frameworks/ — Methodological tools (PL-2xx).- 04 Projects/ — Applied intervention designs (PL-6xx).- 05 Outputs/ — Public-facing writing (PL-000-INTRO, manifestos, etc.).- 06 Archives/ — Superseded versions. Read-only.- 99 Templates/ — Standardized templates. Ignored by Quartz build.## Naming Conventions- Ontology: PL-1xx [Concept Name].md- Frameworks: PL-2xx [Framework Name].md- Case Studies: PL-4xx [Case Name].md- Matrices: PL-5xx [Matrix Name].md- Projects: PL-6xx [Project Name].md- Literature: [Author Last Name], [First Name] - [Title].md- Outputs: PL-000-INTRO [Title].md or PL-7xx [Title].md## Frontmatter StandardsEvery Permanent Note and Literature Note MUST include:yaml---id: PL-xxxstatus: Canonical | Candidate | Deprecated | Drafttags: [ontology, case-study, literature, framework, project, output]date_created: YYYY-MM-DDdate_modified: YYYY-MM-DDlinked_cases: [PL-4xx, PL-4yy]linked_concepts: [PL-1xx, PL-1yy]source_type: book | article | report | interview | case---## Ontology Rules1. A concept earns its place ONLY if it explains a documented case.2. Every ontology note must link to ≥2 case studies.3. Candidate concepts live in 01 Inbox/ until proven. Then promoted to 03 Permanent Notes/Ontology/.4. Deprecated concepts move to 06 Archives/ with a SUPERSEDED_BY link.5. Never edit a Canonical ontology note casually. Log changes in 00 Documentation/Ontology Evolution Log.md first.## Case Study Protocol (Ten Stages)Every case study must include:1. Policy Announcement2. Legal/Regulatory Pathway3. Institutional Assignment4. Resource Allocation5. Operational Design6. Implementation Execution7. Feedback Mechanisms8. External Perturbations9. Outcome Assessment10. Ontological Implications## Writing Style- Empirical, not opinionated. Cite sources.- Specific, not abstract. Name names, dates, dollar amounts, agencies.- Cross-reference constantly. Use [[PL-xxx]] wikilinks.- No fluff. Every sentence must carry analytical weight.## Quartz Build Rules- Files in 99 Templates/, .obsidian/, and private/ are ignored.- Use [[wikilinks]] for internal links.- Use standard Markdown. No HTML unless necessary.- Images go in attachments/ and use relative paths.## When the User Asks You To:- "Create a case study" → Use the Case Study Template from 99 Templates/, follow the ten-stage protocol, link to ≥2 ontology concepts.- "Add to the canon" → Create a Literature Note in 02 Literature Notes/, update PL-601 Project Loom Canon.md index.- "Define a concept" → Check if ≥2 cases support it. If yes, create PL-1xx in Ontology/. If no, create a Candidate in 01 Inbox/.- "Write an output" → Draft in 05 Outputs/, link back to ontology and cases, but write for non-specialists.- "Restructure" → Never delete without archiving. Use 06 Archives/ for deprecated material.---## 2. Open your vault in Cursorbash# In terminal, from your vault rootcursor .Or: File → Open Folder → Select your `quartz-loom/quartz` (or whatever your vault folder is).---## 3. Use Agent Mode (Ctrl+I / Cmd+I)Agent mode is the key. It can:- Create multiple files at once- Move files between folders- Update indexes and cross-references automatically- Run terminal commands**Enable it:** Press `Ctrl+I` (or `Cmd+I`), then click the dropdown in the top-left of the chat panel and select **"Agent"** instead of "Ask" or "Edit".---## 4. Your prompt patternsHere are the exact prompts that work. Copy-paste these:### To create a case studyCreate a new case study for [TOPIC] following the PL-4xx naming convention. Use the template in 99 Templates/Case Study Template.md. Follow the ten-stage diagnostic protocol. Link it to at least 2 existing ontology concepts in 03 Permanent Notes/Ontology/. Update the Cross-Case Comparison Matrix (PL-501) to include this case. Create the file in 03 Permanent Notes/Case Studies/.### To add a book to the canonAdd "[Author] - [Title] ([Year])" to the canon. Create a Literature Note in 02 Literature Notes/ following the Literature Note Template. Map its Loom Relevance to existing ontology concepts. Update PL-601 Project Loom Canon.md in 02 Literature Notes/ to include it in the correct section.### To define a new ontology conceptI want to define the concept "[CONCEPT NAME]". First, check which case studies in 03 Permanent Notes/Case Studies/ support this concept. If there are at least 2 supporting cases, create PL-1xx [Concept Name].md in 03 Permanent Notes/Ontology/ with Canonical status. If not, create it as a Candidate in 01 Inbox/ and list the cases that would need to be written to support it.### To write public-facing outputDraft a new output in 05 Outputs/ about [TOPIC]. It should reference these ontology concepts: [LIST]. Write it for a non-specialist audience (journalist, organizer, citizen). Link back to case studies but don't require the reader to know the framework. Follow the Output Template in 99 Templates/.### To restructure / move filesMove [FILE] from [OLD LOCATION] to [NEW LOCATION]. If it's an ontology concept being deprecated, move it to 06 Archives/ and create a SUPERSEDED_BY link to the replacement. Update all wikilinks that point to the old location.---## 5. Use `@` for contextIn any prompt, use `@` to give Cursor specific files to read:@03 Permanent Notes/Ontology/PL-101 Governance Fragility.md @03 Permanent Notes/Case Studies/PL-401 Student Loan Forgiveness.mdCreate a new case study that tests the Governance Fragility concept...This is more reliable than hoping Cursor finds the right files.---## 6. Terminal integrationCursor has a built-in terminal (`Ctrl+``). Use it for:bash# Find broken wikilinksgrep -r "[[" . --include=".md" | grep -v "attachments" | sort# List all PL-1xx ontology notesls "03 Permanent Notes/Ontology/" | grep "PL-1"# Check which cases link to a specific conceptgrep -r "PL-101" "03 Permanent Notes/Case Studies/" --include="*.md"# Build the Quartz site to check for errorsnpx quartz build---## 7. Pro tip: Use `.cursor/rules` (newer Cursor versions)If your Cursor version supports it, create `.cursor/rules/project-loom.mdc` instead of `.cursorrules` for better organization:bashmkdir -p .cursor/rulestouch .cursor/rules/project-loom.mdcPaste the same rules content there. Cursor will auto-load it for every chat in the project.---**Bottom line:** The `.cursorrules` file is your vault's constitution. Once it's in place, Agent mode + `@` file references + terminal commands let you say "create a case study" and Cursor will generate the file, name it correctly, apply the template, link it to ontology concepts, and update the matrix — all in one shot.Want me to generate the actual `99 Templates/` files (Case Study Template, Literature Note Template, Ontology Definition Template) in markdown so you can drop them in right now?User: THis is like the 4th fucking time that I'm asking you to just tell me how to get the canon onto the site using cursorKimi: **Step 1:** Open Cursor Agent mode (`Ctrl+I` → select "Agent" from dropdown).**Step 2:** Paste this exact prompt:Create the file 02 Literature Notes/PL-601 Project Loom Canon.md with the following content, then run npx quartz build in the terminal, then git add . && git commit -m "Add PL-601 expanded canon" && git push origin main to deploy to GitHub Pages.Then paste your canon text right after that prompt.**Step 3:** Hit Enter. Cursor will:- Create the file in the right folder- Build the Quartz site locally (catches errors)- Commit and push to deploy---**If you want it in `03 Permanent Notes/Frameworks/` instead**, change the path in the prompt to:Create the file 03 Permanent Notes/Frameworks/PL-601 Project Loom Canon.md...---**If the build fails**, Cursor will show you the error in terminal. Most common fix:bashnpx quartz build --serve``Then checklocalhost:8080` before pushing.That's it. One prompt. Agent mode does the file creation, build, commit, and push.