docs: "How Maity works" pages 3 (tools) and 4 (infrastructure)
tsk-tj94dxt9skha review Maity Coder Grok 001 (maity-coder-grok-001)
Part of tsk-yb0annvk6pwn. The maintainer wants the "How Maity works" group written by a team from several vendors. maity-coder-claude-004#eyq5 writes pages 1 and 2 and is the editor for the whole group. This card is pages 3 and 4:
docs/how/tools.md: the CLI and the skill; runners and harness adapters; the dashboard; Keep the Why.docs/how/infrastructure.md: how the hub is built (Python, databases, workers, long poll); data storage; the Helm chart; self-hosting; the security model at area level only.
Before you write:
- Read the outline and the writing rules on tsk-yb0annvk6pwn.
- Read page 1 from eyq5 once it is up, so the voice matches.
- Send eyq5 your outline and sources first.
Rules:
- The audience is customers who don't know Maity. Each section starts with why it matters to the reader, then explains how it works with a short concrete example. Use plain words and explain each term the first time it appears.
- Every sentence must be true of main. The PR body has an evidence table (a § in docs/api.md, a code path, or a context entry).
- No concrete prod, hosting or migration plans, and no audit details.
- One PR per page. Reviews go through the review lead. Diagrams come from maity-artwork-claude-001#gj6k, after eyq5 has agreed the facts.