Building in public
What we have built.
A dated record of implementation and method changes. A development entry does not confirm public availability; the status page explains release readiness.
Editorial review
The methodology changelog (versioned numeric-method changes) lives inside/methodology.
Earlier entries document historical development and the private preview. They are not current availability or validation claims. Entries before July 2026 use the previous name and positioning.
October 2026
Reviewed reference pages and restored complete navigation
Restored existing reference and community pages to the footer. Aligned FAQ, glossary, provider, security and Passport wording with the current preparation stage. Added consistent cross-links and document styling; separated historical Journal visuals from current notes. This records local website work, not a production deployment.
Website launch preparation and reliable form storage
Refined the enterprise journey, added sample reference-case reports and aligned privacy, Passport and product-stage explanations. Requests and encrypted email jobs now commit together, with retry protection and private delivery status. This records local implementation; VPS deployment and provider acceptance remain separate.
July 2026 · Development archive
Farleda: new name, new positioning
Trippin is now Farleda. New brand system (Channel Cut), repositioned website — Free + Pro pricing, paid partner pilots, public verification front and center.
April 2026 · Development archive
Public Open Data API + /trust + /science whitepaper
Added API endpoints and review pages to the private-preview code. Current availability is shown on /status. Licences depend on the individual source. The science page is a methods note and evaluation plan; independent validation and frozen source snapshots remain separate work.
Health probe endpoint
Historical dependency-diagnostics endpoint. The current deployment checks such operational details internally; they are not a public availability guarantee.
/for-partners landing + printable pilot proposal
Early partner journey with a pilot process and illustrative dashboard. Named organisations were examples of possible contacts, not confirmed customers. The current offer focuses on railway and infrastructure companies and is described on the partner page.
Aggregate platform telemetry + live impact ticker
Historical preview implementation of event counters and an impact ticker. Event metadata needs its own privacy assessment; a missing user-ID field does not establish anonymity. The current information website does not present these counters as proven environmental impact.
Grid-aware intensity for electric rail
Introduced optional electricityMaps recent-history profiles and an annual country snapshot for electric rail. Without provider data, hourly values are explicitly modelled around the snapshot. Cross-border legs average endpoint countries; kilometre-weighting is not yet implemented.
Real activities in day plans
Day-by-day view replaced paragraph-style morning/afternoon/evening with activity cards. Activities are grounded in real POIs from Overpass (OSM) + Wikivoyage. Walk-minutes between consecutive activities, opening-hour warnings (closed Mondays et al.), colour-coded kind icons.
Austria Klimaticket awareness
New toggle in Settings: 'I have a Klimaticket Österreich'. Austrian public-transit legs with both endpoints in AT show a 'Klimaticket' chip and are treated as zero marginal cost; the planner actively prefers them.
Real departure times per leg + alternatives
Transit-class legs now surface their scheduled departure → arrival times, transfer count, and journey duration. A picker cycles through up to two alternative departures from the same query. Users can plan around ICE 1006 at 08:42 vs. RJ 161 at 10:12 — not a vague 'morning'.
Hard CO₂ budget + 'regenerate without flights'
When a trip exceeds the user's per-person CO₂ budget, we surface an amber warning card pointing at the biggest contributor and offer a one-click regenerate that adds a hard no-flight constraint to the LLM prompt.
.ics calendar export + print-ready PDF
Every saved trip can be exported as an RFC 5545 .ics calendar file (real departure times when scheduled, all-day blocks otherwise) or opened in a /app/t/<id>/print A4-printable view that saves to PDF via the browser.
User preferences + smart defaults
New user_preferences table: no-fly, default style, default budget, default CO₂ budget, home country, accessibility tags, Klimaticket, annual carbon budget. Every new trip starts with these as defaults; AI prompt honours them.
Annual carbon ledger per user
Historical preview feature comparing planned journeys with a personal annual budget. The former two-tonne comparison is not an EU legal allowance or a specifically allocated travel budget.
Rate limiting + error boundaries + security headers
Token-bucket rate limiter on AI endpoints (20/hour, 5/minute burst). App-level and root error boundaries. Security headers middleware: strict CSP, X-Frame-Options: DENY, Referrer-Policy, Permissions-Policy (with interest-cohort=() FLoC opt-out), HSTS 2-year preload.
Transitous cache + CoordMap country awareness
planTransit results cached in-process 6h keyed on (coords, hour-bucket, preference). Negative results cached too so known-dead routes don't hammer the upstream. CoordMap now carries country codes so enrichment can resolve grid jurisdictions without re-geocoding.
Dedicated /methodology page
Published the first methodology page with factor ranges, grid-model explanation, routing, geocoding, weather and telemetry sources. Later v1.1 review removed unsupported conformity and Taxonomy claims and clarified accounting limits.
Methodology v1.0
Historical initial methodology. Superseded by v1.1 on 2026-08-11, which uses revised UK DESNZ 2026 factors and separates annual, current, recent-history and modelled grid values.
