Sigilkore

Sigilkore treats the sigil as an engineering problem. Given a statement, produce a glyph that carries it, and be able to say exactly what each stroke encodes. This page works through that sequence in the order it has to happen, from the reduction of a sentence to the deletion of the file afterwards, and it treats the aesthetic dimension as real but secondary. The assumption throughout is that you want a method you can repeat and somebody else could audit, not a one-off gesture. That assumption changes several things people usually skip, including how the intent is worded, how long the charge runs, and why the forgetting step is the one worth getting right. Everything claimed here is checkable, including the parts most instructions leave vague.

The reduction, done as a separate act

Start with a sentence in the imperative. Not a wish, not an aim, not a noun phrase. Something with a subject you can identify and a verb you could watch somebody perform.

The discipline here is doing more work than it appears to. Most people write a statement they would be embarrassed to say aloud, and the reduction surfaces that immediately. If you cannot read the sentence back without wincing, the problem is the sentence, and no amount of glyph refinement will fix it.

Choosing the reduction method, and why it matters

Three methods are in regular use: dropping vowels, letter-by-letter substitution, and position counting. Each produces a different glyph from the same sentence, and none of them is the correct one.

Choose on a practical basis. Use a method you can execute without software so that you can do it at a train station, and use the same method every time, because consistency is what makes your archive legible later. Switching methods mid-corpus produces a collection you will not be able to decode.

1. Write the imperative sentence and read it back aloud
2. Apply one method consistently, vowels removed, substituted, or counted
3. Group the resulting letters into a shape you can draw without lifting the pen
4. Check that the shape is legible at the size you will actually view it

Drawing, and what the drawing stage is for

The glyph does not have to be beautiful. It has to be traceable, which is a different requirement and one that most people meet without noticing they were aiming at it.

A traceable glyph can be redrawn from memory by someone who was not there. Test that once per sigils: sketch your finished shape from memory on a fresh page. If the result is unrecognisable, your glyph was over-detailed and the extra strokes were decoration rather than information.

The charge, with enough specification to repeat

A charge specification is four fields: duration, instrument, focus and release. Duration as a count or a candle length rather than minutes. Instrument as something specific you can name.

Focus as the single thing you are holding in mind for the whole interval, described precisely enough that you could tell whether you drifted. Release as a physical action that ends it, not a decision to stop thinking about it.

The charge as a sequence of actions

This is the part where sigilkore is most specific, and where generic instruction is least useful. The sequence matters because each step removes a way of failing quietly.

If you cannot name the instrument, you will not find it, and the charge will happen elsewhere by accident. If you cannot define the focus, you will drift, and drift produces nothing you can evaluate. If the release is not physical, the working will be re-entered every time you see the object.

1. Lay the instrument where you can see it and nothing else is in your hand
2. Set the interval on a timer, using a duration you chose in advance
3. Hold the focus as a single sentence, and note the time if you lose it
4. Complete the release action, then move the object out of sight before standing up

Forgetting, which is the stage most people skip

The release is not complete until the object is somewhere you will not look at it. Screen practice makes this harder rather than easier, because the file remains reachable, and reachable files get re-opened.

Delete rather than archive for anything you have charged. Move it out of the visible image folder. The purpose is to break the attention loop, and an object you check on every few days keeps the loop open indefinitely. This is also the stage most consistently omitted in written instructions, which is a strong hint that it does more work than it appears to.

Recording the encoding itself

Store the sentence alongside the glyph. It takes four seconds and it is the difference between a working and an ornament, because without the plaintext you cannot tell, a year later, whether a shape is a sigil or a scribble.

The record should carry the date, the method used, the charge specification and the outcome. Outcomes written the same day are worth far more than outcomes remembered in November, and the gap between the two is where almost all the useful data about practice gets lost.

Nothing happens, and what that means

Nothing is the most common result and it is not a failure state. A run of sigils with no attributable effect is exactly what a correctly specified procedure should produce if the underlying claim is weak, and the response is to check the procedure before checking the claim.

Four things to audit, in this order: was the intent checkable, was the glyph legible, was the charge timed, and was the release complete. A sigil that fails any of those has not been tested, it has been attempted. Fix the first failure you find and run it again before concluding anything.

Derivatives, and when they are worth the trouble

A derivative is a sigil made from an existing sigil, usually for a connected intention: a series of payments, a repeating task, a sustained condition rather than a single event.

The argument for them is that a repeated intention amortises the design work across many activations, which is the same logic that makes a prayer wheel work. The argument against is that each design step adds a chance to encode something other than what you meant, and a derivative chain is harder to audit than the original.

• Worth it for repeated, scheduled intentions where the wording is stable
• Worth it when the base sigil has already proved legible and traceable
• Not worth it for a first attempt, since it doubles the steps that can go wrong
• Risky when the chain gets long, because errors compound and hide

A month, in the order that works

Week one, one sigil, made slowly, with the full record. Week two, the same statement reduced by a different method, to see what the method changes. Weeks three and four, a condition you have actually been avoiding, run twice at a fixed frequency.

The point of the second week is diagnostic rather than productive. If the two glyphs produce comparable results, the method is not the variable. If one consistently outperforms, you have found something about your own working that no amount of reading would have told you.

What this method gives up

Specifying everything makes the practice slower and much less romantic. A sigil made with four recorded fields and a deletion step is not the object you saw in somebody's video.

That trade is worth making once, and then relaxing. The specification is scaffolding, and the goal of building it carefully is to be able to stop counting. A method that requires transcription is a method you will abandon in week five. A method you have verified in a structured month is one you can carry for years without the notebook open.

Frequently Asked Questions

How exactly do I charge a sigil, and does the detail actually change the result?

Use four fields: a duration set in advance, a named instrument, a single focus sentence, and a physical release action. The detail matters mostly because each field removes a way of failing quietly, not because the numbers carry meaning. A timed charge stops the working turning into daydreaming. A named instrument prevents the charge happening somewhere else. A defined focus makes drift observable. None of this is numerology, and all of it is repeatable.

Do I need to be able to draw well to make a sigil?

No. Legibility is a functional requirement rather than an artistic one, and the test is whether you can redraw it from memory. If you can, the drawing is good enough. Most people who think they cannot draw have made a sigil with forty unnecessary strokes and could make the same one in eight. Reduce until the shape is traceable, then stop refining.

What counts as a derivative, and should I bother making one?

A derivative is built from an existing sigil, usually for a connected or repeating intention. The benefit is amortising design work across many activations. The cost is an extra design step, which is another opportunity to encode something you did not intend. For a first working, make originals only. Derivatives earn their place once you have a base sigil that has already proved traceable.

Is a one-time purchase of a sigil app worth it for a casual user?

Occasionally, and for a narrow reason. Reduction by hand and drawing on paper cost nothing and last forever, so the thing worth paying for is convenience and storage rather than capability. Batch generation, an archive that will still open in five years, and no adverts interrupting a concentration you are holding deliberately. If you make one sigil a month, none of that is worth money, and the paper method will outlast the app.

Why does the forgetting step matter so much?

Because the release is the part that ends the working, and a release you can undo is not a release. An object you still see keeps the attention loop open, and a loop left open turns the sigil into a reminder to worry rather than a completed operation. Deleting the file and moving the object out of sight is unglamorous and it is the step most written instructions skip, which is suggestive. In practice it is what stops a single working from quietly consuming attention every few days for the rest of the year.