featkpr Private demo

Roadmap: what is done, what is next, and every idea on the table

The route runs solid through what has shipped, stops at an open node on this week, and runs dashed through what is decided. Ideas that are not decided are listed on their own, with who raised them.

shipped, datedin progress nowdecided, not startedidea, not decided

The project starts

Specification written

the test plan and 48 packages

The first build runs in production

all 26 automated packages merged

The first map, and a name

BookStack's features named for $0.99 · 12 screens live · featkpr

Sign-in and a second product

Shlink added beside BookStack

The crawl sends forms

167 screens · 28 goals drafted

The first test runs, proven

304 of 304 pass · 269 refused to the wrong user · the Runs page · the from-zero audit

Decisions and a timeline

model experiment done for $1.10 · branching v2 agreed

Week 0 · from 28 Sep

Branching explained as a diagram · done early, 27 Sep
A crawl that edits and deletes what it made · released as a draft after approval
The goal ledger · a goal's identity and 3 kinds of event

Week 1 · from 5 Oct

Effects in every run · mail, off-host calls, downloads, rows
Zero-code OpenTelemetry · on the test product
Complexity, drafted by featkpr · no owner ranking
Which model drafts goals · done early, 27 Sep, $1.10

Week 2 · from 12 Oct

Release flow and a Kargo plan · where a goal counts as proven
Goals from the code · the analyser writes their facets
Queue, mirror and /ops · stays up through forge outages

Weeks 3–4 · from 19 Oct

Goals view · design pass first
Whole-system tracing during runs · every state change
Your product's own telemetry · any stack
Merge-request verdict, end to end
Product three, and the public demo
Viewer and guest journeys · 92 of them, once Flows filters by role

After the timeline · the MVP stage

featkpr on featkpr · it reads, crawls and tests itself
GitHub-hosted products
InvenTree, Immich, Formbricks · the next three in the library
Connect a codebase · a form instead of a folder
Node and Python readers · Uptime Kuma first
Recall measured by a judge · at least 0.9
TypeScript test output
Owners on features

Production stage

Teams and tenancy
The extractor in your own CI
Selenium and Cucumber outputs
The first team on it

Later, researched

Fakes for SSO, LDAP and webhooks
Fault injection
Reading GrowthBook, PostHog and Sentry · what owners already run
Load tests with k6
Structure mining

Ideas raised, not decided

A demo environment per feature or feature set

with a read-only demo link for clients and leads; half of it runs today

Tim · 27 Sep
A private read-only demo

for friends and potential clients, once the value is visible; the public demo is dated weeks 3–4

Tim · 27 Sep
Several models verify each draft

votes, not a single model; a verify experiment is running

Tim · 27 Sep
Questions as a floating dot

quick decisions in a corner instead of a screen

Tim · 26 Sep
Flows at every scale

a conversation beside a canvas that draws what you are talking about

Tim · 25 Sep
A product wiki and a flags hub

what the product does and what is switched on

Tim · 22 Sep
A features hub from every source

code, docs, release notes and feedback, not only code

Tim · 22 Sep
Findings filed with maintainers

discovery, approval, then a post under Tim's name; nothing filed yet

Tim · 22 Sep
A guide to your product, from the map

steps with screens, who can, where it fails

Tim · 21 Sep
A read-only server for agents

the map as an MCP server

the first site design · 22 Sep
Process mining on real traces

once real traces exist

branching v2 · 27 Sep
A phone crawl lane

after a phone crawl exists

branching v2 · 27 Sep
Pricing

one seat price with a credit limit and top-up is decided; no number yet

decided · PK

An idea of your own? Tell us in the demo form →