COCHICHOLUPOS

COCHICHOLUPOS is not on any list. It is not one of the seventy-two, it appears in no pseudepigrapha roster, and it is not a transliteration of anything recoverable from a dead language. That absence is the interesting part, because it isolates the architecture of an entity working from the entity. What remains when you take the spirit away is a four-part structure: a name, a compressed glyph, a written office, and a single task. Each piece has a job, and each piece has a specific shape because of what it has to do. This article takes the framework apart and explains why it is built the way it is, so you can construct your own consistently rather than assembling one from fragments of other people.

The name is a handle, and nothing more

Start with the part most likely to be overstated. A name attached to an entity working exists so you can refer to one intention without restating it. That is its whole function. It compresses a description into a sound short enough to say out loud twice in a sitting, and in exchange it gives you one referent rather than a paragraph.

COCHICHOLUPOS does that job well as a sound. It has no referent behind it, and pretending otherwise is the most common way a working of this type goes wrong, because the moment you attach a biography to a coined name you have created a claim you will not be able to support. Invented histories are easy to generate and hard to unwind. Leave the name empty and it stays a useful instrument.

The glyph is a compression, not a symbol

The second component is the glyph, and the useful way to think about it is as a compression rather than a sign. A statement of intent is long and its length is its weakness: it can be reinterpreted after the fact, adjusted to fit whatever happened, quietly rewritten by someone who wants a particular conclusion. Reducing it to a minimal form removes the room for that reinterpretation.

That is also why the glyph is usually drawn from memory rather than copied. A copied glyph is a picture. A drawn glyph is a proof that you can reproduce the reduction, and it makes the charging step something you did rather than something you confirmed. The shapes themselves carry no fixed meaning in any authoritative source; what they encode is the specific statement you reduced.

The office is where most workings are skipped

The third component is the office: a written sentence describing what the entity is for. This is the piece that gets skipped, and skipping it is why so many entity workings produce nothing a practitioner can later evaluate. An office turns a vague intention into a specification, in the same way that a job description turns a person into an employee.

Write it in the imperative and keep it to one line. If it runs to three sentences, it contains three separate workings pretending to be one, and they will interfere with each other. A workable office sounds like a job title plus a verb and an object: fetch one specific thing, hold one specific state, interrupt one specific pattern. If you cannot write that line, the aim is not yet clear enough to be encoded.

One task, not a portfolio

The fourth component is the task, and the architectural rule is that there is only one. Multiple tasks produce a working that can be confirmed by any outcome, which is another way of saying it produces nothing. If the entity holds three offices, then anything that happens is consistent with at least one of them, and the structure cannot fail, so it cannot tell you anything either.

This is the same constraint that governs good experimental design, and it is not an occult principle. It is the requirement that a prediction be falsifiable in advance. The framework is worth keeping precisely because its components are ordinary instruments rather than mystical furniture, and the discipline of one office per name is the component most often abandoned when a working stops producing results.

Why documented catalogues were easier to work with

Compare this assembly to a Goetic entry. There you are handed rank, a visible form, an office and a list of powers. Every slot in the four-part structure is pre-filled by a source you can read, and your only work is selection. That is why the catalogues have been so widely used: they hand you the specification and let you skip the design.

The cost is that the specification is inherited rather than chosen, and it is not always coherent with what the person invoking it actually wants. A spirit listed as a marquis who rewards artisans is being asked for a different job than one listed as a president who grants wealth, and choosing between them means trusting a source compiled in a political and religious context entirely unlike your own.

What modern practice changed, and why

The later esoteric movements relaxed most of the classical apparatus. The ceremony gave way to the intention, the sigil replaced the circle, and entities came to be treated as fragments of pattern that a practitioner could use to interrupt repetitive thinking rather than as intelligences to be negotiated with. Nothing was removed so much as reclassified: a description of what entities are for became a description of how they function in a working.

The consequence is a much lower entry cost and a much smaller set of claims. You no longer need a licence, a temple or a lineage to attempt a working, and in exchange you are not asserting anything about the entity's nature. Peter Carroll's framing was that these figures are best understood as aspects of the practitioner's own mind, which strips almost all of the risk without requiring anyone to become materialist about the practice.

Servitors versus spirits, structurally

This is the cleanest place to compare the two constructions. A servitor is designed, task-limited and understood to be an aspect of the operator. It has an office and a term, and the usual discipline is a retirement date, because a designed device with no expiry accumulates unintended scope over months.

An entity, in the older sense, is external, characterised from a source, and addressed rather than designed. The two answer different needs. If your intent is sustained helpfulness over weeks, the servitor format suits it. If your intent is a single defined question or a defined state, the entity format suits it. Mixing the two usually produces a servitor with an inflated identity, which is the worst of both.

Consistency is the part you can actually learn

Nobody can verify what COCHICHOLUPOS did. What can be verified, and improved, is whether you can build and run this architecture again next month with the same discipline. Keep the written statement, the glyph, the office, the date and the outcome note, and you will have five lines per working instead of an impression.

That record will show you things you could not otherwise notice: whether you keep the one-task limit, whether you close what you open, whether your outcomes cluster around what you asked for or scatter randomly, whether the workings you closed properly leave residue or not. These are the observable behaviours of a practice, and unlike the entity's alleged activity they are fully within your control.

Where the framework fails

Two failure modes dominate. The first is inflation: the name acquires a biography, a lineage, a temperament and a history, and the working becomes a relationship narrative maintained by both parties. The second is confirmation: every result is read as a message, so the record fills with successes and no nulls ever appear. A practice with no nulls in it is not a practice with a high success rate; it is a practice not recording.

A third failure is quieter. Designing entities to fill gaps in a life produces a great many names, each with an office, none of which is ever checked. The architecture is fine; the discipline of stopping is missing. One working followed through to a conclusion teaches more than nine designed and abandoned, and the reason is that only the followed-through one produces data.

How to build one properly

Write the office first, in one imperative line, and check that it names one thing. Reduce that line to a glyph and draw it from memory tomorrow to confirm it holds. Set the date before you close the notebook. On the day, say the office, use the name, then sit in silence for twenty minutes without narrating what happens. Record one word if anything occurs and one word if nothing does. Close it explicitly.

Then leave it alone until the review date you set. The gap is part of the design, because a working checked the same evening tells you what your expectation was, not what happened. Nothing in this structure requires a belief about the name. It requires that you follow the same sequence twice and be willing to write down the second result.

What the framework is actually for

Strip out the symbolism and four things remain: compression of an intention, a written specification, a fixed time, and a recorded outcome. Those four are the whole yield, and they are worth having because they are portable. The same four can be applied to a documented spirit, to a servitor, to a piece of creative work, or to a habit, with no change in structure and no supernatural claim required at any point.

Which is the argument for COCHICHOLUPOS and every other coined name. There is no being behind the word. There is a structure around it, the structure is ordinary, and you can learn it, repeat it and check whether it works on you. That is a smaller claim than the grimoires make and a more useful one.

Frequently Asked Questions

Who or what is COCHICHOLUPOS?

No catalogue documents it. It is a coined label, and the article treats it as a name you would attach to a working of your own design. No biography, lineage or attributed office is invented for it, because inventing one would create an unsupportable claim.

Why does the framework need four separate parts?

Name, glyph, office and task each do a different job. The name gives you a short referent, the glyph compresses the statement so it cannot be quietly rewritten, the office makes the aim specific, and the single-task limit makes the outcome checkable. Remove any one and the remaining three start substituting for it.

Is it better to use a spirit from the Goetia?

A documented entry gives you a finished specification, which saves design work and lets you skip the office-writing step. A coined name gives you an office you chose, which is more coherent with your actual aims. Neither is privileged; the recorded catalogues were compiled for purposes unrelated to modern practice.

What does Carroll's framing change in practice?

Treating entities as aspects of the operator's own mind removes the hazard without requiring scepticism about the practice. Nothing in the four-part structure changes. What changes is that you no longer have to make any claim about an independent intelligence in order to run the sequence.

How do I know whether any of it worked?

You do not, from a single session, and the article says so. What you can know is whether you ran the sequence as specified and what you recorded. After several workings the pattern in your own records is more informative than any impression from one evening.