RIA-MS408 / Voynich - Final Document / Review Candidate
Posted: Mon May 25, 2026 4:17 pm
RIA-MS408 / Voynich - Final Document / Review Candidate
Workshop protocol, formal structural approach, and controlled release for external review
Author SirJoe
Version formatted English review copy
Date 2026-05-25
Status Review Candidate / personal closing version / no semantic release
Claim boundary: This document claims no plaintext, no translation, and no true decipherment. It presents a formally testable, non-semantic structure candidate for external review.
Contents Overview
1. Preface: It All Began with a Spark
2. Personal Closing Formula
3. The Derivation Chain: From Public Findings to the RIA System
4. The Closed Dynamic System Model
5. Why the Aries Context Is So Strong for Me
6. Why the Tube and Bus System Is So Strong for Me
7. Why the Circular Tables and Data Sets Matter
8. Why Bus and Circular Tables Carry the Mechanism Together
9. Why Stars Are Strong Template and STATE Marker Candidates
10. Why the Different Nymphs Matter as Slots
11. Why Stars and Nymphs Together Open the Template Logic
12. Why Curved Circular Templates and Vortex Lines Are Strong
13. Why the Rosettes Foldout Looks Like the System Mainboard
14. Why All Drawings May Have Function - But Not Arbitrarily
15. My Personal Analogy: The RIA-MS408 OSI Layer Model
16. Claim Boundary
17. Quality-Gate Evidence Chain
18. Core Model: RECORD / STATE / PAYLOAD / MARKER / CONTROL
19. Section Models: Zodiac, Balneo, Pharma, Gallows, Q3
20. Adversarial Review: What Critics Should Attack
21. What I Consciously No Longer Do
22. Status Formula
Preface: It All Began with a Spark
It all began with a spark. Not with an academic plan. Not with an institute. Not with a completed model. It began with that one inner moment: something is off here. There is something. An order is gripping the material, but I cannot yet name it.
I first seriously heard and read about the Voynich Manuscript roughly one month ago. I did not come from Voynich research, not from a school, not from an old debate. I entered as an analyst and IT-minded observer: with a systems view, with mistrust toward overly smooth explanations, and with the reflex not to read an unknown structure first as text, but as structure.
Even language uses mathematical regularities. That was where my curiosity and project mode began. It was not smooth or elegant from the start. It contained curiosity, overreach, AI drift, embarrassment, correction, hard brakes, false trails, better trails, rollback, and counter-checking. That is exactly why this document is not a victory text. It is a closure: a deliberately set line under a working state.
It would itself become a form of drift if the checking, and thus the project, had no end. I do not claim to have deciphered the Voynich Manuscript. I claim no plaintext, no alphabet, no language, no translation. I prove nothing in the academically final sense. I have been there before. What I close is a circle for myself, through the lens of an IT analyst.
For me personally, the evidence chain is sufficient. Not as an unshakable final scientific proof, but as a working certainty: in essential areas, the manuscript behaves less like ordinary running text and more like a layered, formally organized system of image, text, position, markers, and control structures.
Whether others later prove, refute, improve, or dismantle this lies no longer with me. I am making the current state open enough so that exactly this becomes possible. The forums excluded me. Yale and other prominent institutions have not reacted so far. Today I understand why. I do not take that as evidence against my work, and I do not take it as evidence for it. It is only the external state.
Internally, I have reached the point where duty calls again and I do not want to carry this project any longer under pressure. I would like to thank Mr. Klaus Schmeh for replying to my e-mail. What carries, I name clearly. What is only metaphor remains metaphor. What is personally closed for me is not sold as scientifically closed.
All documents and protocols have been secured. This document is therefore two things: a review candidate for others and a workshop closure for me. The full workshop protocol, from the first to the last day, including all its highs and lows, derivation chains, the embarrassing AI drift, the RIA project that emerged against drift, and further projects, I will write when there is time and desire again. The world may now work on it. Regards, Maik Jörn
Personal Closing Formula
This project ends for me with a simple distinction.
Formally: no true decipherment, no semantic release, no plaintext.
Personally: I have seen enough that I can no longer dismiss the mechanism candidate as random. For me, the circle is closed. Not because every stone is watertight, but because the way the stones lie together produces a system form. Like a puzzle, the pieces are in front of us.
Others do not have to turn this into belief. Quite the opposite: they should test it. They should attack it. They should show where I am wrong. But they should not look only at individual stones. They should look at the coupling: Aries, register logic, stars as template/STATE anchors, nymphs as slot/RECORD carriers, Gallows block openings, Pharma band structure, Balneo graphs, Herbal layering, and the consistent separation of RECORD, STATE, PAYLOAD, MARKER, and CONTROL.
The Derivation Chain: From Public Findings to the RIA System
This document is written for anyone who does not want to wait for the full workshop protocol. It shows why the approach does not come out of nowhere. Many individual observations about the Voynich Manuscript are public or have been discussed for years: word repetitions, Currier A/B, circular and rosette structures, conspicuous Zodiac special cases, labels, figures, tubes, text blocks, stars, differing nymphs, curved circular templates, rosettes, and Gallows.
I could unfortunately make some of these connections only in the last days. Today they support my personal view even more. My work does not claim to have discovered each of these individual stones first. Its contribution lies in the synthesis: the known disturbances are not interpreted one by one, but read as layers of a formal system. That is exactly why the model is strong for me.
Important: this derivation is not a semantic release. It is a bridge from public findings to the RIA system reading.
1. Word Repetitions -> MARKER / PAYLOAD
Public finding: Voynichese, or the so-called Voynich language, shows conspicuous repetitions, word-like series, and monotone variants. Classical linguistics struggles with this, because such accumulations appear unusual for natural language in this form.
Derivation: This behavior fits a mechanically generated or strongly formalized system. If a scribe works with fixed syllable, token, or fragment tables and runs them through a position-dependent grid, repetitions, variants, and language-like patterns necessarily arise without implying plaintext.
Gordon Rugg's Cardan-grille approach is therefore not a final explanation for me, but an important public connection: it shows that template/table mechanics can in principle generate Voynich-like surface text.
RIA integration: In my model, this becomes the separation of PAYLOAD and MARKER. Recurring tokens or label groups are not automatically words, but possible payloads, table remnants, register values, or formal output fragments. Slots, positions, margins, block starts, circles, and segmentations operate as MARKER: they determine when and where a given formal state appears.
Status: Strong as a derivation path. Not proven as a Cardan grille. Not released as a hoax claim.
2. Currier A/B -> GALLOWS Interface
Public finding: Prescott Currier described the well-known split into Currier A and Currier B: two statistically different text modes within the same manuscript. Whether these represent different languages, registers, subjects, scribes, modes, or something else remains open.
Derivation: For an IT analyst, an abrupt statistical mode shift is a strong signal. In a technical system it would not be surprising: different mode, different table, different register, different template, different writing rule.
RIA integration: This is where the Gallows trace becomes central. The hard coupling between paragraph block openings and Gallows line-open provides a formal interface signal: 200 of 229 @P0/@P1 block openings begin with Gallows, that is 87.34%. The remaining paragraph lines are at 18.70%. This is not a small stylistic impression, but a massive positional finding. The Gallows are therefore not treated as normal letters, but as opening/timing markers for text blocks. Not as proven opcodes, not as commands, but as a formal channel-change candidate.
Status: GALLOW_BLOCK_OPEN is strongly supported. IF3 is strongly supported. IF4 remains open.
3. Circular, Rosette, and Angular Structures -> Angular Matrix / CONTROL
Public finding: The manuscript contains circles, rosettes, segmentations, star-like fields, and diagrammatic pages that do not fit neatly into an ordinary text tradition. In such areas the page feels more like an instrument than like an illustration.
Derivation: If a circle is not merely image or drawing, but a geometric form, angles suddenly matter. A circle can be a register, a rosette can be a control surface, and a segmentation can serve as an address or selection grid. Where 18-part structures occur, a 20-degree step is mathematically close. This fits a volvelle or calculating-disc lens, without proving a final output.
RIA integration: The circles are treated as CONTROL candidates: not as decoration, but as possible output registers, selection spaces, or reference discs. The angular matrix remains deliberately cautious. It is not the final proof. It is a test assignment: do segments, figures, stars, labels, and text orientation line up stably enough when treated as an angle/position system?
Status: Strong as a system bridge. Exact angular decoding remains open. Rigid 22.5-degree claims remain blocked.
4. Gemini and Aries -> STATE Gate / Initialization
Public finding: The Zodiac pages contain several conspicuous special cases. Gemini f72r2 carries the strong NULL special case: a physical figure or intermediate anchor is locally supported, but the associated regular label is missing. Aries is doubled and appears as a 15+15 structure in the context of an otherwise dominant 30-register.
Derivation: In a formal system, headers, null cases, start areas, and control slots are not side issues. They explain how an area begins, how a state is set, and how gaps or special cases are processed. From an IT perspective, Aries is therefore not only a Zodiac image, but a start context: the cycle is not continued smoothly; it is split and calibrated at the beginning.
RIA integration: Gemini is treated as a NULL/header context, Aries as an initialization candidate. When I say BIOS or reset, this is not a historical computer claim. It is laboratory language: a starting area in which basic states are set. This is where the circle closes for me: Aries sets, Zodiac holds registers, Balneo couples, Pharma segments, Gallows time the blocks, and circular/angular structures order the space.
Status: Aries is for me the strongest initialization context. Formally it remains an initialization candidate, not a proven BIOS.
5. Stars and Nymphs -> Template / Slot Logic
Public finding: In the Zodiac, star, and bathing pages, figures, stars, labels, containers, and positions do not appear arbitrarily. They repeat, but they are not fully identical. Precisely this mixture of repetition and deviation is conspicuous.
Derivation: In a template or register system one needs more than text values. One needs anchor points. A slot is a place where a state can sit. A star can mark a state or coupling point. A figure can be the visible carrier of that slot.
RIA integration: Nymphs and figures are therefore treated as slot/RECORD carriers. Stars are treated as template/STATE anchors. Labels remain PAYLOAD. Ring, sector, basin, tube, or block opening remain MARKER. This explains why missing stars, weak star traces, container figures, differing postures, or missing labels need not immediately be errors, but may be boundary cases of a system.
Status: Strong as a template-logic candidate. Not proven as a lost physical tool. No stars-as-bits claim. No nymphs-as-data-packets claim.
6. Curved Circular Templates -> Timing Generator / Transfer Function
Public finding: Some diagrams show not merely straight sector lines, but curved, vortex-like, or dynamic line fields. This especially concerns circular template areas such as f57v and dynamic axes in the rosettes.
Derivation: A straight sector disc divides. A curved disc modulates. Once lines are not radial, they intersect angle or segment grids at changing radii. A simple position system then becomes a distorted transfer surface: same angle, different radius, different intersection point.
RIA integration: These curved templates are treated as timing-generator, frequency-divider, or transfer-function candidates. Not because a historical apparatus is proven, but because they could formally take on exactly the role that a rigid register lacks: delay, phase shift, jump logic, and non-linear selection.
Status: Strong as functional metaphor and test assignment. Not proven as algorithm. Not released as a concrete cipher curve.
7. The Rosettes Foldout -> Central System Board / Mainboard Candidate
Public finding: The large Rosettes foldout is the most complex visible system sheet of the manuscript. It connects several circles, centers, margin structures, tubes, transitions, and dense fields into a total surface.
Derivation: If the individual sections show registers, slots, buses, timing markers, and control surfaces, then the Rosettes foldout is the natural place to expect the coupling of all subsystems. Not as a geographic map, but as a system overview: inputs, main center, couplings, outputs.
RIA integration: The Rosettes foldout is therefore treated as a mainboard or system-board candidate. Upper areas may be input registers or calibration surfaces, the center may be read as a central CONTROL or processor-like area, and lower areas may be output or test registers. The tubes are then not decoration, but visible coupling axes between functional surfaces.
Status: Strong as a bridge for the overall model. Not proven as a real mainboard. No historical computer claim.
The Closed Dynamic System Model
The derivation can be read as a working chain:
[ ARIES ANOMALY ]
Initialization / reset / starting state
|
v
[ ZODIAC CIRCLES / CIRCULAR TABLES ]
Registers / static data sets / control surfaces
|
v
[ STARS + NYMPHS / FIGURES ]
Template anchors / slots / state carriers
|
v
[ CURVE TEMPLATES / VORTEX LINES ]
Timing deformation / transfer function / phase shift
|
v
[ TUBES / PORTS / TRANSITIONS ]
Coupling / graph / filter / transitions
|
v
[ PHARMA BANDS ]
Segmentation / object-text coupling / local reference
|
v
[ GALLOWS ANCHORS ]
Block opening / timing / formal channel change
|
v
[ CIRCULAR AND ANGULAR MATRIX ]
Position space / output register / CONTROL candidate
[ ROSETTES FOLDOUT ]
Higher-level system board / coupling and control surface
This is the form that is understandable for a broader audience: not a single mysterious sign solves everything. Instead, the coupling of many publicly known disturbances produces a system image.
The hard sentence remains: The model explains several known Voynich anomalies as layers of a formally testable, non-semantic mechanism.
The blocked sentence remains: The model proves the decipherment of the Voynich Manuscript.
Why the Aries Context Is So Strong for Me
Aries is not strong for me because a single page contains a striking image. An isolated anomaly would be too little. Aries becomes strong only in context.
First, Aries lies at a place where a system start is plausible. In the annual cycle, Aries is not just any sign, but a candidate beginning. Even if every astrological interpretation is blocked, the formal role remains: beginning, transition, cycle start, calibration.
Second, Aries is doubled. Instead of a smooth 30-structure, a split 15+15 pattern appears. That is exactly what makes it operationally interesting for me, not decorative. A 30-circle can be calendar, list, or register. Two 15-halves at the starting point, by contrast, look like initialization: first split, then continue counting.
Third, Aries does not stand alone. Other Zodiac pages act as control surfaces: Cancer stabilizes the 30/30 case, Gemini shows the strong NULL special case, Pisces carries a central CONTROL candidate, Taurus light/dark shows the contrast between a clean half-register and physical ambiguity. Aries is therefore not a pretty idea, but part of a comparison series.
Fourth, Aries fits exactly into the IT lens. When I say BIOS, I do not mean a modern computer BIOS in the historical sense. I mean a structural metaphor: a start/reset/initialization area in which basic states are set before the system moves into other register areas.
Fifth, non-semantics are precisely the point. Aries does not have to mean “Aries means X.” It only has to perform formally: start position, split, state change, control relation. These four things are enough for it to become strong as an initialization gate in the model.
The hard sentence is not: Aries is a proven BIOS.
The hard sentence is: The Aries doubling is, in the register context, a particularly strong initialization candidate because it lies at the cycle start, breaks the 30-schema into 15+15, and is formally connectable through other Zodiac control cases.
For me personally, exactly this context is the key. Not the single page. Its position in the system.
Why the Tube and Bus System Is So Strong for Me
The tubes are not strong for me because they look like modern lines. That would be too simple. They become strong because they repeatedly appear precisely where separated areas are coupled: basin with basin, body with transition, image zone with text zone, upper level with lower level.
For an IT analyst, that is not a minor ornament. It is a coupling structure. I say bus system not to press medieval material into a modern computer image. I use the word as a working metaphor: a bus is a shared connection layer. It does not itself carry meaning; it couples carriers, states, and target areas. That is exactly how I read tubes, funnels, channels, transitions, and port points.
The strong point is repetition across different pages. In the Balneo pages, basins, tube runs, port points, and text zones form a graph-capable architecture. f78r is not an isolated accident: f81r, f83r, and f84r show related but not identical graph forms. That matters. If all pages were the same, it would be template compulsion. If all were completely different, it would be free decoration. Here there is something in between: the same grammar, different expression.
This tube logic also explains why the images are not simply illustrations next to text. The page organizes paths. It does not merely show objects; it shows transitions between objects. In the RIA grid this means NODE, PORT, EDGE, PAYLOAD, and CONTROL can be handled separately. A bathing page thereby becomes a testable network.
The protection sentence remains important: tubes are not proven data buses, nymphs are not bits, and flow direction is not released meaning. As a formal coupling model, however, the tube structure is strong because it closes the gap between static registers and dynamic processing. Without this coupling, the circles would be only tables and the text blocks only text. With it, a system flow emerges.
The hard sentence is not: The tubes are proven data buses.
The hard sentence is: The tube, port, and basin structures form a strong graph/coupling candidate because, across several folios, they repeatedly connect separated image, text, and object zones and thereby become testable as a formal interface layer.
For me personally, exactly this coupling is decisive. Aries sets the beginning. The circles hold registers. But without tubes, ports, and transitions, the model would have no moving body.
Why the Circular Tables and Data Sets Matter
The circular and ring texts are not merely decorative captions for me. They are the area in which the manuscript most strongly behaves like an ordered data surface. Precisely because text, figures, stars, segments, inner/outer rings, and centers appear together here, these pages are so important for the model.
Running text is linear. A circular table does something else: it orders entries by position, ring, sector, proximity to the center, and relation to visible objects. A register idea arises immediately. Not in the sense of proven storage, but in the formal sense: an entry does not stand somewhere, but at a specific address in the layout.
The Zodiac circles and diagram pages are therefore, for me, the static data sets of the model. They provide stable areas against which other sections can even be tested. If Gemini shows a NULL case, Cancer works as a 30/30 control, Pisces carries a central CONTROL candidate, and Aries breaks the 30-field into 15+15, then these are no longer loose curiosities. They are register cases.
The circular tables are also important because they make the difference between PAYLOAD and CONTROL visible. A label can be payload. A star can be state. A ring can be address. A center can be control. A sector can be selection space. This separation is hard to see in running text, but almost imposed by circular diagrams.
When I say ROM or database, that too is an IT metaphor. I do not mean a modern electronic storage unit. I mean a static reference surface: something from which a procedure could obtain values, states, or selection possibilities. Without such static reference surfaces, the manuscript would have to carry everything in running text. It apparently does not do that. It distributes information across image, circle, ring, label, and position.
The hard sentence is not: The circular tables are proven databases.
The hard sentence is: The circular, ring, and Zodiac structures are strong register/data-set candidates because they couple text, object, state, segment, and center in stable positional spaces and thereby provide a formal reference layer.
For me personally, these circular tables are the resting storage of the model. They are what remains once every translation is blocked: ordered data sets without released semantics.
Why Bus and Circular Tables Carry the Mechanism Together
Only together do the two levels become strong. Circular tables without coupling would be isolated diagrams. Tubes without registers would be confusing lines. The mechanism candidate arises only when both are read together: static reference surfaces on one side, dynamic coupling and transition structures on the other.
That is the actual IT lens: a system needs not only data. It also needs paths. It needs states, boundaries, timing, and control points. That is why no single finding is enough for me. Not Aries alone, not Gallows alone, not Balneo alone, not Pharma alone. The model becomes strong because the roles recur across sections.
The circular tables answer: where are the entries and states? The tube/bus model answers: how are separated areas connected? Gallows answer: where does a block or mode begin? Pharma shows: how is local segmentation organized? Herbal shows that, even in a very different section, image, sub-object, color, and text proximity are layered.
This produces a dynamic reading frame without translating a single word. That is the core for me: meaning does not generate the order; the order is already visible before meaning is released.
The short system formula is:
[ ARIES ] sets the starting state.
[ CIRCULAR TABLES ] hold registers and static reference data.
[ STARS ] mark template/STATE anchors.
[ NYMPHS / FIGURES ] form slot/RECORD carriers.
[ CURVE TEMPLATES / VORTEX LINES ] deform timing and positional access.
[ TUBES / PORTS / TRANSITIONS ] couple and route between areas.
[ PHARMA BANDS ] segment local object-text groups.
[ GALLOWS BLOCK OPENINGS ] time formal text blocks.
[ ROSETTES FOLDOUT ] bundles the subsystems as a system-board candidate.
[ ANGULAR AND CONTROL SURFACES ] order output and control spaces.
This is not a decipherment. But for me it is a closed system image strong enough to be reviewed publicly.
Why Stars Are Strong Template and STATE Marker Candidates
The stars are not strong for me because they look attractive, or because stars would be expected in an astronomical manuscript. They become strong only because, in the Voynich context, they are repeatedly coupled to figures, rings, segment boundaries, text proximity, and centers. They rarely stand fully free in empty space. They sit on bodies, beside bodies, above hands, at ring positions, or in fields that already behave like register or control surfaces.
When I read stars as template elements, I do not mean that every star carries a finished meaning. I mean that stars can function as recurring anchor points at which a template logic becomes visible. A star then marks not the sense, but a state, a position, a selection point, or a coupling. This fits the RIA grid: the body or figure is the RECORD carrier; the star is a STATE or anchor channel; the label is PAYLOAD; ring, sector, or line are MARKER; the center or circular logic remains CONTROL.
The strong point is the separation. Once stars are no longer treated as illustration but as their own channel, it becomes visible why some pages feel so mechanical. The figure alone is not enough. The label alone is not enough. Only figure plus star plus ring position plus text proximity produces a testable data set. That is why the small stars are not a side issue for me. They may be the points at which the visible template grips the layout.
This applies especially where stars are missing, weak, reconstructed, or visibly executed differently. In a purely decorative system, a missing or weak star may be only damage or carelessness. In a formal system it becomes a test point: is the figure still present? Is the label still present? Does the position remain? Is there a homologous star on a neighboring figure or another ring? Such questions turn ornament into a template hypothesis.
The hard sentence is not: Stars are proven templates or bits.
The hard sentence is: The star structures are strong template/STATE marker candidates because they repeatedly couple figures, ring positions, labels, and control surfaces, forming a separate non-semantic test channel.
For me personally, the stars are the small nails in the board. Without them, figures and labels would have less hold. With them, the page becomes a marked working surface.
Why the Different Nymphs Matter as Slots
The nymphs are not strong for me because they depict people. The opposite matters: I do not need to know who they are. I do not need to know what they mean. I only need to see that they stand in the layout as recurring but distinguishable bodies. That makes it possible to read them as slots.
In IT terms, a slot is not content, but a place that can carry content. That is how the nymphs behave in the model: they stand at ring positions, in basins, in containers, at tubes, beside stars, near labels, or in zones separated from one another. Their differences - posture, gaze direction, clothing, container, hand position, star relation, body position - are therefore not automatically meaning, but they are formal state features.
It matters that the nymphs are not all the same. That is what makes them strong as slots. If they were completely identical, they would be mere counters. If they were completely freely invented, any system reading would be weak. They lie in between: recurring enough for a register, different enough for states. This intermediate position is the core for me.
In Zodiac, nymphs can be ring slots: bodies at a position, often with star and label. In Balneo they can be node or state carriers: bodies in basins, at tubes, in transitions. In Pharma the nymph logic does not appear identically, but the idea remains: visible object carriers stand in local relation to text zones and layout boundaries. The carriers change, the role remains recognizable.
This also explains why pure text analysis falls short. If the body itself is a slot, then part of the information is not in the word, but in the position of the body and in its visible attributes. That is not semantics. It is layout mechanics.
The hard sentence is not: Nymphs are proven data slots.
The hard sentence is: The different nymphs are strong slot/RECORD candidates because they appear as recurring bodies at register, graph, and layout positions and there bundle state features, star relation, text proximity, and transitions.
For me personally, the nymphs are the sockets of the system. The stars mark states. The labels carry payload. The position turns it into a register.
Why Stars and Nymphs Together Open the Template Logic
Only together do stars and nymphs become truly strong. A nymph alone is a figure. A star alone is a sign. A label alone is text. Together, however, they form a testable slot: body plus state plus payload plus position.
This is the point that pulls the template idea out of pure speculation for me. A template needs anchors. It needs places where something locks in. In the Voynich context, these anchors may be visible: body positions, star positions, ring sectors, label proximity, block openings, tube transitions. The template therefore does not necessarily have to be a lost physical tool; it can also appear as layout logic within the manuscript itself.
This explains why some figures have stars, some weak star traces, some no clear label, and some stand in containers or tubes. These deviations are not immediately errors, but test cases. A template system shows its strength not only in the rule, but in boundary cases: NULL, EXTRA, START, CONTROL, weak star, hidden body, missing label.
The hard sentence is not: Stars and nymphs prove a lost template.
The hard sentence is: Stars and nymphs together form a strong template-logic candidate because they generate recurring slot-state-payload packages that remain testable across ring, graph, and layout areas.
For me personally, this is one of the most alive parts of the model: the page is not merely written on. It is plugged, marked, and timed.
Why Curved Circular Templates and Vortex Lines Are Strong
Not every drawing in the manuscript behaves like a static table. Some circles and rosette axes show curved, vortex-like, or dynamic lines. These forms matter to me because they break open the rigid register model.
A straight circle with sectors can count, order, and store. A curved circular template can do more: it can shift. It can delay. It can intersect an angle at different radii. A simple two-dimensional grid becomes a transfer surface. The same angle can land at a different point depending on the curve. That is interesting for a formal system because it breaks repetition without creating arbitrariness.
When I say timing generator, frequency divider, or cam disc, I again mean laboratory language. I do not claim a historical metal apparatus. I mean a mechanical-symbolic role: a surface that transforms linear timing into non-linear selection. In the IT lens, this would be a transfer function. In the template lens, it would be a curve that decides which next slot becomes valid.
This explains why such drawings are not marginal art for me. They may be exactly the places where the system switches from a rigid table mode into a dynamic mode. The Zodiac circles hold registers. The curved circular templates may modulate access to these registers.
The hard sentence is not: The curved lines are proven algorithms or real mechanical cam discs.
The hard sentence is: Curved circular templates and vortex lines are strong timing-generator/transfer-function candidates because they geometrically distort a rigid angular or register grid and thereby make a non-linear selection or coupling logic testable.
For me personally, these lines are the movement in the system. The circles store. The tubes couple. The Gallows time. But the curves can deform the timing.
Why the Rosettes Foldout Looks Like the System Mainboard
The large Rosettes foldout is not simply a world image for me, nor merely a decorative overview. It is the sheet on which the previously separated subsystems most visibly come together: circles, centers, tubes, margin structures, dense fields, transitions, and several coupled functional surfaces.
When I say mainboard, I do not mean a modern computer board in the historical sense. I mean a system board as metaphor: a central surface on which registers, buses, timing surfaces, control zones, and output areas are visibly interconnected. That is precisely why the Rosettes foldout is so strong for me. It does not merely show individual elements; it shows the coupling of elements.
In this reading, the upper circles can be treated as input or calibration registers. A curved rosette can be a timing or frequency-divider candidate. A symmetrical wheel can be read as a synchronization surface. A dense detail field can act as a fine-grained selection table. The center becomes the large CONTROL candidate: not as a proven CPU, but as the main node where visible axes converge.
The tubes and connecting paths are decisive. Without them, the rosettes would be individual pictures. With them, the page becomes a coupled surface. Top, center, and bottom are then not isolated, but levels: input, processing, output, or control. The margin structures, towers, gate-like, or fortress-like forms are not automatically architecture in the literal sense. They can be tested as boundary gates, margin markers, or transition structures.
The lower rosettes are also not read semantically in this view. A mesh field can be treated as a fine angular-matrix candidate. A star field can appear as a test or STATE field. A funnel or outflow area can be read as an output/interface candidate. All of this remains formal. No value, no language, no translation is released.
The hard sentence is not: The Rosettes foldout is a proven mainboard or a real machine.
The hard sentence is: The Rosettes foldout is a strong system-board/mainboard candidate because it bundles register, curve, tube, control, and output structures into one coupled total surface and thereby becomes testable as an overview of the mechanism.
For me personally, this page is the great convergence. One sees not only parts. One sees why the parts might belong together.
Why All Drawings May Have Function - But Not Arbitrarily
The sentence “all drawings have function” is dangerous if misunderstood. It must not mean that every line has a secret meaning that I can freely interpret. That would be drift.
In the RIA model, the sentence means something else: every drawing may first be tested as a possible carrier of a formal role. A plant can be RECORD. An organ can be SUBRECORD. A nymph can be slot. A star can be STATE anchor. A tube can be EDGE. A circle can be register. A curve can be transfer surface. A rosette can be CONTROL or system surface.
This proves nothing automatically. But it prevents image areas from being set aside too early as mere illustration. In the Voynich Manuscript in particular, the separation between text and image is too hard. Many pages look as if text, image, and layout are working together. Therefore all drawings must first be tested as possible structure carriers before they are called decorative.
The hard sentence is not: Every drawing is proven function.
The hard sentence is: All drawings are tested in the RIA model as possible formal carriers, but only roles supported by repetition, coupling, position, counterexample, and falsifiability remain in the model.
This is the boundary that protects the model: open enough to take the drawings seriously; hard enough not to claim everything.
My Personal Analogy: The RIA-MS408 OSI Layer Model
This analogy is important to me because it brings the entire mechanism into a form that IT people immediately understand. I am not claiming that the Voynich Manuscript is a modern network protocol. I use the OSI model as a thinking image: a layer model showing how a system can be built from lower carriers, states, connections, timing, formatting, and visible output.
This is what makes the manuscript graspable for me. It no longer looks like a collection of individual riddles, but like a protocol stack made of parchment, image, figure, star, tube, circle, angle, block opening, and text. Each layer does not have to speak the same language. It only has to fulfill its role in the stack.
The personal analogy is:
Layer RIA-MS408 role in the analogy
Layer 7: Application final text on the parchment / running text
Layer 6: Presentation component-based token construction / formatting
Layer 5: Session Gallows interface / timing and block control
Layer 4: Transport tubes, funnels, channels / bus and coupling system
Layer 3: Network angular matrix, rosette distributors, routing surfaces
Layer 2: Data Link nymphs, stars, slots, state and test candidates
Layer 1: Physical Aries anomaly / starting state / zero-point calibration
Here too the RIA brake applies: these layers are not a historical claim, but a functional reading lens. They make visible why the individual parts might work together.
Layer 1: Physical Layer - Aries as Start and Zero-Point Candidate
The lowest level for me is the Aries context. Not as a proven BIOS, but as the starting area of the model. The split 15+15 structure behaves like zero-point calibration: before a register, slot, or text block can be read meaningfully, it must be defined in which basic state the system begins.
In the OSI analogy, Aries is therefore the physical grounding: the point where the system receives its beginning, its split, and its first state. Without this start context, the later registers look like loose circles. With it, they obtain a direction in the system.
What remains blocked: Aries = proven BIOS. What remains allowed: Aries = strong start/initialization candidate.
Layer 2: Data Link Layer - Stars and Nymphs as Slot and STATE Layer
The second level contains the nymphs and stars. The nymphs are not proven data packets. But as recurring bodies at positions they behave like slot carriers: they sit, stand, dive, hold stars, are partly missing, hidden, or dressed differently. Precisely these differences make them strong as RECORD and slot candidates.
The stars form the separate STATE channel. They can be present, weak, colored, dotted, reconstructed, or absent. This variation itself behaves like a safeguarding and state surface. A star does not have to carry “meaning.” It may only mark: this slot has a state, this body is coupled, this position is active or testable.
The Gemini NULL context fits this level because body, position, and label gap come together as a test point. Pisces, with its central control candidate, also belongs here as a bridge. Not as a proven check bit, but as a STATE/CONTROL question.
What remains blocked: Stars = bits, nymphs = data packets. What remains allowed: Stars and nymphs form strong slot/STATE/RECORD candidates.
Layer 3: Network Layer - Angular Matrix, Rosettes, and Routing Surfaces
The third level is addressing. Here sit the circular diagrams, rosettes, segmentations, and angular relations. A linear script has sequence. A circle has position, sector, radius, center, and direction. This produces routing: a value can lie not only before/after, but in an angular space.
The 20-degree matrix is not a proven decoder in this analogy, but a routing candidate. The same applies to the Rosettes foldout: in this model it behaves like an upper-level distribution surface in which several circles, axes, tubes, and control spaces are brought together.
The curved templates also belong here. They would not be direct output, but a transfer function: they could distort a straight angle or register run, shift it in phase, or move it to another radial point. A rigid grid becomes a dynamic position space.
What remains blocked: Rosette = proven CPU, 20 degrees = proven code. What remains allowed: Rosettes, angles, and curved templates are strong mediation/routing candidates.
Layer 4: Transport Layer - Tubes, Funnels, and Channels as Bus Candidate
The fourth level is the transport level. Here sit tubes, funnels, channels, basins, ports, and transitions. These forms are strong because they visibly couple separated areas. They connect top and bottom, left and right, basin and basin, body and text zone, input and output.
In the OSI analogy, this is the bus. Not as a proven data line, but as a coupling layer. A bus does not have to possess meaning itself. It connects carriers and target areas. That is what the tubes do in the model: they give the static register world a moving body.
Balneo especially carries this layer: f78r with port points, f81r as control graph, f83r as a different node type, f84r as a multilevel basin and connection layer. The repetition is not identical, but grammatically related. That makes it strong as a layer.
What remains blocked: Tubes = proven data buses. What remains allowed: Tubes, funnels, and channels = strong transport/graph/coupling candidates.
Layer 5: Session Layer - Gallows as Timing and Block-Opening Interface
The fifth level is timing. Here sits the strongest formal text finding: Gallows at block openings. The coupling of @P0/@P1 paragraph block starts with Gallows line-open is massive. This is exactly why my model does not primarily read Gallows as ordinary letters, but as opening or timing markers.
In the OSI analogy, this is the session layer: it does not decide what a word means, but when a block begins, when a mode becomes active, and where a section is formally opened. The suppression phenomenon f99v is especially important here: it shows that visible block structure and Gallows activation do not always have to run identically. That speaks more for a mode than for simple decoration.
What remains blocked: Gallows = opcodes or commands. What remains allowed: Gallows block openings = hard timing/interface candidate.
Layer 6: Presentation Layer - Pharma and Token Construction as Formatting Level
The sixth level is presentation. Here local structures are brought into a visible text or token format. Pharma matters to me because it shows that object groups, vessel columns, text proximity, and band boundaries work together without requiring the section to be a literal recipe.
In the OSI analogy, Pharma is a formatting and segmentation level. The data are no longer only transported; they are pressed into local groups: object group, text zone, reference object, band boundary. f99r shows a strong TYPE-A case. f100r, as TYPE-D, shows that the vessel column on the left is not a globally mandatory operator. The system therefore remains flexible.
What remains blocked: Pharma = recipe. What remains allowed: Pharma = strong variable band and presentation layer.
Layer 7: Application Layer - Visible Running Text as Output
The top level is the text we see. In this analogy it is not the start of the analysis, but the end of the stack. The running text is the user interface of the system: the visible result of starting state, slot/STATE layer, routing, transport, timing, and formatting.
This explains for me why the text looks language-like but resists natural language in many respects. It could be output emerging from several formal layers, not from a simple plaintext alphabet.
What remains blocked: Running text = proven output of an apparatus. What remains allowed: In the model, running text is the final visible output layer.
Why This Analogy Rounds Off the Document for Me
The OSI model is the calmest summary of the entire project for me. It does not force anything into a modern technology claim. It only shows that a complex system can consist of layers in which each level has its own task.
The analogy also makes clear why I no longer believe in pure text. If one looks only at layer 7, the manuscript appears as a language puzzle. If one sees all layers together, it appears as a functional transmission and generation structure.
The hard sentence is not: MS408 is a seven-layer data-transmission machine.
The hard sentence is: The OSI layer model is a personal, functional analogy that brings the observed RIA roles - start, slot, state, routing, transport, timing, formatting, and output - into a testable system order.
For me personally, that is the closure: not one sign solves the manuscript. The stack makes it understandable.
Claim Boundary
This document works with a strict boundary between finding, model, and personal conclusion.
Category Boundary
What is claimed MS408 shows a formally testable structure candidate. Several sections can be described as layered information layouts. The roles RECORD, STATE, PAYLOAD, MARKER, and CONTROL are viable as a working model. Gallows block openings are a hard formal text finding. Zodiac, stars, nymphs/figures, Pharma, Balneo, Herbal, curved circular templates, and Rosettes provide recurring but differing carriers of the same layer logic.
What is not claimed No translation, no plaintext, no language identification, no alphabet, no substitution, no opcode, no firmware, no medical or botanical identification, no recipe as fact, no stars-as-bits claim, no nymphs-as-data-packets claim, no cam-discs-as-proven-algorithms claim, no rosettes-as-proven-mainboard claim, and no true decipherment.
Guiding rule MS408 shows a formally testable, non-semantic structure candidate with recurring layered roles and strongly supported block-opening/layout signals.
Blocked guiding formula MS408 is deciphered.
Quality-Gate Evidence Chain
The evidence chain is not a smooth victory march. It is a workshop path with brakes.
REC Content Status
REC-01 / QG1 Circular-graphic, EVA, and crop basis; kanchas as image/circular-graphic candidate basis secured
REC-02 / QG2 15/30 Zodiac register model; START / NULL / EXTRA / CONTROL separated strong test model
REC-03 / QG3 Q3 pretable; f72r2 NULL strong; f72r1 EXTRA quarantined; 22.5 degrees blocked private
REC-04 / QG4 Mechanism matrix across Zodiac, Herbal, Balneo, Pharma, and text-only areas cross-section supported
REC-05 / QG5 Balneo graph-capable; Pharma band architecture; Gallows line-open hard confirmed structure supported
REC-06 / QG6 GALLOW_BLOCK_OPEN strongly supported; IF3 visually strongly supported; Q3 frame pass, no final lock private
REC-07 / QG7 Publication polish lock; formal output path; review lock; archive/no-input locks review candidate
The chain is strong because it does not wave everything through. Micro-reading, semantics, substitution, rigid 22.5-degree geometry, recipe reading, opcode language, and overly smooth AI confirmations were braked or blocked.
Core Model: RECORD / STATE / PAYLOAD / MARKER / CONTROL
The model does not read MS408 first as text, but as a coupling of several visible levels.
Role Working definition
RECORD Primary object, carrier unit, nymph/figure, or visible slot body.
STATE State, feature, color, star, star shape, posture, or emphasis.
PAYLOAD Text proximity, label, token sequence, or local text block.
MARKER Start, gap, margin, ring, block opening, star anchor, or layout boundary.
CONTROL Center, axis, dominant organ group, node, or reference column.
These roles are not a translation. They are an IT grid: What is the carrier? What is the state? What is the text load? What is the boundary? What locally controls or orders? And it goes considerably further. The value of the model is not that every section looks identical. On the contrary: the carriers change. That is precisely what makes it systemically interesting.
Zodiac: Registers, Start, and Special Cases
The Zodiac group is the strongest image-textual register area. Aries is the initialization candidate: doubled, split, at the cycle start, connectable to 15/30 logic.
Gemini f72r2 remains the strongest NULL special case: a physical intermediate anchor is locally supported, but functionally not released. Pisces f70v2 remains a CONTROL candidate: central object and 29/30 tension are formally strong, but not proven as parity bit. Cancer f72r3 remains the control case for 30/30 and START_ONLY: important precisely because not every special case looks like Gemini. Taurus light/dark stabilizes the contrast logic: clean half-register case versus physically active but not finally confirmed EXTRA trace.
Stars and nymphs visibly carry this register logic with them: the figure forms the slot, the star the state/template anchor, the label the text load, and the ring position the address. Exactly this fourfold coupling makes the Zodiac group central for the mechanism.
Status: ZODIAC_MECHANISM = STRONGLY SUPPORTED. Q3_FINAL = OPEN.
Balneo: Graphs Instead of Decorative Baths
The Balneo section is not read as a “bath story,” but as a graph-capable structure. Visible elements include basins, tubes, transitions, port points, nymph positions, text zones, vertical and horizontal couplings. This permits a node/edge test.
Allowed: NODE = basin, node, transition, nymph, tube mouth. EDGE = visible connection or tube run. PORT = connection or transition point. PAYLOAD = text zone or text proximity. CONTROL = main basin, main node, or axis as candidate.
Blocked: Tubes are data buses. Nymphs are bits. Flow direction is meaning. Basins are storage.
Status: BALNEO_GRAPH = SUPPORTED / MARKUP REPLICATION REQUIRED.
Pharma: Band Architecture Instead of Recipe Claim
At first glance the Pharma section appears recipe-like. That is exactly where caution is necessary. The hard finding is not: take four of this and three of that. The hard finding is: there is a variable object/text band architecture.
A band can consist of: vessel or reference object, object group, text proximity or text block, horizontal or local layout boundary. f99r is strong as TYPE-A. f88v brakes the overly smooth text-block assignment. f100r, as TYPE-D, shows that the left vessel column is not a globally mandatory operator. This does not weaken Pharma, but makes it more honest: it is not a simple recipe table, but a flexible band structure.
Status: PHARMA_BAND_ARCHITECTURE = STRONGLY SUPPORTED AS STRUCTURE. RECIPE = BLOCKED.
Gallows: The Strongest Formal Text Finding
The Gallows trace is the hardest formal text finding. Paragraph block openings @P0/@P1: 229 lines, 200 of them LINE_OPEN with Gallows, share: 87.34%. Remaining paragraph lines: 3,728 lines, 697 of them LINE_OPEN with Gallows, share: 18.70%. Statistic: odds ratio approximately 29.99, p approximately 9.33e-104.
The artifact brake matters: the @ sign alone does not explain the effect. Non-paragraph lines with @ fall back to baseline.
Admissible: Paragraph block openings are massively and reproducibly coupled with Gallows line-open.
Blocked: Gallows are opcodes.
Status: GALLOW_BLOCK_OPEN = STRONGLY SUPPORTED. IF3 = STRONGLY SUPPORTED. IF4 = OPEN.
Q3: Why I Do Not Force the Final Lock
Q3 remains open. This is a deliberate decision. The global frame carries. But pixel-level precision would be dishonest because the source is soft: faint contours, hand drawing, parchment distortion, fold and panel deformation, unclear star/label boundaries, overlapping ring texts.
Therefore: Q3_FRAMEPASS = PARTIAL_PASS. Q3_FRAME_BASED = ACTIVE. Q3_FINAL = OPEN. 22.5 degrees = BLOCKED.
For me, this does not weaken the work. It protects it. Whoever claims too much here destroys the core.
Adversarial Review: What Critics Should Attack
This document invites refutation. Attack points:
1. Does the Gallows block-open finding replicate on alternative transcriptions?
2. Does @P0/@P1 remain visually coupled corpus-wide to real text block starts?
3. Does the 15/30 Zodiac register logic hold under independent object marking?
4. Does Aries remain strong as an initialization candidate if astronomical start assumptions are removed?
5. Does Balneo remain graph-capable under a second independent node/edge marking?
6. Does Pharma remain band architecture when recipe intuition is completely blocked?
7. Does IF3 remain stable under controlled covariates?
8. Is there a more natural explanation that explains all sections together more simply?
9. Does the tube/bus hypothesis hold if a second person independently marks nodes, ports, and edges?
10. Do circular tables remain stable as register/data-set candidates if the terms ROM and database are fully removed?
11. Do stars remain stable as template/STATE markers if every astronomical meaning is blocked?
12. Do different nymphs remain stable as slot/RECORD carriers if a second person independently codes figures, star relation, label proximity, and position?
If these points fall, the model falls. If they hold, the model must be taken seriously, even without semantics.
What I Consciously No Longer Do
I will not expand this project further only to get a stronger feeling. I will not turn Aries into a final BIOS proof. I will not turn tubes into data buses. I will not turn Pharma into a recipe. I will not turn Gallows into opcodes. I will not turn curved templates into proven algorithms. I will not turn the Rosettes foldout into a real mainboard. I will not claim that every drawing automatically has a deciphered function. I will not turn stars into proven bits. I will not turn nymphs into proven data packets. I will not pretend that silence from Yale, forums, or researchers has confirmed or refuted anything.
What I do: I make the circle open. I make the brakes open. I make the strongest findings open. And I make the open wounds open. That is my closure.
Status Formula
Category Status / Statement
Final working status Mathematical blueprint: completed in the sense of a formal review candidate.
Working paper Review-capable.
Gallows block-open Strongly supported.
Stars as template/STATE markers Strong candidate.
Nymphs as slot/RECORD carriers Strong candidate.
IF3 Strongly supported.
IF4 Open / not locked.
Q3_FINAL Open.
Semantics Not released.
Substitution Not released.
Plaintext Not released.
Opcode Blocked.
True decipherment 0%.
OSI layer model Personal functional analogy / not presented as historical proof.
Personal status The circle is closed for me.
External status The world may test it.
Workshop protocol, formal structural approach, and controlled release for external review
Author SirJoe
Version formatted English review copy
Date 2026-05-25
Status Review Candidate / personal closing version / no semantic release
Claim boundary: This document claims no plaintext, no translation, and no true decipherment. It presents a formally testable, non-semantic structure candidate for external review.
Contents Overview
1. Preface: It All Began with a Spark
2. Personal Closing Formula
3. The Derivation Chain: From Public Findings to the RIA System
4. The Closed Dynamic System Model
5. Why the Aries Context Is So Strong for Me
6. Why the Tube and Bus System Is So Strong for Me
7. Why the Circular Tables and Data Sets Matter
8. Why Bus and Circular Tables Carry the Mechanism Together
9. Why Stars Are Strong Template and STATE Marker Candidates
10. Why the Different Nymphs Matter as Slots
11. Why Stars and Nymphs Together Open the Template Logic
12. Why Curved Circular Templates and Vortex Lines Are Strong
13. Why the Rosettes Foldout Looks Like the System Mainboard
14. Why All Drawings May Have Function - But Not Arbitrarily
15. My Personal Analogy: The RIA-MS408 OSI Layer Model
16. Claim Boundary
17. Quality-Gate Evidence Chain
18. Core Model: RECORD / STATE / PAYLOAD / MARKER / CONTROL
19. Section Models: Zodiac, Balneo, Pharma, Gallows, Q3
20. Adversarial Review: What Critics Should Attack
21. What I Consciously No Longer Do
22. Status Formula
Preface: It All Began with a Spark
It all began with a spark. Not with an academic plan. Not with an institute. Not with a completed model. It began with that one inner moment: something is off here. There is something. An order is gripping the material, but I cannot yet name it.
I first seriously heard and read about the Voynich Manuscript roughly one month ago. I did not come from Voynich research, not from a school, not from an old debate. I entered as an analyst and IT-minded observer: with a systems view, with mistrust toward overly smooth explanations, and with the reflex not to read an unknown structure first as text, but as structure.
Even language uses mathematical regularities. That was where my curiosity and project mode began. It was not smooth or elegant from the start. It contained curiosity, overreach, AI drift, embarrassment, correction, hard brakes, false trails, better trails, rollback, and counter-checking. That is exactly why this document is not a victory text. It is a closure: a deliberately set line under a working state.
It would itself become a form of drift if the checking, and thus the project, had no end. I do not claim to have deciphered the Voynich Manuscript. I claim no plaintext, no alphabet, no language, no translation. I prove nothing in the academically final sense. I have been there before. What I close is a circle for myself, through the lens of an IT analyst.
For me personally, the evidence chain is sufficient. Not as an unshakable final scientific proof, but as a working certainty: in essential areas, the manuscript behaves less like ordinary running text and more like a layered, formally organized system of image, text, position, markers, and control structures.
Whether others later prove, refute, improve, or dismantle this lies no longer with me. I am making the current state open enough so that exactly this becomes possible. The forums excluded me. Yale and other prominent institutions have not reacted so far. Today I understand why. I do not take that as evidence against my work, and I do not take it as evidence for it. It is only the external state.
Internally, I have reached the point where duty calls again and I do not want to carry this project any longer under pressure. I would like to thank Mr. Klaus Schmeh for replying to my e-mail. What carries, I name clearly. What is only metaphor remains metaphor. What is personally closed for me is not sold as scientifically closed.
All documents and protocols have been secured. This document is therefore two things: a review candidate for others and a workshop closure for me. The full workshop protocol, from the first to the last day, including all its highs and lows, derivation chains, the embarrassing AI drift, the RIA project that emerged against drift, and further projects, I will write when there is time and desire again. The world may now work on it. Regards, Maik Jörn
Personal Closing Formula
This project ends for me with a simple distinction.
Formally: no true decipherment, no semantic release, no plaintext.
Personally: I have seen enough that I can no longer dismiss the mechanism candidate as random. For me, the circle is closed. Not because every stone is watertight, but because the way the stones lie together produces a system form. Like a puzzle, the pieces are in front of us.
Others do not have to turn this into belief. Quite the opposite: they should test it. They should attack it. They should show where I am wrong. But they should not look only at individual stones. They should look at the coupling: Aries, register logic, stars as template/STATE anchors, nymphs as slot/RECORD carriers, Gallows block openings, Pharma band structure, Balneo graphs, Herbal layering, and the consistent separation of RECORD, STATE, PAYLOAD, MARKER, and CONTROL.
The Derivation Chain: From Public Findings to the RIA System
This document is written for anyone who does not want to wait for the full workshop protocol. It shows why the approach does not come out of nowhere. Many individual observations about the Voynich Manuscript are public or have been discussed for years: word repetitions, Currier A/B, circular and rosette structures, conspicuous Zodiac special cases, labels, figures, tubes, text blocks, stars, differing nymphs, curved circular templates, rosettes, and Gallows.
I could unfortunately make some of these connections only in the last days. Today they support my personal view even more. My work does not claim to have discovered each of these individual stones first. Its contribution lies in the synthesis: the known disturbances are not interpreted one by one, but read as layers of a formal system. That is exactly why the model is strong for me.
Important: this derivation is not a semantic release. It is a bridge from public findings to the RIA system reading.
1. Word Repetitions -> MARKER / PAYLOAD
Public finding: Voynichese, or the so-called Voynich language, shows conspicuous repetitions, word-like series, and monotone variants. Classical linguistics struggles with this, because such accumulations appear unusual for natural language in this form.
Derivation: This behavior fits a mechanically generated or strongly formalized system. If a scribe works with fixed syllable, token, or fragment tables and runs them through a position-dependent grid, repetitions, variants, and language-like patterns necessarily arise without implying plaintext.
Gordon Rugg's Cardan-grille approach is therefore not a final explanation for me, but an important public connection: it shows that template/table mechanics can in principle generate Voynich-like surface text.
RIA integration: In my model, this becomes the separation of PAYLOAD and MARKER. Recurring tokens or label groups are not automatically words, but possible payloads, table remnants, register values, or formal output fragments. Slots, positions, margins, block starts, circles, and segmentations operate as MARKER: they determine when and where a given formal state appears.
Status: Strong as a derivation path. Not proven as a Cardan grille. Not released as a hoax claim.
2. Currier A/B -> GALLOWS Interface
Public finding: Prescott Currier described the well-known split into Currier A and Currier B: two statistically different text modes within the same manuscript. Whether these represent different languages, registers, subjects, scribes, modes, or something else remains open.
Derivation: For an IT analyst, an abrupt statistical mode shift is a strong signal. In a technical system it would not be surprising: different mode, different table, different register, different template, different writing rule.
RIA integration: This is where the Gallows trace becomes central. The hard coupling between paragraph block openings and Gallows line-open provides a formal interface signal: 200 of 229 @P0/@P1 block openings begin with Gallows, that is 87.34%. The remaining paragraph lines are at 18.70%. This is not a small stylistic impression, but a massive positional finding. The Gallows are therefore not treated as normal letters, but as opening/timing markers for text blocks. Not as proven opcodes, not as commands, but as a formal channel-change candidate.
Status: GALLOW_BLOCK_OPEN is strongly supported. IF3 is strongly supported. IF4 remains open.
3. Circular, Rosette, and Angular Structures -> Angular Matrix / CONTROL
Public finding: The manuscript contains circles, rosettes, segmentations, star-like fields, and diagrammatic pages that do not fit neatly into an ordinary text tradition. In such areas the page feels more like an instrument than like an illustration.
Derivation: If a circle is not merely image or drawing, but a geometric form, angles suddenly matter. A circle can be a register, a rosette can be a control surface, and a segmentation can serve as an address or selection grid. Where 18-part structures occur, a 20-degree step is mathematically close. This fits a volvelle or calculating-disc lens, without proving a final output.
RIA integration: The circles are treated as CONTROL candidates: not as decoration, but as possible output registers, selection spaces, or reference discs. The angular matrix remains deliberately cautious. It is not the final proof. It is a test assignment: do segments, figures, stars, labels, and text orientation line up stably enough when treated as an angle/position system?
Status: Strong as a system bridge. Exact angular decoding remains open. Rigid 22.5-degree claims remain blocked.
4. Gemini and Aries -> STATE Gate / Initialization
Public finding: The Zodiac pages contain several conspicuous special cases. Gemini f72r2 carries the strong NULL special case: a physical figure or intermediate anchor is locally supported, but the associated regular label is missing. Aries is doubled and appears as a 15+15 structure in the context of an otherwise dominant 30-register.
Derivation: In a formal system, headers, null cases, start areas, and control slots are not side issues. They explain how an area begins, how a state is set, and how gaps or special cases are processed. From an IT perspective, Aries is therefore not only a Zodiac image, but a start context: the cycle is not continued smoothly; it is split and calibrated at the beginning.
RIA integration: Gemini is treated as a NULL/header context, Aries as an initialization candidate. When I say BIOS or reset, this is not a historical computer claim. It is laboratory language: a starting area in which basic states are set. This is where the circle closes for me: Aries sets, Zodiac holds registers, Balneo couples, Pharma segments, Gallows time the blocks, and circular/angular structures order the space.
Status: Aries is for me the strongest initialization context. Formally it remains an initialization candidate, not a proven BIOS.
5. Stars and Nymphs -> Template / Slot Logic
Public finding: In the Zodiac, star, and bathing pages, figures, stars, labels, containers, and positions do not appear arbitrarily. They repeat, but they are not fully identical. Precisely this mixture of repetition and deviation is conspicuous.
Derivation: In a template or register system one needs more than text values. One needs anchor points. A slot is a place where a state can sit. A star can mark a state or coupling point. A figure can be the visible carrier of that slot.
RIA integration: Nymphs and figures are therefore treated as slot/RECORD carriers. Stars are treated as template/STATE anchors. Labels remain PAYLOAD. Ring, sector, basin, tube, or block opening remain MARKER. This explains why missing stars, weak star traces, container figures, differing postures, or missing labels need not immediately be errors, but may be boundary cases of a system.
Status: Strong as a template-logic candidate. Not proven as a lost physical tool. No stars-as-bits claim. No nymphs-as-data-packets claim.
6. Curved Circular Templates -> Timing Generator / Transfer Function
Public finding: Some diagrams show not merely straight sector lines, but curved, vortex-like, or dynamic line fields. This especially concerns circular template areas such as f57v and dynamic axes in the rosettes.
Derivation: A straight sector disc divides. A curved disc modulates. Once lines are not radial, they intersect angle or segment grids at changing radii. A simple position system then becomes a distorted transfer surface: same angle, different radius, different intersection point.
RIA integration: These curved templates are treated as timing-generator, frequency-divider, or transfer-function candidates. Not because a historical apparatus is proven, but because they could formally take on exactly the role that a rigid register lacks: delay, phase shift, jump logic, and non-linear selection.
Status: Strong as functional metaphor and test assignment. Not proven as algorithm. Not released as a concrete cipher curve.
7. The Rosettes Foldout -> Central System Board / Mainboard Candidate
Public finding: The large Rosettes foldout is the most complex visible system sheet of the manuscript. It connects several circles, centers, margin structures, tubes, transitions, and dense fields into a total surface.
Derivation: If the individual sections show registers, slots, buses, timing markers, and control surfaces, then the Rosettes foldout is the natural place to expect the coupling of all subsystems. Not as a geographic map, but as a system overview: inputs, main center, couplings, outputs.
RIA integration: The Rosettes foldout is therefore treated as a mainboard or system-board candidate. Upper areas may be input registers or calibration surfaces, the center may be read as a central CONTROL or processor-like area, and lower areas may be output or test registers. The tubes are then not decoration, but visible coupling axes between functional surfaces.
Status: Strong as a bridge for the overall model. Not proven as a real mainboard. No historical computer claim.
The Closed Dynamic System Model
The derivation can be read as a working chain:
[ ARIES ANOMALY ]
Initialization / reset / starting state
|
v
[ ZODIAC CIRCLES / CIRCULAR TABLES ]
Registers / static data sets / control surfaces
|
v
[ STARS + NYMPHS / FIGURES ]
Template anchors / slots / state carriers
|
v
[ CURVE TEMPLATES / VORTEX LINES ]
Timing deformation / transfer function / phase shift
|
v
[ TUBES / PORTS / TRANSITIONS ]
Coupling / graph / filter / transitions
|
v
[ PHARMA BANDS ]
Segmentation / object-text coupling / local reference
|
v
[ GALLOWS ANCHORS ]
Block opening / timing / formal channel change
|
v
[ CIRCULAR AND ANGULAR MATRIX ]
Position space / output register / CONTROL candidate
[ ROSETTES FOLDOUT ]
Higher-level system board / coupling and control surface
This is the form that is understandable for a broader audience: not a single mysterious sign solves everything. Instead, the coupling of many publicly known disturbances produces a system image.
The hard sentence remains: The model explains several known Voynich anomalies as layers of a formally testable, non-semantic mechanism.
The blocked sentence remains: The model proves the decipherment of the Voynich Manuscript.
Why the Aries Context Is So Strong for Me
Aries is not strong for me because a single page contains a striking image. An isolated anomaly would be too little. Aries becomes strong only in context.
First, Aries lies at a place where a system start is plausible. In the annual cycle, Aries is not just any sign, but a candidate beginning. Even if every astrological interpretation is blocked, the formal role remains: beginning, transition, cycle start, calibration.
Second, Aries is doubled. Instead of a smooth 30-structure, a split 15+15 pattern appears. That is exactly what makes it operationally interesting for me, not decorative. A 30-circle can be calendar, list, or register. Two 15-halves at the starting point, by contrast, look like initialization: first split, then continue counting.
Third, Aries does not stand alone. Other Zodiac pages act as control surfaces: Cancer stabilizes the 30/30 case, Gemini shows the strong NULL special case, Pisces carries a central CONTROL candidate, Taurus light/dark shows the contrast between a clean half-register and physical ambiguity. Aries is therefore not a pretty idea, but part of a comparison series.
Fourth, Aries fits exactly into the IT lens. When I say BIOS, I do not mean a modern computer BIOS in the historical sense. I mean a structural metaphor: a start/reset/initialization area in which basic states are set before the system moves into other register areas.
Fifth, non-semantics are precisely the point. Aries does not have to mean “Aries means X.” It only has to perform formally: start position, split, state change, control relation. These four things are enough for it to become strong as an initialization gate in the model.
The hard sentence is not: Aries is a proven BIOS.
The hard sentence is: The Aries doubling is, in the register context, a particularly strong initialization candidate because it lies at the cycle start, breaks the 30-schema into 15+15, and is formally connectable through other Zodiac control cases.
For me personally, exactly this context is the key. Not the single page. Its position in the system.
Why the Tube and Bus System Is So Strong for Me
The tubes are not strong for me because they look like modern lines. That would be too simple. They become strong because they repeatedly appear precisely where separated areas are coupled: basin with basin, body with transition, image zone with text zone, upper level with lower level.
For an IT analyst, that is not a minor ornament. It is a coupling structure. I say bus system not to press medieval material into a modern computer image. I use the word as a working metaphor: a bus is a shared connection layer. It does not itself carry meaning; it couples carriers, states, and target areas. That is exactly how I read tubes, funnels, channels, transitions, and port points.
The strong point is repetition across different pages. In the Balneo pages, basins, tube runs, port points, and text zones form a graph-capable architecture. f78r is not an isolated accident: f81r, f83r, and f84r show related but not identical graph forms. That matters. If all pages were the same, it would be template compulsion. If all were completely different, it would be free decoration. Here there is something in between: the same grammar, different expression.
This tube logic also explains why the images are not simply illustrations next to text. The page organizes paths. It does not merely show objects; it shows transitions between objects. In the RIA grid this means NODE, PORT, EDGE, PAYLOAD, and CONTROL can be handled separately. A bathing page thereby becomes a testable network.
The protection sentence remains important: tubes are not proven data buses, nymphs are not bits, and flow direction is not released meaning. As a formal coupling model, however, the tube structure is strong because it closes the gap between static registers and dynamic processing. Without this coupling, the circles would be only tables and the text blocks only text. With it, a system flow emerges.
The hard sentence is not: The tubes are proven data buses.
The hard sentence is: The tube, port, and basin structures form a strong graph/coupling candidate because, across several folios, they repeatedly connect separated image, text, and object zones and thereby become testable as a formal interface layer.
For me personally, exactly this coupling is decisive. Aries sets the beginning. The circles hold registers. But without tubes, ports, and transitions, the model would have no moving body.
Why the Circular Tables and Data Sets Matter
The circular and ring texts are not merely decorative captions for me. They are the area in which the manuscript most strongly behaves like an ordered data surface. Precisely because text, figures, stars, segments, inner/outer rings, and centers appear together here, these pages are so important for the model.
Running text is linear. A circular table does something else: it orders entries by position, ring, sector, proximity to the center, and relation to visible objects. A register idea arises immediately. Not in the sense of proven storage, but in the formal sense: an entry does not stand somewhere, but at a specific address in the layout.
The Zodiac circles and diagram pages are therefore, for me, the static data sets of the model. They provide stable areas against which other sections can even be tested. If Gemini shows a NULL case, Cancer works as a 30/30 control, Pisces carries a central CONTROL candidate, and Aries breaks the 30-field into 15+15, then these are no longer loose curiosities. They are register cases.
The circular tables are also important because they make the difference between PAYLOAD and CONTROL visible. A label can be payload. A star can be state. A ring can be address. A center can be control. A sector can be selection space. This separation is hard to see in running text, but almost imposed by circular diagrams.
When I say ROM or database, that too is an IT metaphor. I do not mean a modern electronic storage unit. I mean a static reference surface: something from which a procedure could obtain values, states, or selection possibilities. Without such static reference surfaces, the manuscript would have to carry everything in running text. It apparently does not do that. It distributes information across image, circle, ring, label, and position.
The hard sentence is not: The circular tables are proven databases.
The hard sentence is: The circular, ring, and Zodiac structures are strong register/data-set candidates because they couple text, object, state, segment, and center in stable positional spaces and thereby provide a formal reference layer.
For me personally, these circular tables are the resting storage of the model. They are what remains once every translation is blocked: ordered data sets without released semantics.
Why Bus and Circular Tables Carry the Mechanism Together
Only together do the two levels become strong. Circular tables without coupling would be isolated diagrams. Tubes without registers would be confusing lines. The mechanism candidate arises only when both are read together: static reference surfaces on one side, dynamic coupling and transition structures on the other.
That is the actual IT lens: a system needs not only data. It also needs paths. It needs states, boundaries, timing, and control points. That is why no single finding is enough for me. Not Aries alone, not Gallows alone, not Balneo alone, not Pharma alone. The model becomes strong because the roles recur across sections.
The circular tables answer: where are the entries and states? The tube/bus model answers: how are separated areas connected? Gallows answer: where does a block or mode begin? Pharma shows: how is local segmentation organized? Herbal shows that, even in a very different section, image, sub-object, color, and text proximity are layered.
This produces a dynamic reading frame without translating a single word. That is the core for me: meaning does not generate the order; the order is already visible before meaning is released.
The short system formula is:
[ ARIES ] sets the starting state.
[ CIRCULAR TABLES ] hold registers and static reference data.
[ STARS ] mark template/STATE anchors.
[ NYMPHS / FIGURES ] form slot/RECORD carriers.
[ CURVE TEMPLATES / VORTEX LINES ] deform timing and positional access.
[ TUBES / PORTS / TRANSITIONS ] couple and route between areas.
[ PHARMA BANDS ] segment local object-text groups.
[ GALLOWS BLOCK OPENINGS ] time formal text blocks.
[ ROSETTES FOLDOUT ] bundles the subsystems as a system-board candidate.
[ ANGULAR AND CONTROL SURFACES ] order output and control spaces.
This is not a decipherment. But for me it is a closed system image strong enough to be reviewed publicly.
Why Stars Are Strong Template and STATE Marker Candidates
The stars are not strong for me because they look attractive, or because stars would be expected in an astronomical manuscript. They become strong only because, in the Voynich context, they are repeatedly coupled to figures, rings, segment boundaries, text proximity, and centers. They rarely stand fully free in empty space. They sit on bodies, beside bodies, above hands, at ring positions, or in fields that already behave like register or control surfaces.
When I read stars as template elements, I do not mean that every star carries a finished meaning. I mean that stars can function as recurring anchor points at which a template logic becomes visible. A star then marks not the sense, but a state, a position, a selection point, or a coupling. This fits the RIA grid: the body or figure is the RECORD carrier; the star is a STATE or anchor channel; the label is PAYLOAD; ring, sector, or line are MARKER; the center or circular logic remains CONTROL.
The strong point is the separation. Once stars are no longer treated as illustration but as their own channel, it becomes visible why some pages feel so mechanical. The figure alone is not enough. The label alone is not enough. Only figure plus star plus ring position plus text proximity produces a testable data set. That is why the small stars are not a side issue for me. They may be the points at which the visible template grips the layout.
This applies especially where stars are missing, weak, reconstructed, or visibly executed differently. In a purely decorative system, a missing or weak star may be only damage or carelessness. In a formal system it becomes a test point: is the figure still present? Is the label still present? Does the position remain? Is there a homologous star on a neighboring figure or another ring? Such questions turn ornament into a template hypothesis.
The hard sentence is not: Stars are proven templates or bits.
The hard sentence is: The star structures are strong template/STATE marker candidates because they repeatedly couple figures, ring positions, labels, and control surfaces, forming a separate non-semantic test channel.
For me personally, the stars are the small nails in the board. Without them, figures and labels would have less hold. With them, the page becomes a marked working surface.
Why the Different Nymphs Matter as Slots
The nymphs are not strong for me because they depict people. The opposite matters: I do not need to know who they are. I do not need to know what they mean. I only need to see that they stand in the layout as recurring but distinguishable bodies. That makes it possible to read them as slots.
In IT terms, a slot is not content, but a place that can carry content. That is how the nymphs behave in the model: they stand at ring positions, in basins, in containers, at tubes, beside stars, near labels, or in zones separated from one another. Their differences - posture, gaze direction, clothing, container, hand position, star relation, body position - are therefore not automatically meaning, but they are formal state features.
It matters that the nymphs are not all the same. That is what makes them strong as slots. If they were completely identical, they would be mere counters. If they were completely freely invented, any system reading would be weak. They lie in between: recurring enough for a register, different enough for states. This intermediate position is the core for me.
In Zodiac, nymphs can be ring slots: bodies at a position, often with star and label. In Balneo they can be node or state carriers: bodies in basins, at tubes, in transitions. In Pharma the nymph logic does not appear identically, but the idea remains: visible object carriers stand in local relation to text zones and layout boundaries. The carriers change, the role remains recognizable.
This also explains why pure text analysis falls short. If the body itself is a slot, then part of the information is not in the word, but in the position of the body and in its visible attributes. That is not semantics. It is layout mechanics.
The hard sentence is not: Nymphs are proven data slots.
The hard sentence is: The different nymphs are strong slot/RECORD candidates because they appear as recurring bodies at register, graph, and layout positions and there bundle state features, star relation, text proximity, and transitions.
For me personally, the nymphs are the sockets of the system. The stars mark states. The labels carry payload. The position turns it into a register.
Why Stars and Nymphs Together Open the Template Logic
Only together do stars and nymphs become truly strong. A nymph alone is a figure. A star alone is a sign. A label alone is text. Together, however, they form a testable slot: body plus state plus payload plus position.
This is the point that pulls the template idea out of pure speculation for me. A template needs anchors. It needs places where something locks in. In the Voynich context, these anchors may be visible: body positions, star positions, ring sectors, label proximity, block openings, tube transitions. The template therefore does not necessarily have to be a lost physical tool; it can also appear as layout logic within the manuscript itself.
This explains why some figures have stars, some weak star traces, some no clear label, and some stand in containers or tubes. These deviations are not immediately errors, but test cases. A template system shows its strength not only in the rule, but in boundary cases: NULL, EXTRA, START, CONTROL, weak star, hidden body, missing label.
The hard sentence is not: Stars and nymphs prove a lost template.
The hard sentence is: Stars and nymphs together form a strong template-logic candidate because they generate recurring slot-state-payload packages that remain testable across ring, graph, and layout areas.
For me personally, this is one of the most alive parts of the model: the page is not merely written on. It is plugged, marked, and timed.
Why Curved Circular Templates and Vortex Lines Are Strong
Not every drawing in the manuscript behaves like a static table. Some circles and rosette axes show curved, vortex-like, or dynamic lines. These forms matter to me because they break open the rigid register model.
A straight circle with sectors can count, order, and store. A curved circular template can do more: it can shift. It can delay. It can intersect an angle at different radii. A simple two-dimensional grid becomes a transfer surface. The same angle can land at a different point depending on the curve. That is interesting for a formal system because it breaks repetition without creating arbitrariness.
When I say timing generator, frequency divider, or cam disc, I again mean laboratory language. I do not claim a historical metal apparatus. I mean a mechanical-symbolic role: a surface that transforms linear timing into non-linear selection. In the IT lens, this would be a transfer function. In the template lens, it would be a curve that decides which next slot becomes valid.
This explains why such drawings are not marginal art for me. They may be exactly the places where the system switches from a rigid table mode into a dynamic mode. The Zodiac circles hold registers. The curved circular templates may modulate access to these registers.
The hard sentence is not: The curved lines are proven algorithms or real mechanical cam discs.
The hard sentence is: Curved circular templates and vortex lines are strong timing-generator/transfer-function candidates because they geometrically distort a rigid angular or register grid and thereby make a non-linear selection or coupling logic testable.
For me personally, these lines are the movement in the system. The circles store. The tubes couple. The Gallows time. But the curves can deform the timing.
Why the Rosettes Foldout Looks Like the System Mainboard
The large Rosettes foldout is not simply a world image for me, nor merely a decorative overview. It is the sheet on which the previously separated subsystems most visibly come together: circles, centers, tubes, margin structures, dense fields, transitions, and several coupled functional surfaces.
When I say mainboard, I do not mean a modern computer board in the historical sense. I mean a system board as metaphor: a central surface on which registers, buses, timing surfaces, control zones, and output areas are visibly interconnected. That is precisely why the Rosettes foldout is so strong for me. It does not merely show individual elements; it shows the coupling of elements.
In this reading, the upper circles can be treated as input or calibration registers. A curved rosette can be a timing or frequency-divider candidate. A symmetrical wheel can be read as a synchronization surface. A dense detail field can act as a fine-grained selection table. The center becomes the large CONTROL candidate: not as a proven CPU, but as the main node where visible axes converge.
The tubes and connecting paths are decisive. Without them, the rosettes would be individual pictures. With them, the page becomes a coupled surface. Top, center, and bottom are then not isolated, but levels: input, processing, output, or control. The margin structures, towers, gate-like, or fortress-like forms are not automatically architecture in the literal sense. They can be tested as boundary gates, margin markers, or transition structures.
The lower rosettes are also not read semantically in this view. A mesh field can be treated as a fine angular-matrix candidate. A star field can appear as a test or STATE field. A funnel or outflow area can be read as an output/interface candidate. All of this remains formal. No value, no language, no translation is released.
The hard sentence is not: The Rosettes foldout is a proven mainboard or a real machine.
The hard sentence is: The Rosettes foldout is a strong system-board/mainboard candidate because it bundles register, curve, tube, control, and output structures into one coupled total surface and thereby becomes testable as an overview of the mechanism.
For me personally, this page is the great convergence. One sees not only parts. One sees why the parts might belong together.
Why All Drawings May Have Function - But Not Arbitrarily
The sentence “all drawings have function” is dangerous if misunderstood. It must not mean that every line has a secret meaning that I can freely interpret. That would be drift.
In the RIA model, the sentence means something else: every drawing may first be tested as a possible carrier of a formal role. A plant can be RECORD. An organ can be SUBRECORD. A nymph can be slot. A star can be STATE anchor. A tube can be EDGE. A circle can be register. A curve can be transfer surface. A rosette can be CONTROL or system surface.
This proves nothing automatically. But it prevents image areas from being set aside too early as mere illustration. In the Voynich Manuscript in particular, the separation between text and image is too hard. Many pages look as if text, image, and layout are working together. Therefore all drawings must first be tested as possible structure carriers before they are called decorative.
The hard sentence is not: Every drawing is proven function.
The hard sentence is: All drawings are tested in the RIA model as possible formal carriers, but only roles supported by repetition, coupling, position, counterexample, and falsifiability remain in the model.
This is the boundary that protects the model: open enough to take the drawings seriously; hard enough not to claim everything.
My Personal Analogy: The RIA-MS408 OSI Layer Model
This analogy is important to me because it brings the entire mechanism into a form that IT people immediately understand. I am not claiming that the Voynich Manuscript is a modern network protocol. I use the OSI model as a thinking image: a layer model showing how a system can be built from lower carriers, states, connections, timing, formatting, and visible output.
This is what makes the manuscript graspable for me. It no longer looks like a collection of individual riddles, but like a protocol stack made of parchment, image, figure, star, tube, circle, angle, block opening, and text. Each layer does not have to speak the same language. It only has to fulfill its role in the stack.
The personal analogy is:
Layer RIA-MS408 role in the analogy
Layer 7: Application final text on the parchment / running text
Layer 6: Presentation component-based token construction / formatting
Layer 5: Session Gallows interface / timing and block control
Layer 4: Transport tubes, funnels, channels / bus and coupling system
Layer 3: Network angular matrix, rosette distributors, routing surfaces
Layer 2: Data Link nymphs, stars, slots, state and test candidates
Layer 1: Physical Aries anomaly / starting state / zero-point calibration
Here too the RIA brake applies: these layers are not a historical claim, but a functional reading lens. They make visible why the individual parts might work together.
Layer 1: Physical Layer - Aries as Start and Zero-Point Candidate
The lowest level for me is the Aries context. Not as a proven BIOS, but as the starting area of the model. The split 15+15 structure behaves like zero-point calibration: before a register, slot, or text block can be read meaningfully, it must be defined in which basic state the system begins.
In the OSI analogy, Aries is therefore the physical grounding: the point where the system receives its beginning, its split, and its first state. Without this start context, the later registers look like loose circles. With it, they obtain a direction in the system.
What remains blocked: Aries = proven BIOS. What remains allowed: Aries = strong start/initialization candidate.
Layer 2: Data Link Layer - Stars and Nymphs as Slot and STATE Layer
The second level contains the nymphs and stars. The nymphs are not proven data packets. But as recurring bodies at positions they behave like slot carriers: they sit, stand, dive, hold stars, are partly missing, hidden, or dressed differently. Precisely these differences make them strong as RECORD and slot candidates.
The stars form the separate STATE channel. They can be present, weak, colored, dotted, reconstructed, or absent. This variation itself behaves like a safeguarding and state surface. A star does not have to carry “meaning.” It may only mark: this slot has a state, this body is coupled, this position is active or testable.
The Gemini NULL context fits this level because body, position, and label gap come together as a test point. Pisces, with its central control candidate, also belongs here as a bridge. Not as a proven check bit, but as a STATE/CONTROL question.
What remains blocked: Stars = bits, nymphs = data packets. What remains allowed: Stars and nymphs form strong slot/STATE/RECORD candidates.
Layer 3: Network Layer - Angular Matrix, Rosettes, and Routing Surfaces
The third level is addressing. Here sit the circular diagrams, rosettes, segmentations, and angular relations. A linear script has sequence. A circle has position, sector, radius, center, and direction. This produces routing: a value can lie not only before/after, but in an angular space.
The 20-degree matrix is not a proven decoder in this analogy, but a routing candidate. The same applies to the Rosettes foldout: in this model it behaves like an upper-level distribution surface in which several circles, axes, tubes, and control spaces are brought together.
The curved templates also belong here. They would not be direct output, but a transfer function: they could distort a straight angle or register run, shift it in phase, or move it to another radial point. A rigid grid becomes a dynamic position space.
What remains blocked: Rosette = proven CPU, 20 degrees = proven code. What remains allowed: Rosettes, angles, and curved templates are strong mediation/routing candidates.
Layer 4: Transport Layer - Tubes, Funnels, and Channels as Bus Candidate
The fourth level is the transport level. Here sit tubes, funnels, channels, basins, ports, and transitions. These forms are strong because they visibly couple separated areas. They connect top and bottom, left and right, basin and basin, body and text zone, input and output.
In the OSI analogy, this is the bus. Not as a proven data line, but as a coupling layer. A bus does not have to possess meaning itself. It connects carriers and target areas. That is what the tubes do in the model: they give the static register world a moving body.
Balneo especially carries this layer: f78r with port points, f81r as control graph, f83r as a different node type, f84r as a multilevel basin and connection layer. The repetition is not identical, but grammatically related. That makes it strong as a layer.
What remains blocked: Tubes = proven data buses. What remains allowed: Tubes, funnels, and channels = strong transport/graph/coupling candidates.
Layer 5: Session Layer - Gallows as Timing and Block-Opening Interface
The fifth level is timing. Here sits the strongest formal text finding: Gallows at block openings. The coupling of @P0/@P1 paragraph block starts with Gallows line-open is massive. This is exactly why my model does not primarily read Gallows as ordinary letters, but as opening or timing markers.
In the OSI analogy, this is the session layer: it does not decide what a word means, but when a block begins, when a mode becomes active, and where a section is formally opened. The suppression phenomenon f99v is especially important here: it shows that visible block structure and Gallows activation do not always have to run identically. That speaks more for a mode than for simple decoration.
What remains blocked: Gallows = opcodes or commands. What remains allowed: Gallows block openings = hard timing/interface candidate.
Layer 6: Presentation Layer - Pharma and Token Construction as Formatting Level
The sixth level is presentation. Here local structures are brought into a visible text or token format. Pharma matters to me because it shows that object groups, vessel columns, text proximity, and band boundaries work together without requiring the section to be a literal recipe.
In the OSI analogy, Pharma is a formatting and segmentation level. The data are no longer only transported; they are pressed into local groups: object group, text zone, reference object, band boundary. f99r shows a strong TYPE-A case. f100r, as TYPE-D, shows that the vessel column on the left is not a globally mandatory operator. The system therefore remains flexible.
What remains blocked: Pharma = recipe. What remains allowed: Pharma = strong variable band and presentation layer.
Layer 7: Application Layer - Visible Running Text as Output
The top level is the text we see. In this analogy it is not the start of the analysis, but the end of the stack. The running text is the user interface of the system: the visible result of starting state, slot/STATE layer, routing, transport, timing, and formatting.
This explains for me why the text looks language-like but resists natural language in many respects. It could be output emerging from several formal layers, not from a simple plaintext alphabet.
What remains blocked: Running text = proven output of an apparatus. What remains allowed: In the model, running text is the final visible output layer.
Why This Analogy Rounds Off the Document for Me
The OSI model is the calmest summary of the entire project for me. It does not force anything into a modern technology claim. It only shows that a complex system can consist of layers in which each level has its own task.
The analogy also makes clear why I no longer believe in pure text. If one looks only at layer 7, the manuscript appears as a language puzzle. If one sees all layers together, it appears as a functional transmission and generation structure.
The hard sentence is not: MS408 is a seven-layer data-transmission machine.
The hard sentence is: The OSI layer model is a personal, functional analogy that brings the observed RIA roles - start, slot, state, routing, transport, timing, formatting, and output - into a testable system order.
For me personally, that is the closure: not one sign solves the manuscript. The stack makes it understandable.
Claim Boundary
This document works with a strict boundary between finding, model, and personal conclusion.
Category Boundary
What is claimed MS408 shows a formally testable structure candidate. Several sections can be described as layered information layouts. The roles RECORD, STATE, PAYLOAD, MARKER, and CONTROL are viable as a working model. Gallows block openings are a hard formal text finding. Zodiac, stars, nymphs/figures, Pharma, Balneo, Herbal, curved circular templates, and Rosettes provide recurring but differing carriers of the same layer logic.
What is not claimed No translation, no plaintext, no language identification, no alphabet, no substitution, no opcode, no firmware, no medical or botanical identification, no recipe as fact, no stars-as-bits claim, no nymphs-as-data-packets claim, no cam-discs-as-proven-algorithms claim, no rosettes-as-proven-mainboard claim, and no true decipherment.
Guiding rule MS408 shows a formally testable, non-semantic structure candidate with recurring layered roles and strongly supported block-opening/layout signals.
Blocked guiding formula MS408 is deciphered.
Quality-Gate Evidence Chain
The evidence chain is not a smooth victory march. It is a workshop path with brakes.
REC Content Status
REC-01 / QG1 Circular-graphic, EVA, and crop basis; kanchas as image/circular-graphic candidate basis secured
REC-02 / QG2 15/30 Zodiac register model; START / NULL / EXTRA / CONTROL separated strong test model
REC-03 / QG3 Q3 pretable; f72r2 NULL strong; f72r1 EXTRA quarantined; 22.5 degrees blocked private
REC-04 / QG4 Mechanism matrix across Zodiac, Herbal, Balneo, Pharma, and text-only areas cross-section supported
REC-05 / QG5 Balneo graph-capable; Pharma band architecture; Gallows line-open hard confirmed structure supported
REC-06 / QG6 GALLOW_BLOCK_OPEN strongly supported; IF3 visually strongly supported; Q3 frame pass, no final lock private
REC-07 / QG7 Publication polish lock; formal output path; review lock; archive/no-input locks review candidate
The chain is strong because it does not wave everything through. Micro-reading, semantics, substitution, rigid 22.5-degree geometry, recipe reading, opcode language, and overly smooth AI confirmations were braked or blocked.
Core Model: RECORD / STATE / PAYLOAD / MARKER / CONTROL
The model does not read MS408 first as text, but as a coupling of several visible levels.
Role Working definition
RECORD Primary object, carrier unit, nymph/figure, or visible slot body.
STATE State, feature, color, star, star shape, posture, or emphasis.
PAYLOAD Text proximity, label, token sequence, or local text block.
MARKER Start, gap, margin, ring, block opening, star anchor, or layout boundary.
CONTROL Center, axis, dominant organ group, node, or reference column.
These roles are not a translation. They are an IT grid: What is the carrier? What is the state? What is the text load? What is the boundary? What locally controls or orders? And it goes considerably further. The value of the model is not that every section looks identical. On the contrary: the carriers change. That is precisely what makes it systemically interesting.
Zodiac: Registers, Start, and Special Cases
The Zodiac group is the strongest image-textual register area. Aries is the initialization candidate: doubled, split, at the cycle start, connectable to 15/30 logic.
Gemini f72r2 remains the strongest NULL special case: a physical intermediate anchor is locally supported, but functionally not released. Pisces f70v2 remains a CONTROL candidate: central object and 29/30 tension are formally strong, but not proven as parity bit. Cancer f72r3 remains the control case for 30/30 and START_ONLY: important precisely because not every special case looks like Gemini. Taurus light/dark stabilizes the contrast logic: clean half-register case versus physically active but not finally confirmed EXTRA trace.
Stars and nymphs visibly carry this register logic with them: the figure forms the slot, the star the state/template anchor, the label the text load, and the ring position the address. Exactly this fourfold coupling makes the Zodiac group central for the mechanism.
Status: ZODIAC_MECHANISM = STRONGLY SUPPORTED. Q3_FINAL = OPEN.
Balneo: Graphs Instead of Decorative Baths
The Balneo section is not read as a “bath story,” but as a graph-capable structure. Visible elements include basins, tubes, transitions, port points, nymph positions, text zones, vertical and horizontal couplings. This permits a node/edge test.
Allowed: NODE = basin, node, transition, nymph, tube mouth. EDGE = visible connection or tube run. PORT = connection or transition point. PAYLOAD = text zone or text proximity. CONTROL = main basin, main node, or axis as candidate.
Blocked: Tubes are data buses. Nymphs are bits. Flow direction is meaning. Basins are storage.
Status: BALNEO_GRAPH = SUPPORTED / MARKUP REPLICATION REQUIRED.
Pharma: Band Architecture Instead of Recipe Claim
At first glance the Pharma section appears recipe-like. That is exactly where caution is necessary. The hard finding is not: take four of this and three of that. The hard finding is: there is a variable object/text band architecture.
A band can consist of: vessel or reference object, object group, text proximity or text block, horizontal or local layout boundary. f99r is strong as TYPE-A. f88v brakes the overly smooth text-block assignment. f100r, as TYPE-D, shows that the left vessel column is not a globally mandatory operator. This does not weaken Pharma, but makes it more honest: it is not a simple recipe table, but a flexible band structure.
Status: PHARMA_BAND_ARCHITECTURE = STRONGLY SUPPORTED AS STRUCTURE. RECIPE = BLOCKED.
Gallows: The Strongest Formal Text Finding
The Gallows trace is the hardest formal text finding. Paragraph block openings @P0/@P1: 229 lines, 200 of them LINE_OPEN with Gallows, share: 87.34%. Remaining paragraph lines: 3,728 lines, 697 of them LINE_OPEN with Gallows, share: 18.70%. Statistic: odds ratio approximately 29.99, p approximately 9.33e-104.
The artifact brake matters: the @ sign alone does not explain the effect. Non-paragraph lines with @ fall back to baseline.
Admissible: Paragraph block openings are massively and reproducibly coupled with Gallows line-open.
Blocked: Gallows are opcodes.
Status: GALLOW_BLOCK_OPEN = STRONGLY SUPPORTED. IF3 = STRONGLY SUPPORTED. IF4 = OPEN.
Q3: Why I Do Not Force the Final Lock
Q3 remains open. This is a deliberate decision. The global frame carries. But pixel-level precision would be dishonest because the source is soft: faint contours, hand drawing, parchment distortion, fold and panel deformation, unclear star/label boundaries, overlapping ring texts.
Therefore: Q3_FRAMEPASS = PARTIAL_PASS. Q3_FRAME_BASED = ACTIVE. Q3_FINAL = OPEN. 22.5 degrees = BLOCKED.
For me, this does not weaken the work. It protects it. Whoever claims too much here destroys the core.
Adversarial Review: What Critics Should Attack
This document invites refutation. Attack points:
1. Does the Gallows block-open finding replicate on alternative transcriptions?
2. Does @P0/@P1 remain visually coupled corpus-wide to real text block starts?
3. Does the 15/30 Zodiac register logic hold under independent object marking?
4. Does Aries remain strong as an initialization candidate if astronomical start assumptions are removed?
5. Does Balneo remain graph-capable under a second independent node/edge marking?
6. Does Pharma remain band architecture when recipe intuition is completely blocked?
7. Does IF3 remain stable under controlled covariates?
8. Is there a more natural explanation that explains all sections together more simply?
9. Does the tube/bus hypothesis hold if a second person independently marks nodes, ports, and edges?
10. Do circular tables remain stable as register/data-set candidates if the terms ROM and database are fully removed?
11. Do stars remain stable as template/STATE markers if every astronomical meaning is blocked?
12. Do different nymphs remain stable as slot/RECORD carriers if a second person independently codes figures, star relation, label proximity, and position?
If these points fall, the model falls. If they hold, the model must be taken seriously, even without semantics.
What I Consciously No Longer Do
I will not expand this project further only to get a stronger feeling. I will not turn Aries into a final BIOS proof. I will not turn tubes into data buses. I will not turn Pharma into a recipe. I will not turn Gallows into opcodes. I will not turn curved templates into proven algorithms. I will not turn the Rosettes foldout into a real mainboard. I will not claim that every drawing automatically has a deciphered function. I will not turn stars into proven bits. I will not turn nymphs into proven data packets. I will not pretend that silence from Yale, forums, or researchers has confirmed or refuted anything.
What I do: I make the circle open. I make the brakes open. I make the strongest findings open. And I make the open wounds open. That is my closure.
Status Formula
Category Status / Statement
Final working status Mathematical blueprint: completed in the sense of a formal review candidate.
Working paper Review-capable.
Gallows block-open Strongly supported.
Stars as template/STATE markers Strong candidate.
Nymphs as slot/RECORD carriers Strong candidate.
IF3 Strongly supported.
IF4 Open / not locked.
Q3_FINAL Open.
Semantics Not released.
Substitution Not released.
Plaintext Not released.
Opcode Blocked.
True decipherment 0%.
OSI layer model Personal functional analogy / not presented as historical proof.
Personal status The circle is closed for me.
External status The world may test it.