Nakshatr AI · planned role
Help a team decide where to look next.
- Navigate the mission
- Offer progressively stronger hints
- Track attempts and evidence
- Surface an investigative next step
- Escalate when human judgment is needed
SYSTEMS LEARNINGBHAVNAGAR / INDIA
The programme · in design
Thirty missions. One unfamiliar system. Less guidance every day.
Nakshatr is designing one five-week journey in which teams of five work hands-on through a connected physical system, ending in a safe unfamiliar challenge with no supplied starting point.
- Teaching days
- 30
- Learning hours
- 90
- Weeks
- 5
- Missions
- 30
- Learners per team
- 5
These are programme design characteristics, not outcome statistics. Detailed mission engineering and the integrated implementation are under development.
01 · The progression
Two side wheels, then one, then a hand on the saddle, then nothing.
The thirty missions are built the way you learned to ride. Teams meet the whole machine, trace what connects it, bring systems alive, integrate them, diagnose behaviour, create autonomy, redesign — and finish with no starting point supplied. The road underneath never disappears: safety is the one support that is never removed.
- 01–05See the whole
The complete system and its connections are made visible.
- 06–14Build the subsystems
Prompts focus attention, but the team must connect cause and effect.
- 15–24Integrate and diagnose
Physical behaviour and recorded evidence determine the next move.
- 25–30Redesign and transfer
The team owns more of the route, ending with a safe unknown challenge.
02 · The complete mission map
Every day has a name. The route between them is the learning.
Open any mission to see where it sits in the progression. The eight phase groupings are only a reading aid — the thirty mission names and their order are the programme itself.
See the whole
Days 1–5
Power & propulsion
Days 6–10
Control & intelligence
Days 11–14
Build & integrate
Days 15–18
Fly & diagnose
Days 19–21
Autonomy
Days 22–24
Redesign
Days 25–28
Transfer
Days 29–30
03 · Inside each mission
A result is not enough. The team has to show how it knows.
The designed learning loop repeats across the programme. A successful output may begin the proof, but explanation, reproduction and transfer test whether capability belongs to the learner.
- 01Mission
- 02Action
- 03Observation
- 04Evidence
- 05Hypothesis
- 06Test
- 07Guidance
- 08Retry
- 09Accomplish
- 10Explain
- 11Reproduce
- 12Transfer
Competency is designed to progress from Not Yet to Assisted, Competent, Independent and finally Transfer. Attendance and team output do not establish individual competency by themselves.
04 · Guidance and judgment
The AI is designed to point to the evidence. A human retains the consequential call.
Nakshatr AI and the Student & Alumni App are separate products. Both are under development.
Programme status
Designed at the system level. Still being engineered and validated.
The first complete pilot has not run. The exact hardware, per-mission timing, evidence rules, safety gates, AI behavior and assessment details remain under development.