// play · two minutes · no sign-up

Navigate your first qutub.

Pick a goal. Complete steps by attaching proof. The dial runs the same readiness formula as the product — claims earn 0.4, documents earn full credit, and the needle always points at the step worth most right now.

// mission

Give every serious goal
an honest instrument.

Know where you are. Know what is next. Prove you are moving forward. Qutub exists so that the decisions that shape a life are navigated with the same rigour the systems judging you already use.

01

The problem

Your most important life decisions — a promotion, a visa, an admission, a company — are managed in scattered notes, spreadsheets, and memory. Companies use systems to evaluate you. Almost no one has a system to navigate them.

02

What we believe

Life is navigable. Most people drift. Qutub gives them instruments.
Progress must be visible. If it is not tracked, it disappears — and cannot compound.
Effort without structure is wasted. Qutub turns chaos into systems.
Big goals are structured quests. Career, fitness, immigration, startups: the same mechanics, different domains.
Evidence beats memory. What is not recorded does not exist in the system.

03

Our commitments

No credit without proof

A finished step earns full credit only when proof is attached. A claim earns 0.4. No proof earns 0.25.

The cap lives in code

Grounding gates, tier weights, and the needle are deterministic. A model may annotate — it never decides.

Scores can fall

An honest instrument reports bad weather — calmly, with what recovers the bearing.

Calm, not a casino

No streaks-as-threats, no loot boxes, no confetti. A quiet glimmer on the star when a milestone lands.

04

What Qutub will never be

A motivational guru no “crush your goals” energy
A productivity hack not about doing more — about doing what matters
A social network no feeds, likes, or followers
A casino no streak anxiety or variable-reward traps

05

How we build

The vision is everything that matters in a life. The product ships one quest at a time — seven modules — plus any you name — over one engine, each a lens on the same model: Goal → Milestones → Steps → Evidence → Readiness.

Play your first qutub Read the lore

// lore

The sky turns.
One star holds still.

For as long as people have crossed deserts and seas, they have steered by the one point of the sky that does not move. This is the story of that star, the instrument that finds it, and the needle that knows the moment.

I

The Star — قطب شمالی

Qutub · Arabic qutb · Persian qotb · Urdu Qutub — the pole, the axis, the pivot

In Urdu, the North Star is Qutub-e-Shumali: the pole of the north. While the whole sky wheels through the night, it alone stays fixed. Arab astronomers charting the desert crossings, Persian caravans, Mughal pilots on the Indus — all of them navigated by it.

In Qutub, the star is your ideal self: the outcome you are steering toward. Fixed, defined, non-negotiable — the point everything else orients by.
II

The Instrument — قطب نما

Qutub Numa · Urdu — “that which shows the pole”

The Urdu word for a compass is Qutub Numa. The name is the product description: an instrument whose only job is to show you the pole, wherever you stand.

Open Qutub and you do not see a task list. You see the dial — every module of your life a constellation in one sky, and a needle that already knows where to point.
III

The Needle — καιρός

Kairos · Greek — the opportune moment

The Greeks had two words for time: chronos, the clock, and kairos, the right moment. The needle is the Kairos Pointer. It does not wander. It points at the single next step that brings you closest to your star — chosen by arithmetic, never by mood.
IV

The Tower

Qutub Minar · Delhi

The Qutub Minar has pointed at the sky over Delhi since the twelfth century — a tower seen from afar, marking a world of Arabic astronomy, Persian poetry, and the Urdu of the Mughal age. The compass needle in our mark carries its taper.
V

The Register

Words the system keeps close

رحلة Rihla
The journey — the travel chronicle of Ibn Battuta.

سیمرغ Simorgh
The bird the thirty birds set out to find — and found they were. The ideal-self myth.

ستارہ Sitara
Star — the poetic vocabulary of Iqbal.

سفرنامہ Safarnama
A travel chronicle — the evidence you leave along the way.

راهنما Rāhnamā
The way-shower — a guide who knows the road.
VI

The Names Before

StarForge → JourneyOS → Polaris → Qutub

The system began as StarForge, a career tracker. It became JourneyOS when one domain became many, and passed briefly through Polaris — the Latin name for the pole star. It settled on the older name for the same star: Qutub.

ستاروں سے آگے جہاں اور بھی ہیں

“Beyond the stars, there are yet more worlds.” — Iqbal

Find your star Our mission

// status

Shipped. Measured.
Shipping.

Every milestone that landed is telemetry — and the needle is already pointed at what comes next.

0milestones shipped

0phases complete

0post-roadmap PRs

0tests green

Backend & Data

✓NestJS API on :4000 with global `api/v1` prefix
✓Prisma + PostgreSQL schema, migrations, seeds
✓JWT auth, qutubs / milestones / steps CRUD
✓Evidence vault with S3 / MinIO storage
✓Activity log on every mutation

Engine & Pipeline

✓6-stage pipeline (normalize → artifact)
✓BullMQ workers, Redis queue, parallel batch
✓Readiness scoring (structure × 0.5 + eval × 0.5)
✓Pipeline integrity checkers, dedup, repair
✓Cron-scheduled health diagnostics

Interfaces

✓Next.js web — Compass, qutub detail, inline proof
✓Pipeline Monitor with live status
✓`qutub` CLI — headless auth, module subcommands
✓AI Operating Surface (modes / configs / playbooks)
✓Docker Compose deploy + integration tests

Per-module wiring · Phase 3

✓Per-module scanners with module-tagged registry
✓Mode overrides + scoring dimensions per module
✓YAML milestone templates & evidence subtypes
✓`qutub <module>` CLI subcommands
✓`/modules/<m>` web dashboards with cross-links

Orchestration & capacity · Phase 4

✓Cross-qutub scheduler with priority + capacity weighting
✓Capacity prefs UI — weekly hours, peak / quiet windows
✓Best-effort plan regeneration on qutub or capacity edits
✓`/orchestration/plan/{today,week}` allocation endpoints
✓Conflict detection across overlapping step windows

TUI & visualizations · Phase 4

✓`qutub tui` — Ink + React 19 dashboard with j/k/r/q keys
✓Auto-fallback to static frame when stdout is non-TTY
✓QutubTimeline — D3 horizontal bars across time scale
✓ReadinessHeatmap — qutubs × dimensions colour grid
✓CapacityBurndown — planned vs actual cumulative hours

Portability & reach · Phase 4

✓Mode-files run on claude-code, opencode, and codex unmodified
✓YAML frontmatter contract — `name` + `description` universal
✓`pnpm lint:modes` validator catches missing host metadata
✓UI in English + Spanish via next-intl, cookie-based selection
✓Pipeline localizes generated plans + artifacts per user locale

Outcome prediction · Phase 5

✓Three-tier basis: baseline → historical → llm-refined
✓Per-milestone success probability + ETA range
✓Velocity from real timestamps; deadline-aware penalties
✓LLM blends with heuristic — neither alone, both averaged
✓Doctor surfaces predictor + LLM-refinement error rates

Auto-generated drafts · Phase 5

✓Scanner signals → match-score gate → predictor → QutubDraft inbox
✓Filter Principle: below threshold the system suppresses, not surfaces
✓Accept atomically promotes to a real qutub + seeded milestones
✓Reject records reason — used by future filtering
✓Web inbox + `qutub drafts {list,show,accept,reject,generate}`

Proactive re-planning · Phase 5

✓Deadline shift triggers a propose-and-confirm PlanRevision
✓Compute-without-persist preview — reject is a true no-op
✓Material-change threshold (≥1h) suppresses sub-hour drift
✓Day-by-day diff: added / removed / changed / steady
✓Web revisions inbox + `qutub revisions {accept,reject,show}`

Calibration & privacy · Phase 5

✓Brier score + 10-decile calibration curve (web admin view)
✓Predictions snapshotted; outcomes recorded on terminal state
✓`qutub export` — versioned JSON, round-trippable into a fresh DB
✓`qutub delete-account` — S3 wipe + cascade + SHA-256 audit row
✓Per-user only; no cross-user training; full data export contract

Honest CI · post-roadmap

✓e2e suite TCP-probes Postgres at module load
✓describe.skipIf cleanly skips 32 tests when DB unreachable
✓Green CI by default + visible skip count, not red with 31 expected failures
✓Re-enable with `pnpm docker:up` — full suite runs automatically
✓Resolved the Phase 3-5 retro callout with zero new dependencies

Predictor recalibration · post-roadmap

✓Per-user Platt sigmoid fitted from accumulated OutcomeRecord rows
✓Centered on 0.5 — identity model maps midpoint to itself
✓Refuses below 10 samples; falls back to identity if Brier worsens
✓Predictor applies calibrator in O(1) before returning
✓`qutub calibration {show, model, refit}`

Scope-limited share tokens · post-roadmap

✓Mint a single-use token for one qutub, hashed at rest
✓256-bit base64url entropy, 1h–7d TTL, default 24h
✓Recipient redeems via unauthenticated URL — token IS the auth
✓Marked used BEFORE envelope build — single-use is the contract
✓`qutub share {create, list, revoke}` + revokable from API

// philosophy

Eight truths.
One compass.

The beliefs underneath the instrument — navigation over motivation, evidence over memory.

Most people drift.

Career. Immigration. Fitness. Startups. Life's biggest moments happen without a map, without evidence, without readiness.

Qutub turns drift into navigation. Invisible work into visible proof. Wishes into readiness.

Signal appears when structure and evidence align.

Without structure

✗ Goal, but no milestones
✗ Effort, but no evidence
✗ Progress, but invisible
✗ Work, but no proof
✗ Busy, but unmeasurable

With Qutub

✓ Goal → Milestones → Steps
✓ Every step backed by evidence
✓ Progress is visible, compounding
✓ Readiness is computed, clear
✓ Navigate with precision

The problem

Life's most important qutubs—career, fitness, immigration, education—share a common struggle.

○

People drift

Without a clear map, effort scatters. You work hard but lack direction. Months pass without knowing if you're moving toward your goal or just staying busy.

○

Progress disappears

Achievements live in memory, emails, and browser history. Nothing compounds because nothing is captured. What isn't recorded doesn't exist in the system.

○

Goals stay fuzzy

"Get better at X" feels good but means nothing. Without structure, you can't distinguish motion from progress. You can't measure readiness.

○

Effort doesn't compound

Each action exists in isolation. No system connects them into a coherent narrative. Your work becomes invisible to yourself—and to others.

What we believe

Qutub is built on a few irreducible truths.

1

Life is not random—it is navigable

Most people feel like passengers. Qutub treats you as the pilot. Your goal is navigable; you just need instruments. The right structure lets you see where you are, where you're going, and what's next.

2

Progress must be visible

What isn't tracked disappears. If it disappears, it cannot compound. Qutub makes progress visible—to yourself, to others, to systems. Visibility enables agency.

3

Effort without structure is wasted

You are already working hard. Qutub doesn't ask you to work harder; it asks you to work structured. It turns chaos into systems, fragments into narratives.

4

Big goals are structured qutubs

Career. Fitness. Immigration. Startups. Education. Apprenticeships. These look different on the surface, but they're all the same shape: a goal, broken into milestones, executed through steps, backed by evidence. One engine, seven lenses — and any you name yourself.

5

Evidence beats memory

Your memory of your progress is unreliable. But your evidence is not. Qutub runs on evidence: documents, artifacts, proof. What is not recorded does not exist in the system.

How Qutub answers

We solve the problem with three principles.

1

Structure

Every qutub breaks into goals → milestones → steps → evidence. This isn't busywork; it's the shape of all big accomplishment. Qutub provides the frame, you fill in the content.

Goal: Land a promotion
├ Milestone: Master skill X
│ ├ Step: Complete course
│ │ ├ Evidence: Certificate
│ └ Step: Ship project
│ │ ├ Evidence: Deployed code

2

Evidence

Don't tell the story; show it. Every step is backed by evidence—documents, code, artifacts, proof. Evidence makes progress real, trackable, and credible. It's what you show yourself (motivation), and what you show others (proof).

Evidence = documents + artifacts
+ certificates + code
+ credentials + outcomes

3

Readiness

Not "am I working hard?" but "am I ready?" Qutub computes readiness from structure and evidence. Know exactly what's missing, what's ready, and what's next. Turn uncertainty into a dashboard.

Readiness = Structure (50%)
+ Evidence (50%)
= Your true north

Why this matters

For you

Know where you are at any moment
See what's next, clearly
Prove your progress to yourself (motivation)
Compound effort across time
Stop drifting; start navigating

For others

Show your readiness, not your wishes
Prove your qualifications with evidence
Make your story coherent and credible
Turn invisible work into visible proof
Share your qutub; earn trust

Qutub is not about doing more. It's about knowing where you are, knowing what's next, and proving you're moving forward.

See the walkthrough Explore Qutub

The Name

Why this system is called Qutub — and what the word has always meant.

قطب

Qutub · koo-TOOB · noun

the pole, the pivot, the fixed point

Arabic qutb · Persian qotb · Urdu Qutub

✦

The star that holds still

In Urdu, the North Star is Qutub-e-Shumali — the pole of the north. It is the one point of the sky that does not move while everything turns around it. Desert crossings, Persian caravans, pilots on the Indus: everyone steered by it. Your ideal self is your Qutub — fixed, non-negotiable, the point everything orients by.

✧

The instrument: Qutub Numa

The compass, in Urdu, is Qutub Numa — "that which shows the pole." That is this product, exactly. The needle is the Kairos Pointer: it does not wander. It points at the single next step that brings you closest to your Qutub.

◈

The Minar

The Qutub Minar has pointed at the sky over Delhi since the twelfth century — a tower seen from afar, marking a civilisation of Arabic astronomy, Persian poetry, and the Urdu of the Mughal world. Our compass needle carries its taper.

☾

A note of respect

In Sufi tradition, the Qutub is the axial saint of the age. We use the word in its everyday, astronomical sense — the pole star. The resonance is respected, not invoked.

ستاروں سے آگے جہاں اور بھی ہیں

"Beyond the stars, there are yet more worlds." — Iqbal

// the universal abstraction

Everything is a Qutub.

One model powers every module. The same engine that runs a career transition runs an immigration filing or a marathon training cycle.

Goal

The destination — a measurable outcome state.

Milestones

Major checkpoints — phase transitions on the path.

Steps

Atomic, executable actions you can ship today.

Evidence

Proof artifacts & metrics — what the system trusts.

Readiness

Computed signal — where you stand, right now.

// the model

One model.
Every domain.

The same engine powers every high-stakes qutub — career, fitness, immigration, education, startups, certifications, apprenticeships. Every one climbs the same ladder.

What is structure?

Every big goal shares the same architecture. Qutub makes it explicit.

Goal

The north star. Where you're navigating toward. Not vague ("get better at X") but specific ("Land a promotion to Principal Engineer by Q3 2026"). This is your primary objective.

Milestones

The major waypoints. If your goal is "Land a promotion," milestones might be "Master distributed systems," "Lead a team," "Deliver high-visibility project." Each is a big enough task to require steps.

Steps

Concrete, executable actions. Under "Master distributed systems," steps might be "Complete course," "Read papers," "Build a system," "Review PRs." Each step is something you can do in days or weeks.

Evidence

Proof that you did the step. Course certificate. Papers you read. Deployed code. PR reviews. Documents you wrote. Evidence is what makes progress real, visible, and credible. It's the foundation of readiness.

How readiness is computed

Qutub turns structure and evidence into a single, actionable number.


            readiness_score = 

              structure_score × 0.5 

              + evidence_score × 0.5

Structure

Evidence

Structure Score (50%)

How complete is your roadmap? Do you have goals, milestones, and steps defined? This measures your readiness to execute.

Example: 75% of structure defined

Evidence Score (50%)

How much have you proven? What artifacts back your progress? This measures your actual advancement toward the goal.

Example: 60% evidence collected

Readiness isn't "how hard are you working?" It's "are you prepared?" It combines both your planning and your proof into a single metric you can track and improve.

Try the model

Interactive demo: Click through a real qutub from goal to readiness.

Ready to navigate?

The model is the same across all domains. Pick your qutub and start building structure.

Explore modules See how it works Play a qutub

// modules — seven lenses, one engine

Same engine. Different domains.

Each module is a specialized lens over the Qutub Engine — never a separate product. Hover any card to see the actual scoring dimensions.

Qutub: Career

Career

Job searches, role transitions, promotion readiness, performance evidence.

Scoring dimensions

Role fit0.25
Skill match0.20
Risk factors0.15
Growth potential0.15
Compensation0.15
Culture fit0.10

Qutub: Admissions

Admissions

University & program applications — deadlines, SOPs, tests, recommendations.

Scoring dimensions

Academic profile0.30
Test scores0.20
SOP quality0.20
Recommendations0.15
Research fit0.10
Application completeness0.05

Qutub: Immigration

Immigration

Visa pathways, document tracking, submission pipelines, compliance.

Scoring dimensions

Eligibility profile0.30
Document completeness0.25
Evidence strength0.20
Timeline alignment0.15
Risk indicators0.10

Qutub: Fitness

Fitness

Physical transformation — periodized programming, metrics, recovery.

Scoring dimensions

Adherence rate0.30
Progressive overload0.20
Body composition trend0.20
Recovery quality0.15
Performance markers0.15

Qutub: Startup

Startup

Idea-to-traction — validation, MVP velocity, growth, investor readiness.

Scoring dimensions

Problem-solution fit0.25
Traction signals0.25
Team strength0.20
Market opportunity0.15
Capital efficiency0.15

Qutub: Certifications

Certifications

Exam prep — study cadence, practice tracking, readiness modeling.

Scoring dimensions

Practice test trend0.30
Domain coverage0.25
Spaced repetition0.20
Hands-on labs0.15
Test-day readiness0.10

Qutub: Apprenticeship

Apprenticeship

Mission spirals — build, deploy, journal, prove readiness under mentor review.

Scoring dimensions

Mission completion0.30
Evidence quality0.25
Review outcomes0.20
Journal consistency0.15
Production readiness0.10

Qutub: Your Own

Custom

Name your own module — learn a language, buy a home, write a book. General milestones, the same engine, the same honesty.

Scoring dimensions

Capability0.25
Progress0.25
Outcome clarity0.20
Constraints0.15
Risk factors0.15

// modules

Seven qutub types — and yours. One engine.

Different domains, identical mechanics. Each a constellation in one sky.

📈

Career

Navigate promotions, skill mastery, and job transitions with clear structure.

The same structure, every time

Different domains. Identical model. Here's how it works across all seven:

🎯 Goal

Career: Become a Principal Engineer
Fitness: Run a sub-2-hour marathon
Immigration: Secure permanent residency
Education: Complete master's degree
Startups: Launch product and reach $10K MRR
Certifications: Earn AWS Solutions Architect certificate
Apprenticeship: Complete four mission spirals with portfolio-grade evidence

🗺️ Milestones

Break goal into 3-5 major checkpoints. Each is a phase of work: foundation, depth, proof, execution.

⚙️ Steps

Concrete actions that can be completed in days or weeks. Execute and collect evidence.

Evidence

Artifacts proving completion. Certificates, code, documents, credentials, photos, metrics. What makes progress real and visible.

Why one model works

🎯

Universal shape

Every big goal naturally breaks into goals, milestones, steps, and evidence. This isn't a Qutub invention—it's how humans actually accomplish things. We just made it explicit.

🧠

Cognitive clarity

One model means one way of thinking. You switch between domains without relearning the system. You take what you learn in career and apply it to fitness.

🔄

Composability

One engine means you can run multiple qutubs at once. Career and fitness. Immigration and education. One dashboard. One source of truth.

⚡

Scaling the product

One model scales. New domains don't require new systems—just new scanners, new templates, new evidence types. The engine stays constant.

Ready to structure your qutub?

Pick your domain and start building. The model is the same. Only the context changes.

Understand the model See the qutub flow Play a qutub

Qutub walkthrough

From intention to evidence-backed readiness.

Qutub gives every high-stakes goal the same reliable operating loop: define, structure, execute, verify, adapt.

0 Core steps

0 Structure weight

0 Evidence weight

Qutub signal Building → Ready

Step-by-step flow

Walk through the exact loop Qutub runs in every domain.

What changes after this loop

You stop reacting and start steering with explicit signals.

🛰️

Clear instrumentation

You can point to exactly what is done, what is missing, and why readiness moved.

🧱

Compounding structure

Each milestone and evidence artifact makes future planning faster and more accurate.

🧾

Shareable proof

You can export coherent progress instead of reconstructing your story from memory.

Ready to run your first loop?

Open the model for scoring logic, or jump into modules to pick your domain lens.

Open the model Choose a module

// pipeline

Every verdict,
capped by proof.

Six stages turn raw input into outcome. The gold node is the grounding gate — no score certifies beyond your evidence.

01

Input Normalizer AI

URL · text · document → structured payload

●

02

Classifier AI

Detect domain · archetype · qutub type

●

03

Gap Analyzer AI

Current state ↔ required state

●

04

Scorer AI

Weighted dimensions → readiness signal

●

05

Plan Generator AI

Action roadmap · milestone breakdown

●

06

Artifact Creator AI

Report · checklist · draft · plan

●

report.md

artifacts/

tracker entry

readiness%

~/qutub — zsh

$ qutub pointer
  ✦ Collect two peer recommendations
    career · Δ0.080 · ×1.79 · fit 1 — closes its milestone
  considered 3 · deterministic — no model chose this
$ qutub evidence search "migration"
  · Case study — zero-downtime migration [verified] 0.91
$ qutub embed create career-481
  ✦ widget live — revoke anytime, PII-free

// cli

The compass in your terminal.

// operating surface

Steer the system
in YAML.

Modes are markdown, scoring is config, the needle is deterministic. Retune the engine — no rebuild, no deploy.

config/scoring/career.yml

thresholds:
  not_ready: 0.40
  building:   0.60
evidenceTierWeights:
  verified:   1.0
  documented: 1.0
  claimed:    0.4
  reference:  0.0
grounding:
  minEvidenceDensity: 0.5
unprovenCredit: 0.25

config/scoring/career.yml Claude proposes…

● awaiting edit…

Three properties fall out of this: auditability (every change is a git diff), reversibility (`git revert` undoes any AI edit), correctness by construction (schema rejects nonsense).

// readiness

score = structure × 0.5 + evaluation × 0.5
structure = proven steps×0.4 + proven milestones×0.4 + tiers×0.2
proof: verified 1.0 · documented 1.0 · claimed 0.4 · none 0.25

The score that tells the truth.

A published formula where a finished step only earns full credit with proof attached. Tier-weighted evidence, a badge that never contradicts the content, and falling scores are features.

Career — Staff promotion 72%

ready · gaps

Admissions — Stanford MS 61%

ready · gaps

Immigration — O-1A petition 54%

building

Fitness — Sub-3 marathon 39%

not ready

# BRD §9 — readiness formula
readiness = structure × 0.5
           + evaluation × 0.5

structure =
  (Σ step_credit / steps_total)    × 0.4
+ (Σ milestone_credit / total)     × 0.4
+ (evidence       / expected)      × 0.2

step_credit = // best proof on the step
  verified|documented 1.0 · claimed 0.4
  no proof 0.25  // unprovenCredit

evaluation =
  Σ // per dimension from
    weight × score
    // config/scoring/<module>.yml

classification =
  < 40   → not_ready
  < 60   → building
  < 80   → ready_with_gaps
  >= 80  → ready

// architecture

Layered for evolution.

A modular monolith — local-friendly today, cloud-portable tomorrow. Hover any layer to see its tech and what depends on it.

UI Layer

Web (Next.js) + CLI (`qutub`) — both call the API

Next.js · React · TS · Tailwind · Commander · Chalk

API Layer

REST surface, auth, validation, owner-scoped queries

NestJS · Zod · JWT · Passport

Domain Layer

Qutub engine, evidence, readiness, activity log

TypeScript · domain services

Pipeline Layer

6 stages — normalize → classify → gap → score → plan → artifact

Stage processors · mode files · scoring configs

AI Operating Surface

YAML configs, MD modes, MD playbooks — re-read on every run

YAML · Markdown · gray-matter · Zod schemas

Worker Layer

Async jobs, batch parallelism, integrity checkers, cron

BullMQ · Redis · @nestjs/schedule

Data Layer

Relational + object storage

PostgreSQL · Prisma · S3 / MinIO

// architecture

Three layers.
One contract.

The interface you steer, the system that processes, the evidence that proves — every layer answers to the one below it.

Layer 1: The CLI

The interface. First-class, not an afterthought.

$ qutub goal define

✓ Goal created: Land principal engineer promotion

$ qutub milestone add --to career

✓ Milestone: Master distributed systems

$ qutub evidence log --step "read-papers"

✓ Evidence recorded: 5 papers reviewed

$ qutub readiness --show

Readiness: 68% (improving ↗)

Built for speed and clarity

✓ Zero-friction interface for power users
✓ Tab completion for all commands
✓ Real-time output in your terminal
✓ Local-first (no internet required)
✓ Human-readable, parseable output
✓ Composable with standard Unix tools

Layer 2: The Evidence Pipeline

How evidence is discovered, structured, and stored.

1. Scanners

Discover evidence from GitHub, LinkedIn, documents, certificates, emails, calendar.

2. Modes (Prompts)

LLM-powered extraction: "Extract this evidence into our schema."

3. Storage

Store in Postgres with full-text search and cross-referencing.

4. Readiness

Compute readiness score combining structure + evidence.

Modes are markdown files

No recompile. No deployment. You or Claude edit the prompts directly. The system uses them immediately.

Scanners are pluggable

Write a scanner for any source: GitHub, Stripe, Strava, AWS, Jira, Notion. If it has data, we can extract evidence.

Layer 3: The Database Schema

Postgres. Normalized. Auditable.

// Core schema

├─ users (auth, preferences)

├─ qutubs (goal, status, module)

├─ milestones (parent_qutub, position, evidence_count)

├─ steps (parent_milestone, status, evidence_links)

├─ evidence (type, source, artifact_url, parsed_data)

├─ readiness_snapshots (qutub_id, score, breakdown)

└─ audit_log (who, what, when)

Normalized

No redundancy. Clear relationships. Easy to query and reason about.

Auditable

Full audit log. Track who changed what, when. Immutable evidence trail.

Design principles

🎯

Replaceability

Each component can be swapped. Use our CLI or build yours. Use our scanners or write new ones. Use Postgres or plug in your database.

📝

Files as config

Modes (prompts) are markdown. Scanners are YAML. No hidden config. Everything is versionable and editable.

🔌

Composition over centralization

CLI, API, and database are independent. Run locally or in cloud. Compose them however you want.

🛡️

Privacy by default

Run on your machine or your servers. Your data doesn't phone home. Scanners are opt-in.

The complete qutub

From first goal to readiness tracking, here's how a user experiences Qutub.

1

Define Goal

What's your objective?

→

2

Add Milestones

Break into checkpoints

→

3

Create Steps

Executable actions

→

4

Log Evidence

Track progress

5

Compute Readiness

Get clarity

→

6

Share & Prove

Show your work

→

7

Iterate & Improve

Refine strategy

→

🚀

Achieve Goal

Mission complete

Ready to dig deeper?

Walk the operating loop end to end, or run the readiness math yourself in the playable demo.

Play a qutub Open walkthrough Play a qutub

// application

The actual
Qutub application.

Captured by pnpm screenshots from the running app with the demo persona — real data, real readiness math, not mockups.

Qutub Compass with the Kairos Pointer — Compass — your bearing at a glance

Where you land: the Kairos Pointer names the one step worth most right now, above every active qutub and its readiness band.

Qutub detail page with readiness dial and breakdown — A qutub, up close

The quest path on the left — tick a step and attach its proof in place; the readiness dial, band ladder, and proof-weighted breakdown on the right.

Fitness qutub detail page — Same engine, another domain

A fitness qutub uses the identical model — only the milestones, evidence types, and scoring weights change.

Career module dashboard — Module view

Every qutub in one module, the latest scanner signals, and the scoring contract the module is judged by — all from editable YAML.

Observatory with completed pipeline runs — Observatory

Paste a job post, a program page, or an exam guide; six stages normalise, classify, find gaps, score, plan, and draft artifacts.

Star Chart with timeline and readiness heatmap — Star Chart

Timeline, a readiness heatmap across qutubs, and a capacity burndown of planned versus logged hours.

Helm with weekly capacity — Helm

Weekly capacity and peak windows shape how the scheduler spreads steps across your week.

Qutub sign-in screen — Sign in

Calm, single-purpose entry under the compass.

Explore the full architecture behind these screens

Move from interface to model, modules, and pipeline design.

Open architecture See the walkthrough

// roadmap

Beyond shipped.

Signed exports (NX.1–2), rectification and embed widgets (NX.3–4), and federated calibration (NX.5 — opt-in, aggregate-only, honestly labeled) are shipped. The whole next layer is green. The pole stays fixed; the route extends.

Navigate what matters.

Claims are capped by proof.

Evidence on record

What the system may claim

The needle knows your next step.

The problem

What we believe

Our commitments

No credit without proof

The cap lives in code

Scores can fall

Calm, not a casino

What Qutub will never be

How we build

The Star — قطب شمالی

The Instrument — قطب نما

The Needle — καιρός

The Tower

The Register

The Names Before

Shipped. Measured.Shipping.

Backend & Data

Engine & Pipeline

Interfaces

Per-module wiring · Phase 3

Orchestration & capacity · Phase 4

TUI & visualizations · Phase 4

Portability & reach · Phase 4

Outcome prediction · Phase 5

Auto-generated drafts · Phase 5

Proactive re-planning · Phase 5

Calibration & privacy · Phase 5

Honest CI · post-roadmap

Predictor recalibration · post-roadmap

Scope-limited share tokens · post-roadmap

Eight truths.One compass.

Most people drift.

The problem

People drift

Progress disappears

Goals stay fuzzy

Effort doesn't compound

What we believe

Life is not random—it is navigable

Progress must be visible

Effort without structure is wasted

Big goals are structured qutubs

Evidence beats memory

How Qutub answers

Structure

Evidence

Readiness

Why this matters

For you

For others

The Name

The star that holds still

The instrument: Qutub Numa

The Minar

A note of respect

Everything is a Qutub.

Goal

Milestones

Steps

Evidence

Readiness

One model.Every domain.

What is structure?

Goal

Milestones

Steps

Evidence

How readiness is computed

Structure Score (50%)

Evidence Score (50%)

Try the model

Ready to navigate?

Same engine. Different domains.

Career

Admissions

Shipped. Measured.
Shipping.

Eight truths.
One compass.

One model.
Every domain.

Every verdict,
capped by proof.

Steer the system
in YAML.

Three layers.
One contract.

The actual
Qutub application.