ShoddyHub lane • philosophy, scope, and policy

Right to Repair

Right to Repair is the philosophy, scope, and policy lane inside ShoddyHub. This page explains what the site means by repair access, what is real today, and what still needs careful validation.

The goal is practical owner visibility and better repair usability, not broad claims. Hardware holds the technical plan, Hardware Demo shows the interactive preview, and this page keeps the repair stance clear.

View Current Scope Open ShoddyHub Hardware Architecture

One-person independent effort Atlas-family focus Verified behavior first Safety-gated development

Where this page fits

This lane describes the repair-access posture and scope. It intentionally leaves technical architecture to Hardware and interactive preview behavior to Hardware Demo.

ShoddyHub

Umbrella hardware/product lane for product direction, validation posture, and companion app routing.

Open ShoddyHub

Hardware

Architecture and hardware plan for host platforms, interface tiers, write-path safety gates, and bench validation.

Open Hardware

Hardware Demo

Interactive/static demo showing telemetry context, table operations, and simulated feed behavior without live write paths.

Open Demo

Right to Repair

Philosophy, scope, and policy lane for owner visibility, diagnostics access, and cautious Atlas-family boundaries.

Open Right to Repair

What Right to Repair means here

In plain terms, owners should be able to understand, diagnose, maintain, and repair what they own using usable data and tools.

Practical definition

Access to diagnostic data that is readable and actionable.
Access to repair information and procedures that are usable in real service situations.
Access to tools and parts without unnecessary lockout barriers.
Software interfaces that help users understand system behavior instead of hiding it.

Why this page exists

This is not legal advice or a formal policy brief. It is a transparent build lane for how ShoddyTechGarage approaches repair accessibility in software and diagnostics tooling.

The emphasis is honest scope, verified behavior, and responsible progression, not claiming support across every platform.

Why it matters

Modern systems can make routine repair harder than it should be. That affects DIY owners, independent shops, and anyone trying to keep older platforms running well.

Important diagnostic signals can be limited, hidden, or difficult to interpret.
Proprietary tooling and paid access walls can make basic troubleshooting expensive.
Dealer dependence can become the default even for issues that should be owner-visible.
Independent shops and home builders often lose time on access barriers instead of real repair work.

Where ShoddyTechGarage fits

This lane is part of a small independent ecosystem built one step at a time. Each module has a practical role.

ShoddyDrive

Makes real-time vehicle data more usable in daily driving contexts so owners can see what the vehicle is doing without digging through opaque menus.

ShoddyScan and ShoddyTune

ShoddyScan expands diagnostics visibility and controller-aware analysis. ShoddyTune is now the alpha Android companion surface for ShoddyHubHardware, with conservative boundaries, API/sample-data ingest, and no flash/write tooling in the first alpha.

Atlas Bot

Provides structured, reference-oriented help so users can move from raw codes or symptoms toward clearer interpretation and next-step investigation.

Independent build model

ShoddyTechGarage is a one-person effort. That means progress is deliberate and practical, with scope control prioritized over overpromising.

Current scope

The active Right to Repair development scope is centered on the GM Atlas family with clear priority ordering. LL8 is the baseline platform for live validation.

Primary

LL8

Primary development and real-world validation platform.

Baseline for diagnostics behavior modeling.
Reference platform for visibility and interpretation tooling.
Primary source of verified lane behavior before expansion.

Secondary

L52

Secondary compatibility and cross-Atlas validation target.

Evaluated from LL8-validated foundations.
Used to test what carries over and what does not.
Expansion only where behavior is confirmed.

Limited

LK5

Limited-scope, early-stage mapping and review lane.

Not yet fully validated.
Treated as exploratory, not broad support.
Included for careful staged review only.

Expansion is intentional, not assumed. Features are added only after verified behavior, stability checks, and practical safety review.

Why start with these engines

Starting inside the Atlas family allows controlled growth with shared architecture, easier comparison, and more credible validation between related platforms.

Shared platform traits make cross-checking behavior more reliable.
Validation quality is stronger when expansion is staged from a proven baseline.
A controlled start reduces false compatibility assumptions and unsafe shortcuts.
It is a safer development path than pretending every platform works the same way.

What is being explored

OBD2 and enhanced diagnostics access where supported.
Safer interpretation of real vehicle data for practical decision-making.
ECU behavior and controller support mapping where applicable.
Responsible read and write boundaries with explicit safety posture.
User-facing tools that make diagnostics understandable instead of opaque.
Platform-specific validation over generic cross-platform guesses.

What is coming next

Documentation and education

More practical explainers for common repair and diagnostics barriers.
Real-world diagnostic case examples as validation coverage expands.
Clearer platform notes on what is validated, partial, or out of scope.

Validation roadmap

Continued Atlas-family depth before any broad expansion claims.
Incremental stability and safety checks tied to real sessions.
Future support only after proven accuracy, stability, and safety.

Share your repair barriers and use cases

If you are dealing with blocked diagnostics, limited data access, or confusing repair workflows, your real-world examples help shape this lane. Feedback from independent shop and DIY use is especially useful.

Join Testing Open Dev Hub Open Atlas Bot Back to Projects

Quick routes

New here? Start with Projects. Testing? Go to How to Join. Technical? Open Dev Hub. Hardware? Open Hardware Demo.