Remove a signal to measure its contribution.
AMF is the infrastructure that fabricates intelligence realizations
AMF is a mission-first engineering infrastructure: Scientist experimentation, fabrication of exact executable realizations, Ledger provenance, bounded qualification and runtime authority checks. One model is an output; the foundry is the product.
Capability may propagate. Authority may not.
A capability that is inherited, transferred or recomposed never automatically inherits the authority of its source.
The foundry matters more than any single model.
Mission → fabrication
Define measurable requirements, compare options and materialize an executable realization for the mission.
Persistent Scientist
Form hypotheses, run experiments and use observations in decision scores. A cumulative advantage across missions is not yet established.
Ledger & lineage
Connect identities, interventions, measurements and verdicts to the exact artifacts produced. Provenance alone does not prove a measurement is true.
Evidence & runtime
Bound qualification claims, then separate AI output from authorization to act during execution.
A neural realization, not a generic promise.
AMF produced a Mistral 7B descendant for a billing-versus-technical classification mission: four transformer layers removed, adapted with LoRA and measured on development test sets.
No independent FP2 QIR was performed. Comparisons with the unmodified parent, inference speed and cost savings are not established here.
Inspect FP2 and its limitsparameters removed
ROB · development
OOD · development
recorded Ledger events
AMF terms, in plain English
Mission
A specific problem and the results required.
Realization
The working system: models, data, tools and rules.
Qualification
One exact version passed predefined tests for a specific task.
Evidence
Test results and files that support the reported claims.
Passing one mission does not mean every other task is proven. AMF should always state exactly what was evaluated.
Start with a real goal. Test before you deploy.
Mission
Objectives, constraints, budgets, evidence criteria and termination conditions.
Search
Bounded hypotheses and experiments across models, representations, data, knowledge, composition and runtime.
Materialize
Reuse, transform, train, rematerialize or compose exact candidates.
Measure
Measure utility, robustness, cost, collateral effects, interactions and execution integrity.
Qualify
Apply protected gates to a frozen realization and record a bounded verdict.
Operate
Execute an admitted realization within authorized runtime bounds; admission requires its own qualification evidence.
Different tools can solve different parts of a task.
CHARACTERIZE
What already exists?
INTERVENE
What changes under controlled perturbation?
REPRESENT
Can the function be represented differently?
LEARN / RECOVER
Can observed deficits be repaired?
REMATERIALIZE
Can the function exist in another substrate?
COMPOSE
What system interactions emerge?
DATA / KNOWLEDGE
Is the deficit informational rather than structural?
DEPLOY
Which runtime envelope is justified?
Ten ways to test how an AI component affects the result.
Hide a head, neuron, path or block without erasing its source.
Route around a component to test whether it is necessary.
Substitute an activation, component or baseline.
Vary influence continuously instead of making a binary cut.
Stress a pathway and measure the robustness of the realization.
Reduce rank, dimension or retained structure.
Lower precision or substrate quality under controlled conditions.
Test whether another implementation can preserve the bounded function.
Constrain learning to identify where adaptation is necessary.
Historically documented interventions include HEAD_OUTPUT_ZERO, Q / K / V / QK / QKV paths and ATTN_SCALE. A measured drop indicates contribution under the tested conditions — not the universal location of a capability.