public hub
Start here when orientation matters.
This is the calmer front door for identity, project framing, and the readable explanation of how Walter's surfaces relate.
Walter Franchetti
Use this page only when the right route is not obvious yet.
If you already know you need the lab, writing, updates, or contact, go there directly. This page exists to reduce uncertainty, not to become another stop.
Network map
The `lter.*` domains exist to separate concepts, editorial rhythm and operational functions. They are not a backlink wheel, they do not replicate articles and they do not all launch at once.
Active path
First the center of the system becomes solid. Then the properties that truly deserve to exist can open.
main hub
Main hub of Walter Franchetti's personal network.
It holds identity, projects, orientation and cornerstone pages together. It should explain the system in a few minutes without asking visitors to chase scattered domains.
public lab
Home for experiments, systems and the build log.
It collects technical notes, changelog entries, experiments and internal operational surfaces. It is the right place to show process, tools and discipline.
writing surface
Home for long-form writing and structured reflection.
It now carries the first migrated legacy corpus and new long-form writing. It should not become a generic blog, but keep a sharp editorial voice.
updates surface
Short digest layer and periodic selection surface.
It is not the canonical source of content, but the editorial downstream of the network. It should help people follow the rhythm, not duplicate pages that already exist elsewhere.
Five-surface atlas
This is the whole system as it should read today: four public climates with one separate operator plane. The split matters because the lab should not quietly become an internal admin surface.
public hub
This is the calmer front door for identity, project framing, and the readable explanation of how Walter's surfaces relate.
public lab
Notes, experiments, changelog, and public process belong on the lab when implementation detail is part of the value.
writing surface
Arguments, frameworks, and essays live here when the work can stay useful later instead of only reporting current motion.
updates surface
Short signals, current focus, and lighter downstream entries belong here when the network needs readable present tense without duplication.
operator surface
Studio is the internal control plane for readiness, queues, and authenticated review. It should stay separate from the public lab even when the auth boundary is still shared.
Use the map when it helps
If the right next surface is already obvious, go there directly. The map matters when someone needs orientation, not when they already know the kind of signal they need.
When someone is meeting Walter or the network for the first time, wa.lter.it should still do the introductory work.
Technical truth belongs on wa.lter.dev, slower arguments on wa.lter.ink, and lighter present-tense signals on wa.lter.today.
This page is useful when the network starts feeling decorative, duplicated, or harder to explain than the work itself.
Launch order
The network grows in waves. Each wave must be maintainable, indexable and understandable.
The public hub and public lab need to become credible before other properties go live.
They activate once the legacy corpus is migrated and the publishing rhythm is credible.
The utility layer and the public bookmark downstream matter only when they solve a concrete problem.
Reserved inventory
Buying a domain is not the same as giving it a product. Discipline here avoids fragmentation and useless maintenance.
Domains that could become small tools, redirects, collections or secondary public layers.
Domains to evaluate only if a precise format appears that does not fit the hub or the lab.
They stay parked until there is a strong reason to activate and maintain them over time.
Operating rules
If a choice damages clarity, accessibility or maintainability, it has to be reconsidered.
The network can grow only if it stays readable, accessible and governable. When a choice adds noise or ambiguity, it should be discarded.
WCAG 2.2 AA as the minimum baseline, with explicit attention to cognitive load and neurodivergence.
Italian and English inside the same editorial system, with coherent routing and metadata.
No duplicated content across TLDs and no sitewide backlink blocks.
Every domain must be explainable in one sentence before it goes live.
Canonical sources stay few and strong; digests, short notes and updates always point back to them.
Pages must be easy to read, extract and cite: human clarity before any SEO or GEO hack.