Add Running Indexterity, carrying what the README used to
PostgreSQL is the third shipped engine: adapter mapping, capabilities and §9.4
Home says both engines; the connecting page's title matches its contents
Take the reference material the README was carrying
The README had grown to 935 lines by explaining everything twice: most of its
prose restated Architecture at length, and the parts that did not — the policy
knobs, the observe-window table, the score, the plans — had no wiki home at all.
New page, Plans and policy: the seven per-cluster knobs, how the observe window
is chosen per index at hide time, the five-minute health probe, how the change
window picks itself, the score weights, and the plan entitlements with the
billing reasoning behind them.
Connecting a cluster gains the version floor, which members of a replica set are
read (and why passives count and hidden members cannot), and what a
mongodb+srv:// string carries outside its own text.
Architecture: 7.5 gains the severity tiers, measured in documents walked rather
than table size, and the hourly workload cadence. 11.2 gains the cadence
ceiling — latency_samples run-lengths nothing, so it, and not storage, is what
bounds how often we collect. It still said 6h in places.
Link the repo by HEAD, not by branch name
blob/main hard-codes a branch name in a page nobody would think to update if it
ever changed. HEAD follows the default branch.
Move the prose docs out of the repo
Architecture and Connecting a cluster were docs/architecture.md and
docs/mongo-user.md. The decision log stays in the repository (docs/decisions.md)
so a decision is reviewed in the same pull request as the change that makes it.
Home says what is deliberately not here and why, so the split is discoverable
from either side.