Stage 01 / 10
Request
A customer describes the need
The request arrives on the public board with acceptance criteria and urgency, and gets its permanent CHERT-REQ number.
Powered by
Open-source training & venture platform
CHERT Think Tank turns real demand for software into training, and trained builders into founders. Claim a request, build it in a browser workspace, test it on a real Android or iPhone, ship it through review — and every delivery becomes the next cohort’s curriculum.
Three ways in
Customers bring real needs. Students turn them into skills. Founders turn skills into companies. One platform carries all three.
Describe it. It is classified, scored and routed — to maintainers when it must be production-grade, to students when it is a good thing to learn on.
Claim a real request, get a workspace in one click, ship a pull request and have a mentor review it. Not exercises — the actual backlog.
Build a startup on contributed skill instead of capital. The Inpower ledger records every contribution, and shares follow the work.
The request lifecycle
Ten recorded stages. Every one is an event with an actor, a time and a reason. Select a stage to see what happens — and which parts of CHERT make it work.
Stage 01 / 10
A customer describes the need
The request arrives on the public board with acceptance criteria and urgency, and gets its permanent CHERT-REQ number.
Powered by
Stage 02 / 10
Classified and scored for teaching value
The Board sets the track, a difficulty tier from 1 to 5 and the skills involved, and scores how much a student would learn from it.
Powered by
Stage 03 / 10
Production or student track
Work that must be production-grade goes to maintainers; work that is good to learn on goes to students, gated by tier.
Powered by
Stage 04 / 10
A student takes it; a workspace spawns
One click creates the record's branch and a sealed browser workspace with the repository cloned and the toolchain ready.
Powered by
Stage 05 / 10
Code, design and media
The student builds in VS Code with Flutter, Layla and Claude Code at hand, and designs or edits assets in the creative engines.
Powered by
Stage 06 / 10
Real Android and iPhone, from the browser
From the editor: run integration tests on the iOS simulator, launch the app with hot reload, or install it on the Android emulator.
Powered by
Stage 07 / 10
A mentor reads the pull request
The pull request opens on the Tank; CI posts its result; the mentor reviews and can join the live workspace to help.
Powered by
Stage 08 / 10
The customer gets what they asked for
The change is merged, tagged and released; the customer is notified on their original request.
Powered by
Stage 09 / 10
The work becomes training
The workspace, criteria and feedback are frozen into a scenario. Every shipped request teaches the next cohort — automatically.
Powered by
Stage 10 / 10
A badge, and points on the ledger
The student earns a verifiable badge. In a startup record, the task's points land on the Inpower ledger, where shares follow the work.
Powered by
Interactive architecture
Select any component to learn what it does, or play a user journey and watch a request move through the platform.
Real requests from real customers, and the people who turn them into work.
Where the work is actually done — code, design and media, in the browser.
Every change runs on real devices and real pipelines before it reaches a customer.
Shipped work becomes curriculum; contribution becomes ownership.
One sign-in, sealed workspaces, nothing shared by accident.
Assistants inside the editor, and a platform that checks itself.
Details appear in the panel above the diagram.
One platform, many engines
Each engine does one job well. One sign-in carries you across all of them.
VS Code in the browser
A pre-seeded workspace per claimed request: Flutter, Dart, Android SDK, Layla and Claude Code, with one-click tests on real devices.
think.cherttt.comSource control & CI
Repositories, issues, pull requests, reviews and Actions — bilingual, light and dark, on the platform's own servers.
tank.cherttt.comA real phone in the browser
Boots on the platform's mobile node and streams to you; install your build and use it by touch.
A live iPhone, no Mac needed
Integration tests, Run with hot reload and the Flutter debugger, on the platform's own macOS machine.
Collaborative design
Interface and product design together in the browser, saved into the record.
design.cherttt.comImage generation
Generated art on the platform's GPU node, with an expert layer for deeper pipelines.
art.cherttt.comBrowser image editing
Fast raster editing that saves straight into the record's media folder.
paint.cherttt.comCustomer intake
A public board where customers post needs, vote, and follow status to delivery.
requests.cherttt.comThe equity ledger
Contribution becomes ownership on an append-only, event-sourced record; shares are derived, never typed.
Inside the platform
Not mock-ups: captured from the live Think Tank, in both languages and both themes.
Why CHERT Think Tank
Students learn on the live backlog of real customers, reviewed by mentors and delivered for real.
Shipped requests are frozen into scenarios automatically — the curriculum grows with every customer.
Equity is derived from an append-only history: every point traces to a task, a time and an approver.
The whole platform runs on its own servers — forge, editors, devices, AI models and backups. No third-party cloud.
Every engine speaks both languages, with proper Arabic typography and right-to-left layouts where they belong.
Editor, forge, Android and iPhone all run in the browser — a laptop, or a tablet, is enough.
Create an account — CHERT reviews it and activates the right role: customer, student, mentor or founder.