Quest Future Pioneers is the public brand on qfp.org. “Institute” language names a studio practice. It does not, by itself, prove a legal form, campus, or ministry licence.
core / QFP
A pioneer institute built around student quests.
QFP exists so STEM ambition becomes a build cycle: quest brief, prototype, test, demo, and a smaller next quest.
For partners
Five facts before a conversation.
Standing project-based STEM training is operating: quest briefs, prototypes, tests, and demos. This is not a trophy season. Cohort dates, fees, and room lists are confirmed after email.
Write a constraint. Build a cheap first object. Run a test that could embarrass it. Show a visitor the object and the trade-off that produced this version.
Evidence is a brief, a versioned object, a fail note, and a demo a visitor can handle. This site lists no awards, kit suppliers, or official partners.
Public inquiries: info@qfp.org. English welcome. Administration: admin@qfp.org. Do not send other people’s identifiers in the first mail.
Who hosts this studio
Quest Future Pioneers is the public brand on qfp.org. The one-line job is to prototype under a written constraint and show the trade-off. A partner should leave this page knowing that the practice is operating, that the assessed object is a handleable prototype plus a fail note, and that the public mailbox is info@qfp.org.
“Institute” names a studio method. It does not prove a legal registration, a workshop inventory, or a ministry licence. Owner confirmation on 2026-10-04 covers that programs operate and that the mailbox exists. It does not cover awards, kit lists, enrollment dates, or official partners, so those claims stay off this page.
QFP is not HNK’s explanation loop, not QKV’s rerunnable test, and not PQK’s field-friction inquiry. Those are related projects of the same institution, disclosed below. This studio starts from a constraint a student can build against this week.
What a quest looks like on the table
The work has to leave the notebook and become an object a visitor can handle. Write a one-page brief with a user, a constraint, and a demo promise. Build the first version from cheap materials. Run one test that could embarrass it. Photograph the miss. Then demo the object and the trade-off that produced this version, not a speech about the future.
- User, constraint, demo promise — on one page, visible during the session.
- Cheap first object before anyone orders impressive parts.
- A fail note the visitor can read without a presenter translating it.
- Named roles: builder, tester, demo lead. Spectating is not a role.
Tests, roles, sequel
If the object cannot fail, the team is still pitching. Mentors shrink scope; they do not steal the build. The forbidden move is changing the quest every day so nothing ships, or hiding failed builds so the table looks clean. After the demo, name a smaller, harder constraint. Do not declare the future solved.
Write info@qfp.org. Bring a constraint, not a world problem. Admissions stays at /admissions/.