Audit Learned Component Boundaries
Apply Models From First Principles Step 03 to determine whether Q, V, policy or other learned submodels should be separate components or simpler shared heads.
How to use this
- Open a repository-aware AI assistant.
- Give it access to the repository or files you want reviewed.
- Copy the prompt below and run it unchanged first.
- Use the evidence it finds to decide what to inspect or change next.
PromptCopy and run against your own project
Review the learned component boundaries in this repository.
The question is not whether the architecture can be decomposed into separate models. The question is whether those boundaries improve correctness, evidence, ownership or independent evolution enough to justify their cost.
Trace each learned submodel end to end and record:
- inputs and outputs;
- training data and target;
- optimizer/update path;
- checkpoint lifecycle;
- inference caller;
- dependencies on other learned components;
- whether it can be evaluated independently.
For every boundary ask:
1. Does this component solve a distinct prediction problem?
2. Does it require different data or optimization?
3. Does it need independent deployment/versioning?
4. Can its quality be measured independently?
5. Would a shared encoder/head produce the same observable behavior more simply?
Check for:
- duplicate encoders with no demonstrated benefit;
- separate models that are always trained and deployed together;
- implicit circular dependence between outputs;
- stale checkpoints or version skew;
- duplicated preprocessing;
- component APIs that hide incompatible semantic assumptions;
- separate models created only because the concept has a separate name.
Cite exact repository evidence for every conclusion.
Output:
1. Learned component graph
2. Boundary justification table
3. Shared versus independent training analysis
4. Version/deployment coupling risks
5. Boundaries that should remain
6. Boundaries that could collapse
7. Smallest ablations needed
8. Recommendation with expected simplification benefit
A component boundary should correspond to a real independence property, not a diagramming preference.