Study track

Preview only

Finance, software, and economics operating track

Preview study track

Preview study-track detail validating how structured learning, modules, milestones, and linked outputs should appear on the public platform.

Author

Yasir Haque

Published

Preview only

Updated

March 26, 2026

Version

v0.4

Status

Preview

Track state

Mapping

Topic tags

FinanceSoftwareEconomics

Track actions

Keep the artifact inspectable.

View track Open learn hub Give feedback

Why this track matters

The learning surface should show that study is not private overhead; it is a visible system that produces public artifacts over time.

Track status

Current state

Mapping

Progress

36%

Milestones

Start

March 2026

Target end

June 2026

Modules

The track is made visible through modules, not vague goals.

Module 1

Macro interpretation for operators

In progress

Translate macro context into planning questions instead of abstract commentary.

Output goal

Working paper and dashboard notes

Resource notes

Central-bank releases, operator memos, and structured note synthesis.

Module 2

Software systems and platform leverage

Mapped

Study how software architecture and product choices shape durable leverage.

Output goal

Project case study and essay

Resource notes

Architecture notes, product teardowns, and systems writing.

Module 3

Finance as operating language

Mapped

Build stronger instincts around capital, unit economics, and financial framing.

Output goal

Research note and internal decision rubric

Resource notes

Investor letters, public filings, and finance primers.

Module 4

Founder judgment and public credibility

Queued

Connect the operating model back to what should become visible in public work.

Output goal

Whitepaper and platform essay

Resource notes

Brand system notes and platform revision history.

Milestones

Map the first four modules and their public output targets.
Link one research artifact and one project artifact back into the track.
Clarify the reading list and output cadence for the next revision.

Section

Why tracks exist

The learning surface is meant to prove that structured study in public can be concrete, cumulative, and tied to visible outputs.

Section

Product implication

A study track should not read like a course page. It should read like an operating system for focused learning.

Section

Relationship to the rest of the site

Tracks matter because they connect future research, projects, essays, and proofs back to a visible learning process.

Linked outputs

The track should point to the artifacts it is producing.

Research preview

Macro signal tracking for founder planning cycles

Preview entry showing how longer-form working papers can carry scope, maturity, and evidence fields without turning into a generic blog card.

PreviewPlanned output

Open detail

Project preview

Founder-readable macro dashboard shell

Preview case-study card showing how architecture, stack, and shipping status can be framed without falling into screenshot-first portfolio patterns.

PreviewLinked system

Open detail

Essay preview

Why visible revision matters more than polished positioning

Preview essay entry used to tune long-form archive rhythm before real essays are published.

PreviewSynthesis output

Open detail

Version history

Visible revision belongs on the page, not in private memory.

v0.4

March 26, 2026

Layout validation

Aligned the public reading surface with the live App Router routes and detail-module system.

v0.3

March 25, 2026

Trust block pass

Separated proof links, methodology notes, and version history so credibility does not rely on tone alone.

Related work

Keep the artifact connected to the rest of the platform.

Research preview

Public credibility systems for technical founders

Preview entry for flagship-style layouts where trust metadata, sources, and revision history need to be visible at archive level.

PreviewWhitepaper

Open detail

Project preview

Proof archive system for visible revision

Preview case study demonstrating how the public project archive can explain constraints, lessons, and architecture in the same surface.

PreviewCase study

Open detail