# Perpetuals First Visitor Experience ## Purpose of This Document This document defines the communication model for a first-time visitor arriving at perpetuals.io with no prior knowledge of the project. It is not a layout brief, user interface specification, copywriting exercise, marketing plan, or implementation guide. It does not redesign the project and does not replace existing canonical architecture documents. Its purpose is narrower: to define what the homepage should help a first-time visitor understand, feel, and be ready to do during the first minute. The homepage should communicate Perpetuals as a research-led product ecosystem concerned with making digital subjects and claims inspectable through evidence, provenance, continuity, and explicit uncertainty. It should also introduce Inspect as the first product within that ecosystem without allowing Inspect to be mistaken for the whole project. --- ## Part 1 — First Impression A first-time visitor should not be expected to understand the full architecture immediately. The first minute should progressively reduce confusion. The communication task is to move the visitor from: ```text What is this? ``` toward: ```text This project helps people inspect digital claims and subjects before relying on them. ``` ### Within 10 Seconds The visitor should understand the basic category of the project. They should be able to say: - Perpetuals is about digital information that people need to inspect carefully. - It is concerned with claims, evidence, provenance, continuity, and uncertainty. - It is not simply a website, protocol announcement, AI tool, blockchain project, or trust badge. The visitor should feel: - oriented rather than impressed; - invited to examine rather than asked to believe; - confident that the project is careful with its claims. The homepage should avoid requiring the visitor to decode internal terminology before they know why the project exists. ### Within 30 Seconds The visitor should understand the problem Perpetuals addresses. They should be able to say: - Digital subjects and claims often appear across fragmented systems. - Data may be available without being easy to inspect. - People need to understand what is being claimed, what supports it, where it came from, how it changed, and what remains uncertain. - Perpetuals exists in the space between raw data and final judgment. The visitor should feel: - that the problem is real and recognizable; - that Perpetuals is not overstating what existing systems fail to do; - that the project is defining a disciplined inspection problem, not inventing a vague trust problem. At this stage, the visitor does not need a full model of the ecosystem. They need to understand why inspection matters. ### Within 60 Seconds The visitor should understand the relationship between the ecosystem and its first product. They should be able to say: - Perpetuals is the broader ecosystem, research framework, and product architecture. - Inspect is the first product that applies the Perpetuals approach. - Inspect helps make the evidentiary structure of digital subjects and claims easier to examine. - Perpetuals does not claim to make final judgments for the visitor. - The project exists to support better-grounded human and institutional judgment. The visitor should feel: - that they know where to go next; - that Inspect is a concrete entry point; - that the broader project remains larger than one product; - that uncertainty is treated as part of responsible communication, not as a weakness to hide. The desired first-minute outcome is not conversion. It is comprehension. --- ## Part 2 — Mental Model After one minute, a visitor should be able to explain the following in plain language. ### What Perpetuals Is Perpetuals is a research-led product ecosystem for helping people inspect digital subjects and claims. A digital subject may be an account, organization, agent, model, project, credential, work, identity, synthetic persona, or other entity represented across digital systems. Perpetuals focuses on the relationships among: - what is being claimed; - who or what made the claim; - what evidence supports it; - where the information came from; - what changed over time; - what remains uncertain; - what a person can responsibly conclude from the available evidence. In plain language: ```text Perpetuals helps make the structure behind digital claims easier to inspect. ``` ### What Problem It Addresses Digital systems often expose pieces of information without making their meaning easy to examine. A system may show a result, credential, provenance trail, event log, generated answer, profile, signature, or status. But a thoughtful observer may still need to know: - What exactly is being claimed? - What is the subject of the claim? - What evidence supports it? - Where did the evidence come from? - Has the subject changed? - Which earlier states still matter? - Is the claim current, disputed, superseded, partial, or uncertain? - What can be inspected directly, and what is only interpretation? Perpetuals addresses the gap between access to data and understanding of evidence. In plain language: ```text Having data is not the same as being able to inspect what it means. ``` ### What Perpetuals Is Not Perpetuals should be clearly separated from adjacent categories. It is not: - a universal trust system; - a reputation score; - a replacement for identity systems; - a replacement for provenance systems; - a blockchain-first project; - an AI-first project; - a protocol-first project; - a claim that software can decide truth on behalf of people; - a promise to remove ambiguity from digital life; - a single product called Inspect. Perpetuals may relate to identity, provenance, verification, credentials, attestations, logs, governance, AI systems, or blockchain systems. But those categories do not define the project. In plain language: ```text Perpetuals is not asking visitors to trust a system. It is about helping them inspect before they trust, rely, or decide. ``` ### Why Perpetuals Exists Perpetuals exists because people and institutions increasingly make decisions about digital subjects they cannot directly observe and histories that are spread across many systems. The project begins from a conservative position: ```text Before asking someone to trust an output, a system should help them inspect the evidence, provenance, continuity, and uncertainty behind it. ``` Perpetuals does not remove the need for judgment. It improves the conditions under which judgment happens. --- ## Part 3 — Visitor Questions A thoughtful visitor is likely to ask the following questions. The homepage does not need to answer every question exhaustively, but it should answer enough to prevent confusion. ### What is Perpetuals? Perpetuals is the broader ecosystem for making digital subjects and claims inspectable through evidence, provenance, continuity, and explicit uncertainty. ### Why does this matter? Because digital systems increasingly ask people to rely on claims, outputs, identities, credentials, records, and histories without clearly showing the evidentiary structure behind them. ### Who is this for? It is for people and organizations that need to evaluate digital subjects or claims carefully. This may include researchers, builders, institutions, governance teams, infrastructure designers, analysts, and future users of products built within the ecosystem. ### What problem does it solve? It helps address the gap between seeing digital information and understanding what supports it, how it changed, where it came from, and what remains uncertain. ### Why should I trust this? The homepage should not ask for trust first. It should earn confidence by being clear about scope, showing the research-led basis of the project, distinguishing evidence from conclusions, and avoiding exaggerated claims. ### Why not use existing tools? Existing tools may provide identity, provenance, credentials, verification, logs, analytics, or generated answers. Perpetuals does not replace those categories. It focuses on the inspection layer between available information and responsible judgment: how claims, evidence, provenance, continuity, and uncertainty are examined together. ### Is this a protocol? Not primarily. Perpetuals is not defined by being protocol-first. Protocols may become relevant in specific contexts, but the project is defined by the inspection problem and the ecosystem that addresses it. ### Is this a blockchain project? No. Blockchain systems may be relevant to some evidence, provenance, or recordkeeping contexts, but Perpetuals is technology-neutral. It is not blockchain-first. ### Is this an AI product? No. AI may be relevant to some products, workflows, or digital subjects, but Perpetuals is not AI-first. The project is concerned with inspectability across digital systems, including but not limited to AI contexts. ### Is Perpetuals trying to decide what is true? No. Perpetuals should help expose the structure of claims and evidence. It should not imply that the system replaces human or institutional judgment. ### What is Inspect? Inspect is the first product in the Perpetuals ecosystem. It is the first practical product surface for examining digital subjects and claims through the Perpetuals approach. ### Why is Inspect the first product? Inspection is the most immediate practical expression of the Perpetuals thesis. Before people can responsibly rely on a claim, compare histories, evaluate continuity, or understand provenance, they need a way to inspect what is being asserted and what supports it. ### Is Inspect the whole project? No. Inspect is the first product. Perpetuals is the ecosystem, research foundation, architecture, and set of principles that can guide Inspect and future products. ### What should I do next? A first-time visitor should know whether to explore the product, read the research and architecture, or learn more about the problem space. The homepage should make those paths feel distinct without forcing the visitor into one path prematurely. --- ## Part 4 — Communication Priorities The homepage should communicate only the minimum ideas needed for first-minute comprehension. ### Minimum Ideas That Must Be Communicated #### 1. Perpetuals is the ecosystem Visitors should understand that Perpetuals is not a single interface or feature. It is the larger research-led product ecosystem. #### 2. The core concern is inspection The central action is inspection: examining digital subjects and claims through evidence, provenance, continuity, and uncertainty. #### 3. The problem is the gap between data and understanding The homepage should make clear that access to data does not automatically explain what is claimed, what supports it, how it changed, or where uncertainty remains. #### 4. Evidence comes before conclusions The project should feel disciplined because it foregrounds evidence and limitations before asking for belief, reliance, or acceptance. #### 5. Uncertainty remains visible The homepage should communicate that uncertainty is not a failure of the project. It is part of responsible inspection. #### 6. Inspect is the first product Visitors should understand that Inspect is the first concrete product and the natural first place to see the Perpetuals approach applied. #### 7. Perpetuals does not replace human judgment The homepage should make clear that the project supports better-grounded judgment rather than automating truth or trust. ### Ideas That Should Not Appear on the Homepage The following ideas may be important elsewhere, but they would overwhelm or misdirect first-time visitors if introduced too early. #### Detailed architecture taxonomies A first-time visitor does not need the full internal architecture of subjects, claims, evidence, continuity, provenance, products, records, or research cycles. #### Deep terminology before plain explanation Terms such as continuity records, portable transition meaning, agentic subjects, attestations, provenance graphs, or evidentiary structures should not appear before the visitor understands the plain-language problem. #### Future product speculation The homepage should not emphasize possible future products. Doing so would distract from the basic ecosystem-product relationship and could make the project appear unfocused. #### Protocol or infrastructure claims The homepage should avoid implying that Perpetuals is already a universal protocol, infrastructure layer, trust layer, identity layer, or verification layer. #### Overly broad civilizational claims The homepage should avoid framing Perpetuals as solving truth, trust, authenticity, identity, AI safety, governance, or the internet as a whole. #### Implementation detail The homepage should not explain storage models, schemas, APIs, system diagrams, deployment architecture, or technical implementation. #### Visual or interface mechanics The homepage should not depend on layout, animations, dashboards, diagrams, or UI mechanics to carry the core communication model. #### Marketing slogans The homepage should not rely on slogans that sound compelling but obscure the project's boundaries. Clarity is more important than memorability. --- ## Part 5 — Relationship Between Perpetuals and Inspect The homepage should introduce Inspect as the first concrete product without allowing it to collapse the meaning of Perpetuals. The relationship should be communicated as: ```text Perpetuals is the ecosystem. Inspect is the first product. ``` ### How the Homepage Should Introduce Inspect The homepage should first establish the broader problem: - digital subjects and claims are increasingly difficult to evaluate; - evidence, provenance, continuity, and uncertainty are often fragmented or implicit; - people need better ways to inspect before they rely. Only after that foundation should Inspect appear as the first product response. Inspect should be introduced as: - a practical entry point into the Perpetuals ecosystem; - the first product applying the Perpetuals inspection model; - a way to examine digital subjects and claims through their supporting evidence and uncertainty; - an example of the ecosystem's principles in use. Inspect should not be introduced as: - the whole of Perpetuals; - a finished answer to every problem the ecosystem studies; - a universal verification tool; - a trust engine; - a replacement for human judgment; - a proof that all future products are already defined. ### Why This Distinction Matters If the visitor sees Inspect before understanding Perpetuals, they may assume the project is only a tool. If the visitor sees only Perpetuals without Inspect, they may assume the project is only research or theory. The homepage should resolve both risks by presenting the relationship in sequence: 1. There is a recurring inspection problem. 2. Perpetuals is the ecosystem organized around that problem. 3. Inspect is the first product expression of the ecosystem. 4. The visitor can explore Inspect to see the approach made practical. This sequence preserves the architecture while giving the visitor a concrete next step. --- ## Part 6 — Success Test A successful homepage should make a first-time visitor capable of answering basic questions after one minute. The visitor does not need to repeat project language exactly. Their answers should show that they understood the communication model. ### Successful Answers If interviewed after one minute, a visitor should be able to say something close to the following. #### What is Perpetuals? Perpetuals is a broader ecosystem for helping people inspect digital subjects and claims by looking at evidence, provenance, change over time, and uncertainty. #### What problem is it addressing? Digital systems show a lot of information, but they do not always make it clear what is being claimed, what supports it, where it came from, how it changed, or what is still uncertain. #### What is Inspect? Inspect is the first product from Perpetuals. It is a practical way to apply the ecosystem's inspection approach. #### Is Inspect the same as Perpetuals? No. Inspect is the first product. Perpetuals is the larger ecosystem and research-led architecture behind it. #### What is Perpetuals not? It is not a trust score, reputation system, identity replacement, blockchain project, AI product, or tool that decides truth for people. #### Why does the project exist? It exists because people need better ways to examine digital claims before relying on them, especially when information is fragmented, changing, or uncertain. #### What should happen next? A visitor should know whether to learn more about the research, understand the ecosystem, or explore Inspect as the first product. ### Warning Signs The homepage has failed if a visitor says: - Perpetuals is just Inspect. - Perpetuals is mainly a blockchain protocol. - Perpetuals is an AI truth engine. - Perpetuals gives trust scores. - Perpetuals replaces identity or provenance systems. - Perpetuals removes uncertainty. - Perpetuals is only a research essay with no product direction. - Inspect is unrelated to the broader project. - The project sounds impressive but they cannot explain what problem it addresses. ### Minimum Passing Standard The minimum successful first-minute understanding is: ```text Perpetuals is a research-led product ecosystem for inspecting digital subjects and claims. It helps people examine evidence, provenance, continuity, and uncertainty before making judgments. Inspect is the first product that applies this approach. ``` If a visitor can express that idea in their own words, the homepage has communicated the project successfully.