Repair Commons: Difference between revisions
Create repair index and safety boundaries |
Add Magnuson–Moss warranty context and limits |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''Repair Commons''' collects repair methods and observations in a form that another person can inspect. A repair record is useful when it names the device and revision, symptom, diagnostic path, parts, conditions, result, failures, and limits. It should distinguish a personal field observation from an independent test or certified fix. | '''Repair Commons''' collects repair methods and observations in a form that another person can inspect. A repair record is useful when it names the device and revision, symptom, diagnostic path, parts, conditions, result, failures, and limits. It should distinguish a personal field observation from an independent test or certified fix. | ||
== Start with an assessment == | |||
* [[What makes a device repairable?]] — access, diagnostics, parts, software pairing, verification, safety, and support, with a counterargument for controlled service. | |||
== What belongs here == | == What belongs here == | ||
| Line 8: | Line 11: | ||
Use [[Documenting a repair]] as a submission guide. Check [[Aletheia:Article standards]] before presenting a repair as verified. | Use [[Documenting a repair]] as a submission guide. Check [[Aletheia:Article standards]] before presenting a repair as verified. | ||
== Warranty and access == | |||
The U.S. [https://uscode.house.gov/view.xhtml?req=%28title%3A15+section%3A2302+edition%3Aprelim%29 Magnuson–Moss Warranty Act's tie-in provision] generally prevents a consumer-product warrantor from requiring a named brand or service as a condition of warranty coverage, subject to the statutory free-service and FTC-waiver exceptions. A repair-caused defect can still be excluded; the Act does not automatically grant access to parts, tools, or firmware. [[Does independent repair void a warranty?]] reviews the precise claim and FTC guidance. Record the actual warranty terms and causal evidence for a particular dispute, without treating this as a blanket repair license. | |||
== Safety and disclosure == | == Safety and disclosure == | ||
Latest revision as of 18:58, 31 October 2026
Repair Commons collects repair methods and observations in a form that another person can inspect. A repair record is useful when it names the device and revision, symptom, diagnostic path, parts, conditions, result, failures, and limits. It should distinguish a personal field observation from an independent test or certified fix.
Start with an assessment
[edit]- What makes a device repairable? — access, diagnostics, parts, software pairing, verification, safety, and support, with a counterargument for controlled service.
What belongs here
[edit]- Device and component maps that can be shared lawfully, with revision and provenance.
- Reproducible diagnostics, maintenance and replacement procedures, and parts cross-references.
- Before-and-after measurements, including failed attempts and unintended effects.
- Right-to-repair source material and specific claims for review at Claims Under Examination.
Use Documenting a repair as a submission guide. Check Aletheia:Article standards before presenting a repair as verified.
Warranty and access
[edit]The U.S. Magnuson–Moss Warranty Act's tie-in provision generally prevents a consumer-product warrantor from requiring a named brand or service as a condition of warranty coverage, subject to the statutory free-service and FTC-waiver exceptions. A repair-caused defect can still be excluded; the Act does not automatically grant access to parts, tools, or firmware. Does independent repair void a warranty? reviews the precise claim and FTC guidance. Record the actual warranty terms and causal evidence for a particular dispute, without treating this as a blanket repair license.
Safety and disclosure
[edit]Some equipment controls building access, health, or other life-safety functions. In these cases, publish a bounded problem statement and evidence status first. Withhold bypass instructions, sensitive facility details, and unreviewed installation advice while the relevant disclosure and safety review is underway. Do not represent a proposed mitigation as a certified product. Follow local codes, manufacturer requirements, and a qualified professional where needed.
Current record
[edit]Aletheia has a founder-reported exit-device safety observation and proposed mitigation. Its public technical write-up is deferred pending disclosure and safety review; independent certification has not been established here. This index does not provide an operational procedure.
Kinetic Torch is a separate open-source mobile-interface project whose present public repository is documentation only; its implementation and verified release remain pending.
Contribute
[edit]A repair account is strongest when it includes a repeatable test and a second person's reproduction. Submit a concise proposal through Aletheia:Suggest a claim or correction. Record a correction at Aletheia:Corrections log when a published method fails under stated conditions.