Language
wa.lter.it / network

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.

only if unsureclear routesshort map

Network map

One personal internet, more domains, explicit roles.

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

The surfaces with a defined trajectory are few and intentional.

First the center of the system becomes solid. Then the properties that truly deserve to exist can open.

main hub

wa.lter.it
active

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.

Focus
Positioning, network map, projects, canonical pages and clear entry points.
Audience
People who need to quickly understand who Walter is, what he is building and where to go next.

public lab

wa.lter.dev
active

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.

Focus
Experiments, technical notes, changelog, operational memory and auth-protected internal tools.
Audience
Technical collaborators, clients curious about process and people interested in the builder side.

writing surface

wa.lter.ink
active

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.

Focus
Essays, reflections, evergreen pieces and multilingual adaptations without duplication.
Audience
Readers looking for context, reasoned opinions and a broader narrative than a simple update.

updates surface

wa.lter.today
active

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.

Focus
Now page, digest entries, periodic updates and selections that always point back to the main sources.
Audience
People who want to follow the present state of the network without going deep immediately.

Five-surface atlas

The network is public in four places and operated in one.

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.

wa.lter.itpublic

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.

wa.lter.devpublic

public lab

Publish method and technical truth here.

Notes, experiments, changelog, and public process belong on the lab when implementation detail is part of the value.

wa.lter.inkpublic

writing surface

Move slower when a thought needs a durable shape.

Arguments, frameworks, and essays live here when the work can stay useful later instead of only reporting current motion.

wa.lter.todaypublic

updates surface

Keep the present brief and legible.

Short signals, current focus, and lighter downstream entries belong here when the network needs readable present tense without duplication.

studiointernal

operator surface

Operate the network without dragging the lab into backoffice work.

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

This page should clarify routes, not become another stop.

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.

Use the hub if the person is new.

When someone is meeting Walter or the network for the first time, wa.lter.it should still do the introductory work.

Skip this page if the intent is already clear.

Technical truth belongs on wa.lter.dev, slower arguments on wa.lter.ink, and lighter present-tense signals on wa.lter.today.

Come back here when the system drifts.

This page is useful when the network starts feeling decorative, duplicated, or harder to explain than the work itself.

Launch order

Activation order is part of the product.

The network grows in waves. Each wave must be maintainable, indexable and understandable.

01

Now

The public hub and public lab need to become credible before other properties go live.

wa.lter.itwa.lter.dev
02

When the corpus is ready

They activate once the legacy corpus is migrated and the publishing rhythm is credible.

wa.lter.inkwa.lter.today
03

Only if they solve a real need

The utility layer and the public bookmark downstream matter only when they solve a concrete problem.

wa.lter.clickwa.lter.surf

Reserved inventory

The rest of the domains stay still until there is a strong reason.

Buying a domain is not the same as giving it a product. Discipline here avoids fragmentation and useless maintenance.

Utility candidates

Domains that could become small tools, redirects, collections or secondary public layers.

wa.lter.clickwa.lter.surfwa.lter.helplter.site

Editorial candidates

Domains to evaluate only if a precise format appears that does not fit the hub or the lab.

lter.blogwa.lter.inkwa.lter.todaywa.lter.world

Parked inventory

They stay parked until there is a strong reason to activate and maintain them over time.

wa.lter.barwa.lter.casawa.lter.fitwa.lter.livewa.lter.lovewa.lter.rest

Operating rules

The rules matter more than the number of domains.

If a choice damages clarity, accessibility or maintainability, it has to be reconsidered.

Operating principle

The network can grow only if it stays readable, accessible and governable. When a choice adds noise or ambiguity, it should be discarded.

Accessibility and cognitive load

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.

Publishing discipline

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.

SEO and GEO without theater

Pages must be easy to read, extract and cite: human clarity before any SEO or GEO hack.


Percorsi chiave

Back to homeOpen wa.lter.devLaunch orderSystem guardrails