Hidden, Lost and Forbidden Knowledge

There is a version of self-directed occult study that never stops: you read the traditional texts, find them lacking, buy the ones that promise to fill the gap, and discover inside them three more books to read. The way out is to stop accumulating and start building. A system of your own, assembled deliberately from a small number of sources you have actually checked, is more workable than any borrowed lineage because you know every piece of it and can change any piece of it. This article is about how to do that, using four documents as the raw material and being explicit about which parts you are taking on trust.

Customising your own system, and what the phrase promises

The promise of customisation is usually sold as liberation, and it is worth taking seriously rather than treating as marketing. A lineage you did not choose asks you to accept a set of commitments, transmissions and authorities you cannot evaluate. A system you assembled asks only that you be able to justify the pieces, which is a much lower and more achievable bar.

There is a real risk on the other side, which is that a self-authored system drifts toward whatever you already believed, and you end up with a confirmation engine wearing esoteric vocabulary. The defence is structural rather than moral. Write down the source of every element, keep the ones that came from a tradition separate from the ones that came from you, and require that at least one retained element does something you find inconvenient.

Why self-authored systems outperform borrowed ones

Three reasons, and none of them are about power. First, comprehension: you cannot maintain or troubleshoot a practice made of components you do not understand, and the troubleshooting is where all the real work happens. Second, revision: a system you built can be changed in an afternoon, which matters because the first version of anything you design is wrong in at least two respects you cannot yet see.

Third is the log. A system of your own can be evaluated properly, because you know what each component was supposed to do and can drop the ones that produce nothing. Borrowed systems come with a claim of completeness, which means a failed practice cannot be narrowed, only abandoned, and abandonment loses you everything you had built. Narrowing is the technique that keeps a practice alive, and it is only available to people who can see the components.

Choosing three sources and no more

Three is not a mystical number here, it is a practical limit imposed by attention. Pick one text that gives you a complete working sequence, one that supplies a framework for thinking about what you are doing, and one from a system that does not share your assumptions. That third one is the one people skip and it is the one that makes the difference between a practice and a preference.

Test each candidate against four questions before committing. Does it state a sequence I can follow? Does it claim anything checkable? When was it first published, and by whom? Would I still be reading it if it were not fashionable? A text that fails the fourth question is a status object, and a status object in a practice of three is a quarter of your system spent on nothing.

The Book of Enoch, without the mystique

The Book of Enoch is among the oldest surviving fragments of Jewish apocalyptic literature, partly preserved in the Dead Sea Scrolls and known to some church fathers before it was excluded from most modern Bibles. That is a genuinely strong provenance: early witnesses, late antique preservation, and a documented reason for later exclusion from the canon.

What it does not give you is a method. It is a apocalyptic vision with cosmology, angelology and judgement, not an operational manual, and the temptation to treat it as an instruction book is how it most often gets misused. Keep it as a source of imagery and cosmology, mark it clearly as such, and do not build a technique on a passage you have not translated or located in a scholarly edition.

Liber Null and psi as a working skeleton

Liber Null and psi is the piece most people borrow when they assemble a first system of their own, and on this question it is the right one to borrow. As a component it earns its place for a single reason: it gives you a complete sequence in an evening's reading, so the rest of your system can be built on something you actually do rather than something you admire.

Its weakness is that it is a pamphlet, so it has no depth, and its later editions contain material Carroll did not write, which matters if you are recording sources. Use it for the sequence, note which edition you are reading, and treat everything beyond that sequence as belonging to the commentary rather than to the author.

The Kybalion and the risk of borrowed authority

The Kybalion, published anonymously in 1908, is not attributed to any known author and its provenance claims are unsupported. No translator, no manuscript, no scholarly engagement with the source it asserts. It is a New Thought self-help text of the period, and the seven principles have circulated for a century in forms that frequently depart from what the book says.

In a system you are assembling, the specific danger is that anonymous authority is easy to adopt because adopting it costs nothing and sounds deep. Including it as a clearly labelled reading, with the note that its provenance does not hold up, is fine. Including it as a framework is a way of importing someone else's conclusions while believing you chose them, and that is the failure mode this whole exercise is designed to avoid.

Assembling the dossier, step by step

One page per source, four fields: author and date, stated sources, stated purpose, and the claims that are checkable. Add a fifth field, which is the one that matters most: the component of your practice this text is actually supplying. If you cannot fill that field, the text is decoration and should be moved off the working shelf.

Then write a single page for the system itself. The elements in the order you will use them, what each is for, what you would do if it stopped working, and the one element you are keeping only because it is inconvenient. That last item is the test of whether the system is yours, and a system with nothing in it that you find difficult is a copy with extra steps.

Deciding what to leave out

Most of what you will want to keep should go. A three-source system with one page per source is enough to work with for a year, and everything else is deferred rather than rejected. Deferral is the right move because you can return to a text with a specific question later, and a shelf of unread books produces a chronic low-grade sense of incompleteness that is worse for practice than an empty shelf.

The exceptions are worth naming. Keep a critical text about one of your sources, because it will show you where you are being sold something. Keep one practical reference, because you will use it constantly. And keep anything that contradicts you, at least for a year, because a system made only of agreeable parts will confirm whatever you already believed and teach you nothing at all.

The first working out of your own system

Run it the way your primary source specifies, without additions, and log it. The temptation to improve the method by combining techniques from all three sources is strong and premature, because a combination cannot be evaluated. One source's method, repeated several times, produces results you can attribute, and a combination produces activity.

Use a small dated aim in your own domain, and score it strictly with no impressions column. After three or four workings you will have the first evidence you can get about whether your chosen sequence does anything, and the answer will be more useful than any amount of reading, because it is a fact about the system you actually built rather than about the system you were sold.

Evidence that yours works better than a copy

The comparison is available and almost nobody runs it. Alternate five workings from your own assembled system with five from a single borrowed source, use the same class of aim, and log both identically. Because you built your system, you know what each component is for, so when something fails you can drop or swap a component and try again, which is the practical advantage you claimed at the start.

The result will probably be a small set of differences rather than a dramatic gap. Your system will be easier to remember, easier to schedule, and far easier to change when it stops producing results. That is the real return on assembling it, and it is worth having even if the workings themselves turn out to be indistinguishable from the borrowed ones, which is also a useful thing to know.

Responsibility for what you invented

Once you have authored a component, you own its consequences in a way you did not with a borrowed element, and the two most common failures are modesty and inflation. Modesty means quietly dropping the components that do not work and never mentioning them, which makes your log a survivorship record. Inflation means treating your own design as more fundamental than the traditions it came from, which is the error every lineage was invented to avoid.

Keep a revision history. Date each change, say what you changed and why, and leave superseded components in the file with a line through them rather than deleting them. A system with a visible history is a practice you can learn from, and a system that has been tidied into elegance has quietly become a belief rather than a method.

Tearing it down when it stops working

The right moment is defined by evidence, not by boredom. If three consecutive working sequences have produced nothing you would score as a hit, the problem is in the method or the aims, and the fix is to drop the weakest component and retest rather than to intensify. Intensification is what people do instead, and it produces a longer log of the same null result.

If nothing works after a full cycle of revisions, the honest conclusion is that the system is not producing outcomes, and you have three legitimate options. Keep it as a framework for attention and meaning, which is what it demonstrably does. Return to a single traditional source and use that. Or set the whole thing down, which is a better outcome than continuing indefinitely, and cheaper than it looks, because everything you built is written down and can be picked up again in an afternoon.

Frequently Asked Questions

Is it legitimate to build a personal magical system?

Yes, and it is what most practitioners do in practice, whether or not they label it that way. The early texts were written so a reader with no teacher could work from them, and the movement's own contribution was making it acceptable to test claims rather than inherit them. The requirement is only that you record where each component came from, keep tradition and invention in separate columns, and keep at least one element that you find inconvenient.

How many books do I need to read?

Three is enough to start and more is worse in practice. One that gives a complete sequence, one that supplies a framework, and one from a system that does not share your assumptions. Everything else can be deferred, and a shelf of unread material is more obstructive than an empty one, because it generates a persistent sense of incompleteness that has nothing to do with your actual competence.

Should I include texts whose provenance I doubt?

Include them as readings with a clear note about what you could not verify, and keep them out of the framework. The problem with anonymous or invented-provenance material is never that it is useless, it is that adopting it as authority means importing someone else's conclusions while believing you selected them. A labelled reading is fine, and it becomes a serious problem the moment you stop being able to say which parts are the author's and which are yours.

What is the single most important thing to keep in the system?

The component you find inconvenient. A practice assembled entirely from things you already agree with will confirm what you believed before you started, and you will learn nothing from it. Keeping one element that argues with you forces you to either operate it properly or explain why you are not, and that requirement is most of what separates a method from a preference.

How do I know when to abandon my own system?

After three consecutive working sequences produce nothing you would score as a hit, which is a technical failure signal rather than a mood. Drop the weakest component and retest once. If a full cycle of revisions still yields nothing, the honest conclusion is that the system is not producing outcomes, and you can keep it deliberately as a framework for attention, fall back to one traditional source, or set it down. All three are legitimate and all three are better than indefinite intensification.