# Ordered · Tools Local-only tools for running Ordered engagements. Everything computes in the browser, nothing is sent anywhere, and no server or account exists. The whole system rests on one idea: ## The client file Every tool reads and writes the same portable JSON file, one per client. The intake tool creates it, the inventory tool fills it, the handbook tool renders it. The file is the engagement: it travels between tools, between machines, and eventually between operators. Convention: `surname-ordered-client.json` (e.g. `ellison-ordered-client.json`). Keep client files wherever you keep client materials. Treat them as confidential documents. **The file never contains passwords, master phrases, recovery codes, or any other secret.** It records that an account exists, how it is reached, and what its state is. Credentials live only in the client's own password manager. ## The tools (v0.1) | File | Stage | What it does | |---|---|---| | `01-intake.html` | Qualify & scope | Intake questionnaire, tier and fee recommendation with visible reasoning, situation summary. Creates the client file. | | `02-inventory.html` | Inventory | Fast structured capture of devices, accounts, subscriptions, and people. Risk tab computes single points of failure live, ranked, with deadlines from the access-end date. | | `03-handbook.html` | Handbook | Renders the client file into the print-ready Handbook: narrative sections editable in place, tables generated from the data, never a password. | | `04-cutover.html` | Separation | Generates the dated, phase-ordered cutover plan from the inventory (tasks that do not apply are left out automatically), plus the per-account migration board: six-step state per account, synced back to inventory status. | | `05-hardening.html` | Rebuild | The full audit: 102 items across ten domains, from the everyday to the rarely needed (Lockdown Mode, Innovis and ChexSystems freezes, NAS exposure, vehicle telematics, WHOIS privacy). Applicability grades E/M/V/R, before-and-after record per item, printable audit report. | | `06-review.html` | Annual Review | Loads baseline and current files, diffs everything: new, gone, changed field by field, regressions (weakened 2FA, lost backups, status slippage), and risk-posture deltas (cleared, improved, worsened). Plus the ten annual re-checks that decay regardless of change. Printable review report; export carries the record forward. | | `07-handover.html` | Handover | Generates the independence check from the client's real inventory (pick three of the generated candidates), the personalized options page with reasons shown and editable prices, and the graduation and thirty-day notes, editable and copyable. Prints the session sheet (yours) and the options page (theirs) separately. | | `08-dashboard.html` | Cross-cutting | Read-only. Drop all active client files at once: stage, access-window countdown, critical findings, open tasks, and the next due task per engagement, sorted by urgency. Nothing is stored; the drop is the load. | ## The public tools (discovery layer) Standalone pages for the Ordered site. No client file, no account, no email gate, no tracking: everything computes in the visitor's browser and nothing they enter leaves the page (each says so in the header). Each gives a complete, printable answer and ends with one honest line about having the same work done as an engagement. | File | Shadows | What the visitor gets | |---|---|---| | `p1-retirement-countdown.html` | Life After The Office | Ten questions plus the last-day date; builds a personalized, phase-ordered checklist dated backward from the day access ends, with tight-window and window-closed variants. Print or download as text. | | `p2-estate-readiness.html` | The Estate in Order | Fifteen weighted questions; a readiness score with a named band, the gaps ranked fix-first with the fix written next to each, and what is already solid. | | `p3-parent-checkup.html` | Looking After Mom and Dad | Twelve questions about a parent's setup; a protection plan ranked by protection per hour, with an on-the-visit tip for each step. | | `p4-photo-calculator.html` | The organization sprint | Six inputs; an honest estimate of library size, duplicate rate, and the do-it-yourself hours with the math itemized, plus the target architecture. | | `p5-scam-test.html` | Security and privacy | Six realistic scam scenarios (wire change, cloned-voice grandchild, bank-text, code read-back, tech-support pop-up, romance/long-game); scores exposure and names the defense per miss. Teaches, never shames. | | `p6-executor-firstweek.html` | After a Loss | A few gentle questions produce a calm, phase-ordered list of what to do about a deceased person's digital life, what can wait, and what never to rush. An overwhelmed answer trims to the essential few. | | `p7-icloud-untangler.html` | Apple and device care | Diagnoses why iCloud/device storage is full in plain English, corrects the deletion myth and shared-account trap, and gives an ordered, safe fix. The friendliest front door in the set. | | `p8-digital-life-audit.html` | The paid onboarding assessment | The wide-angle capstone: fifteen minutes across all four disciplines, a score per area, a written narrative, and a plan ordered weakest-area-first. The strongest single lead magnet and the top of the ladder. | | `p9-retirement-scorecard.html` | B2B: Life After The Office as an employer benefit | Completed by HR, benefits, or IT: scores the organization's retirement-transition readiness across five weighted dimensions (runway, personal separation, executive layer, security both directions, the relationship after), 18 questions, with per-gap fixes, consequence framing, and a printable report built to circulate internally. | ## The launcher and the Webflow kit `index.html` is the operator's local homepage: every tool as a card, split into the engagement sequence and the public layer. Open it from this folder; all links are relative. `webflow-embeds/` holds the publish kit for the four public tools. Each tool ships as a `-embed.html` fragment (the whole tool, stripped of html/head/body wrappers, sized well under Webflow's 50,000-character Code Embed limit) and a `-head.html` snippet (font links plus the title and meta description for the page's SEO settings). See READ-FIRST.txt in that folder, and the publishing guide that accompanies the kit. The operator tools (01-08) and this launcher are never published; they run from this folder. ## Deferred AI hooks in the public tools Each public tool keeps rules/data separate from rendering, with a marked SEAM comment where a later API layer drops in. The cleanest hooks: - p8 Digital Life Audit: `narrativeFor()` and the per-action `why` text are the only prose the report renders; an API layer can replace them with a tailored narrative from the same scores object, no other change. - p7 iCloud Untangler: `buildDiagnosis()` returns a structured object; the prose fields can be enriched from the same inputs. - p5 Scam Test: `SCENARIOS[].lesson` can expand into tailored coaching; the scoring is untouched. - p6 Executor: the `reassure` preamble and task wording can soften to tone without changing selection logic. Planned next: the AI-assisted layer on this schema (narrative in the Handbook, judgment support in scoping) and the paid Digital Estate Workbook (the rung between p2 and The Estate in Order). ## Using them 1. Open `01-intake.html` in any modern browser. Fill it in during or after the first call. Export: this downloads the client file. 2. Open `02-inventory.html`, load the client file, and capture the inventory during the discovery session. Watch the Risk tab as you go. Export when done (this replaces your working copy; the file is the single source of truth). 3. Open `03-handbook.html`, load the file, adjust the handbook settings and narrative, and print to PDF for the client copy. There is no autosave and no hidden storage. If you close a tab with unsaved changes the tool warns you. Export often; the downloaded file is the save. ## Notes - Fonts: Ringside (interface and copy) and Sentinel (headlines and headers) are called directly by name. They are installed locally, so local viewing always renders correctly, and they are served by Monotype once the site is published (no stylesheet link needed in these files). IBM Plex Mono (labels and data) loads from Google Fonts. The whole stack lives in three CSS variables in each file's :root (--font-body, --font-display, --font-mono), so if an installed or Monotype family name differs, it is a one-line edit. System faces are listed as fallbacks so nothing looks broken before the Monotype fonts resolve online. - Type treatment: major headlines are set in Sentinel Light; subheads in Ringside Bold, all-caps with extended tracking. This is enforced by the h1 / h2 rules appended at the end of each file's