Framework Record
Framework record
Select a record from the framework library to load its specification.
—Record Not ResolvedAR-FRM-404
That record is not in the library.
A framework record is addressed by identifier. The one requested does not correspond to any record currently held. The twelve that do exist are listed below.
01Core EdgeAR-FRM
What this framework
claims to exploit.
Record summary
02Regime PermissionAR-EXP-071
Where this logic belongs,
and where it does not.
Regime permission is a precondition rather than a filter. Declared ideal states are the conditions the edge argument depends on; declared hostile states are those in which the same mechanism works against the position. In every state not listed, the framework has no particular reason to expect anything.
03Trade ArchitectureAR-FRM-SPEC·03
Entry, invalidation, exit.
The geometry of a single trade. These three blocks decide the shape of every outcome the framework can produce: the entry sets location, the stop sets what being wrong costs, and the exit decides how much of a favourable move reaches the account.
The two standing difficulties
04Branch PossibilitiesAR-BRN-001…004
The management populations
this framework can deploy.
A branch is not a separate strategy. It is the same entry managed to a different objective, and the populations below behave differently enough that blending them without measuring them separately conceals which one is failing.
05Relevant ParametersAR-SIM-047
The controls that move
this framework most.
All 159 engine controls apply to every framework. These are the ones whose effect on this particular record is large enough to change the conclusion, listed with the control's own description and its default value in the preview engine.
06Illustrative BehaviourAR-SIM-047·RUN
What the model does
with this shape.
One run of the preview engine using this record's archetype at its own design ATR coefficient, with every other control at the laboratory default. It is a demonstration of the model's behaviour, not a history and not a prediction.
Median of nine seeded histories.
Simulated demonstration data. This visualization illustrates proposed product behaviour and does not represent historical, live, or guaranteed trading performance.
How this figure is produced
The engine converts the archetype and the 159 controls into a working stop, a friction charge expressed against that stop, an outcome ladder and a trade frequency. Those feed a seeded simulator that groups trades into concurrency blocks and lets correlation pull outcomes inside a block toward a shared sign.
Nine histories are generated from nine seeds and the middle one by final return is drawn, so the curve on screen matches the drawdown figure quoted beside it. No market data is involved at any point.
07Planned DiagnosticsAR-FAC-002·03
The measurements declared
in advance.
Diagnostics chosen after a result is known will tend to explain that result. These are named in the record before any sample is examined, so a later disappointment has to be argued against a measurement that was already agreed on. All are planned capability at the levels marked.
08Related Wizard FrameworksAR-PUB-142
Doctrines that argue
for this approach.
Educational abstractions of publicly discussed trading doctrines, matched to this framework by the claim they make rather than by the instruments they traded. They are interpretations of public material, not reconstructions of any private method.
09MARS CompatibilityAR-VAL-031
How much a governance
layer changes this.
MARS sits above signal quality: a drawdown-derived deployment envelope, a tier ceiling, and open exposure subtracted from the authorised pool before any new position is sized. It is optional, and its cost is explicit — it compresses risk in adverse states and gives up growth in favourable ones.
MARS intelligence in full →Calibration is not published
The gate boundaries, pool percentages and tier tables belong to the MARS workbook product. What is described here is the structure and the principle; the comparison shown above uses an illustrative ladder rather than the workbook's calibration.
10Typical Failure ModesAR-FRM-SPEC·10
How practitioners
break this framework.
Written into the record before any result is produced, so it cannot be retrofitted to explain a disappointing outcome. Each of these is a change that feels locally reasonable and destroys the mechanism the framework depends on.
11Record LimitationsAR-FRM-SPEC·11