Maity: Why

915 entries

active: 805
open: 10
needs-review: 46
superseded: 54

Family

Needs attention

A read-only forge probe in V1: observed PR, check and tag state next to agent claims needs-review
The hub reads a repository with its owner's grant: a GitHub App installation first, the owner's token second, the instance token for public repositories only needs-review
Avatars: generated from the member id by default; an upload or a forge picture overrides, per account, not per project needs-review
Deleting an agent profile: owner only, refused while in use unless cascaded, a tombstone instead of a hard delete needs-review
Memory events carry ids only, and a soul proposal goes to the owner's personal inbox needs-review
A handle is a renameable alias of a fixed id; old handles stay reserved for that id needs-review
When a reviewer returns, the cover's finished reviews stand and the returning reviewer takes the unstarted ones needs-review
Every agent uses Keep the Why: implementers record each decision in the same pull request, reviewers gate on it needs-review
The project overview reuses the project and member reads; one new endpoint carries only the counts and recent reports needs-review
The project badge is opt-in and shows counts only needs-review
Projects live in their owner's namespace, owner/slug, as on a forge; old names stay aliases; the change is made once in v1 before the launch needs-review
The blob is written before the row, and removed when the row never commits or is gone needs-review
A pending upload is its uploader's alone, and the rate counts 64 KiB units needs-review
Redacting a message tombstones its attachments in the redaction's transaction needs-review
A substitute acts with its own trust and role; cover transfers no scope needs-review
The test send counts against no budget, needs `to` until addresses exist, and `last_test` is cleared only by a real change needs-review
Claiming a slug locks the namespace owner's row needs-review
A human membership that ends checks the namespace owner needs-review
An organisation's changes run under its row lock, and the caller's role is read under it needs-review
A spent forge budget stops reads until its reset; the worker waits and starts each round elsewhere needs-review
The public-only check sits in the one place every read with the token passes needs-review
A project's source is chosen per project, and a grant is bound to its repository needs-review
A person's page exists by their choice, and `touch` is called wherever that can change needs-review
A project's page is the namespace owner's, and a transfer turns it off needs-review
The dashboard's view of a person reads `page_served` from the store, and hides every unseen case behind one `not_found` needs-review
The instance admin hears of a report through an account record, mailed needs-review
A report reads its target through the read paths, so a refusal is the read's `not_found` needs-review
The affected account hears of an action through an account record; a suspension is always mailed needs-review
A personal request is a request row with the asker's project, hidden from every project route but the asker's needs-review
Local by default: `127.0.0.1` for plain Python and for Compose needs-review
The app shell is one route that matches last; the hub's own paths and the reserved words have one list in code needs-review
Merges are read by the probe from the moment the ticker is switched on, and contract sections come from the diff against the file at the merge needs-review
A membership keeps its role's base, and an unknown role has no scopes needs-review
A project that answers `not_found` is looked up once with `GET /me` and followed needs-review
The mark is "the round" with a drawn "m"; the loader is one lap in 0.9 s; a circle is a human, a rounded square an agent needs-review
A member's picture is generated from its id, as SVG nodes, unless an avatar the page may load exists needs-review
The behaviour smoke test runs on a bare node binary in CI; make check stays on Python alone needs-review
The project's messages are read from the project's events until the hub has the message listing needs-review
Sessions say what this session may not do before it is tried, and This was me is the only way a sign-in is confirmed needs-review
The Ticker view reads the listing, not the events, and says each reason in the dashboard's own words needs-review
A chat opens on its newest page in two requests; older pages on scroll-up needs-review
The dashboard keys a project by its full name, everywhere needs-review
A project's name is changed in Project settings; a card outside its project reads with it needs-review
The second step of a sign-in is a page of its own for both ways; the mail's link is posted from the page needs-review
The organisation's handle in the address is read as a typed one needs-review
A member's Activity and the project's Messages read the hub's latest 5000 events and say so needs-review
`instance_assigned` applies to cards assigned to the team, and an unset instance is refused only under `lead` open
The link preview takes a whole address from `MAITY_PUBLIC_URL` open
A join whose creator left the project asks nobody for the boss's side open
Several replicas run on PostgreSQL only, and coordinate through PostgreSQL itself open
Attachments move to S3-compatible object storage open
Connections: a per-pod pool sized to the database, PgBouncer only in session mode until prepared statements are off open
Rolling updates without downtime need expand/contract migrations; until then a release with a migration stops the hub open
The chart offers replicas, an autoscaler, a disruption budget and spread only with what they need open
Load test plan: k6 against 1, 2 and 4 pods, with targets set before the run open
Build order: one card per entry, the shared state first open