Part 15 of 18

The First 90 Artifacts: Concrete Starting Points

1. Purpose of This Part

The previous parts created the philosophy, roadmap, domains, research sources, operating system, GitHub strategy, and public identity.

This part turns the plan into a concrete artifact backlog.

The goal is to answer:

   What should actually exist?

Not vague goals. Not “learn AI.”

Not “study physics.”

Not “get better at coding.”

Actual artifacts.

Files. Repos. Essays. Notebooks. Projects. Reports. Simulations. Circuits. Writeups. Dashboards. Case studies. Logs. Tools.

This part defines the first 90 serious artifacts that can become the foundation of the entire life’s work.

The purpose is not to complete all 90 immediately.

The purpose is to create a visible backlog of what the life plan is trying to produce.

2. The Artifact Categories

The first 90 artifacts are divided into 9 categories:

1. Software Development, Product Engineering, and Design 2. AI Engineering and AI Research 3. Mathematics 4. Physics and Quantum 5. Electrical and Electronic Engineering 6. Cybersecurity 7. Operating Systems, Linux, C, Rust, and Low-Level Programming 8. Philosophy 9. Research, Writing, Design, GitHub, and Public Identity

Each category has 10 artifacts.

Together, these create the first serious body of work.

3. Category 1 — First 10 Software

Development Artifacts

Software Artifact 1 — Developer Operating System Repo A repository containing environment setup, Git workflow, terminal notes, project templates, README templates, debugging checklists, and personal development conventions.

Done means:

GitHub repo exists
README explains the purpose
environment setup checklist exists
Git workflow notes exist
reusable README template exists
project creation checklist exists

Priority: Very high Status: Active early

Software Artifact 2 — Web Foundations Portfolio A collection of HTML, CSS, and JavaScript projects built without frameworks.

Projects may include:

personal homepage
responsive landing page
form-heavy page
JavaScript quiz app
local-storage habit tracker
API dashboard

Done means:

at least 5 small projects exist
each has README notes
code is pushed to GitHub
at least one is deployed

Priority: High

Software Artifact 3 — TypeScript Practice Lab A repository for TypeScript fundamentals, typed utilities, API clients, type modeling, form validation, and small CLI tools.

Done means:

typed functions and utilities exist
TypeScript notes exist
at least one small typed project exists
README explains what TypeScript helped with

Priority: High

Software Artifact 4 — React Component Library A small reusable component system containing buttons, inputs, cards, modals, tables, layouts, navbars, alerts, and loading states.

Done means:

components are implemented
examples exist
responsive behavior works
accessibility basics are considered
README documents usage

Priority: High Software Artifact 5 — Full-Stack Study Planner A practical app for planning study sessions, topics, revision cycles, weak areas, and exam preparation.

Done means:

frontend exists
backend exists
database exists
authentication exists
study topics can be created
sessions can be tracked
app is deployed
README and case study exist

Priority: Very high Reason: It directly helps your actual life.

Software Artifact 6 — Admin Dashboard Project A polished dashboard with tables, filters, search, pagination, charts, user roles, and settings.

Done means:

dashboard UI exists
mock or real data is displayed
filters and search work
charts exist
responsive layout works
README explains architecture

Priority: Medium-high

Software Artifact 7 — Clone Project Rebuilt Independently One serious clone project such as Trello, Notion, GitHub Issues, Spotify, YouTube, or Airbnb-style booking.

Done means:

not just tutorial copied
rebuilt independently
modified features added
deployed
README explains differences
case study exists

Priority: Medium

Software Artifact 8 — SaaS-Style Multi-Tenant App A more serious product-style app with users, workspaces, roles, settings, audit logs, and notifications.

Done means:

organizations/workspaces exist
users have roles
permissions work
database schema is documented
tests exist
deployment exists
architecture document exists

Priority: Later high

Software Artifact 9 — Open-Source Developer Tool A useful CLI, package, template, API client, or automation tool that others could realistically use.

Done means:

install/use instructions exist
examples exist
license exists
issues are enabled
tests exist if appropriate
release version exists

Priority: Medium

Software Artifact 10 — Software Case Study A long-form writeup of one serious software project.

It should cover:

problem
user
architecture
database
API
frontend
testing
deployment
failures
lessons learned

Done means:

published on website or GitHub
links to repo/demo
includes diagrams/screenshots
honestly explains limitations

Priority: High once one serious project exists

4. Category 2 — First 10 AI Engineering

and AI Research Artifacts

AI Artifact 1 — AI Usage Constitution A written rulebook for using AI without destroying learning.

Done means:

rules for code, math, research, writing, cybersecurity, and philosophy exist
bad AI use is defined
verification rules exist
document is saved and referenced in the master system

Priority: Very high

AI Artifact 2 — Python AI Experiment Template A reusable repo structure for AI experiments.

Includes:

notebooks
scripts
data folder
results folder
README
environment file
experiment log template

Done means:

template repo exists
one sample experiment is included
setup instructions work

Priority: High

AI Artifact 3 — Classical ML Basics Repo A repository containing basic ML experiments.

Projects:

linear regression
logistic regression
classification metrics
train/test split
confusion matrix
model comparison

Done means:

at least 5 notebooks/scripts exist
metrics are explained
README explains what was learned

Priority: High

AI Artifact 4 — Deep Learning Lab PyTorch and/or TensorFlow/Keras notebooks covering tensors, training loops, image classification, text classification, and model saving.

Done means:

basic neural network trained
results documented
overfitting discussed
model saved and loaded
README explains workflow

Priority: High after ML basics

AI Artifact 5 — LLM API Playground A repo for experimenting with model APIs, prompts, structured outputs, latency, cost, model comparison, and failure cases.

Done means:

API calls work
structured output example exists
cost/latency notes exist
prompt examples are versioned
failure cases are documented Priority: Very high

AI Artifact 6 — Source-Grounded RAG Document Assistant A document assistant that answers only from uploaded or indexed sources and provides citations.

Done means:

document ingestion works
embeddings/indexing work
retrieval works
answer generation works
citations/source references appear
retrieval failures are documented
README explains limitations

Priority: Very high

AI Artifact 7 — Ollama Local Model Lab A lab for running local models, testing local inference, embeddings, structured outputs, and local RAG.

Done means:

Ollama setup notes exist
at least two local models tested
latency/memory notes exist
local embedding example exists
local RAG demo exists
cloud vs local comparison exists

Priority: Medium-high

AI Artifact 8 — Agent Workflow Lab A repo for tool-calling workflows, agents, human approval, logs, and failure analysis.

Done means:

at least one workflow exists
at least one tool-calling agent exists
logs/traces are recorded
human approval point exists
failure cases documented

Priority: Medium-high

AI Artifact 9 — AI Evaluation Lab A repo for prompt tests, RAG evals, model comparisons, human grading, LLM-as-judge experiments, and failure taxonomies.

Done means:

eval dataset exists
at least one model comparison exists
RAG evaluation exists
failure taxonomy exists
before/after improvement report exists

Priority: High

AI Artifact 10 — AI Product Case Study A full case study of one AI system.

It should cover:

problem
users
model choice
data
prompts
retrieval
evals
failures
risks
limitations
improvements

Done means:

published on website or GitHub
includes architecture diagram
includes examples and failure cases
does not overclaim

Priority: High once one AI project exists

5. Category 3 — First 10 Mathematics

Artifacts

Math Artifact 1 — Mathematics Diagnostic Report A written self-assessment of current math ability, weak areas, and starting point.

Done means:

strengths listed
weaknesses listed
starting layer chosen
first 4-week math plan created

Priority: Very high

Math Artifact 2 — Arithmetic and Algebra Repair Notebook A notebook covering fractions, exponents, equations, inequalities, graphing, and word-problem translation. Done means:

problem sets completed
mistakes logged
weak topics marked
review problems scheduled

Priority: Very high

Math Artifact 3 — Function and Graphing Atlas A visual notebook of major function families.

Includes:

linear
quadratic
polynomial
rational
exponential
logarithmic
trigonometric

Done means:

each function type has definition, graph, transformations, examples, and applications

Priority: High

Math Artifact 4 — Trigonometry and Unit Circle Notebook A notebook connecting trigonometry to circles, waves, rotations, physics, and signals.

Done means:

unit circle understood
trig graphs included
identities practiced
wave examples included Priority: High

Math Artifact 5 — Calculus I Notebook A serious notebook on limits, derivatives, chain rule, optimization, related rates, and physical interpretation.

Done means:

representative problems solved
derivations included
error log exists
derivative meaning is explained in words

Priority: High after algebra/precalculus

Math Artifact 6 — Calculus II Notebook A notebook on integrals, accumulation, techniques, applications, sequences, series, and Taylor series.

Done means:

integration techniques practiced
application problems solved
series notes exist
Taylor visualizations included if possible

Priority: Medium-high

Math Artifact 7 — Linear Algebra Lab A coding and notes repo for matrices, vectors, transformations, eigenvectors, least squares, and SVD.

Done means:

matrix operations implemented
visualizations exist
SVD image compression demo exists
AI/quantum links explained

Priority: Very high for AI/quantum

Math Artifact 8 — Discrete Math and Proof Notebook A notebook covering logic, sets, induction, relations, graph theory, counting, recurrences, and Big-O.

Done means:

proof exercises exist
induction practiced
graph theory notes exist
algorithms connection explained

Priority: High for CS/cybersecurity

Math Artifact 9 — Probability and Statistics Simulation Lab A notebook/repo covering distributions, Bayes, expectation, variance, LLN, CLT, hypothesis testing, confidence intervals, and regression.

Done means:

simulations exist
distributions visualized
statistics concepts explained
AI evaluation link included

Priority: High for AI/research

Math Artifact 10 — Math for AI, Physics, and Electronics Manual A personal manual connecting math topics to real domains.

Done means:

sections for AI, physics, EEE, quantum, cybersecurity
examples included
references included
gaps listed

Priority: Medium-high

6. Category 4 — First 10 Physics and

Quantum Artifacts

Physics Artifact 1 — Physics Diagnostic Report A self-assessment of current physics knowledge, mathematical prerequisites, and starting point.

Done means:

weak areas listed
starting layer chosen
resources selected
first study track created

Priority: Very high

Physics Artifact 2 — Units, Dimensions, and Measurement Notebook A notebook on SI units, dimensional analysis, measurement, uncertainty, estimation, and model assumptions.

Done means:

dimensional analysis problems solved
unit conversion practiced
uncertainty notes written
measurement mindset explained

Priority: Very high

Physics Artifact 3 — High-School Physics Foundations Notebook A notebook covering motion, force, energy, waves, heat, light, electricity, magnetism, and atoms.

Done means:

basic topics summarized
formula meanings explained
practice problems solved
weak topics marked

Priority: Very high

Physics Artifact 4 — Mechanics Problem and Simulation Lab A repo/notebook for kinematics, Newton’s laws, energy, momentum, rotation, and oscillations.

Done means:

solved problems exist
at least 3 simulations exist
physical interpretation included

Priority: High

Physics Artifact 5 — Waves and Oscillations Lab A repo covering simple harmonic motion, resonance, interference, standing waves, and sound. Done means:

wave simulations exist
oscillation problems solved
superposition explained
quantum connection noted

Priority: High

Physics Artifact 6 — Electricity and Magnetism Lab A notebook/repo covering fields, potentials, Gauss’s law, circuits, magnetism, induction, and Maxwell’s equations.

Done means:

E&M problem sets exist
field visualizer exists
circuits linked to EEE
Maxwell concept map exists

Priority: High for EEE/quantum hardware

Physics Artifact 7 — Modern Physics Transition Notebook A notebook covering relativity basics, blackbody radiation, photoelectric effect, Compton scattering, Bohr model, matter waves, and uncertainty.

Done means:

experimental motivation for quantum mechanics explained
modern physics problems solved
classical failure points explained

Priority: Medium-high

Physics Artifact 8 — Quantum Foundations Notebook A serious notebook on wavefunctions, probability amplitudes, Schrödinger equation, operators, measurement, and simple quantum systems.

Done means:

core concepts explained
simple problems solved
simulations included where possible
confusion log maintained

Priority: High long-term

Physics Artifact 9 — Qiskit Quantum Computing Lab A repo for qubits, gates, circuits, Bell states, teleportation, Grover, QFT, noise, and simple quantum algorithms.

Done means:

notebooks run
circuits explained mathematically
results interpreted
README explains prerequisites

Priority: Medium-high

Physics Artifact 10 — Quantum Hardware Overview Map A structured overview of superconducting qubits, trapped ions, photonics, spin qubits, decoherence, control, readout, and fabrication constraints.

Done means:

qubit modalities compared
hardware requirements explained
EEE/physics prerequisites listed
papers/resources linked

Priority: Medium-high long-term

7. Category 5 — First 10 Electrical and

Electronic Engineering Artifacts

EEE Artifact 1 — Electronics Diagnostic Report A self-assessment of remembered EEE knowledge, missing foundations, available equipment, and starting projects.

Done means:

skills assessed
equipment listed
missing tools listed
first lab sequence chosen

Priority: Very high

EEE Artifact 2 — Electronics Safety and Lab Setup Manual A personal manual for safe bench work, power supply use, current limiting, multimeter use, oscilloscope use, and component handling.

Done means:

safety checklist exists
equipment workflow exists
pre-power checklist exists
lab notebook template exists

Priority: Very high EEE Artifact 3 — Circuit Fundamentals Notebook A notebook covering voltage, current, resistance, power, Ohm’s law, KCL, KVL, series/parallel circuits, dividers, nodal analysis, and Thevenin/Norton.

Done means:

theory notes exist
problems solved
simulations included
measurement labs included

Priority: Very high

EEE Artifact 4 — LTspice Simulation Lab A repo of simulated circuits.

Includes:

resistor networks
RC/RL/RLC circuits
filters
diodes
transistors
op-amps

Done means:

simulations are organized
screenshots/results exist
README explains each circuit
real-world comparison planned

Priority: High

EEE Artifact 5 — Passive Components and Measurement Lab A lab notebook for resistors, capacitors, inductors, tolerances, RC curves, ESR basics, and real measurements.

Done means:

measurements taken
expected vs actual compared
error sources discussed

Priority: High

EEE Artifact 6 — Semiconductor Devices Notebook A notebook using Boylestad-style study for diodes, BJTs, FETs, MOSFETs, biasing, switching, amplification, and device behavior.

Done means:

notes exist
problems solved
datasheet studies included
lab circuits included

Priority: High

EEE Artifact 7 — Op-Amp Circuit Lab A lab for inverting amplifiers, non-inverting amplifiers, buffers, comparators, active filters, and instrumentation amplifiers.

Done means:

circuits simulated
circuits built where possible
measurements logged
real op-amp limitations discussed

Priority: High EEE Artifact 8 — Embedded Systems Starter Lab A repo for Arduino/Pico projects covering GPIO, PWM, ADC, sensors, UART, I2C, SPI, displays, and basic firmware structure.

Done means:

at least 5 embedded projects exist
wiring diagrams included
firmware documented
debugging notes included

Priority: Medium-high

EEE Artifact 9 — First KiCad PCB Project A simple PCB designed, checked, exported, ordered if possible, assembled, and tested.

Done means:

schematic exists
PCB layout exists
ERC/DRC checked
Gerbers exported
BOM exists
bring-up notes written

Priority: Medium-high

EEE Artifact 10 — Hardware Case Study A full writeup of one electronics project from requirement to circuit, simulation, build, measurement, failure, and revision.

Done means:

published on GitHub or website
includes schematic/simulation/photos/results
includes failures and lessons learned

Priority: High once one hardware project exists

8. Category 6 — First 10 Cybersecurity

Artifacts

Cybersecurity Artifact 1 — Cybersecurity Ethics and Scope Policy A personal code of conduct for legal and ethical testing.

Done means:

authorization rules written
scope rules written
responsible disclosure rules written
stopping conditions defined

Priority: Very high

Cybersecurity Artifact 2 — Security Lab Setup Manual A guide for VMs, snapshots, isolated networks, Kali/Parrot, vulnerable labs, and safe practice environments.

Done means:

lab architecture documented
VM setup steps included
reset/snapshot process included
legal-only reminder included

Priority: Very high Cybersecurity Artifact 3 — Linux and Networking Security Notebook A combined notebook for Linux permissions, processes, services, logs, TCP/IP, DNS, HTTP, TLS, ports, subnetting, and packet captures.

Done means:

notes exist
practice labs completed
Wireshark examples included
common commands documented

Priority: Very high

Cybersecurity Artifact 4 — Web Security Foundations Notebook A notebook on HTTP, cookies, sessions, auth, authorization, CORS, browser security, APIs, SQL basics, and common web failure points.

Done means:

concepts explained
examples included
developer prevention notes included

Priority: High

Cybersecurity Artifact 5 — OWASP / PortSwigger Lab Archive A structured archive of web security lab notes and vulnerability-class explanations.

Done means:

labs categorized
root causes explained
remediation included
no unauthorized material included

Priority: High

Cybersecurity Artifact 6 — Enumeration Methodology Playbook A repeatable legal-lab methodology for enumeration, service analysis, note-taking, attack-path mapping, and evidence collection.

Done means:

checklist exists
service notes exist
attack-path template exists
dead-end review process exists

Priority: Very high

Cybersecurity Artifact 7 — HTB Academy Penetration Tester Tracker A tracker for HTB modules, notes, exercises, weak areas, checklists, and CPTS readiness.

Done means:

all modules listed
progress tracked
notes linked
weak areas marked

Priority: High

Cybersecurity Artifact 8 — Vulnerability Report Template Pack A professional set of report templates for lab findings, executive summaries, evidence, impact, remediation, and retesting.

Done means:

templates exist
sample lab report exists
severity explanation included
evidence handling rules included

Priority: High

Cybersecurity Artifact 9 — CPTS / OSCP Readiness Portfolio A private or semi-private portfolio of practice reports, methodology, checklists, weak-area reviews, and exam readiness evidence.

Done means:

readiness checklist exists
practice reports exist
weak areas listed
revision plan exists

Priority: Later high

Cybersecurity Artifact 10 — Bug Bounty Scope Analysis Template A template for reading program scope, exclusions, safe harbor, assets, testing limits, and report requirements.

Done means:

template exists
at least one sample public program analyzed safely
rules of engagement section exists

Priority: Medium-high after labs

9. Category 7 — First 10 Operating

Systems / Low-Level Artifacts

Systems Artifact 1 — Linux Daily Fluency Notebook A notebook for Linux commands, filesystem, permissions, processes, services, logs, package management, shell workflows, and troubleshooting.

Done means:

● commands organized ● examples included ● troubleshooting notes included ● daily-use workflow documented

Priority: Very high

Systems Artifact 2 — Shell Scripting Tools Repo A repo of practical shell scripts.

Examples:

● backup script ● log parser ● file organizer ● project initializer ● system health checker

Done means:

● at least 5 scripts exist ● each has usage instructions ● errors handled reasonably

Priority: High Systems Artifact 3 — C Fundamentals Repo A repo for pointers, structs, arrays, strings, malloc/free, file I/O, Makefiles, and debugging.

Done means:

exercises exist
Makefile exists
memory notes exist
debugging notes exist

Priority: High

Systems Artifact 4 — Man Page Study Notebook A notebook summarizing important Linux/POSIX functions and system calls.

Done means:

at least 30 functions/syscalls summarized
examples included
failure modes listed

Priority: High

Systems Artifact 5 — Mini Unix Utilities Repo Implementations of small command-line tools such as cat, wc, cp, directory walker, text searcher, and file parser.

Done means:

at least 5 utilities implemented
README exists
tests/manual examples exist

Priority: High Systems Artifact 6 — POSIX Systems Programming Lab A repo for file descriptors, pipes, fork, exec, wait, signals, mmap, and process control.

Done means:

demos exist
diagrams included
system-call failures handled
README explains concepts

Priority: High

Systems Artifact 7 — Build Your Own Shell A C shell with command execution, built-ins, redirection, pipelines, and basic signal handling.

Done means:

shell runs commands
cd and exit work
redirection works
pipelines work
README explains architecture

Priority: Very high long-term

Systems Artifact 8 — Memory Allocator Lab A toy malloc/free implementation with free lists, splitting, coalescing, tests, diagrams, and fragmentation notes.

Done means:

allocator works for simple cases
tests exist
limitations explained
memory bugs discussed

Priority: Medium-high

Systems Artifact 9 — Rust Systems Tools Repo A repo for Rust CLI tools, file parsers, log analyzers, network servers, and safe systems utilities.

Done means:

at least 3 Rust tools exist
ownership notes included
tests included where appropriate

Priority: Medium-high

Systems Artifact 10 — OS Concepts Simulation Lab A repo for scheduler simulation, page replacement, deadlock detection, process states, and filesystem simulations.

Done means:

at least 3 simulations exist
concepts explained
results visualized or documented

Priority: Medium-high

10. Category 8 — First 10 Philosophy

Artifacts Philosophy Artifact 1 — Philosophy Method Notebook A notebook on argument reconstruction, premises, conclusions, objections, replies, conceptual analysis, and charitable interpretation.

Done means:

templates exist
examples included
method is usable for future readings

Priority: High

Philosophy Artifact 2 — Logic Foundations Notebook A notebook covering validity, soundness, truth tables, propositional logic, predicate logic, quantifiers, and natural deduction basics.

Done means:

exercises completed
argument examples included
logic errors logged

Priority: High

Philosophy Artifact 3 — Argument Map Archive A collection of argument maps from readings, personal beliefs, ethical questions, AI questions, and philosophy of science questions.

Done means:

at least 10 argument maps exist
objections and replies included
revision dates included

Priority: High Philosophy Artifact 4 — Epistemology Notebook A notebook on knowledge, belief, truth, justification, skepticism, testimony, disagreement, evidence, and intellectual humility.

Done means:

core positions summarized
personal learning implications written
AI connection included

Priority: Very high

Philosophy Artifact 5 — Personal Epistemic Discipline Document A rulebook for how to trust sources, use AI, verify claims, revise beliefs, and avoid fake understanding.

Done means:

source hierarchy written
AI verification rules included
belief revision principles included

Priority: Very high

Philosophy Artifact 6 — Ethics and Technology Notebook A notebook on virtue ethics, deontology, consequentialism, responsibility, harm, AI ethics, cybersecurity ethics, research ethics, and engineering ethics.

Done means:

major theories summarized
applied technology cases included
personal code of conduct linked Priority: High

Philosophy Artifact 7 — Philosophy of Science Notebook A notebook on scientific explanation, models, evidence, realism, falsification, confirmation, laws, and scientific revolutions.

Done means:

core concepts explained
physics/AI research links included
paper-reading implications included

Priority: High

Philosophy Artifact 8 — Philosophy of AI and Mind Essay Pack A set of essays on AI understanding, consciousness, agency, language, human judgment, machine intelligence, and moral status.

Done means:

at least 5 essays exist
arguments are structured
uncertainty is stated

Priority: Medium-high

Philosophy Artifact 9 — Life Project Statement A serious philosophical statement explaining what kind of life this master plan is trying to build.

Done means:

purpose stated
values stated
service definition included
revision date included

Priority: Very high

Philosophy Artifact 10 — Worldview Revision Log A living document tracking beliefs that changed, why they changed, what source/argument caused the change, and what action followed.

Done means:

template exists
first entries exist
review schedule exists

Priority: Medium-high

11. Category 9 — First 10 Research,

Writing, Design, GitHub, and Public Identity Artifacts

Public Artifact 1 — Mini Essay Archive A folder or repo containing short essays across all domains.

Done means:

template exists
at least 10 mini essays exist
essays are tagged by domain

Priority: Very high Public Artifact 2 — Zotero / Research Library System A structured research library for software, AI, math, physics, EEE, cybersecurity, systems, philosophy, and research methods.

Done means:

collections created
tags created
at least first sources added
processing rules written

Priority: Very high

Public Artifact 3 — Paper Reading Log A structured log for papers, including problem, method, results, limitations, equations, figures, and possible reproductions.

Done means:

template exists
at least 5 papers processed
open questions listed

Priority: High

Public Artifact 4 — Literature Map Repository A repo or folder for mapping topics, papers, debates, methods, and gaps.

Done means:

at least 2 literature maps exist
sources linked
gaps identified

Priority: Medium-high Public Artifact 5 — Technical Report Template Pack Reusable templates for AI reports, software architecture reports, EEE lab reports, physics simulation reports, cybersecurity reports, and research reports.

Done means:

templates exist
one sample report exists
documentation included

Priority: High

Public Artifact 6 — Figma / Design System Starter A Figma file or design repo containing typography, colors, spacing, buttons, forms, cards, tables, modals, dashboards, and states.

Done means:

base components exist
examples exist
design decisions documented
later React implementation planned

Priority: Medium-high

Public Artifact 7 — GitHub Profile README A polished GitHub profile README explaining identity, current focus, featured work, domains, and links.

Done means:

profile README exists
bio is clear
featured sections included
no fake claims Priority: Very high

Public Artifact 8 — Personal Website v1 A simple public website with home, projects, writing, about, and contact pages.

Done means:

deployed
linked from GitHub
at least 3 projects shown
writing page exists
about page explains the mission

Priority: High

Public Artifact 9 — Project Case Study Template A reusable template for software, AI, hardware, security, and research case studies.

Done means:

template exists
sections included
one case study started

Priority: High

Public Artifact 10 — Body of Work Index A master index linking all major artifacts by domain.

Done means:

categories exist
artifacts listed
links included
statuses included - updated monthly

Priority: Very high

12. The First Active Set

Do not start all 90.

Start with a small active set.

The first active set should be:

1. Developer Operating System Repo 2. AI Usage Constitution 3. Mathematics Diagnostic Report 4. Physics Diagnostic Report 5. Electronics Diagnostic Report 6. Cybersecurity Ethics and Scope Policy 7. Linux Daily Fluency Notebook 8. Philosophy Life Project Statement 9. Mini Essay Archive 10.GitHub Profile README

These are not the most impressive artifacts.

They are the foundation artifacts.

They create the operating base.

13. The First Build Set

After the foundation artifacts, the first actual build set should be:

1. Web Foundations Portfolio 2. Full-Stack Study Planner 3. LLM API Playground 4. Source-Grounded RAG Document Assistant 5. Arithmetic and Algebra Repair Notebook 6. High-School Physics Foundations Notebook

7. Circuit Fundamentals Notebook

8. Security Lab Setup Manual 9. C Fundamentals Repo 10.Personal Website v1

This creates visible technical momentum.

14. The First Public Proof Set

The first public proof set should eventually be:

1. GitHub Profile README 2. Personal Website v1 3. Web Foundations Portfolio 4. Full-Stack Study Planner 5. Source-Grounded RAG Assistant 6. Mini Essay Archive 7. Technical Report Template Pack 8. Body of Work Index 9. Software Case Study 10.AI Product Case Study

This gives the public identity a strong starting shape.

15. Active, Maintenance, and Dormant

Starting Recommendation Active First Start with:

1. Software Development 2. AI Engineering 3. Mathematics 4. Research/Writing/Public Identity

Reason:

These produce fast visible artifacts and support all other domains.

Maintenance First Keep lightly active:

1. Philosophy 2. Linux/Systems 3. Physics

Reason:

These are important but should not overload the first season.

Dormant First Pause initially:

1. Advanced EEE 2. Advanced Cybersecurity 3. Quantum Mechanics 4. Quantum Hardware 5. OS kernel work 6. Formal paper publishing

Reason:

These require foundations first.

Dormant does not mean abandoned.

It means:

  “Not yet.”

16. The First Season Recommendation

The first season should be called:

Season 1 — Become Operational

Its purpose is not mastery.

Its purpose is to establish the system and produce early evidence.

Season 1 Active Domains

Software
AI
Math
Public identity / research writing

Season 1 Main Artifacts

Developer Operating System Repo
GitHub Profile README
Mini Essay Archive
Mathematics Diagnostic Report
Web Foundations Portfolio
LLM API Playground
AI Usage Constitution
Body of Work Index
Personal Website v1 draft
Arithmetic and Algebra Repair Notebook

Season 1 Minimum Success Season 1 is successful if:

GitHub is cleaned and structured
profile README exists
at least one web project is deployed
AI usage rules exist
first AI playground exists
math starting point is diagnosed
mini essay habit begins
body-of-work index exists

This is enough. Do not overload Season 1.

17. The First 30-Day Artifact Plan

Week 1 — Foundation and Setup

Focus:

GitHub cleanup
Developer Operating System Repo
AI Usage Constitution
Math Diagnostic Report
Mini Essay Archive

Evidence:

1 repo created
1 AI rules document
1 math diagnostic
2 mini essays

Week 2 — Web and Public Identity

Focus:

GitHub Profile README
Web Foundations Portfolio
Personal Website v1 skeleton
Body of Work Index

Evidence:

profile README live
first static project live
website skeleton deployed
body-of-work index started

Week 3 — AI Playground and Math Repair

Focus:

LLM API Playground
Arithmetic/Algebra Repair Notebook
TypeScript or JS practice
one mini essay

Evidence:

API call working
structured output example working
first algebra notebook section complete
one essay published or archived

Week 4 — First Integration Review

Focus:

improve README files
add first case study draft
continue algebra
continue web portfolio
monthly review

Evidence:

1 polished repo
1 case study draft
1 algebra progress update
1 monthly review document

18. The Artifact Completion Rule

An artifact is not done because it exists.

It is done when it has: 1. clear purpose

2. actual content 3. evidence of work 4. documentation 5. next-step or completion note 6. honest limitations

For technical projects, add:

7. setup instructions 8. screenshots, outputs, or tests 9. source references 10.GitHub link

The rule:

A shallow artifact is a placeholder. A serious artifact teaches future me or helps someone else.

19. The First 90 Artifacts Standard

The first 90 artifacts are not a checklist to finish quickly.

They are the first visible shape of the life’s work.

The standard is:

Across all domains, I will create artifacts that prove learning, preserve struggle, document growth, and eventually serve others.

The point is not to say:

  “I have 90 projects.”

The point is to say:

  “I am building a body of work.”

A body of work is not created by intensity alone.

It is created by accumulation. One repo. One essay. One problem notebook. One lab report. One circuit. One security writeup. One case study. One review.

Repeated for years.