ShowerThoughts Presentation edition 0.1 Give a promising idea room to become real. An idea may matter before it is easy to build, and a useful business may answer a different question. Explore how ShowerThoughts holds those judgments apart—and where they remain uncertain. Editorial reading of the social purpose Editorial synthesis: Make more possible futures discussable by welcoming ideas without requiring a public persona, considering possible social benefit before ease of execution, and leaving room for disagreement. Keep commercial promise legible on its own terms, then let future evidence challenge present judgment. This is a product-purpose reading of the available design, not a formal long-term mission statement. Start with the idea [implemented] ShowerThoughts invites people to put forward ideas without making a public biography the price of taking part. The Good ideas track asks who could benefit, how deeply, and who might be left out. Anonymous contribution can widen the conversation, but it cannot make a claim true or an idea original by itself. How: A public submission enters the Good ideas track by default and receives explicit assessor judgments under a social-benefit rubric. Possibility: A quiet proposal with little institutional backing can still be considered for what it might make possible. Tension: Words can describe a future benefit; they cannot show who can reach it, who carries its costs, or what happens when the idea meets daily life. Sources: project-brief, good-idea-rubric Credit without a public profile [implemented] Credit is a choice a contributor can make, not a prerequisite for submitting an idea. A private contribution key can support a later claim without requiring a public name. Contributors may also choose a durable key that connects their own submissions, so the product should explain that choice instead of promising perfect unlinkability. How: The authorship flow checks whether the claimant controls the signing credential associated with the idea before accepting a credit claim. Possibility: Someone can share an idea while keeping their public identity separate, then seek attribution if they choose. Tension: Proof of key control is narrow. It does not establish a real-world identity, originality, legal ownership, or the truth of the idea's claims. Sources: authorship-design, authorship-flow Let social benefit lead [implemented] The Good ideas rubric considers reach, depth, equity, confidence, and safety as parts of social benefit. Technical and operational viability can shape the composite without deciding the idea's whole worth. Economic potential adds only a small lift in proportion to social benefit, so commercial promise cannot rescue a proposal with little social value. How: The canonical Good ideas composite applies a soft, time-varying viability modifier and a small social-value-linked economic bonus. The Robust impact lens uses a separate set of stated assumptions about how feasibility may change over time. Possibility: An ambitious idea can remain worth considering even if today's tools or institutions cannot yet deliver it. Tension: Keeping possibility alive depends on assumptions about future feasibility. Those assumptions can be made visible and debated, but a formula cannot settle them. Sources: project-brief, good-idea-rubric, robust-method Keep two questions apart [implemented] The Good ideas track asks about possible social benefit. Strong business asks whether a product or business could be built and plausibly earn revenue, considering a named buyer, willingness to pay, distribution, and other commercial factors. An idea may appear in both tracks, but a business score does not feed the Good ideas composite and does not forecast profit. How: Each track has its own versioned rubric, assessment history, and current ranking. The business rubric is an explicit comparison of assessor judgments, not market validation. Possibility: An idea could be socially compelling without a clear business case, or commercially promising while offering limited public benefit. Tension: Combining both questions into one ranking could hide whose interests the score rewards and what kind of value it describes. Sources: project-brief, business-track Make disagreement visible [implemented] The same rubric can produce different judgments across assessors. ShowerThoughts can compare assessors on ideas they have both reviewed, and its Robust lenses account for reliability and disagreement when presenting a conservative view. These are ways to inspect judgments, not ways to discover an unquestionable true score. How: Paired assessor comparisons report differences on shared ideas. Read-only Robust engines shrink uncertain scores and widen their bounds when assessors disagree; they do not change canonical rankings. Possibility: Disagreement can point to the assumptions, affected groups, or evidence that deserve another look. Tension: A model's confidence is not lived evidence. Repeatability, assessor coverage, and authorship effects can all limit what a comparison means. Sources: assessor-comparison, robust-method, good-idea-rubric Let experience challenge the judgment [proposed] Today's scoring records assessor judgments, not whether an idea improved people's lives. A next step could bring back evidence from a bounded, voluntary pilot: what was delivered, who could use it, who was excluded, and which assumptions failed. That feedback loop would need consent, privacy protections, and a way to correct the record; it is a proposal for future work, not a feature established by the reviewed implementation. How: The current rubrics preserve factors and rationales but explicitly distinguish assessments from measured outcomes. A pilot-to-assessment learning process is proposed here. Possibility: Evidence from use could reveal benefits and burdens that a written proposal or model assessment missed. Tension: Outcomes rarely have one cause, and a small pilot cannot speak for every setting. Learning from use still requires careful comparison and humility. Sources: good-idea-rubric, business-track, learning-boundary PRINCIPLES Judge proposals, not people An idea score says nothing about an author's human worth, sincerity, credentials, or right to participate. Keep reasons close to judgments Explicit factors, rationale, assessor identity, and version history make a score easier to question and revise. Protect more than one kind of value Possible public benefit and commercial viability can both matter while remaining distinct and visible on their own terms. Treat uncertainty as part of the answer A low confidence judgment, a disagreement, or a missing outcome is information to preserve, not a gap to fill with certainty. ILLUSTRATIVE SCENARIO: A neighborhood repair library Fictional idea: a neighborhood group lends common tools and hosts low-risk repair sessions. The question is which first test could reveal its value without hiding who gets access, does the work, or carries the risk. The branches are questions, not scores or predictions. Start: first-offer first-offer: Choose a first offer The idea group has enough volunteer time to begin with one clear promise. Lending and hands-on repair could help different people, and each raises different responsibilities. What should the group offer first? Choice: Begin with a borrowing shelf Tool lending is the first offer; guided repair remains a later possibility. Possible next: A simple service may make shared tools easier to discover and use. Still unresolved: Opening hours, deposits, transport, tool condition, and maintenance may still make access unequal. Continue at: borrower-rules Choice: Begin with repair sessions The first offer is a place to learn or receive help with simple repairs. Possible next: People who lack tools or confidence may find practical support close by. Still unresolved: Repair work brings questions about safety, skill, responsibility, and who can participate. Continue at: repair-roles borrower-rules: Set borrowing rules The group needs a fair way to handle scarce tools, busy times, and different levels of need before the first item is lent. How should it learn which borrowing rules are workable? Choice: Ask residents about access barriers The group invites residents to describe what would make borrowing possible or difficult. Possible next: Barriers such as opening hours or transport may become visible before they become routine exclusions. Still unresolved: Asking for personal reasons can pressure people to disclose more than the group needs. Continue at: access-check Choice: Open the shelf to everyone under the same rule The initial rule is simple and applies to every borrower. Possible next: A clear rule is easier to understand and challenge. Still unresolved: Equal wording does not guarantee equal access when people have different time, mobility, or resources. Continue at: steward-check repair-roles: Set the repair boundary The group wants repair sessions to be useful while keeping risk and responsibility understandable to participants. How should it decide who can guide or perform repairs? Choice: Start with low-risk tasks The first sessions have a narrow scope and a clear route for tasks they cannot handle. Possible next: A small offer can generate specific questions about demand and accessibility. Still unresolved: The tasks easiest to support may not match the most urgent needs. Continue at: skills-check Choice: Invite neighbors to share repair knowledge Participants may teach one another, with roles negotiated as the group learns. Possible next: More people may be able to contribute skills and experience. Still unresolved: Informal roles can blur responsibility when a repair goes wrong. Continue at: shared-tools access-check: Choose what to learn The group can learn about unmet need without making people justify their circumstances to borrow a tool. What evidence is proportionate for a small voluntary pilot? Choice: Record unmet request types without names The group keeps a limited, non-identifying record of requests it could not meet. Possible next: Patterns may reveal gaps in tools, hours, or location. Still unresolved: A small or unusual need can still be recognizable, and the record may miss people who never ask. Continue at: pilot-learning Choice: Collect no information about personal need yet The group delays needs tracking until participants agree on safeguards and purpose. Possible next: People can try the service without explaining private circumstances. Still unresolved: Without some feedback, the group may not see who could not use the offer. Continue at: privacy-redesign steward-check: Make the open shelf workable A rule open to everyone still needs people to maintain tools, manage returns, and explain what happens when equipment is damaged. What should the group settle before it grows the shelf? Choice: Publish care and maintenance roles The group names who checks tools, handles repairs, and decides when something is unsafe. Possible next: Shared responsibility can become visible and contestable. Still unresolved: A small volunteer group may struggle to sustain duties that look simple on paper. Continue at: shared-stewardship Choice: Keep the shelf small and learn from use The group limits its offer while noting requests, returns, and maintenance needs. Possible next: Actual use may clarify which responsibilities need owners. Still unresolved: A small trial may reflect the volunteers who are easiest to reach, not the wider neighborhood. Continue at: pilot-learning skills-check: Make skill and safety visible Even low-risk sessions need a way to explain what is in scope and where participants should seek qualified help. What should happen when a task exceeds the group's competence? Choice: Stay in scope and record where help was missing The group offers only the tasks it can support and notes unmet requests without implying success. Possible next: The team can learn whether the narrow offer meets any useful need. Still unresolved: A pilot could show unmet demand without identifying a safe or affordable way to meet it. Continue at: pilot-learning Choice: Bring qualified repair partners in first The group waits to offer sessions until it has responsible partners for the intended work. Possible next: Clear roles may support safer and more dependable help. Still unresolved: Finding partners can delay a small experiment and may narrow who can participate. Continue at: shared-stewardship shared-tools: Agree on shared responsibility Neighbor-led repair depends on more than access to tools; participants need to know who is responsible for each part of the work. What should the group do before inviting more people? Choice: Agree on handoff, repair, and replacement duties The group sets public responsibilities for shared equipment and repair sessions. Possible next: Clear commitments may make participation more trustworthy. Still unresolved: Formal roles can concentrate control or burden the people who already volunteer. Continue at: shared-stewardship Choice: Pause until a responsible steward is clear The group delays expansion while it works out who can safely oversee the shared offer. Possible next: A pause can prevent the appearance of a service the group cannot sustain. Still unresolved: People who need help now may continue to lack an accessible option. Continue at: pause-before-scale pilot-learning: Ending: learn from a bounded pilot The group tests a limited, voluntary offer and records requests, handoffs, inaccessible times, and maintenance needs. These observations describe this small pilot; they do not prove impact at scale. Possible ending: A small test creates questions the group can answer with participants before deciding whether to continue. Still unresolved: Who still could not use the service, and would the same offer work in another neighborhood? privacy-redesign: Ending: redesign evidence gathering The group pauses needs tracking and asks participants what information, if any, would be safe and useful to collect. Possible ending: The service can remain open to reconsideration while its evidence practices are redesigned. Still unresolved: Can the group learn who is missing without asking people to expose private circumstances? shared-stewardship: Ending: build stewardship first The group names repair, maintenance, safety, and access responsibilities before widening the offer. Possible ending: The idea advances through shared rules and accountable roles rather than enthusiasm alone. Still unresolved: Who will carry these duties over time, and how can users challenge the rules? pause-before-scale: Ending: pause before scaling The group does not expand while responsibility remains unclear. It can revisit the idea when people and capacity are available to support it. Possible ending: A pause preserves the option to try later without presenting an unsupported service as ready. Still unresolved: What minimum safeguards and real capacity would justify restarting? ILLUSTRATIVE SCENARIO: A tool for small repair shops Fictional idea: a lightweight tool helps independent repair shops track quotes and job status, with an option to share spare-part availability with nearby shops. It might ease access to repairs and save shops time; neither benefit nor willingness to pay is established. The Good ideas and Strong business lenses ask different questions. Start: first-promise first-promise: Choose the first promise The team can start with a private tool for one shop or try to coordinate several shops. The second route may be more useful if cooperation works, but it asks people to share information and trust a new process. Which uncertainty should the first test address? Choice: Make one shop's repair workflow easier The first version focuses on quotes and job status inside one shop. Possible next: A narrow tool could reveal whether one recurring task causes enough friction to matter. Still unresolved: A single shop may not represent other businesses or people seeking affordable repairs. Continue at: shop-evidence Choice: Help nearby shops share capacity or parts The idea begins as a small network for opt-in availability or referrals. Possible next: Coordination might help shops handle jobs or parts they cannot manage alone. Still unresolved: A network needs shared rules, enough willing participants, and careful limits on customer information. Continue at: network-agreement shop-evidence: Find the shop's real problem The team should understand the work before assuming that software is the answer or that a shop will pay for it. What would make the first problem statement more credible? Choice: Follow one repair from quote to handoff The team observes where a repair job is delayed, repeated, or difficult to explain. Possible next: A specific workflow may show a useful first product boundary. Still unresolved: One observed case cannot establish that the problem is common or worth paying to solve. Continue at: payer-test Choice: Ask about administrative work without pitching software The team learns how shop owners currently handle job updates, quotes, and parts. Possible next: Listening first can surface workarounds and problems the team did not expect. Still unresolved: Reported frustration alone does not show budget, adoption, or willingness to change. Continue at: scope-test network-agreement: Set a sharing boundary Sharing can range from a simple signal that a part is available to referrals involving a customer's repair. Those choices create different privacy and accountability questions. What should participating shops be asked to share first? Choice: Share only opt-in part availability The network excludes customer records and begins with a limited availability signal. Possible next: A narrow exchange may test whether shops have a reason to coordinate. Still unresolved: Inventory accuracy, compatibility, and the work of keeping information current remain open. Continue at: data-boundary Choice: Try referrals for jobs a shop cannot take The network explores introductions between shops for overflow work. Possible next: A referral could connect a customer with a shop that has relevant capacity. Still unresolved: Consent, responsibility for the handoff, and the quality of the next service need clear rules. Continue at: network-trust payer-test: Test the buyer question A commercial case depends on more than a painful task; the proposed buyer must see enough value to make a real commitment. What evidence should the team seek before describing a business case as stronger? Choice: Invite a shop to a clearly scoped paid trial The team tests whether a named shop will commit real money to a limited offer. Possible next: A paid commitment can provide evidence about a buyer and a specific use case. Still unresolved: One buyer does not establish a reachable market, sustainable economics, or a social benefit. Continue at: paid-pilot Choice: Observe the workflow before discussing price The team first documents what the current process actually involves. Possible next: A clearer workflow may prevent building a solution to the wrong problem. Still unresolved: Observation alone leaves willingness to pay unresolved. Continue at: workflow-only scope-test: Choose what to narrow The project can investigate a single recurring task or postpone product work until it knows who owns the problem and budget. What should the team do with a broad but unverified complaint? Choice: Measure one time-consuming task The team narrows the idea to a task that can be observed in a shop's daily work. Possible next: A small scope makes later usefulness easier to inspect. Still unresolved: A task that takes time may still be too minor to justify a product or subscription. Continue at: workflow-only Choice: Find out who owns the budget and decision The team names the likely buyer and learns how a purchase would be approved. Possible next: A real buyer path can strengthen or challenge the business hypothesis. Still unresolved: The person who pays may not be the person who uses the tool or benefits from repairs. Continue at: paid-pilot data-boundary: Keep the network accountable Even a limited availability signal needs a shared meaning, an update practice, and an agreed way to correct mistakes. What should participating shops do before relying on shared availability? Choice: Try an opt-in signal with simple correction rules Shops test a narrow, reversible availability exchange and agree how to correct it. Possible next: The group may learn whether limited coordination is useful without sharing customer details. Still unresolved: A stale signal can still waste time or create expectations that a shop cannot meet. Continue at: limited-network Choice: Agree on responsibilities before sharing The team delays the network while shops define consent, accuracy, and correction rules. Possible next: Participants can decide what the exchange means before they depend on it. Still unresolved: Coordination may remain too costly or difficult to sustain. Continue at: pause-and-define network-trust: Build trust into referrals An introduction can help only if participating shops and customers understand the handoff and can decline it. How could a small network test referrals responsibly? Choice: Make referrals opt-in, transparent, and reversible Shops and customers can see and accept a specific introduction before information is shared. Possible next: A small test may reveal whether a referral helps complete a repair. Still unresolved: Consent and careful handoffs add work, and there may be too few suitable partners. Continue at: limited-network Choice: Return to a one-shop tool until terms are clear The team defers referrals and tests a private workflow within one business. Possible next: A narrower product may be easier to understand and govern. Still unresolved: The network's possible benefit remains untested. Continue at: workflow-only paid-pilot: Ending: test a buyer commitment A consenting shop tries one scoped service and decides whether to pay. The Strong business track can consider what that commitment shows; the Good ideas track separately asks whether the service changes access to repair. Neither judgment substitutes for the other. Possible ending: A real commitment could sharpen the business case while leaving social benefit as a separate question. Still unresolved: Will another buyer make the same choice, and who benefits or loses from the service? workflow-only: Ending: keep the product narrow The team focuses on one shop's observable workflow and learns what a useful tool would need to do before adding a network. Possible ending: The product idea becomes more specific without claiming that shops will pay or that repairs become more accessible. Still unresolved: Is the friction important enough to justify adoption, maintenance, and a sustainable price? limited-network: Ending: try a limited network A small group of willing shops tries an opt-in, reversible exchange. It records what the agreement allowed and where coordination failed, without claiming general market demand. Possible ending: The pilot can test whether participating shops find a bounded exchange useful. Still unresolved: Can the arrangement include enough shops to be useful while keeping consent, accuracy, and responsibility clear? pause-and-define: Ending: define terms before sharing The team pauses the network while shops decide what information may be shared and who corrects an error or handles a failed handoff. Possible ending: A pause protects participants from depending on rules that have not been agreed. Still unresolved: Can the network deliver enough value to justify the effort and accountability it requires? BOUNDARIES A score is a judgment Assessments express structured opinions about an idea. They are not measured social outcomes, market validation, public consent, or proof that a proposal will work. Authorship proof has a narrow reach A contributor can prove control of the credential attached to a credit claim. That does not prove real-world identity, originality, legal ownership, or the truth of an idea. Reusing a durable credential can connect that contributor's submissions. The two tracks do not merge Good ideas and Strong business keep separate questions, rubrics, histories, and rankings. Neither score guarantees social benefit, a buyer, or profit. A ranking cannot decide for a community Assessors do not provide consent on behalf of people affected by an idea. Real use, exclusion, burdens, and disagreements need attention beyond a ranking; a pilot-feedback loop is proposed here, not established as a current feature. SOURCE NOTES project-brief: Project brief [Project specification] Defines ShowerThoughts as an isolated social-ideas application, with anonymous submissions, provable authorship, separate Good ideas and Strong business tracks, and social benefit leading the Good ideas ranking. good-idea-rubric: Good ideas assessment [Project specification] Describes explicit assessor judgments about reach, depth, equity, confidence, safety, viability, and economic potential. The project distinguishes these judgments from measured outcomes. business-track: Strong business assessment [Project specification] Defines a separate commercial track based on a named buyer, customer pain, willingness to pay, reachable market, feasibility, distribution, unit economics, differentiation, and evidence confidence. It is not a profit forecast. robust-method: Robust scoring method [Enhancement assessment] Describes read-only views that account for assessor reliability and disagreement. The Good ideas view also uses explicit, tunable assumptions about future feasibility; those assumptions are not observations about what will happen. assessor-comparison: Assessor comparison notes [Enhancement assessment] Describes paired comparison of assessors and records limits in the current evidence, including authorship confounding, uneven coverage, and unmeasured repeatability. authorship-design: Identity and authorship design [Project specification] Uses contributor-controlled keys to support idea-level credit, with ephemeral submission keys by default and an opt-in durable key. Key control is not the same as real-world identity or legal ownership. authorship-flow: Authorship claim flow [Source code] Checks a signed, time-limited claim against the credential stored with an idea before allowing an authorship claim. learning-boundary: From assessment to outcomes [Enhancement assessment] Current scoring material treats ratings as assessor judgments rather than evidence of impact. Connecting carefully gathered pilot outcomes back to ideas is presented here as a future proposal. Leave the score open to question A ranked idea is not a mandate. ShowerThoughts is most useful when it keeps possible benefit in view, gives judgments reasons, and leaves contributors and communities room to disagree about what should happen next. Which possibility deserves a careful, shared test while the answer is still unknown?