Folium XThe Higher-Order Library
Menu

Manifesto

Formal definitions, status labels, sources and limits.

Within the Φ Framework, the product treats a personal library as a changing epistemic environment: a network of physical books, evidence, memory, interpretation and inquiry in which understanding may be revised, provenance remains traceable, relationships can reveal emergent patterns, and validated discoveries can become new instruments for further discovery.

The Φ Framework is a formal conceptual model, not a claim that every expression is an implemented mathematical algorithm. Φ is project-defined notation for a constrained transformation of the library’s state: not the golden ratio, not integrated information (IIT Φ), and not any other established phi quantity.

FOLIUM → X → Φ → HIGHER ORDER

This is an explanatory/product architecture, not a claim that the app literally executes a four-stage mathematical pipeline in every workflow.

Four questions

  1. FOLIUM What exactly is this?
  2. X What is it related to, and how?
  3. Φ What changes because of this evidence/relation/correction?
  4. HIGHER ORDER What becomes possible next?

Object → Relation → Consequence → Possibility · Identify → Relate → Reconsider → Continue

The manifesto structure

This sequence is conceptual/brand notation, not a single mathematical theorem.

X

X is the inspectable relational field in which preserved objects can be connected, questioned, compared, challenged and recontextualized without being collapsed into one another.

X marks where another relationship becomes possible.

Three models

These models are complementary projections, not competing definitions.

The AI’s role

AI = capability / instrument, not entity. Intelligence appears as something Folium X can do, not as another someone the user must learn. The AI is not a fifth layer and not a separate epistemic actor with authority over the reader.

The human remains the reader and authority over personal meaning. Books/copies/passages remain the objects. X is the relational field. Φ describes constrained transformation. Higher-order behavior concerns qualified discoveries altering later inquiry. AI assists across those operations.

Language: Ask Folium X · Explore this interpretation · Folium X found a possible relationship · Compare these passages · Trace this inference · Show counterevidence. Provenance and status labels, not a persona: AI-proposed · Reader-confirmed · Source-supported · Inferred · Hypothesized · Disputed · Unresolved · Superseded.

The differentiator is not “AI plus books.” It is identity-preserving, provenance-aware, recursively extensible inquiry over a personal physical library.

Books are the objects. Relationships are the territory. Inquiry is the movement.

Return without repetition, but never without provenance.

Why Folium X

Where the name comes from, and what it does and does not mean. Brand evocation is kept apart from mathematical meaning.

A real bibliographic object

Folium is rooted in the leaf/page territory from which folio derives. It therefore signals books and material textual culture before the user learns anything about the software. The intended brand use does not require claiming that “Folium X” is a historical phrase. Folium X is the modern composite mark.

Folium and X divide the product concept

X is deliberately polyvalent, not assigned a fake single definition

In the brand it is a controlled, polyvalent symbol that can legitimately evoke crossing/intersection, relation, an unknown under inquiry, a variable open to revision, interdisciplinary intersection and generative combination.

Folium × Context; Book × Book; Passage × Memory; Claim × Evidence; Interpretation × Counterevidence; Discovery × Future Inquiry.

These are explanatory/brand notations, not claims that the application performs literal multiplication.

X, primarily relational

Because x is culturally familiar as an unknown/variable, the symbol can support the product's refusal to pretend that inference equals truth.

Not
X marks what remains to be understood.
But
X marks where another relationship becomes possible.

The second line does not promise that every relationship produces understanding. It preserves uncertainty and makes X primarily relational rather than falsely epistemically conclusive.

Connection without collapse

A central product principle is Relation ≠ Fusion. Books, sources, evidence, interpretations, memories and disciplinary lenses may be connected without being collapsed into one undifferentiated object or one authoritative voice. Folium preserves the thing; X exposes what becomes possible between things.

Every book remains itself. Its relationships can change what becomes visible.

Return without repetition

A page may remain the same while its relational context changes. Folium X therefore supports the existing hermeneutic principle: return to the same book without returning to the same understanding.

Above all thirteen lenses

Folium X can sit above all thirteen disciplinary descriptions because it does not privilege one of them. It is compatible with library science (Work ≠ Edition ≠ Copy), graph/complex systems (relationships as first-class information), hermeneutics (changed context), psychology (mental models without diagnosis), epistemology (evidence/counterevidence/provenance), historiography (path to current understanding), learning science (validated discovery → method), and cybernetics/ethics (assistance without final authority).

The reveal, and the X

The reveal’s motion carries meaning: FOLIUM appears first; one relation leaves the page; another arrives; they cross; X resolves. The reveal on the home page.

Separate from AI branding

Folium X is a library and an intellectual environment first. Its interpretive AI is an instrument inside the product, not the product’s identity.

There is no separately named AI. Intelligence is something Folium X can do, labelled by provenance and status, never a persona.

Formal definitions

The Φ Framework’s notation, made precise, each with what it does not claim.

V in G = (V, E)
the vertices: books, copies, passages and other recorded objects.
V over the arrow
validation / reader authorization / epistemic qualification; not a set of vertices, and not a test of reliability.

S is shorthand for the library state ℒₜ. Φ(S) shortens Φ(ℒₜ, xₜ, Cₜ): it holds the displayed input xₜ and constraints Cₜ fixed for that step. An invariant such as I_P(Φ(S)) = I_P(S) is claimed only for an admissible transition under its stated constraints, not for arbitrary updates.

D0

The common object and its graph view

DESIGN PRINCIPLE
ℒt=(Ot,Rt,Et,Mt,Ht,At)

In words script L sub t equals the tuple O sub t, R sub t, E sub t, M sub t, H sub t, A sub t: objects, relations, epistemic records, methods, history and reader authority at step t

Gt=(V(Gt),E(Gt)),V(Gt)=Ot

In words The graph view: its vertices are the recorded objects; its edges are the relation instances of R sub t.

Φ Framework notation, with the status of what it expresses.

t indexes recorded steps. Oₜ is a finite set of typed objects (Work, Edition, Copy, Passage, Person, Place, Memory, Concept, Question, Inquiry, Instrument). Rₜ holds the relation instances among them. Eₜ holds the epistemic records; each has content, a target, an origin κ and a reader decision δ, kept as separate fields: κ ∈ {source text, bibliographic record, reader testimony, system inference, interpretation, invention} and δ ∈ {undecided, accepted, rejected, revised}. An acceptance never overwrites an origin. Mₜ holds the instruments (D6). Hₜ is the event history, within the scope of D5. Aₜ is the reader’s authority, the only source of δ for personal meaning.

Not claimed. A conceptual model, not a data schema.

D1

Admissible transformation (Plasticity | Fidelity)

DESIGN PRINCIPLE
Φ(ℒt,xt,Ct)=ℒt+1

In words Phi of script L sub t, x sub t, C sub t equals script L at step t plus 1: the library state after input x sub t, under constraints C sub t

apply:𝕃×X⇀𝕃,Φ:𝕃×X×𝒞→𝕃

In words The effect, apply, is partial; the transition Phi is total.

Φ Framework notation, with the status of what it expresses.

The effect is partial: a candidate result exists only when the input can be applied at all. Each constraint c ∈ Cₜ is a predicate on the current state, the input and that candidate. The transition is total. Accepted: if the input applies and every constraint holds, Φ returns the candidate, with the acceptance appended to its history. Refused: otherwise Φ returns ℒₜ with only its history extended by a refusal event, whose reason is “not applicable” or the failed constraints. So ℒₜ₊₁ always exists, and a refusal changes nothing but the history. Constraint families in the framework: provenance, identity, permissions, source fidelity, privacy, reader authority, epistemic status. Revisable fields: interpretations, questions, methods, associations, confidence. Fidelity-protected fields: source origin, exact-copy identity, historical record, permissions, provenance; Φ changes these only through an explicit, recorded correction.

Not claimed. No numerical dynamics, no algorithm running in the app, and no meaning of Φ outside this project: not the golden ratio, not integrated information.

D2

Relation record and temporal consistency

The designDESIGN PRINCIPLEThe theory drawn onESTABLISHED THEORY
e=(u,v,r,τ,π,κ,δ)

In words An edge records its endpoints u and v, its relation type r, the time recorded tau, its provenance pi, its origin kappa and the reader's decision delta.

E(Gt)⊆V(Gt)×Rel×V(Gt)

In words At every moment t, every edge recorded by t has both endpoints recorded by t.

Φ Framework notation, with the status of what it expresses.

The relation vocabulary is partitioned. Derivation: grounded-in, quoted-from, edition-of, contains, generated-by, revision-of, answers, asks-about. Evidential: supports (evidence found later), resists or complicates (E⁻). Descriptive or comparative: compares, shares an image with, located-at, recalls. Only derivation relations are traced as provenance.

Not claimed. Graph theory is established; the relation record is Φ Framework notation for a design principle.

D3

Provenance against evidence

The designDESIGN PRINCIPLEThe theory drawn onESTABLISHED THEORY
der(x,y)⟹τ(y)≤τ(x)

In words If x was formed from y, then y was recorded no later than x.

ev−1(x)=E+(x)∪E−(x)

In words What bears on x splits into supporting and resisting evidence.

Φ Framework notation, with the status of what it expresses.

Two different relations on records. der: x was formed from y; acyclic and time-respecting. ev: y bears on x, as E⁺ or E⁻; it can be added at any time. The provenance trace (the Provenance Microscope) is the der-closure of x (why-provenance) and, for quotations, the exact passage in an exact copy or edition (where-provenance). The evidence balance is ev⁻¹(x). These answer different questions: where a claim came from, and what bears on it (Reichenbach’s distinction of discovery and justification). The origin of a claim is not evidence for it, and a supporting passage found later is evidence, not origin. Gaps are records: an unknown link ends in an explicit gap, never in silence. W3C PROV-DM is a formal analogue, with no conformance asserted.

Not claimed. No claim that the app computes these closures today.

D4

The provenance invariant

DESIGN PRINCIPLE
IP(Φ(S))=IP(S)

In words I sub P of Phi of S equals I sub P of S: on surviving claims that were not corrected and whose sources were not deleted, the transformation leaves each claim's origin and derivation unchanged

IP(S′)|K∖(Corr∪Del)=IP(S)|K∖(Corr∪Del)

In words Restricted to surviving claims K that were neither corrected nor touched by a deletion, the provenance record after the step equals the record before.

Φ Framework notation, with the status of what it expresses.

For one admissible step S → S′ (S is shorthand for the library state ℒₜ; the step is Φ(ℒₜ, xₜ, Cₜ) under its stated constraints, with the displayed input and constraints held fixed), let K be the claims present before and after, Corr those with a correction event in the step, and Del those with a deletion event for the claim or for a record in its derivation closure. The restricted record keeps, for each claim, its origin and its derivation closure. Every surviving claim that was neither corrected nor touched by a deletion keeps exactly its origin and its derivation closure. Exceptions, each recorded: a corrected claim changes exactly as its correction event states, and the event appears in its trace; a deleted record in a closure is replaced by a deletion record without its words (in the app’s intended design, the item’s identifier and the time, which stay linkable to the item on the device), and nothing else changes; new and removed claims lie outside the equality, and a claim leaves only through a recorded deletion. As the framework puts it: “The principle is not that records can never be corrected or deleted; it is that transformation must not silently falsify origin.”

Not claimed. Not equality over all claims: a step may add or remove claims.

D5

Revision without erasure

DESIGN PRINCIPLE
St→St+1,Ht+1=Ht·et+1

In words S sub t becomes S at step t plus 1, and the next history is the current history with one event appended.

Sk=replay(H[1…k])up to deletion

In words An earlier state is recovered by replaying the retained history, with deleted items replaced by their markers.

Φ Framework notation, with the status of what it expresses.

Scope: the synthetic demonstration and, in the product, only retained, authorized records. Revision is recorded, not overwritten: within retained records, Hₜ is a prefix of Hₜ₊₁. Deletion is itself an appended event: it removes the deleted content from every retained state and from the replayable history, and, in the app’s intended design, a record of the deletion stays on the device: the item’s identifier and the time, never its words, linkable to the item. Backups made in the app carry that record, and a device backup may include it. Formal analogues, as correspondence only: persistent data structures (which keep every version by design — exactly where the analogy stops for private content), valid time against transaction time, and AGM belief revision.

Not claimed. Never implies that deleted private content is kept; no claim of completed permanent erasure (for example from backups outside the app’s control) follows. The deletion record is described as intended design until its implementation is verified. The app implements no AGM operator.

D6

Validated generativity

DESIGN PRINCIPLE
Dt⟶VfDt

In words D sub t, arrow labelled V, f sub D sub t: a discovery becomes a method only after validation, reader authorization and epistemic qualification

Mt+1=Mt∪{fDt}if V holds; otherwiseMt+1=Mt

In words The methods gain the instrument only if V holds; otherwise they are unchanged, and the refusal or revision request is recorded.

∀f∈Mt∖M0∃v∈Ht:v=(validate,Df,accept,reader)

In words Every instrument made from a discovery, that is every method not in the initial set M sub 0, has a matching reader validation event in the history.

Φ Framework notation, with the status of what it expresses.

Dₜ ∈ Eₜ is a discovery (a distinction, pattern or question) with its origin and basis. f_Dₜ is an instrument: a function from a library state and a scope to proposals. The map from D to f_D is higher-order: it returns a function (Church; Strachey; Reynolds). V is a guard, not a computation. It holds only when both hold: (i) reader authorization, an explicit accept event by the reader; and (ii) epistemic qualification: purpose, scope and assumptions stated; the basis in Dₜ recorded; the instrument checked against at least one resisting case, or the absence of one recorded; Dₜ’s origin and status still visible. Instrument outputs are proposals, with the origin “instrument f_D, applied”, and need reader review; an instrument never writes trusted state directly.

Not claimed. Not an automatic promotion: no discovery becomes a method because it exists in the system.

D7

Interpretation

The theory drawn onESTABLISHED THEORYThe correspondenceSTRUCTURAL CORRESPONDENCE
ik=h(ik−1,ck)

In words Each interpretation is computed from the previous one in a new context c.

text(p)invariant

In words The passage's text stays byte-identical across the loop.

Φ Framework notation, with the status of what it expresses.

For a passage p with fixed text, an interpretation is context-indexed, i(p ∣ c), for contexts from passage to book, collection, reader and world. The loop recomputes the interpretation in each new context; the invariant is the passage’s text, identical at the start and on return.

Not claimed. No convergence is claimed: understanding is never final (Gadamer).

D8

Counterevidence

The theory drawn onESTABLISHED THEORYThe designDESIGN PRINCIPLE
E+(H),E−(H)⊆Et

In words The supporting and resisting evidence for an interpretation H are both drawn from the epistemic records.

Λ(e)=P(e∣H)P(e∣¬H)

In words In illustrative Bayesian models only: the likelihood ratio of an item of evidence e.

Φ Framework notation, with the status of what it expresses.

E⁺(H) and E⁻(H) are shown together. Resistance comes in two kinds (Pollock): rebutting, evidence for not-H; and undercutting, evidence that a supporting link fails, for example a disputed translation. Bipolar argumentation formalises support together with attack. In illustrative Bayesian models only: factors multiply only under conditional independence; a posterior probability requires exhaustive hypotheses; evidence reduces entropy only on average. Discovery is not similarity: retrieval by resemblance over-selects E⁺ (confirmation bias), so E⁻ must be sought explicitly.

Not claimed. No calibrated probabilities; the app is not claimed to compute any.

D9

Agency

DESIGN PRINCIPLE
κ(p)fixed,δ(p)∈{accept,reject,revise,defer}

In words A proposal's origin kappa is fixed; the reader's decision delta is held separately.

Φ Framework notation, with the status of what it expresses.

An AI proposal has the origin “system inference” (shown as AI-proposed), and that origin does not change when the proposal is accepted or edited. The decision δ is the reader’s, in a separate field. An edit creates a new record authored by the reader, derived from the proposal. Only reader decisions change the status of personal meaning: suggestion followed by human selection, in the levels-of-automation sense.

Not claimed. Assistance ≠ Authority.

D10

Emergence

The correspondenceSTRUCTURAL CORRESPONDENCEThe theory drawn onESTABLISHED THEORY
χ(Gt)∧χ(G′)≠χ(Gt)

In words The pattern chi holds on the arranged graph, and fails on some graph G prime with the same vertex labels.

Φ Framework notation, with the status of what it expresses.

A collection pattern χ is a predicate on the labelled graph Gₜ (χ, not π, which names an edge’s provenance). It is emergent (non-aggregative, in Wimsatt’s sense) if χ(Gₜ) holds and some G′ with the same multiset of vertex labels has χ(G′) ≠ χ(Gₜ): the pattern depends on the arrangement of relations, not only on the parts. Four layers stay distinct: stored facts; derived relationships; emergent pattern; interpretation of the pattern.

Not claimed. No stronger, metaphysical emergence is claimed.

D11

Humility

DESIGN PRINCIPLE
Pattern≠Person

In words A pattern is not a person.

Φ Framework notation, with the status of what it expresses.

A typing rule. Patterns are predicates on the collection graph, never on the reader. No rule maps a pattern to a reader attribute: diagnosis, personality, ideology, identity or stable belief. Any statement about the reader has the origin “reader testimony”. Aggregation can reveal what no single record reveals, which is exactly why emergent patterns stay about books.

Not claimed. Prediction ≠ Identity.

D12

Recursion

DESIGN PRINCIPLE
yt−1=out(ℒt−1),ℒt+1=Φ(ℒt,xt,Ct),xt∋yt−1

In words The next state is Phi of the current state, the input x sub t and the constraints C sub t; when the previous output, y at step t minus 1, the output of the state at step t minus 1, is fed back after review, the input contains it.

Φ Framework notation, with the status of what it expresses.

A system output re-enters trusted state only through reader review (D9), and for methods also through V (D6).

Not claimed. No fixed point, convergence or stability is claimed.

D13

Distinction

The designDESIGN PRINCIPLEThe theory drawn onESTABLISHED THEORY
edition⊆Copy×Edition,embodies⊆Edition×Work

In words The edition relation links copies to editions and need not cover every copy; embodiment relates editions and works, many to many.

H(A∣Edition)=∑eP(Edition=e)·H(A∣Edition=e)

In words The conditional entropy of the recorded copy attributes A given the recorded edition, under a stated distribution over the copies.

Φ Framework notation, with the status of what it expresses.

Relations, not total maps: a copy’s edition may be unknown (“edition not recorded” is a legitimate record) and a bound-with volume can join several editions in one copy; an anthology or omnibus edition embodies several works, and a work has many editions. Only in a labelled, simplified case (one known edition per copy, one work per edition) may these be written as functions. Reference model: IFLA LRM (Work, Expression, Manifestation, Item); the product folds Expression into Edition, a limit it states. Information loss, stated only under a defined distribution: take a finite collection with a stated distribution over its copies, A the recorded copy-level attributes and Edition the recorded edition, written out in full so that it is not confused with E, the edges. H(A ∣ Edition) is positive if and only if some edition with positive probability has copies whose recorded attributes differ; an edition with exactly two copies whose recorded inscriptions differ, in n equally likely copies, contributes (2/n) × 1 bit. By the data-processing inequality, nothing computed from the edition recovers what H(A ∣ Edition) measures. Missing copy detail is a gap, not entropy. An ISBN identifies a publication — a given title in a given edition and binding — not a work and not an individual copy. The ISBN became ISO 2108 in 1970, building on the UK's Standard Book Number of 1966–67. Many older printings carry no ISBN, but publishers must number their backlist, and the ISBN must appear in the first available reprint or reissue of a backlist title (ISBN Users' Manual, 6th ed., 2012, §5.7). A copy record must therefore never require an ISBN.

Not claimed. Nothing is claimed about unrecorded copies or real collections.

Retained theory

The reviewed mathematics of Theories, theorems & principles is kept, with its conditions stated.

T1

Theorem: the data-processing inequality, and the information toy

The theory drawn onESTABLISHED THEORYThe correspondenceSTRUCTURAL CORRESPONDENCE
I(X;Z)≤I(X;Y)forX→Y→Z

In words For a Markov chain X to Y to Z, Z carries no more information about X than Y does.

I(K;T)=0,I(K;T,P)=H(K)

In words Assuming the words alone carry nothing about status: the text T tells nothing about a line's kind K; the text with its provenance label P tells everything.

The inequality is a theorem. The toy is an exact illustrative model: a quoted line and an inferred line with identical text T; the kind K is recoverable only from the provenance label P, and per-claim values are averages. Strip P and no processing of T restores it. The design choice that follows is separate from the theorem: so the design keeps provenance with the claim.

T2

Theory: belief revision and Bayes

The theory drawn onESTABLISHED THEORYThe correspondenceSTRUCTURAL CORRESPONDENCE
K*φ=(K÷¬φ)+φ

In words The Levi identity: revision is contraction then expansion.

P(H∣E)P(¬H∣E)=P(H)P(¬H)·∏iP(ei∣H)P(ei∣¬H)

In words Posterior odds are prior odds times the likelihood ratios, assuming conditional independence and exhaustive hypotheses.

AGM belief revision describes the qualitative change of an accepted set; Bayes’ theorem, graded belief. The product form needs conditional independence of the items given each hypothesis, and a posterior probability needs exhaustive hypotheses (exactly one of H and ¬H holds, so P(¬H) = 1 − P(H)). On this site both describe structure the design shares; the app is not claimed to compute either.

T3

Law: requisite variety (qualitative)

The theory drawn onESTABLISHED THEORYThe correspondenceSTRUCTURAL CORRESPONDENCE
St→Proposalt→Reader Reviewt→Correctiont→St+1

In words The loop, with the reader inside it.

Ashby’s law of requisite variety, stated qualitatively and with its condition: when no single response serves different disturbances, a regulator needs responses as varied as the disturbances it must absorb. No counting or entropy inequality is asserted here; a quantitative form needs its own stated assumptions.

T4

The semiotic tower

The theory drawn onESTABLISHED THEORYThe correspondenceSTRUCTURAL CORRESPONDENCE
I0=Text,In+1=Interp(In)

In words Each order interprets the one beneath it, starting from the text.

Every layer keeps a pointer to the layer beneath: the thing, the sign and what has been said about the sign stay distinct. For AI reliability, that pointer is the difference between a quotation and a statement about a quotation. An interpretation is never displayed as the text.

The five status labels

This site is designed so that no visual presentation erases this distinction: a beautiful animation could otherwise make a structural analogy look like an implemented scientific algorithm.

On anavi.dev, Anavi labels the kind of claim a company statement makes. Here, Folium X labels the specific claim being made: a design, a theory, a correspondence, a mechanism or an exploratory hypothesis. Neither is a confidence score, and the two do not map one to one.

Truth boundaries

What is not claimed here, and what is kept apart.

  1. Φ is project notation, defined where it is first used: not the golden ratio, not integrated information (IIT Φ), and not any other established phi quantity.
  2. No numerical computation of belief is claimed; that would first have to be implemented and verified.
  3. Pattern ≠ Person.
  4. Folium X is designed to keep stored fact, derived relationship, emergent pattern and interpretation distinct; this site aims to do the same.
  5. Folium X is designed to preserve counterevidence, uncertainty, provenance and reader authority; this site aims to do the same.
  6. Design principles are not release claims.
  7. Not every discovery automatically becomes a method. This site writes generativity in the validated form Dₜ →ᵛ f_Dₜ.
  8. Folium X is designed never to infer diagnosis, personality, ideology, identity or stable belief from book ownership or from recurring collection patterns.
  9. Extended cognition is not described as settled empirical proof that a library is literally part of your mind.
  10. No visual here, however sophisticated, is meant to make a structural correspondence appear to be a verified implementation or a scientific validation.
  11. Folium X is not a mathematics app.
  12. The Φ Framework’s symbols are not established formulas for personal libraries; they are project-defined conceptual notation.
  13. The disciplinary correspondences are not claimed to be causal mechanisms implemented in software.
  14. No psychological benefit is claimed, and Folium X is designed not to infer diagnosis, personality or identity from a collection.
  15. Folium X is designed not to turn recurring themes into statements about who a reader is.
  16. Extended cognition is not represented as settled empirical proof that the library is literally part of your mind.
  17. Emergent patterns are not presented as ground truth; stored fact, derived relationship, emergent pattern and interpretation are meant to stay distinct.
  18. Folium X is designed never to become the final authority over personal meaning.
  19. When a reader accepts or edits AI-generated or inferred content, Folium X is designed to keep its origin, not erase it.
  20. A design principle is not to be read as released: unless this site says a behaviour has been verified, it describes what Folium X is designed to do.

Sources, by lens

A working source map: 7 of 126 entries have been checked, and each says what was checked. Every other entry is marked as not yet checked against the source; until it is checked, it is a lead, not a verified reference. 5 further entries were added for names in the lens texts: 3 with a bibliographic record found, and 2 still a lead to confirm. A registry record confirms the reference, not the claim it supports; none of these has had its content checked against the source.

Limitations

How to read the diagrams

The order of priorities is correct meaning, then clear interaction, then accessibility, then visual spectacle: visual ambition is not meant to come before semantic correctness.

The reading key

  • Atlas paths solid for a documented structural correspondence, dashed for an exploratory hypothesis; where nothing is drawn, nothing is claimed.
  • Status labels written in words, so that colour is not the only signal; where a card carries more than one, each says which claim it labels.
  • Uncertainty meant to be stated in words and status labels, not shown by blur.
  • Earlier states meant to stay beneath the present one, not be silently overwritten.
  • Support and resistance in the counterevidence demonstration, set on opposite sides with the interpretation between them; their colours are not meant to code good and bad.
  • Instruments in the forge, an instrument admitted through V is shown apart from the discovery it came from, with its limits.

Motion

Where something moves, the movement is meant to carry meaning:

  • Transformation one state morphs into the next; nothing explodes.
  • Recursion a path returns to an earlier object in a changed context.
  • Higher order a discovery visibly becomes a method or instrument admitted through V.
  • Invariance the provenance trace stays while the rest of the view changes.
  • Emergence a larger pattern becomes visible only once enough relations are present.
  • Agency the animation pauses where the reader decides.

With reduced motion, the steps are designed to appear as still states that keep the full meaning.

In one line

What each lens sees, at its shortest, with two of the principles.

Psychology, without diagnosis

Accessibility and comprehension

The design commitments this site is built toward; see also the site’s accessibility statement.

These are design commitments, not a claim that every page already meets them. If something here does not work for you, please tell us through Support.

Ten questions to ask of any feature

Questions you can put to any Folium X feature, and to this site itself. This page does not claim that every answer is already yes.

  1. Object integrity: What identifiable object(s) does this operate on?
  2. Relation: What relationship is being asserted/proposed, and is its type/status visible?
  3. Provenance: Can the user inspect where the claim/relation came from?
  4. Epistemic status: Is fact separated from inference/interpretation/hypothesis?
  5. Revision: What can change, and is prior history preserved where appropriate?
  6. Counterevidence: Can resisting evidence remain visible?
  7. Agency: Where does the reader accept, reject, correct or authorize?
  8. Higher order: Does the result merely answer, or can a qualified result improve later inquiry?
  9. Scope: If a discovery becomes an instrument, are its limitations retained?
  10. Return: Can the user get back from abstraction to the exact book/copy/passage/evidence?