Try Inheritance in ten minutes

On Sign in, press Explore a built handover. You get a private copy of a year of an IoT club's records, with four accounts of its own, and you are signed in as Arun, the outgoing lead. Nothing you do reaches other visitors.

Open Connect. Five files are listed with their access level: a volunteers chat (everyone), a committee chat and the Trello board (committee), finance minutes (finance), and Dr. Meena's private chat (private). Arun cannot see Dr. Meena's file at all; the database does not return it to him.

Open Reconstruct. Each card is a promise (who owes whom, what, by when) or a recurring duty (how often, whose approval, when to start). The label on each card is its trust state, set by a fixed rule, never by the model: corroborated (two independent records agree), sourced (one verified quote), inferred (only implied, never shown as fact), contradicted, or gap.

Press Open source message on any quote: the original message is shown with the quote highlighted. Code checked that every quote really is in its message before the item was stored.

The Docket tab lists records that disagree (a Trello card moved to Done while the chat says it was not done), with both quotes. The Gaps tab lists promises with no follow-up and items shown as No evidence kept, instead of guessing that they were done.

Open Review. Version 1 is already approved. A few items are still drafts: these are things the model found that a person should check, and some are wrong. Accept or reject each one (a reason is required, and every action is written to the History tab). Then press Mark ready for the advisor.

Switch to Dr. Meena from the menu at the top right. On Conflicts she can rule on each disagreement; on Draft she presses Approve this version to make version 2. Approved versions can never be edited, only replaced by a newer one.

Switch to Kavya and open Handover: the people waiting on her, a calendar of recurring duties with "start now" dates, and sealed placeholders for finance and private matters she may not read. She can accept an item, ask a question or decline it; Arun and Dr. Meena see her answers and can reply to a question.

Switch between Arun, Dr. Meena, Kavya and Divya and open the same pages. Kavya never sees the working ledger, only approved versions; Divya sees finance items; only Dr. Meena sees her private chat. These differences come from Postgres row-level security, not from hiding things on screen.

On Sign in, press Start from your own files. You land on Connect as Arun.

Download the photography club's four sample files from Connect, choose them all, set each to the level shown next to its link (committee, finance, private, committee), tick the authorisation box and import. The page reports what was read from each file.

Open Reconstruct and press Build the ledger. The model (Claude Haiku, through one adapter) reads only messages Arun may read, a few at a time, and the progress bar shows each stage. Everything it proposes is checked by code before it is stored, and arrives as a draft.

Then follow steps 4 to 7 of Path A: accept or reject the drafts, mark ready, approve as Dr. Meena, and read the handover as Kavya.