I · V · O — Open research

Research logbook

A chronological record of questions, experiments and decisions. Work remains visible before it becomes a finished claim.

Current record

Latest entries

This first public record begins with the recent development of I·V·O Core. Later entries can include visual studies, instrument experiments and observations that materially change the direction of the work.

Same notation, different dynamics

A notation can describe what a system looks like at a particular moment. The latest regime study asked whether similar notation also means similar behaviour through time. It did not.

Question

Can one glyph family contain more than one way of moving, persisting or changing?

What became visible

Comparable momentary states separated into different temporal regimes: long-lived locking on one side, short migrating passages on the other.

What remains open

The finding turns a question back toward the notation itself. Should it become more refined, or should temporal dynamics deliberately remain a separate analytical layer alongside it?

Looking beyond individual states

A single state can be striking, but it says little about how a system behaves over time. A new analysis now follows how notational states appear, persist, disappear and return.

Question

Can repeated movement between states reveal structure that is invisible in a still frame?

What we saw

Some states returned through recognisable two-way rhythms, while others appeared mainly as short passages.

What remains open

The tool measures recurrence and duration, but does not decide what should be called an attractor, passage or oscillation. Those names must follow broader evidence rather than precede it.

Bringing notation back to its living source

The notation used by I·V·O Core was compared directly with the current working matrix. This removed the distance that can grow when software and a developing conceptual source evolve separately.

What changed

Descriptions, configurations and transitions were brought back into alignment with the current source.

Why it matters

A notation system is only trustworthy when its origins, meanings and software behaviour continue to agree.

Boundary

The alignment did not fill every empty place or invent new meanings. Sparsity can be intentional; consistency is not the same as completeness.

Can Core stand on its own?

A small terminal explorer was built outside I·V·O Core. It asks Core to run and simply displays the notation that emerges.

What it demonstrates

Core can be used as a separate computational package without absorbing a visual interface or application layer.

Why keep it separate

The distinction protects both parts: Core remains an architecture, while the Explorer remains a simple way to witness it working.

Limit

A working demonstration shows that the boundary functions. It does not by itself establish how a state should be interpreted.

I·V·O Core reaches version 2.0

The second major version sharpened the distinction between movement, relation and observation. The goal was not to add more features, but to make the architecture say more precisely what it already does.

A key correction

Uncertainty belongs to observation. It should not be mistaken for movement or direction.

A clearer boundary

Physical motion and instantiated relation are connected, but they are not the same layer.

Next question

Core can expose relational properties. The next task is to learn from real regimes before deciding where meaningful transitions or thresholds lie.

Reading status

A record, not a final theory

Each entry reflects the state of the work on its date. Later evidence may refine or overturn an interpretation without erasing the observation that led to it. Detailed source material and verification remain preserved in the versioned development repositories.