featkpr
Private demo

What featkpr asks a person, and what happens if nobody answers.

Some things the code cannot decide: who should see a page after an upgrade, whether a flow is real. featkpr asks the owner, one question at a time, and applies a safe default meanwhile, so doing nothing is an answer too.

Ask for a private demoArea 3 of 5 · all five areas

featkpr's app, shot 27 Sep 2026 · the screens show BookStack pull request #6108 on sample data

Screens of featkpr's app run on sample data, so the numbers inside them are examples, not BookStack's. A screen marked "recorded from BookStack" replays featkpr's own records of BookStack's run of 26 Sep.

One question, and who sees what under each answer #

Home opens on what waits for you. Each card asks one question in words, over the real screen it is about, and draws who keeps access under each answer. The default is in force until someone chooses.

Home/homesample data

A question card: #6108 in the Permissions module, BookStack's Page Revisions screen with the heading outlined, the question Public keeps revisions by default, keep that, two frames of roles under Keep and Remove from Public with an eye per role, the default in force, and the buttons Keep, Remove from Public and Ask engineer. Open the whole screen
  1. Where it comes from: the pull request, the module, and who owns it.
  2. The real screen the question is about, the part outlined.
  3. The question, in words.
  4. Who sees revisions under each answer: an eye per role.
  5. The default, already in force.
  6. Keep it, change it, or hand it to an engineer.
  1. Nobody answersThe default stays in force, and the card stays open on Home.
  2. Someone answersThe answer replaces the default and is recorded with who and when.
  3. The answer changes laterThe new answer supersedes the old one; the old one is kept.

149 flows waiting on a person's verdict BookStack · read from the app on 28 Sep 2026

Every answer is kept, never overwritten #

The Questions screen ranks every open card by what it exposes, then keeps the history: what was answered, by whom, and which answer replaced which.

Questions/questionssample data

The Questions history: three rows dated 18 Sep 2026, a rename, a correct that supersedes an earlier answer, and an approve struck through as superseded. Open the whole screen
  1. The newest first: a feature renamed.
  2. An answer corrected: it names the answer it supersedes.
  3. The first answer, struck through but still there.

Who answers for what, and what the models may spend #

Settings wires each owner to the modules they answer for, so a question reaches the right person. It also caps every paid model call: each line has a monthly ceiling and stops before it.

Settings/settingssample data

The Settings screen: an owner wired to the Entities module, then eight paid model lines (naming, drafting goals, votes, drafting tests), each with a bar against its monthly ceiling and an amber tick at 80 percent. Open the whole screen
  1. An owner, wired to the modules they answer for.
  2. Every paid model line, by what it does.
  3. Spend against the month's ceiling; the amber tick is where the line stops, at 80%.

Today an owner opens the app from a signed link; Settings lists who opened each one and when.

See the questions featkpr would ask about your product #

A live walkthrough on BookStack's questions, and which ones your roles would raise.

Ask for a private demo

Open original

↑ ↓ to move, Enter to open, Esc to close