memhouse 0.18.12 → 0.20.1

package/LICENSE

@@ -1,22 +1,202 @@
-MIT License
-
-Copyright (c) 2026 Fatih Kadir Akın (agentlytics — original work)
-Copyright (c) 2026 Ramazan Polat (memhouse — derivative work)
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/LICENSES/agentlytics-MIT.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Fatih Kadir Akın
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/LICENSES/memhouse-MIT-until-0.18.11.txt

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2026 Fatih Kadir Akın (agentlytics — original work)
+Copyright (c) 2026 Ramazan Polat (memhouse — derivative work)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/LICENSES/models.dev-MIT.txt

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2025 models.dev
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+

package/NOTICE

@@ -0,0 +1,28 @@
+memhouse
+Copyright 2026 Ramazan Polat
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE), from
+version 0.19.0. Releases up to and including 0.18.11 were published under the MIT
+License; that text is kept in LICENSES/memhouse-MIT-until-0.18.11.txt and continues to
+apply to those releases.
+
+------------------------------------------------------------------------------------
+This product includes software from agentlytics
+(https://github.com/f/agentlytics), MIT (declared in its README:
+https://github.com/f/agentlytics/blob/master/README.md#license), Copyright (c) 2026
+Fatih Kadir Akın. See LICENSES/agentlytics-MIT.txt.
+
+memhouse was forked from agentlytics at commit 4cba3d8 (2026-06-21); the editor
+adapters, the dashboard and the cost engine originate there, and this repository's
+history carries that lineage. Every commit on main by an author other than Ramazan
+Polat predates the fork.
+
+------------------------------------------------------------------------------------
+pricing.json is derived from the models.dev model catalog
+(https://github.com/anomalyco/models.dev), Copyright (c) 2025 models.dev, licensed
+under the MIT License. See LICENSES/models.dev-MIT.txt.
+
+------------------------------------------------------------------------------------
+The built dashboard (public/) bundles third-party packages (React, chart.js,
+lucide-react, react-markdown, tailwindcss and others) under their own licenses. Their
+notices are in public/THIRD_PARTY_NOTICES.txt, generated at build time.

package/README.md

@@ -13,9 +13,19 @@ Cloud. memhouse runs no service of its own and proxies nothing. Then you, and yo
 can search every past session, see what it cost, and reopen the one that solved this
 before.
 
-Every row says where it came from, in a way no client can fake. `user_id` is stamped by
-the server (`MATERIALIZED currentUser()`), and `host` is a fingerprint derived from
-the machine's own id. A team pointed at one house gets a shared memory with real attribution.
+Every row says where it came from, in a way no client can fake. The server stamps the writing
+user on every conversation and archive row (`writer`, `MATERIALIZED currentUser()`; `user_id` on the 0.18 rooms), and
+`host` is a fingerprint derived from the machine's own id. A team pointed at one house gets a shared memory with real attribution.
+
+## New in 0.20
+
+- **A session is its store.** Every session is keyed by the machine, the harness, the harness's data folder (for OpenCode, its database file) and its own id. Two machines, or two data folders on one machine, never merge into one session.
+- **Ten editors read as they store their sessions:** agy, Copilot CLI, Cursor, cursor-agent, Devin, Gemini CLI, Goose, OpenCode, VS Code and Zed. Each gets a normaliser that reads its store directly. Claude Code and Codex are read natively. The rest go through the 0.18 readers.
+- **Nothing is cut or lost.** Tool output is kept in full. A message an editor reverts, rewinds or deletes stays in the house as a removed version: searchable with `memhouse q removed`, never counted.
+- **A fork is billed once.** Where one session copies another (a fork, a rewind copy), the copied prefix counts only in the original.
+- **Sharing is narrower.** A share is `SELECT` on exactly six conversation tables, full or scoped, and never reaches the capture archive or memhouse's own tables.
+- **Import a claude.ai export** with `memhouse import claude-ai`: [the guide](https://unpkg.com/memhouse/docs/guides/import-claude-ai.md).
+- **New houses start on schema 3.** An existing 0.18 house keeps working on 0.20 as it is until its admin converts it: see [Upgrade to 0.20](https://unpkg.com/memhouse/docs/guides/upgrade-to-0.20.md).
 
 ## Install
 
@@ -26,30 +36,32 @@ memhouse onboard             # finds your editors, sets up a house, ships, start
 
 No ClickHouse yet? `memhouse deploy --local` runs one in docker or podman, bound to
 loopback, and installs against it. Already have one, or an invite from someone who does?
-See [install and onboard](docs/guides/install.md).
+See [install and onboard](https://unpkg.com/memhouse/docs/guides/install.md).
 
 ## What you get
 
 ```bash
 memhouse status                  # is it shipping, and how fresh
 memhouse search "auth error"     # full-text across every session, every machine
+memhouse q recent                # the latest sessions; `memhouse q` lists every named query
 memhouse resume claude-code:6b1f… # prints the command that reopens that session
-memhouse plugins install claude  # /mem:recall and four more skills for your agents
+memhouse plugins install claude  # /mem:recall and four more skills, for Claude Code
 ```
 
-The dashboard is at `http://localhost:4640`, showing sessions, cost, models, tools and
-machines. From any Claude Code session, `/mem:recall how did I fix the ClickHouse auth
-error` answers from your own history.
+`memhouse dashboard` opens the dashboard in your browser, showing sessions, cost, models,
+tools and machines. From any Claude Code session, `/mem:recall how did I fix the ClickHouse
+auth error` answers from your own history.
 
 ## Documentation
 
 | | |
 |---|---|
-| [Tutorials](docs/README.md#tutorials) | your first house, joining a team's house, sharing memory |
-| [Guides](docs/README.md#guides) | install, update, invite, share, admin credentials, daemons, search, troubleshooting |
-| [Examples](examples/README.md) | runnable setups, from one machine up to a self-hosted team house |
-| [Release notes](docs/releases/) | what changed in each version, and how to upgrade |
-| [`AGENTS.md`](AGENTS.md) | installing memhouse as an agent, and working on this repository |
+| [Tutorials](https://unpkg.com/memhouse/docs/README.md) | your first house, joining a team's house, sharing memory |
+| [Guides](https://unpkg.com/memhouse/docs/README.md) | install, update, upgrade to 0.20, invite, share, admin credentials, daemons, search, claude.ai import, troubleshooting |
+| [Examples](https://unpkg.com/memhouse/examples/README.md) | runnable setups, from one machine up to a self-hosted team house |
+| [Release notes](https://unpkg.com/memhouse/docs/releases/) | what changed in each version, and how to upgrade |
+| [`AGENTS.md`](https://unpkg.com/memhouse/AGENTS.md) | installing and deploying memhouse, for an agent doing it for its principal |
+| `CONTRIBUTING.md` | working on this repository (in the repository, not in the npm package) |
 
 Any command's own usage: `memhouse <command> --help`. Every command works both ways:
 interactive for you, and `--yes` / flags / `--json` for an agent.
@@ -72,12 +84,22 @@ node bin/memhouse.js …
 npm test               # syntax gate + unit checks
 ```
 
-See [`AGENTS.md`](AGENTS.md) before your first change. Deeper reading:
-`memhouse/DESIGN.md` (the design and why), `memhouse/house/HOUSE.md` (layout and schema),
-`SECURITY.md` (what holds, and what does not).
+See `CONTRIBUTING.md` (repository) before your first change. Deeper reading:
+`memhouse/DESIGN.md` (the design and why; in the repository only), `memhouse/house/HOUSE.md`
+(layout and schema), `SECURITY.md` (what holds, and what does not).
+
+## License
+
+memhouse is licensed under the [Apache License 2.0](https://unpkg.com/memhouse/LICENSE): the CLI, the shipper, the
+dashboard, the tools and the docs alike. See [`NOTICE`](https://unpkg.com/memhouse/NOTICE).
 
-## Heritage and license
+**Relicensed from MIT to Apache-2.0 from 0.19.0 (the first release under it is 0.20.0); releases up to and including 0.18.11
+remain MIT** (the text is kept in
+[`LICENSES/memhouse-MIT-until-0.18.11.txt`](https://unpkg.com/memhouse/LICENSES/memhouse-MIT-until-0.18.11.txt)).
 
-Built on [agentlytics](https://github.com/f/agentlytics) by Fatih Kadir Akın (MIT). The
-adapters, dashboard and cost engine come from there, and this repository's history carries
-the full lineage. MIT.
+Built on [agentlytics](https://github.com/f/agentlytics) by Fatih Kadir Akın (MIT; see
+[`LICENSES/agentlytics-MIT.txt`](https://unpkg.com/memhouse/LICENSES/agentlytics-MIT.txt)). The adapters, dashboard
+and cost engine come from there, and this repository's history carries the full lineage.
+Model prices come from [models.dev](https://github.com/anomalyco/models.dev) (MIT). The
+built dashboard's bundled packages are listed with their licenses in
+`public/THIRD_PARTY_NOTICES.txt`.

package/SECURITY.md

@@ -28,6 +28,11 @@ makes the security model short, and worth stating without varnish.
   stores it empty; measured on 25.11).
 - **The dashboard binds loopback** (`127.0.0.1`) by default, and `deploy --local`
   binds the ClickHouse container to loopback too.
+- **The dashboard requires a per-user token** on every /api request, as a Bearer header: a
+  random secret in `$MEMHOUSE_HOME/dashboard-token`, mode 600 (a file other users can read is
+  refused). No cookie is set or accepted. `memhouse dashboard` first has the server on
+  `127.0.0.1` prove it holds the token, then opens the dashboard through a mode-600 page with the
+  token in the URL's fragment, never on a command line, and prints the token only to a terminal.
 - **Credentials are never printed.** The skills are under standing instruction not to
   echo the env file, and the API's responses and error bodies were checked for
   credential leakage under the acceptance suite.
@@ -35,10 +40,11 @@ makes the security model short, and worth stating without varnish.
 
 ## What you must know
 
-- **The dashboard has no authentication.** Loopback-only is the protection. If you
-  expose `MEMHOUSE_HOST=0.0.0.0`, anyone who can reach the port can read every
-  transcript in the house and run read-only SQL. Do not expose it; put a reverse proxy
-  with auth in front if you must.
+- **The dashboard's token is house access.** It opens every transcript in the house and the
+  read-only SQL console. The page keeps it for its browser tab only and sends it as a Bearer
+  header; no cookie is set. The dashboard serves plain HTTP and binds `127.0.0.1`: to use it
+  from another machine, forward the port over SSH (`ssh -L 4640:127.0.0.1:4640 <host>`) rather
+  than setting `MEMHOUSE_HOST=0.0.0.0`, which would send the token over the network unencrypted.
 - **`/api/query` is read-only by enforcement, within limits.** Writes and table
   functions (`url()`, `file()`, …) are refused server-side per request; resource use is
   capped per query. It is still full SQL over your own house — treat dashboard access
@@ -61,10 +67,17 @@ makes the security model short, and worth stating without varnish.
   and in a shared house the names are guessable anyway (`<member>_messages`), while
   `SHOW USERS` is granted to members deliberately so `/mem:house` can list who to share
   with. Treat membership as public and content as private.
+- **What a member can see of the other members.** Their user names and their table names, as
+  above. Not their grants: a member cannot read `system.grants`. Not their scoped shares (who
+  reads them, under which filter): a member holds no `SHOW ROW POLICIES`, so
+  `system.row_policies` is closed to it. It sees its own shares through memhouse's record
+  (`memhouse share --list`). Not their rows, except what they share with it. A member made
+  before 0.20 held `SHOW ROW POLICIES` until its admin runs `memhouse migrate --v3-shares`
+  ([release notes](docs/releases/v0.20.0.md#security)).
 
 ## Reporting
 
-The repository is private during beta. Report a security issue privately, never in a
-public issue or channel: once the repository is public, through GitHub's private
-vulnerability reporting (the **Security** tab, **Report a vulnerability**); until then,
-to the maintainer through the channel that gave you access.
+Report a security issue privately, never in a public issue or channel: by e-mail to
+**security@memhouse.io**. The repository is private during beta; once it is public, GitHub's
+private vulnerability reporting (the **Security** tab, **Report a vulnerability**) is a
+second route.