Restarting The Heart grew from a question that still guides our work: how can lived experience, careful evidence, and responsible technology help people communicate what matters without claiming more than the evidence supports?
This month, several development tracks moved forward. They are connected by a common purpose, but they are not one product, and a development result is not a public launch. Here is where the work stands.
SuperstarIQ: from a repeatable slice to a controlled development workflow
SuperstarIQ is our consumer-directed health and wellness data and evidence technology in development. On September 17, 2026, RTH completed a bounded, deterministic MVP-0 engineering validation of one Source-Linked Evidence Summary slice using a frozen synthetic fixture. That established repeatability for a specific recorded setup. It did not establish clinical validation, independent qualification, or authorization to handle identifiable health data in production.
Since then, engineering has exercised a bounded local synthetic browser workflow: loading observations, presenting source-linked summary information, cleaning up a session, and rejecting a revoked token. This is useful development evidence, especially because it tests more of the path a person might eventually see. It does not transform the broader product into an independently reviewed or released service. Least-privilege authority, independent technical and security assessment, and later evidence gates remain open.
Our aim is still to make source identity, recency, uncertainty, and conflicts visible so a user can better organize information and prepare questions. SuperstarIQ is not intended to diagnose, treat, predict an emergency, or replace a qualified professional.
SIQTA: a separate product for trust and assurance
SuperstarIQ Trust & Assurance, or SIQTA, is a separate product in development. Its design asks five practical questions: What was requested? What authority applied? What actually executed? What evidence was observed? What changed afterward?
A system’s ability to perform an action is not the same as permission for that action. A provider’s success message is not necessarily independent proof of the intended effect. The integrity of a record does not automatically establish the truth of every claim within it. SIQTA’s development work is organized around preserving those distinctions.
Its direction is captured in a short line: Authority you can trace. Execution you can prove. That is an aspiration for a rigorously tested system, not a claim that SIQTA is already independently assured, certified, commercially available, or operating as a public enforcement service. SuperstarIQ may eventually use applicable SIQTA capabilities through a separately governed integration.
A cognitive-assistance app is being developed, with a different purpose
SuperstarIQ Memory remains a separately governed future product concept with an accessibility-oriented reminder app in synthetic-only internal development. The current internal work uses synthetic information to explore a reminder workflow that asks for an explicit response and retains an Activity Memory of what the person chose. It is designed around the practical importance of knowing the difference between an alert appearing and a task actually being completed.
This work has progressed beyond an idea into internal app development, but important evidence is still missing. Device-specific alarm delivery and degraded-state reliability, human-factor accessibility, real-data safeguards, and independent review must be established before external testing or release. The app is not available to the public, not a medication-management or emergency-response service, and not an active feature of SuperstarIQ.
Visual learning experiences: useful explanations, not working products
RTH is creating synthetic visual experiences to help people understand its ecosystem and how source-linked evidence may be organized. A diagram or simulator can make an abstract concept easier to grasp, but it can also look more mature than the underlying product. That is why any public interactive experience must be reviewed for accurate claims, accessibility, privacy, security, and its hosting behavior before publication.
We expect the first public-facing candidates to focus on understanding the ecosystem and the difference between a source, an observation, an uncertainty, and a summary. Internal engineering, security, finance, and readiness simulations are not public dashboards and should not be mistaken for live organizational status.
What comes next
Our next steps are specific: complete independent and domain-appropriate review, close the technical and accessibility evidence gaps, and publish only the information and experiences that pass their own release process. We will continue distinguishing planned, implemented, tested, independently qualified, and authorized for public use. Each is meaningful; none should silently stand in for another.
If you would like to follow the development journey or discuss a research or technology collaboration, explore SuperstarIQ, Research & Evidence, and Trust & Governance. Availability of a waitlist or inquiry form does not mean a pilot or product release has begun.
Development-status note: This article describes engineering and product work, not medical advice, a clinical validation result, a certification, a public beta, or an offer of a functioning health or reminder service.
Published October 18, 2026 · Last reviewed October 18, 2026