Securitisation
Bibliographic record
Abstract
Case A company, ABC Ltd, lends money on the security of mortgages/hypothecs on immovables. It now wishes to raise money in the financial markets. It wants to use its portfolio of secured loans as security for the transaction. The goals will be that ABC Ltd will not itself become liable on the transaction, and moreover that investors will not be adversely affected by any subsequent insolvency of ABC Ltd. How can the transaction be structured so as to isolate the portfolio of secured loans from the general business of ABC Ltd? Discussion AUSTRIA There are only a few articles on securitisation in the Austrian literature, and no court decision at all. The following remarks therefore have only a preliminary character. In principle, Austrian law provides all the legal instruments required to structure securitisation transactions. First, it will be necessary to set up a new company, a special purpose vehicle (SPV). In a second step, ABC Ltd shall transfer its secured loans to the SPV. In exchange for them, the SPV shall pay a certain sum to ABC Ltd. To raise the money necessary for this payment, the SPV shall issue bonds to investors. If those investors are the only creditors of the SPV, then the security of the claims assigned to the SPV will also secure the investors' claims. As there is no direct relationship between the investors and ABC Ltd, this company will not be liable for the SPV's debts towards the bondholders.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.003 |
| Scholarly communication | 0.004 | 0.003 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.069 | 0.033 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".