{
  "schemaVersion": 1,
  "categoryId": "category-003",
  "categoryName": "Portable Records, Status and Memory",
  "categoryDescription": "Forecast services that help people move only the records, earned status and memories they choose, correct errors across providers, and keep urgent access open while a transfer or dispute is finished.",
  "rankingMethod": "Each sealed candidate was scored from 1 to 5 for future distance, need scale, global breadth, marketplace clarity, delivery readiness in 2031, and bounded trust and safety. The weighted total is future distance x5, need scale x4, global breadth x3, marketplace clarity x3, delivery readiness x3, and trust and safety x2. Totals anchor the order, followed by a judgement about urgency and observable finish. SiftPass and RouteBright tied on 93; SiftPass ranks higher because it completes a person's live transfer, while RouteBright mainly tests whether that route works.",
  "top10": [
    {
      "candidateId": "category-003-candidate-04",
      "rank": 1,
      "name": "OpenWhile",
      "developerName": "Continuum Civic Labs",
      "salesPitch": "Keep care, food, shelter or income open while humans fix the record that got you blocked.",
      "storeDescription": "OpenWhile is a forecast emergency bridge for the moment a missing or mismatched record blocks something essential. It gathers the smallest useful alternative proof, sends a time-limited continuity request and tracks the named human responsible for the fix. The app does not decide whether you qualify. Its result is simpler and more important: urgent access stays open for a bounded period, or you receive a clear refusal, deadline and outside review route.",
      "whatItDoesSummary": "When an automated check rejects you, OpenWhile builds a minimum-proof emergency case, asks the real service provider to keep access open temporarily, and follows the correction until a named human accepts or refuses it.",
      "whyOnListSummary": "This ranks first because the forecast combines two 2031 pressures: essential services could depend more heavily on linked machine-readable records, while outages, displacement and institutional disruption could make those records less dependable. A reusable continuity bridge would solve a repeated, high-stakes problem with a visible finish: access continues, or an accountable human gives a reason and appeal route.",
      "why2031Not2026": "Services can make manual exceptions today, but they are usually isolated calls and forms. This becomes a distinct 2031 marketplace service only if linked automated gates are normal across several essentials and a failed source record can block more than one part of life at once.",
      "whyThisRank": "OpenWhile has the strongest mix of urgency, global relevance and a result ordinary people can recognise immediately. It does not merely export a file or explain an error; it tries to preserve care, shelter, food or income during the dispute. Its position still depends on providers accepting bounded continuity requests and keeping final authority outside the app.",
      "whyAboveNext": "It sits above SiftPass because preventing immediate loss of an essential service is more urgent than separating records for an ordinary move, even though both could become widely used.",
      "couldMoveUpIf": "It would become even more certain if essential providers adopted common temporary-access receipts and staffed correction deadlines.",
      "couldMoveDownIf": "It would fall if robust sector-specific emergency processes kept working without a shared bridge or if providers refused interoperable requests.",
      "strongestCounterCase": "Health, housing, benefits and payments may each need different safety rules, so specialist emergency teams could remain safer and more trusted than one cross-service product.",
      "scores": {
        "futureDistance": 5,
        "needScale": 5,
        "globalBreadth": 5,
        "marketplaceClarity": 5,
        "deliveryReadiness2031": 4,
        "trustAndSafety": 4,
        "total": 95
      },
      "rating": 4.8,
      "imaginedReviews": [
        {
          "reviewerAlias": "RiverBus22",
          "title": "My medicine pickup stayed open",
          "body": "The clinic could not match my moved record, but the app found a human and showed the pharmacy a temporary continuity receipt. I could see every deadline.",
          "stars": 5,
          "stance": "benefit",
          "fictionalDisclosure": true
        },
        {
          "reviewerAlias": "MinaOffline",
          "title": "The phone route was too slow",
          "body": "The written steps were clear, but my local provider took hours to answer and the app could not force them to continue the service.",
          "stars": 3,
          "stance": "critical",
          "fictionalDisclosure": true
        }
      ]
    },
    {
      "candidateId": "category-003-candidate-01",
      "rank": 2,
      "name": "SiftPass",
      "developerName": "Common Route Works",
      "salesPitch": "Share the one fact you need without handing over the rest of your life—or losing access when you say no.",
      "storeDescription": "SiftPass is a forecast switchboard for a world where work, public contribution and service records may be joined together. It shows which fact a provider wants, where that fact came from and what decision it may affect. You choose a minimum proof bundle, test whether the receiver accepts it and keep a correction receipt. If one fact is disputed, the service tries to protect unrelated income, urgent access and lawful rights while a human reviews it.",
      "whatItDoesSummary": "SiftPass separates a large status record into purpose-specific pieces, sends only the piece you approve, tests the receiving route and checks that saying no did not silently close something unrelated.",
      "whyOnListSummary": "In this forecast, records used for work, identity, contribution and public services could become easier to combine. That convenience creates a new danger: one error or refusal could spread across daily life. SiftPass belongs near the top because it turns privacy and portability into a finished service—select, send, test, correct and keep other routes open—rather than another wallet that only stores documents.",
      "why2031Not2026": "Selective sharing exists in pieces today. The 2031 leap is the joined gate: the same machine-readable status may influence several consequential routes, making continuity testing across operators a mainstream need rather than a specialist privacy feature.",
      "whyThisRank": "The concept is broad, repeatedly useful and unusually clear about completion. A person either gets the chosen proof accepted or reaches a named human review while unrelated routes stay open. It ranks below OpenWhile because many SiftPass uses are planned moves, but above a test laboratory because it directly completes a person's transaction.",
      "whyAboveNext": "SiftPass and RouteBright share a total of 93. SiftPass wins the tie because it carries out the live selective transfer for the person; RouteBright primarily measures routes and warns about failure.",
      "couldMoveUpIf": "It could take first place if cross-domain status reuse becomes common and purpose limits become enforceable across major operators.",
      "couldMoveDownIf": "It would fall if records stay separated by sector or ordinary exports reliably preserve access without an independent switchboard.",
      "strongestCounterCase": "Identity wallets, sector portability tools and public ombuds services could converge on the same functions, leaving no reason for people to install a separate switchboard.",
      "scores": {
        "futureDistance": 5,
        "needScale": 5,
        "globalBreadth": 5,
        "marketplaceClarity": 5,
        "deliveryReadiness2031": 4,
        "trustAndSafety": 3,
        "total": 93
      },
      "rating": 4.7,
      "imaginedReviews": [
        {
          "reviewerAlias": "OneFactOnly",
          "title": "It showed what they actually needed",
          "body": "I proved a training result without sharing my whole work history. The receiving test caught a missing field before I closed my old account.",
          "stars": 5,
          "stance": "benefit",
          "fictionalDisclosure": true
        },
        {
          "reviewerAlias": "NorthPierStudent",
          "title": "Too many provider labels",
          "body": "I liked the minimum sharing, but the purpose screen used terms copied from the provider. I still needed a library adviser to understand them.",
          "stars": 3,
          "stance": "critical",
          "fictionalDisclosure": true
        }
      ]
    },
    {
      "candidateId": "category-003-candidate-11",
      "rank": 3,
      "name": "RouteBright",
      "developerName": "Public Passage Studio",
      "salesPitch": "See whether a new provider really accepts people like you before you risk leaving the old one.",
      "storeDescription": "RouteBright is a forecast public-interest test lab disguised as a simple switching guide. It runs protected, end-to-end journeys through real receiving systems: import, correction, appeal and safe exit. You can preview a route using a small selected bundle and see where people with different devices, languages or records get stuck. Its finish is not a shiny compatibility badge. It produces a dated pass or failure receipt, names the responsible provider and shows the next human route.",
      "whatItDoesSummary": "RouteBright tests the whole journey into a new provider—not just whether a file uploads—and shows whether acceptance, correction, service continuity and later exit work in practice.",
      "whyOnListSummary": "A future portability rule could be technically satisfied while people still cannot make a safe move. Personalised imports, hidden acceptance rules and accumulated context may create barriers that a normal standards badge misses. RouteBright ranks highly because an independent, continuously updated test utility could make the entire market more honest and give individuals a clear result before they take a risky step.",
      "why2031Not2026": "Technical interoperability tests exist now, but this forecast assumes 2031 providers can personalise receiving behaviour deeply enough that documentation and a sample file no longer predict whether a real person's status, correction and continuity will survive.",
      "whyThisRank": "RouteBright scores strongly because it is independent, globally adaptable and produces an observable result without deciding anyone's rights. It ranks below SiftPass after a score tie because testing infrastructure supports a move rather than completing it. It ranks above FactBrake because protected test accounts and published receipts appear easier to bound than pausing live downstream decisions.",
      "whyAboveNext": "It outranks FactBrake because a test lab can expose bad routes without intervening in a live consequential decision, giving it a safer and more achievable authority boundary.",
      "couldMoveUpIf": "It could rise if regulators protect independent live-route testing and switching claims repeatedly fail despite formal technical standards.",
      "couldMoveDownIf": "It would drop if mandatory conformance tests reliably predict real personal journeys or providers block representative testing.",
      "strongestCounterCase": "Regulators and standards bodies may build full person-journey testing into ordinary certification, so a separate consumer-facing marketplace service might duplicate public infrastructure.",
      "scores": {
        "futureDistance": 5,
        "needScale": 4,
        "globalBreadth": 5,
        "marketplaceClarity": 5,
        "deliveryReadiness2031": 4,
        "trustAndSafety": 5,
        "total": 93
      },
      "rating": 4.6,
      "imaginedReviews": [
        {
          "reviewerAlias": "SwitchBeforeSeven",
          "title": "Saved me from a broken move",
          "body": "The provider advertised full import, but RouteBright showed that corrections disappeared after seven days. I waited for the fix instead of losing my history.",
          "stars": 5,
          "stance": "benefit",
          "fictionalDisclosure": true
        },
        {
          "reviewerAlias": "CaseNotTypical",
          "title": "My result differed from the test",
          "body": "The public route passed, but my unusual licence record still failed. The receipt helped with appeal, although the green label had made me too confident.",
          "stars": 3,
          "stance": "critical",
          "fictionalDisclosure": true
        }
      ]
    },
    {
      "candidateId": "category-003-candidate-07",
      "rank": 4,
      "name": "FactBrake",
      "developerName": "ClearTrace Cooperative",
      "salesPitch": "Freeze the damage from one wrong record, then make every affected provider test its decision again.",
      "storeDescription": "FactBrake is a forecast circuit breaker for a status error that has travelled beyond its source. It maps where the disputed fact is being used, sends a clearly labelled dispute marker and offers minimum alternate proof. Providers are asked to pause that fact—not every safety process—while a human checks it. After correction, FactBrake retests affected decisions and leaves a receipt for each place that changed, refused or never answered.",
      "whatItDoesSummary": "FactBrake traces one false, stale or mismatched status fact across connected providers, marks it as disputed, routes correction to humans and retests the decisions it influenced.",
      "whyOnListSummary": "By 2031, a decision-changing fact could move quickly through several concentrated cognitive and service systems. Correcting the source alone may be too slow if other systems keep using yesterday's copy. FactBrake makes the list because it addresses the new shape of the harm: not a bad database row, but a spreading operational failure. Its observable finish is a corrected source, retested decisions and named unresolved owners.",
      "why2031Not2026": "People dispute records provider by provider today. This becomes a genuinely future-native service if status facts propagate automatically across work, learning, finance and services faster than normal correction can reach every receiver.",
      "whyThisRank": "FactBrake could solve frequent and severe exclusion across all nine geographic lenses, but its power must be tightly limited. A private app cannot declare a disputed fact false or reverse a safety-critical decision. That authority risk and the need for receiving systems to recognise a bounded dispute state keep it below RouteBright, despite its very high need score.",
      "whyAboveNext": "It ranks above PocketPassage because record errors could happen every day across connected systems, while offline courier events are likely to be less frequent for many users.",
      "couldMoveUpIf": "It could rise if providers adopt standard dispute markers, fast source correction and automatic retesting of affected decisions.",
      "couldMoveDownIf": "It would fall if automatic refresh prevents copied errors or if providers treat every dispute marker as an unsafe demand to ignore evidence.",
      "strongestCounterCase": "Better source-data quality, instant correction propagation and strong human exception routes could prevent enough cascades that an independent circuit breaker never becomes necessary.",
      "scores": {
        "futureDistance": 5,
        "needScale": 5,
        "globalBreadth": 5,
        "marketplaceClarity": 5,
        "deliveryReadiness2031": 3,
        "trustAndSafety": 4,
        "total": 92
      },
      "rating": 4.7,
      "imaginedReviews": [
        {
          "reviewerAlias": "NotTwoPeople",
          "title": "The duplicate identity stopped spreading",
          "body": "Three services had copied the same mistaken match. FactBrake found the source, marked the copies and showed which decisions were tested again.",
          "stars": 5,
          "stance": "benefit",
          "fictionalDisclosure": true
        },
        {
          "reviewerAlias": "ReviewStillOpen",
          "title": "A marker is not a correction",
          "body": "Two providers paused the bad fact, but the original issuer took twelve days to review it. The dashboard felt finished before my case really was.",
          "stars": 3,
          "stance": "critical",
          "fictionalDisclosure": true
        }
      ]
    },
    {
      "candidateId": "category-003-candidate-08",
      "rank": 5,
      "name": "PocketPassage",
      "developerName": "Lantern Relay Systems",
      "salesPitch": "Carry the proof you need through an outage or move—without carrying your entire private history.",
      "storeDescription": "PocketPassage is a forecast offline proof courier for the days when live digital verification fails. Before a move, storm or provider shutdown, it builds a small encrypted package containing only the records needed for a chosen purpose. A clinic, shelter, employer or service desk can check the seal without reaching the original network. Later, the package reconnects, checks revocations, records acceptance or refusal and destroys temporary copies under a visible rule.",
      "whatItDoesSummary": "PocketPassage turns selected records into an offline-verifiable package, carries them across an outage or displacement, records what the receiver did and reconciles changes when networks return.",
      "whyOnListSummary": "The forecast does not assume a perfectly connected 2031. Digital proof may become the normal gate to essential services at the same time that climate events, conflict, migration, power failures and provider concentration expose brittle points. PocketPassage makes the list because it joins advanced verification with a physical-world finish. It helps a receiver check enough proof now, without demanding a person's whole history or waiting indefinitely for the source.",
      "why2031Not2026": "Paper documents and offline credentials already exist. The 2031 product would be different because most services normally expect live shared records, while selective packages must support revocation, temporary continuity, later reconciliation and copy destruction across providers.",
      "whyThisRank": "PocketPassage is especially strong across regions where connectivity, displacement or institutional reliability varies. It has a clear transaction and can degrade to local human witnesses. It ranks fifth because safe offline revocation and cross-border acceptance are hard, and because many well-connected users may need it only occasionally rather than as a constant service.",
      "whyAboveNext": "It outranks EarnedElsewhere because keeping access alive during outages and displacement applies to more kinds of urgent need than transferring one class of achievement.",
      "couldMoveUpIf": "It could rise if live digital records become near-universal while prolonged outages and displacement expose repeated continuity failures.",
      "couldMoveDownIf": "It would fall if essential providers keep strong manual routes or if offline packages cannot be revoked and accepted safely.",
      "strongestCounterCase": "Resilient networks, ordinary paper documents and staffed exception desks may cover the real need more simply than a new courier system with complex trust rules.",
      "scores": {
        "futureDistance": 5,
        "needScale": 5,
        "globalBreadth": 5,
        "marketplaceClarity": 4,
        "deliveryReadiness2031": 4,
        "trustAndSafety": 3,
        "total": 90
      },
      "rating": 4.6,
      "imaginedReviews": [
        {
          "reviewerAlias": "ThreeDaysNoGrid",
          "title": "Worked when the network did not",
          "body": "The local shelter checked my selected family record from the offline seal. Nothing about my employment or health history was included.",
          "stars": 5,
          "stance": "benefit",
          "fictionalDisclosure": true
        },
        {
          "reviewerAlias": "RevocationLate",
          "title": "Old proof stayed valid too long",
          "body": "The receiving desk had not downloaded the newest revocation list. It accepted the package, but the warning appeared only when we reconnected.",
          "stars": 3,
          "stance": "critical",
          "fictionalDisclosure": true
        }
      ]
    },
    {
      "candidateId": "category-003-candidate-03",
      "rank": 6,
      "name": "EarnedElsewhere",
      "developerName": "Open Merit Forge",
      "salesPitch": "Take proof of what you achieved—not your employer's secret score or your whole behaviour history.",
      "storeDescription": "EarnedElsewhere is a forecast achievement passport built for work and learning that happened inside a closed AI platform. You select one claim, such as a skill, completed project or care contribution. An independent assessor reruns a narrow test, records the method and creates proof a new organisation can check. The passport carries no universal reputation score. It also tracks whether the receiver accepted the claim, requested a fair recheck or rejected it with a human appeal route.",
      "whatItDoesSummary": "EarnedElsewhere turns one trapped achievement into a narrow, independently rechecked proof that another employer, school or service can inspect without seeing your unrelated history.",
      "whyOnListSummary": "This forecast allows for a 2031 in which powerful providers become the main witnesses to economically meaningful work, learning and contribution. Leaving such a provider could otherwise erase standing or force a person to share an invasive history. EarnedElsewhere belongs in the Top 10 because it offers a clear new transaction: choose a claim, re-prove it independently, carry it elsewhere and test whether the receiver truly accepts it.",
      "why2031Not2026": "Portfolios, references and digital credentials already move achievements. The future discontinuity is that much useful cognitive work may be visible mainly inside enclosed provider histories, while receivers need independent proof that does not depend on the original platform.",
      "whyThisRank": "The need could be large and globally important, especially as roles and learning routes change. It ranks below PocketPassage because receiver trust in new proof methods will vary by occupation, culture and law, and because direct practical trials may sometimes be simpler. Its high score reflects the genuinely future-native problem, not a claim that one passport will fit everyone.",
      "whyAboveNext": "It sits above MemoryLifeboat because losing proof of an achievement can immediately block work or learning, while people can sometimes restart an AI relationship with a careful summary.",
      "couldMoveUpIf": "It could rise if closed providers become the dominant witnesses to work and major receivers accept transparent independent rechecks.",
      "couldMoveDownIf": "It would fall if practical trials, public credentials or strong issuer exports remain trusted enough without a new passport layer.",
      "strongestCounterCase": "Employers and learning bodies may prefer live demonstrations tailored to each role, making portable achievement proofs less useful than direct testing at the destination.",
      "scores": {
        "futureDistance": 5,
        "needScale": 5,
        "globalBreadth": 4,
        "marketplaceClarity": 5,
        "deliveryReadiness2031": 3,
        "trustAndSafety": 4,
        "total": 89
      },
      "rating": 4.5,
      "imaginedReviews": [
        {
          "reviewerAlias": "BuiltItInside",
          "title": "My project survived the platform",
          "body": "The assessor reran the important part of my old project and gave the new workshop a proof they could understand without my full activity log.",
          "stars": 5,
          "stance": "benefit",
          "fictionalDisclosure": true
        },
        {
          "reviewerAlias": "DifferentStandard",
          "title": "The receiver wanted another test",
          "body": "The proof was clear, but the licensing body still required its own assessment. I paid for a recheck that only shortened the interview.",
          "stars": 3,
          "stance": "critical",
          "fictionalDisclosure": true
        }
      ]
    },
    {
      "candidateId": "category-003-candidate-02",
      "rank": 7,
      "name": "MemoryLifeboat",
      "developerName": "Second Start Systems",
      "salesPitch": "Leave your old AI without losing the memories that help—or dragging every private moment into the next one.",
      "storeDescription": "MemoryLifeboat is a forecast exit lane for years of AI-held context. It lays out remembered preferences, projects, relationships and disputed guesses in plain language. You choose a small package, ask other people before moving shared memories, and preview how a new provider will use it inside a sandbox. If the move works, the app tests whether unwanted history was deleted later. If it fails, you can return, correct the package or start clean.",
      "whatItDoesSummary": "MemoryLifeboat inventories what an AI provider remembers, helps you choose a safe and understandable subset, previews it with a new provider and checks old-provider deletion after the move.",
      "whyOnListSummary": "By 2031, durable machine memory could shape work offers, service treatment and relationships strongly enough that starting again is not a real choice. That is a different problem from exporting chat logs. MemoryLifeboat makes the list because it treats memory as something to inspect, edit, obtain shared consent for, test at the destination and delete at the source. The outcome is a usable new start, not a giant mystery file.",
      "why2031Not2026": "People can copy prompts, summaries and account exports today. This becomes a future-native service only when years of structured AI memory materially affect treatment and switching, and both old and new providers expose testable import and deletion routes.",
      "whyThisRank": "MemoryLifeboat is one of the clearest products in the set and strongly reflects a possible 2031 enclosure problem. It ranks seventh because the scale depends on durable AI memory becoming both valuable and difficult to recreate. Consent for memories involving family, colleagues or clients also creates hard limits that an attractive interface cannot solve alone.",
      "whyAboveNext": "It outranks StewardMesh because a self-serve memory move could serve many repeated provider trials, while accountable neighbourhood re-verification depends on a slower local steward network.",
      "couldMoveUpIf": "It could rise sharply if durable AI memory becomes a major source of service quality, income access and relationship continuity.",
      "couldMoveDownIf": "It would fall if short summaries work well, providers standardise safe export and deletion, or most people prefer a clean restart.",
      "strongestCounterCase": "Memory export and deletion may become ordinary account settings, and users may find that a short human-written profile transfers the useful context without an independent service.",
      "scores": {
        "futureDistance": 5,
        "needScale": 4,
        "globalBreadth": 4,
        "marketplaceClarity": 5,
        "deliveryReadiness2031": 4,
        "trustAndSafety": 3,
        "total": 86
      },
      "rating": 4.5,
      "imaginedReviews": [
        {
          "reviewerAlias": "FreshStartNotBlank",
          "title": "Kept the useful five percent",
          "body": "I moved my accessibility preferences and active projects, but left years of emotional guesses behind. The preview showed exactly what the new assistant would see.",
          "stars": 5,
          "stance": "benefit",
          "fictionalDisclosure": true
        },
        {
          "reviewerAlias": "SharedMemoryQuestion",
          "title": "Consent took longer than the move",
          "body": "Several work memories involved other people, so the app paused them for permission. That was responsible, but the package became much less useful.",
          "stars": 3,
          "stance": "critical",
          "fictionalDisclosure": true
        }
      ]
    },
    {
      "candidateId": "category-003-candidate-12",
      "rank": 8,
      "name": "StewardMesh",
      "developerName": "Neighbour Grid Federation",
      "salesPitch": "Sit with a real local steward who can re-prove your achievement and stay responsible until it is accepted.",
      "storeDescription": "StewardMesh is a forecast network of trained human stewards connected by shared proof methods. Bring one achievement that is trapped inside a closed provider: a project, skill, care task or community contribution. Your steward helps gather minimum evidence, arranges a narrow practical recheck and sends the result through an independent federation review. They then test the receiving route and remain your named contact for correction or appeal, without claiming authority to grant a job, licence or right.",
      "whatItDoesSummary": "StewardMesh pairs a person with an accountable nearby steward who rechecks one achievement, creates a narrow portable proof, tests receiver acceptance and helps with correction.",
      "whyOnListSummary": "A highly automated 2031 could still need physical access, local language and human responsibility. Remote proof systems may work poorly for people with missing documents, weak connectivity or achievements that only make sense in context. StewardMesh makes the list because it combines machine-checkable receipts with a named person who stays through the receiving journey. That could make portability practical beyond well-connected users, rather than merely available on paper.",
      "why2031Not2026": "Advisers, assessors and credential services perform parts of this work now. The 2031 difference is a federated service responsible from rechecking closed-platform evidence through machine-readable transfer, receiver testing and appeal across a wider provider economy.",
      "whyThisRank": "StewardMesh offers a strong safety boundary and a meaningful route for people underserved by remote systems. It ranks eighth because training, consistency, funding and federation capture are difficult, and the right local institution will differ greatly across nine geographic lenses. It remains above distributed deletion because its human accountability and finished receiver journey are easier to understand and govern.",
      "whyAboveNext": "It ranks above CopyWake because a named steward can complete a bounded proof journey, while proving that every distributed copy is truly gone remains technically and legally uncertain.",
      "couldMoveUpIf": "It could rise if closed-provider achievements spread while remote proof systems repeatedly exclude people who need assisted or offline routes.",
      "couldMoveDownIf": "It would fall if national credential bodies or safe remote assessors provide trusted re-verification more consistently and cheaply.",
      "strongestCounterCase": "A small number of public credential bodies may deliver more consistent recognition and appeal than a local federation, which could vary in quality or be captured by powerful members.",
      "scores": {
        "futureDistance": 5,
        "needScale": 4,
        "globalBreadth": 4,
        "marketplaceClarity": 5,
        "deliveryReadiness2031": 3,
        "trustAndSafety": 4,
        "total": 85
      },
      "rating": 4.6,
      "imaginedReviews": [
        {
          "reviewerAlias": "NoSignalWorkshop",
          "title": "A person stayed with the case",
          "body": "My steward watched me repeat the repair, explained the proof and called the receiver when its import failed. I was not sent back to a bot.",
          "stars": 5,
          "stance": "benefit",
          "fictionalDisclosure": true
        },
        {
          "reviewerAlias": "AcrossTwoRegions",
          "title": "Recognition changed at the border",
          "body": "The local proof was careful, but the receiving federation used a different method. A second review fixed it, although the process took weeks.",
          "stars": 3,
          "stance": "critical",
          "fictionalDisclosure": true
        }
      ]
    },
    {
      "candidateId": "category-003-candidate-05",
      "rank": 9,
      "name": "CopyWake",
      "developerName": "Aftertrace Labs",
      "salesPitch": "Find the memory copies still following you and get a receipt for what was deleted, kept or rebuilt.",
      "storeDescription": "CopyWake is a forecast deletion witness for records that have travelled through connected agents and providers. It builds a privacy-protected map from operator notices, sends the actions you choose and records each response. Later checks look for carefully designed signs that an unwanted memory has resurfaced. The app never promises magical erasure. It labels copies as deleted, lawfully retained, unknown or apparently reconstructed, then packages unresolved items for a named human and outside review.",
      "whatItDoesSummary": "CopyWake maps where a selected record or memory may have travelled, sends deletion or correction actions, checks for later resurfacing and records every known or unresolved result.",
      "whyOnListSummary": "Deletion could become a network problem by 2031 if autonomous services routinely copy, derive and rebuild durable memories across changing providers. An account-level delete button would not show what happened downstream. CopyWake makes the list because people would need an independent witness, not another promise from the system being questioned. Its honest output is a map of confirmed, retained, unknown and resurfaced copies with routes for challenge.",
      "why2031Not2026": "Deletion requests today mostly target known organisations. The future leap is an operator graph where connected agents propagate useful memory automatically, while standard lineage and action receipts make at least part of that graph independently testable.",
      "whyThisRank": "The concept is strongly future-facing and could recur whenever relationships or providers change. It ranks ninth because complete deletion is almost impossible to prove, reconstruction can look like hidden retention, and the map itself could become a dangerous concentration of personal history. Those safety and readiness limits make its finish less certain than StewardMesh's bounded human service.",
      "whyAboveNext": "It outranks TrialSlice because deletion and correction affect anyone leaving a connected service, whereas realistic provider trials may remain a narrower shopping behaviour.",
      "couldMoveUpIf": "It could rise if agent networks widely publish verifiable lineage receipts and hidden downstream retention becomes a common, visible harm.",
      "couldMoveDownIf": "It would fall if providers keep memory inside visible accounts or statutory audits make a separate person-facing witness unnecessary.",
      "strongestCounterCase": "Built-in lineage controls and regulator-run deletion audits could be more complete and safer, while a personal copy map might reveal sensitive relationships without proving true erasure.",
      "scores": {
        "futureDistance": 5,
        "needScale": 5,
        "globalBreadth": 4,
        "marketplaceClarity": 4,
        "deliveryReadiness2031": 3,
        "trustAndSafety": 3,
        "total": 84
      },
      "rating": 4.3,
      "imaginedReviews": [
        {
          "reviewerAlias": "LeftButNotGone",
          "title": "Finally saw the downstream copies",
          "body": "The map found two agents I had forgotten. One deleted the memory and the other explained its legal retention with a real review contact.",
          "stars": 5,
          "stance": "benefit",
          "fictionalDisclosure": true
        },
        {
          "reviewerAlias": "UnknownMeansUnknown",
          "title": "Too many grey boxes",
          "body": "Several providers never returned a usable receipt. I appreciate the honesty, but the app could not tell me whether those memories were actually gone.",
          "stars": 3,
          "stance": "critical",
          "fictionalDisclosure": true
        }
      ]
    },
    {
      "candidateId": "category-003-candidate-06",
      "rank": 10,
      "name": "TrialSlice",
      "developerName": "Switchroom Research",
      "salesPitch": "Test a new provider with enough real history to judge it—then take that history back if you walk away.",
      "storeDescription": "TrialSlice is a forecast trial room for memory-rich services. A blank account may tell you almost nothing, so the app creates a temporary, purpose-bound slice of your real context. It runs inside an isolated receiving account, compares treatment with your current provider and explains what affected the result. When the trial ends, the copy expires and delayed checks look for retention. You receive a switch, stay or unresolved-deletion receipt rather than a marketing score.",
      "whatItDoesSummary": "TrialSlice lends a new provider a temporary, selected piece of your history, compares the real experience, expires the copy and checks later whether the trial data stayed gone.",
      "whyOnListSummary": "If accumulated personal context becomes a major part of service quality, a blank free trial will not show whether switching is realistic. TrialSlice belongs in the Top 10 because it creates a new market transaction: a reversible test using enough genuine history to matter, without making a permanent shadow profile. It could help competition work in a provider economy where memory—not just features or price—creates the strongest lock-in.",
      "why2031Not2026": "Free trials exist now, but they usually start blank. The 2031 need appears only if long-lived context materially changes provider performance and receiving systems can isolate, explain, expire and later prove their handling of temporary real data.",
      "whyThisRank": "TrialSlice has excellent product clarity and plausible 2031 technology, but ranks tenth because its need is less universal than correction, continuity or proof transfer. Some people may recreate context cheaply, and standard operating-system sandboxes could absorb the service. Its bounded temporary copy is still clearer and safer than continuously monitoring an old provider for personalised return pressure.",
      "whyAboveNext": "It stays above the strongest excluded candidate, the clean-exit return-pressure shield, because an isolated trial has a clear start, finish and data boundary; broad post-exit pressure monitoring risks becoming invasive and hard to prove.",
      "couldMoveUpIf": "It could rise if provider quality depends heavily on accumulated memory and blank-account comparisons repeatedly mislead people about switching.",
      "couldMoveDownIf": "It would fall if context can be rebuilt cheaply or operating systems provide trusted temporary-data sandboxes as a standard control.",
      "strongestCounterCase": "Regulators or device operating systems may provide safe trial sandboxes automatically, and people may find that a clean start reveals provider quality better than importing selected history.",
      "scores": {
        "futureDistance": 5,
        "needScale": 3,
        "globalBreadth": 3,
        "marketplaceClarity": 5,
        "deliveryReadiness2031": 4,
        "trustAndSafety": 4,
        "total": 81
      },
      "rating": 4.4,
      "imaginedReviews": [
        {
          "reviewerAlias": "TestedThenMoved",
          "title": "A fair comparison at last",
          "body": "The new provider handled my study plan much better once it had the selected context. The trial expired cleanly and I chose to switch.",
          "stars": 5,
          "stance": "benefit",
          "fictionalDisclosure": true
        },
        {
          "reviewerAlias": "SandboxDoubt",
          "title": "Deletion check was only a signal",
          "body": "The trial was useful, but the later check could not prove the provider had forgotten everything. I wanted a stronger guarantee than the app could give.",
          "stars": 3,
          "stance": "critical",
          "fictionalDisclosure": true
        }
      ]
    }
  ],
  "excluded": [
    {
      "candidateId": "category-003-candidate-09",
      "reason": "The clean-exit return-pressure shield is the strongest excluded concept, but its boundary is too diffuse for this Top 10. Detecting whether poorer treatment after exit is deliberate pressure would require invasive, long-running monitoring across many relationships, and the service could confuse correlation with provider retaliation. TrialSlice covers a narrower switching problem with a clearer start, finish and data boundary."
    },
    {
      "candidateId": "category-003-candidate-10",
      "reason": "The member-governed status separation union may be valuable where powerful operators share proof terms, but it behaves more like a collective institution than an independently callable marketplace product. Its fit also depends heavily on local labour, civic and membership rules, and membership itself could become another status gate. SiftPass preserves the strongest selective-transfer job without requiring a new representative organisation."
    }
  ]
}
