I · V · O — Open research

Research logbook

A dated record from the canonical foundations through current studies. Candidate work, frozen plans, completed checks and unresolved questions retain the status they had at the time.

Current record

Latest entries

The record follows canonical releases, visual studies, instrument experiments and observations that materially change the direction of the work.

Newest first · An open record

A revision candidate separates selection from autonomy

The experimental Lens programme reached a recorded freeze decision for v0.4-amended, with a qualified regression verdict. A comparison with v4.1 then supported drafting a targeted v4.2 revision candidate. The question is whether an evidenced selective function should remain identifiable when its mechanism is fully understood.

What changes in the candidate

The proposed I-rule separates selective function, mechanistic implementation and residual structural openness. It also distinguishes a function’s demonstrated capacity to affect a continuation from the contribution of one realised event. Redundancy or compensation can mask an event’s net effect while causal capacity remains evidenced in relevant admissible conditions.

Decision boundary

v4.1 remains the active canonical Lens. The experimental freeze and permission to draft a revision do not adopt v4.2. The candidate retains O — Structured Possibility, V — Instantiated Relation and I — Situated Selectivity, while proposing changes to the evidence required for I.

What remains open

The candidate still requires regression review, cross-model reproducibility, heterogeneous real-world validation and governance approval. The published dossier preserves supplied summaries and decisions; it is not a complete archive of raw inputs, outputs and execution settings for every reported run.

Full research checkpoint → · v4.2 candidate · Active canonical reference

Positional information survives; an independent position category does not yet earn its place

T4 tested whether location, asymmetric access, memory, persistent baselines and relocation justify an independent I-position dimension. Even the strongest reported cases remained reconstructable through O/V when history, internal state and update rules were included.

What became visible

Identical current inputs can produce different registered results because their carriers retain different histories. That difference matters, but it did not demonstrate additional analytical content from a separate position assignment once the complete reconstruction preserved those histories.

Experimental decision

Independent I-position was demoted to an unresolved research hypothesis. Scope, carrier, access, history and outside view remain required analytical conditions. The earlier positive historical-register assignment, NM-07, was reviewed as UNRESOLVED; ordinary sensor/channel access, NM-07B, remains NOT ESTABLISHED.

Recovery condition

A future positive position claim must show an operationally identifiable distinction that is lost when position is removed, even after full O/V reconstruction including history and state. The current tests do not establish such a distinction, or prove that none could ever be found.

T4 amendment proposal → · Original analysis and review

A causal effect is not enough to establish selection

The first v0.2 cases reported useful positional detail without established I-functions. Deliberately constructed positive cases then exposed the opposite risk: transparent selection mechanisms were absorbed into O/V, while partially reconstructed cases remained unresolved. Matched A/B comparisons opened an experimental distinction between function and autonomy.

The veto boundary

T3 separated ranking, shortlist, final selection and execution, but its positive compliance-veto assignment lacked a principled distinction from thermostat-like thresholding. T3B retained negative gate/classification cases and a positive constrained allocation: changing a competitor could change a project’s admission while that project itself stayed identical.

Qualification

Relational allocation with selective consequences and an effect on continuation supplies a positive discriminator in the tested structure. It has not been shown necessary for every possible selective function. Downstream effects, admission/exclusion labels, threshold sensitivity and classification alone remain insufficient.

Learning from the failure

The fixed independent compliance gate was reclassified as I-function NOT ESTABLISHED. T5 later required another correction: functional capacity and the contribution of a particular event must be assessed separately when redundancy, override or compensation matters. These corrections remain visible alongside the original reports.

v0.2 and A/B record · Qualified T3B review · T5 correction

Stronger evidence safeguards, unchanged operators

I·V·O Lens Prompt v4.1 is now the canonical successor to v4.0, published as release v4.1.0 on Zenodo and synchronized with GitHub. The meanings of O — Structured Possibility, V — Instantiated Relation and I — Situated Selectivity remain unchanged. The update strengthens how an analysis handles evidence and uncertainty.

What changed

Evidence provenance and claim status are separated. Observations do not automatically establish objects, classes or mechanisms; hypotheses remain distinct from established conditions. Unresolved claims are distinguished from supported negative claims, and evidential dependencies, causal status and the requirements for assigning I are made explicit. Synthesis cannot increase claim strength; unresolved analysis prioritizes information gain over intervention.

What was tested

The frozen RC2 candidate was run unchanged across Claude, ChatGPT and Gemini in a controlled Hessdalen regression without an external source base. The major targeted failure modes were prevented across models. Residual variation remained around epistemic ambiguity versus structural openness in human classification. These results concern the tested conditions, not universal validity or immunity to model bias.

Provenance

The exact frozen RC2 regression artifact remains the immutable archival copy in Zenodo. GitHub records a provenance pointer and the canonical v4.1 successor. The v4.0 release remains available as a historical predecessor. The website analysis tool now uses the canonical v4.1 prompt.

Zenodo v4.1.0 · DOI 10.5281/zenodo.23083767 · GitHub synchronization · Hessdalen regression note · Canonical reference · Use the analysis prompt →

One dataset, two ways of looking

The first step with this dataset was to leave the existing instrument closed. In the partner-choice experiment published by Stallen and colleagues, people ranked types of partners; the software then formed the actual pairs. Treating those rankings as choices of individual people would have changed what the data meant. The source did not fit the frozen R12 profile. It did, however, offer a good reason to build a different lens.

From preference to pairing

A separate descriptive instrument followed 24 rounds in 21 partner-choice groups of eight people. The realised partner had the participant’s highest-ranked type in 44.99% of participant-rounds, averaged equally across groups. That fraction describes what the group matching process realised; it is not an individual chance of getting a preferred partner.

Looking between rounds

A second lens followed 3,864 participant transitions. The highest-ranked type stayed the same in 79.14% of transitions, while the complete ranking stayed unchanged in 66.51%. A stable first preference could therefore coexist with movement lower down the list. The same source became informative in a different way when the question shifted from states to their sequence.

What this opens up

Preference, realised pairing and persistence can be measured separately and then studied together through time. Both plans were fixed before their respective calculations, after the original study had already been examined. These are retrospective descriptions, not independent replications or evidence that a pairing caused a later preference. The next questions concern how relationships endure and return, with each new lens responsible for defining what it can actually observe.

Explore the source dataset → · Read the original study →

What the apparatus cannot see

The R9 study reduced how much of O the measuring apparatus could observe while leaving the simulated engine unchanged. The question was whether missing context could be mistaken for a directional relation.

What became visible

In this calibration model, reduced visibility produced a strong rise in apparent I→V and same-step association, while apparent V→I remained approximately stable.

Boundary

This is a finding about Engine 03 and its measurement chain. The stronger idea that system I acts as a substitute sensor for unseen O remains a hypothesis; known construction choices can also explain the asymmetry.

What remains open

A separate R10 intervention study has been proposed to distinguish genuine V→I influence from shared or partly unseen O. It is a design note, not a completed experiment, and would not by itself settle the explanation of the R9 asymmetry.

Ivory threads disappear through dark glass planes, an abstract study of partial visibility.
02 / Partial observationWhat remains outside the frameConceptual illustration

Giving each claim its conditions

A result needs more than a label. Claim records were added to the analysis layer to keep a statement together with its epistemic status, assumptions, treatment of O and the limits of the method that produced it.

What changed

The records distinguish what is observed, derived or dependent on a model. They also retain alternative compatible structures and the observations that could distinguish them.

Why it matters

A known failure of method validity limits the strength of a claim. Calibration evidence can restrict a conclusion; it cannot silently promote it into a stronger one.

What remains open

The record format makes limits explicit. It does not remove the measurement problems or establish whether a proposed relation is present in external data.

Returning to the hard cases

Six earlier stress tests were published as a connected reading series: Gödel, the Liar, random bitstrings, multiple observers, quantum mechanics and time dilation.

What changed

The earlier analyses are presented through the v4.0 operators, with historical notes explaining the change in terminology.

Boundary

The series records where the Lens needed sharper distinctions. It is not a demonstration of universal validity, and the original tests are not retrospectively described as v4.0 experiments.

What remains open

Can these distinctions remain informative when a framework encounters self-reference, ambiguous evidence and limits on observation? Each article keeps its own unresolved question visible.

Read the six stress tests →

A stop rule becomes a finding

Engine 03 was built as a calibration and falsification harness with deliberately configured relations. Its evaluation followed a frozen protocol so that the measurement chain could be tested against cases whose construction was known.

What became visible

The chain passed several checks, but failed the directional, mutual-coupling and shared-cause criteria. In the shared-O case, apparent coupling persisted despite conditioning on O.

What changed

The shared-cause failure triggered the predeclared stop rule. The estimator was not tuned within that evaluation slice to make the failed result disappear.

What remains open

How can the method distinguish a relation from structure induced by a shared cause? Engine 03 calibrates the apparatus; its configured coupling provides no independent evidence for a general V–I hypothesis.

Fine threads and metal measuring frames meet a small red stop marker.
05 / CalibrationA boundary worth keepingConceptual illustration

Separating the engine from the lens

Prototype 1 established a shared Core around two different engines: a small non-spatial synthetic system and an adapter for the existing simulator. Measurement and interpretation were kept outside the invariant infrastructure.

What changed

Explicit scopes and replaceable measurement sets made it possible to state what an instrument accesses and which part of a system its reading concerns.

What was checked

Passivity checks and legacy-reproduction tests examined whether observing or replacing a measurement layer changed the underlying engine state.

What remains open

Passing these architectural checks does not establish that a particular operationalisation is the right one. Different lenses still need to be compared through their assumptions, access and evidence.

A separate glass lens stands before a delicate network inside an open frame.
06 / System and observerOne process, different readingsConceptual illustration

Keeping exploration separate from confirmation

Wave 1 and Wave 1b examined relational observables in the same fixed simulation configuration. The first wave remained exploratory. A statistical procedure was frozen before a separate set of twenty runs was acquired for Wave 1b.

What became visible

Seven of twelve eligible comparisons met the specified multiple-testing threshold in Wave 1b. Other comparisons were excluded where the quantities did not permit an identifiable test.

Boundary

The two sets of runs were not pooled. An association is not evidence of causation or redundancy, and a non-significant result is not evidence of independence. The multiple-testing assumptions were reported as unverified.

What remains open

The findings are limited to the tested configuration. The relation between duration and latency remained ambiguous under the chosen criteria; further configurations would be needed to assess how general it is.

Closing a phase without adding a glyph

The O state-grounding phase was formally closed after its four follow-up investigations. The measured aspects were classified or explicitly bounded as non-discriminative or not applicable.

What became clearer

Some readings describe continuous profiles; others depend on the interaction between field and boundary. A numerical distinction does not automatically justify a separate state or symbol.

What stayed unchanged

None of the investigated aspects justified a new regime or glyph. The canonical notation and readO() remained unchanged; an applicability guard clarified where an existing structure metric can be used.

Next question

The next phase turns to V: how should a macro-level description of movement be distinguished from an attributable relation? Closing the O phase does not answer that separate question.

Measuring O before naming its regimes

Eight additional O aspects were implemented and followed by a shared characterization dataset. The work examined field, boundary and interface properties before deciding how they should be classified.

What changed

The measurement programme covered properties such as permeability, continuity, structure, extent and boundary presence. A first classification then used the frozen dataset.

Why this order matters

Building a measurement is different from establishing a meaningful regime. The sequence keeps a new instrument from becoming an automatic argument for a new symbol.

What remains open

Which distinctions are supported by the measured behaviour, and which belong to continuous profiles or interaction conditions? The later grounding phase takes up those questions.

Letting the process continue beyond the browser

The Live Observer was added as a public research instrument. Its simulation engine was subsequently moved to the server, separating the running process from the browser that displays it.

What changed

The browser receives updates from the running engine. Follow-up changes refined the update flow and simulation cadence.

Boundary

A live display provides access to a process. Its visual continuity does not by itself validate the notation or establish the meaning of the behaviour being shown.

What remains open

Which patterns persist through time, and which depend on the sampling and display conditions through which the observer encounters them?

Open the Live Observer →

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.

Relational notation candidates enter the record

Candidate relational grammars and a field instrument were added for comparison. Their presence in the repository did not make them canonical or empirically validated.

Canonical commit 1aad2c1 →

Kernel v2 and canonical preflight

A founder-reviewed breaking change promoted the v2 kernel contract and added preflight controls. This strengthened the separation between candidate material and the canonical layer.

Canonical commit d11dc4d →

Relation is separated from movement

A change-decision proposal described V as instantiated relation and opened a research route around that distinction. At this date it was proposal-stage work; the existing feedback visual was archived before later rebuilding.

Proposal 4870dce · research route bc80881 · visual archive 7e940fe

Design Protocol v1.1 is released

The protocol made assumptions, implications and stop conditions explicit, using the operator terminology current at that time. It remains preserved as historical provenance; the present design protocol supersedes its operator definitions.

Canonical commit b64f535 · current Design Protocol →

Analysis v3.2 and Baseline 1.0 are frozen

The baseline fixed the planned procedure before execution. The record explicitly contained no empirical result; the proposed 330-call study remained blocked by API and token cost.

Canonical commit d71b567 →

Assumptions are recorded before synthesis

Conceptual stress tests and external critique led to protocol versions 2.2 and 2.3, including constitutive assumptions and a refusal to synthesize when prerequisites failed. These were methodological refinements, not empirical validation.

v2.2 · v2.3 · dialogue provenance

The Assumption Ledger is proposed

A candidate amendment required assumptions and their failure effects to be stated explicitly. The entry preserves its proposal status on that date.

Canonical commit 2234289 →

An early public archive is synchronized

Archive v3 and an AI-alignment formulation recorded the framework in the terminology then in use. Those names are historical and have since been superseded by Situated Selectivity, Instantiated Relation and Structured Possibility.

archive v3 · historical AI text

The canonical repository and briefing layer are established

The versioned canonical architecture began on 31 May. Briefing documents followed on 8 June, creating a traceable layer for definitions, decisions and later revisions.

repository foundation · briefing layer

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. This is a selected chronology rather than a claim that every development is represented; early entries link to exact canonical commits, and later canon may supersede their terminology.