Ablation Study
Record controlled with-factor and without-factor comparisons on a common evaluation corpus using one scorer contract per contrast.
Bundle → Layer → Finding → Questions Filled
6 bundles · 12 layers · 12 findings · 48 questions
Study charter and protocol Identify the study and preserve its declared intent.
Study identity
Proposed record obligations for study identity.
Study identity and accountable scope
One persistent study record binds its purpose and accountable role across protocol revisions. A run, report or reusable experimental recipe has a different identity.
- Which authoritative study identifier and revision distinguish this study from a rerun or replication? identity
- Which accountable study role owns the record and which evidence custodian maintains its references? ownership
- What precise factor contribution is being investigated on which target population? definition
- Is this a planned, exploratory or confirmatory study and how was that classification determined? classification
Protocol and revision
Proposed record obligations for protocol and revision.
Frozen comparison intent
A frozen protocol revision states intended contrasts, metrics and decision rules. Amendments remain visible and post-result choices cannot be relabelled as prespecified.
- When were hypotheses and analysis rules frozen relative to the first outcome inspection? temporal
- Which transitions move this study from design through execution, analysis and review to closure or withdrawal? lifecycle
- Which protocol amendments occurred and which comparisons must be repeated or reclassified? event
- Who may freeze or amend the protocol and what review is required for an outcome-informed change? authority
Interventions and controls Make arm changes and conditional comparison boundaries inspectable.
Factor intervention
Proposed record obligations for factor intervention.
With-factor and without-factor arms
Each contrast names a reference arm and an ablated arm. Removal, masking or replacement semantics are explicit; training-time changes and inference-time disabling answer different questions. Incidental changes limit attribution.
- Which component or configuration factor is removed, masked or replaced in each arm? composition
- Does the intervention require retraining or only alter inference and what remains fixed? process
- How is actual intervention compliance checked against intended arm configurations? validation
- What happens when removing the factor makes an arm non-executable or changes its interface? exception
Experimental controls
Proposed record obligations for experimental controls.
Confounders and interaction limits
The local design records nuisance variables, budget policy and blocks. A contrast at one background setting estimates only that conditional comparison; multiple removals do not automatically identify independent contributions.
- Which nuisance factors and execution budgets are controlled, blocked or left uncontrolled? constraint
- How are run order and repeat allocation determined within declared blocks? process
- Which other factor settings condition the contrast and which interactions are untested? relationship
- Could unequal tuning or resource allowances explain the observed difference? quality
Common evaluation contract Bind the shared corpus and scorer before admitting comparisons.
Corpus binding
Proposed record obligations for corpus binding.
Common evaluation cases and labels
Both arms reference the same frozen evaluation case set, split and label revision for a contrast. Input transformation may be the declared intervention while case identity remains stable. Membership drift and training overlap are recorded as threats.
- Which dataset revision, split and ordered or keyed case membership are common to both arms? identity
- Which label revision and preprocessing lineage support each evaluation case? provenance
- What checks identify leakage, duplicate cases or exposure during tuning and training? quality
- How are case omissions or label corrections handled without silently changing the paired cohort? exception
Scoring contract
Proposed record obligations for scoring contract.
One scorer definition per contrast
A contrast binds one scorer version, rubric, metric direction and aggregation rule across arms. A stochastic scorer needs its own repeat policy. Changing a scorer creates a new scoring revision for both arms.
- Which metric, units, preferred direction and aggregation define the comparison score? measurement
- Which harness, scorer code or rubric revision and configuration are shared by both arms? identity
- How are scorer randomness, blinding and order effects handled? constraint
- What evidence shows both arms were scored with the pinned scoring contract? validation
Execution evidence Connect actual attempts to complete, paired observations.
Run lineage
Proposed record obligations for run lineage.
Execution realization and repeats
Execution remains externally mastered. The study indexes arm assignments, run attempts, environment snapshots and repetition units, preserving differences between a retry, an independent repeat and a reanalysis.
- Which external training, inference and evaluation runs realize each arm and repeat? relationship
- Which environment, configuration, seed and dependency revisions were actually used? provenance
- When did each attempt start and end and which protocol revision governed it? temporal
- Which attempts are retries, independent repeats or rescoring of existing outputs? classification
Paired observations
Proposed record obligations for paired observations.
Complete outcomes and failures
Case and repeat keys join the two arms. Failures and absent results remain explicit; complete-case analysis must disclose exclusions and its population. A successful retry never overwrites a failed attempt.
- Which per-case or aggregate observations and missingness indicators back each arm score? evidence
- Do pair keys join one-to-one and how are duplicates, unmatched cases and nonfinite scores rejected? validation
- Which failures, timeouts and exclusions occurred and how do they affect the denominator? exception
- How are original attempts preserved when a retry or rescore produces a new observation? retention
Analysis and interpretation Keep estimates, uncertainty and conclusions distinguishable.
Effect estimation
Proposed record obligations for effect estimation.
Signed comparison and uncertainty
The proposed convention is delta = score_with_factor - score_without_factor. Metric direction controls interpretation. Uncertainty identifies its sampling unit and method; dataset-level test guidance is not automatically applicable to item-level observations.
- What signed difference and practical importance threshold are reported for each contrast? measurement
- Which variability sources and sampling units support the uncertainty estimate? quality
- Which interval or test procedure was selected and why are its assumptions appropriate? process
- How are undefined relative changes, insufficient repeats and non-estimable intervals represented? exception
Interpretation and robustness
Proposed record obligations for interpretation and robustness.
Bounded conclusions and multiplicity
The study separates observed differences from explanatory claims and deployment decisions. Multiple contrasts, metrics or selected slices require a disclosed analysis family and selection history; a null result alone does not establish equivalence.
- What conclusion is supported within this corpus, scorer and intervention setting? decision
- Which hypothesis family and stopping or selection rules bound multiplicity and selective reporting? constraint
- Which sensitivity checks assess exclusion, scoring or seed choices and where do conclusions change? quality
- What additional evidence is needed before claiming equivalence, causal isolation or wider generalization? requirement
Review and evidence governance Support review and controlled reuse of study evidence.
Review and release
Proposed record obligations for review and release.
Evidence-backed review disposition
A reviewer assesses the record and its limitations independently of execution status. Review can reject or qualify a conclusion. A local release records availability and reproducibility limits without certifying safety or external acceptance.
- Which qualified reviewer evaluated the contrast and what conflicts of interest were declared? authority
- What review disposition and unresolved issues apply to each reported claim? state
- Which evidence export profile and pinned mapping preserve links and disclose losses? interoperability
- Which released artifacts permit recomputation and which dependencies remain unavailable? evidence
Access and retention
Proposed record obligations for access and retention.
Controlled evidence custody
The proposed study policy separates public conclusions from restricted inputs and outputs. Disclosure, retention and disposal use local authority and rights checks. Dangerous evaluations are represented only by policy-level scope and oversight metadata.
- Who may view each bundle, layer, finding and artifact under the evidence access policy? access
- Which personal or sensitive content requires minimization or redaction before release? privacy
- Which retention schedule, preservation holds and disposal rules govern each evidence class? retention
- What authorization and audit trail govern access changes or restricted evaluation metadata? security
Classifiers Filled
- Family
- World Models
- Category
- Information and virtual systems
- Entry kind
- entity
- Navigation path
- NAV.INF.AI.ABL
- Domain
- INF.AI.ABL
- Industry
- Cross-industry
- Tags
- ablationstudyinf.ai.abl
What it is Filled
One persistent, versioned ablation study record owns its protocol, arm comparison intent, evidence references and bounded interpretations. Runs, datasets, scorer implementations and benchmark result masters remain external. This is a proposed research specification, not an executed experiment.
In scope
- Study identity, hypothesis, intervention arms and protocol revisions
- Common evaluation cases, scorer contract, controlled changes and deviations
- Run references, failures, paired observations, effect estimates and uncertainty
- Claim qualification, review, evidence access and retention
Out of scope
- Executing training, inference, scoring or deployment
- Mastering datasets, labels, model weights, scorer code or general benchmark leaderboards
- Universal causal identification, statistical test selection or safety certification
- Operational instructions for harmful evaluations
Why it exists Filled
Record controlled with-factor and without-factor comparisons on a common evaluation corpus using one scorer contract per contrast.
Distinguishing features Derived, awaiting review
- Unlike WM-AI-003 AI Model Evaluation: Registry parent is a conceptual specialization lead. The study adds controlled intervention contrasts; no unverified runtime inheritance or containment is asserted.
- Unlike WM-AI-004 AI Inference / Agent Run and WM-AI-006 Model Training / Fine-tuning Run: Execution attempts have separate masters. A study can exist before runs and may reference optional training runs when retraining is part of its intervention.
- Unlike WM-AI-009 Evaluation Dataset / Benchmark and WM-AI-014 Ground-truth Label Set: Frozen case and label references are used; dataset curation and label lifecycle are not owned here.
- Unlike WM-AI-011 Evaluation Harness and Scorer and WM-AI-012 Benchmark Result: Scorer definitions and result records remain external. The study owns the rationale for comparing arms, not the master scores or implementation.
- Unlike Reusable experiment design and factorial experiment: This root is an instantiated study record, not a design pattern. Multi-arm contrasts are allowed with declared settings; a single ablation cannot isolate all interactions.
Note: Derived from boundary notes against neighbouring models.
What robots and AI may and may not do Derived, awaiting review
Must not
- Never overwrite original observations with retries.
- Deny access unless owner policy grants a role and purpose at the relevant scope; public summaries do not imply public raw data.
May
- Register study intent: Proposed, unimplemented local operation: register study intent.
- Freeze comparison protocol: Proposed, unimplemented local operation: freeze comparison protocol.
- Link execution evidence: Proposed, unimplemented local operation: link execution evidence.
- Check contrast comparability: Proposed, unimplemented local operation: check contrast comparability.
- Record analysis and interpretation: Proposed, unimplemented local operation: record analysis and interpretation.
- Record review and release decision: Proposed, unimplemented local operation: record review and release decision.
Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.
Moral aspects Derived, awaiting review
- Restrict harmful evaluation details to policy-level purpose, authorization, oversight and disclosure decisions.
- Adopters must supply applicable evidence rights, privacy, ethics and retention rules.
- Operational instructions for harmful evaluations
Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.
Owners Filled
Steward
Accountable study steward role and delegated authority record.
Roles
- Study steward
- Own purpose, scope, protocol revisions and lifecycle decisions.
- Experiment operator
- Supply external run and configuration evidence without changing the frozen protocol.
- Analysis reviewer
- Assess pairing, assumptions, uncertainty and bounded claims; declare independence limits.
- Evidence custodian
- Enforce access, integrity, retention and disclosure rules.
- Release reviewer
- Review rights and unresolved holds before recording release eligibility.
Links to other meta-models Filled
aligned
- WM-AI-003 - Candidate conceptual specialization from registry parent; executable inheritance remains unverified.
- https://www.w3.org/TR/prov-o/ - Conceptual provenance mapping only; no implemented conformance claim.
- https://www.researchobject.org/ro-crate/specification/1.2/introduction.html - Optional evidence packaging profile; selected 1.2 must be pinned and mapped before use.
references
- WM-AI-009 - Candidate frozen evaluation corpus binding; required case identity is a study obligation, not a forced dependency on this package.
- WM-AI-011 - Candidate pinned scorer and harness definition; no scorer code is mastered here.
- WM-AI-012 - Candidate external result evidence for each arm or contrast.
- WM-AI-004 - Optional external inference run receipts indexed by arm and repeat.
- WM-AI-006 - Optional training run references for interventions involving retraining.
- WM-AI-014 - Optional label set revision when the evaluation uses ground truth.
neighbor
- WM-AI-003 AI Model Evaluation - Registry parent is a conceptual specialization lead. The study adds controlled intervention contrasts; no unverified runtime inheritance or containment is asserted.
- WM-AI-004 AI Inference / Agent Run and WM-AI-006 Model Training / Fine-tuning Run - Execution attempts have separate masters. A study can exist before runs and may reference optional training runs when retraining is part of its intervention.
- WM-AI-009 Evaluation Dataset / Benchmark and WM-AI-014 Ground-truth Label Set - Frozen case and label references are used; dataset curation and label lifecycle are not owned here.
- WM-AI-011 Evaluation Harness and Scorer and WM-AI-012 Benchmark Result - Scorer definitions and result records remain external. The study owns the rationale for comparing arms, not the master scores or implementation.
- Reusable experiment design and factorial experiment - This root is an instantiated study record, not a design pattern. Multi-arm contrasts are allowed with declared settings; a single ablation cannot isolate all interactions.
parent
- WM-AI-003
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Filled
- Authoritative master-system identifier in its namespace.
- Stable owner-scoped identifier or UUID when no master identifier exists.
- Content hash for integrity and deduplication, not a substitute for logical identity.
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Filled
- Register study intent: Proposed, unimplemented local operation: register study intent.
- Freeze comparison protocol: Proposed, unimplemented local operation: freeze comparison protocol.
- Link execution evidence: Proposed, unimplemented local operation: link execution evidence.
- Check contrast comparability: Proposed, unimplemented local operation: check contrast comparability.
- Record analysis and interpretation: Proposed, unimplemented local operation: record analysis and interpretation.
- Record review and release decision: Proposed, unimplemented local operation: record review and release decision.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- PROV-O: The PROV Ontology
Context of use required Filled
- No jurisdiction or sector is assumed. Adopters must supply applicable evidence rights, privacy, ethics and retention rules.
- English conceptual draft; no localization or legal compliance claim.
Sources Filled
- One variable at a time - NIST
- Two-Sample t-Test for Equal Means - NIST
- How do you select an experimental design? - NIST
- Randomized block designs - NIST
- PROV-O: The PROV Ontology - W3C
- RO-Crate 1.2 Introduction - RO-Crate community
- Statistical Comparisons of Classifiers over Multiple Data Sets - Janez Demsar, research author
- NeurIPS Paper Checklist Guidelines - NeurIPS research community
Open questions
- Complete direct source checks and selected-version verification, review the full statistical paper if a profile needs its methods, and restore independent external review before canonical promotion.
- Develop nested instance schemas and fixtures for scorer drift, unmatched pairs, failed retries, label revisions, budget imbalance and outcome-informed protocol amendments.
- Validate metric-specific analysis profiles with dependent observations, stochastic scorers, multiple contrasts and non-estimable uncertainty, and pin external model contracts and evidence export mappings.
- Independent external provider review is absent.
- Direct HTTP status and immutable source versions remain unverified.
- Nested instance schemas, profile-specific validators and acceptance fixtures remain unimplemented.
- Statistical methods for particular metrics, clusters, adaptive designs and resource-constrained studies need qualified selection.
- Neighbor model contracts and machine-executable mappings remain unpinned.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-ai-013-ablation-study/spec.yaml