wa.lter.today
Start from what is current
Open wa.lter.today if you want the quickest sense of what Walter is actually focused on right now.
Language
wa.lter.it
Walter Franchetti
Personal front door for current work, durable projects, and the clearest way into Walter's public internet.
Walter Franchetti works across systems, product, design, and communication; the network exists to make that mix readable without flattening it into a generic portfolio.
Romesystemsproductpublic internet
Walter Franchetti's personal internet, organized by domains instead of noise.
wa.lter.it is the central house of the network. It explains who I am, what I am building and how projects, writing, experiments and updates are distributed across the `lter.*` properties.
Walter Franchetti works across backend development, product systems, interaction design, and technical strategy. He is most at home where technical truth, product posture, and delivery quality need to be held together without turning the work into process theater.
Who
Builder, backend developer, and systems-oriented product thinker.
Now
Walter works best where architecture, runtime behavior, and delivery quality need to stay coherent over time.
Why this exists
The network is meant to expose notes, essays, experiments, and operating decisions, not just biography and credentials.
Core surfaces
The first properties have clear, complementary roles.
The system starts with a few strong surfaces. Every domain should make orientation easier, not add noise.
main hub
wa.lter.it
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
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
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
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.
Entry paths
Three simple ways to enter the system.
The homepage should reduce cognitive work. Instead of showing everything, it offers a few readable paths.
wa.lter.dev
Go to the lab for method and technical truth
Open wa.lter.dev when you want the builder side: experiments, notes, process, and operating detail.
wa.lter.ink
Go slower for durable writing
Open wa.lter.ink when you want arguments, frameworks, and longer reflections rather than updates or logs.
wa.lter.it / contact
Open a direct line
Use contact when there is a concrete collaboration, product fit, or conversation worth carrying with context intact.
Operator split
The hub should explain the network, not absorb the operator load.
wa.lter.it is the calm front door. It should route people toward the right public climate, while Studio stays separate for queues, readiness, and authenticated next moves.
studio
separate control planeOpen Studio when the next step becomes operational.
Use the operator surface for queue ownership, review posture, and internal follow-through instead of turning the public hub into a soft admin layer.
wa.lter.dev
Keep public method in the lab.
Notes, experiments, changelog, and technical trace should stay on the lab when implementation detail is part of the value.
wa.lter.ink
Keep durable arguments in writing.
When the work wants a slower claim, a framework, or a reusable essay, move to the writing surface instead.
wa.lter.today
Keep the present readable downstream.
Shorter signals and current focus belong on the updates surface when the network only needs a lighter pulse.
Proof of work
The hub should prove how Walter builds before it explains the whole system.
Start from the few cases that show how product shape, systems thinking, and public structure actually come together.
personal platform2026 - present
LTER Network
A multi-surface personal internet that gives Walter a calmer public system than a single portfolio or a noisy social profile could provide.
It shows how Walter approaches systems when product shape, implementation, and editorial posture all need to stay aligned.
It belongs on wa.lter.it because it is the clearest public artifact of Walter's current way of building: personal, systematic, and intentionally multi-surface.
internal publishing system2026 - present
Memory And Editorial System
A working chain from bookmarks and memory capture to editorial candidates, built to keep public publishing connected to real inputs instead of vague content planning.
It demonstrates a recurring strength in Walter's work: turning fuzzy ongoing inputs into a system that is operational, inspectable, and easier to use over time.
It belongs on wa.lter.it because it proves the public publishing system is backed by real operator logic, not just presentation copy.
Guardrails
The network must stay readable for people before systems.
SEO, GEO and design matter, but they cannot compromise accessibility, coherence or trust.
Accessibility as baseline
Contrast, structure, visible focus, reduced motion and managed cognitive load are not late polish.
Multilingual without confusion
Italian and English live in the same editorial system, with clear ownership and metadata.
Domains with a real job
The network grows by concepts and functions, not by multiplying copies of the same content.
Operating rules
- 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.
Next stop
If you want to see the operational side of the network, the next step is wa.lter.dev.
The hub introduces the system. The public lab shows how it is built: notes, experiments, changelog and behind-the-scenes workflows.