Tasks

Recurring routine — see master plan Part 17 for the full template. This task surfaces on every daily cycle as a reminder; mark in-progress while running, then done.

Recurring routine — see master plan Part 17 for the full template. This task surfaces on every daily cycle as a reminder; mark in-progress while running, then done.

Recurring routine — see master plan Part 17 for the full template. This task surfaces on every weekly cycle as a reminder; mark in-progress while running, then done.

Recurring routine — see master plan Part 17 for the full template. This task surfaces on every weekly cycle as a reminder; mark in-progress while running, then done.

Season 1 main artifact — see Part 16 of the master plan for context.

Recurring routine — see master plan Part 17 for the full template. This task surfaces on every monthly cycle as a reminder; mark in-progress while running, then done.

Season 1 main artifact — see Part 16 of the master plan for context.

Season 1 main artifact — see Part 16 of the master plan for context.

Season 1 main artifact — see Part 16 of the master plan for context.

Season 1 main artifact — see Part 16 of the master plan for context.

Season 1 main artifact — see Part 16 of the master plan for context.

Season 1 main artifact — see Part 16 of the master plan for context.

Season 1 main artifact — see Part 16 of the master plan for context.

Recurring routine — see master plan Part 17 for the full template. This task surfaces on every quarterly cycle as a reminder; mark in-progress while running, then done.

Season 1 stretch artifact — see Part 16 of the master plan for context.

Season 1 stretch artifact — see Part 16 of the master plan for context.

Season 1 stretch artifact — see Part 16 of the master plan for context.

Season 1 stretch artifact — see Part 16 of the master plan for context.

Season 1 stretch artifact — see Part 16 of the master plan for context.

Season 1 stretch artifact — see Part 16 of the master plan for context.

Season 1 stretch artifact — see Part 16 of the master plan for context.

Recurring routine — see master plan Part 17 for the full template. This task surfaces on every yearly cycle as a reminder; mark in-progress while running, then done.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

A reusable template for software, AI, hardware, security, and research case studies.

Done means:

• template exists
• sections included
• one case study started

Priority: High

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

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

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

A master index linking all major artifacts by domain.

Done means:

• categories exist
• artifacts listed
• links included
• statuses included - updated monthly

Priority: Very high

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

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

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

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

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

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

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