Part 17 of 18

Templates, Checklists, and Operating Routines

1. Purpose of This Part

This part gives the practical templates that make the whole plan usable.

The previous parts described domains, roadmaps, artifacts, seasons, priorities, GitHub strategy, research methods, and public identity.

This part turns those ideas into copy-paste operating documents. The goal is simple:

      When I sit down to work, I should not have to invent the structure again.

Templates reduce friction.

They help convert:

● vague goals into projects ● projects into tasks ● sessions into evidence ● mistakes into improvement ● notes into research ● repositories into serious artifacts ● learning into visible work ● reflection into direction

The rule is:

Use templates lightly but consistently. They should support action, not become bureaucracy.

2. Master Weekly Planning Template

Use this once per week.

Weekly Plan

Week of:

Active Domains

Main Artifact of the Week

Secondary Artifact

Maintenance Habit

Deep Work Sessions Planned

Minimum Viable Week

If this week goes badly, the minimum evidence I must produce is:

Risks / Obstacles

Recovery Plan

If the week goes off track, I will:

End-of-Week Evidence Target

By the end of this week, I want these to exist:

Notes

3. Daily Execution Template

Use this at the start of the day.

Daily Execution

Date:

Primary Build

Secondary Study

Small Writing / Notes

Evidence Required Today

Possible Obstacles

AI Use Allowed Today

Shutdown Note

At the end of the day, write:

what was done
what remains
next action

4. Daily Shutdown Template

Use this at the end of the day.

Daily Shutdown

Date:

What I Actually Did

Evidence Produced

What Was Hard

What I Learned

What I Avoided

Next Action

Tomorrow’s First Move

5. Build Log Template

Use this after any serious session.

Build Log Entry

Date:

Domain:

Project:

Session length:

What I Worked On

Evidence Produced

Link / File / Repo

What Was Hard

Mistake or Blocker

What I Learned

Next Step

6. Deep Work Session Template

Use this before a focused work block.

Deep Work Session

Date:

Start time:

End time:

Domain:

Project:

Goal

Starting State

Target Evidence

By the end of this session, I want this to exist:

Distractions to Block

AI Use Boundary

AI may be used for:

AI may not be used for:

Result

Next Step

7. Artifact Tracker Template

Use this as the master list of outputs.

Artifact Tracker

|---|---|---|---|---|---|---|---|---|---|---|

| | | | Idea / Active / Draft / Working / Needs Review / Published / Paused / Archived | | | | | | | Raw / Clean / Shareable / Portfolio / Publishable |

8. Project Definition of Done Template

Use this before starting a serious project.

Project Definition of Done

Project Name:

Domain:

Project Type:

Software / AI / Math / Physics / EEE / Cybersecurity / Systems / Philosophy / Research / Design / Public Identity

Purpose

Why does this project exist?

Problem or Question

What problem does it solve or what question does it answer?

Minimum Version

What is the smallest useful version?

Required Features or Sections

Required Artifact

What must exist at the end?

Documentation Required

Testing / Validation Required

Evidence Required

Examples:

screenshots
tests
measurements
solved problems
diagrams
report
simulation
deployment
case study

Not Included

What is intentionally out of scope?

Done Means

This project is done when:

Next Version

If this goes well, the next version could include:

9. Minimum Viable Artifact Template

Use when a project feels too large.

Minimum Viable Artifact

Large Project:

Smallest Real Artifact

Time Limit

What It Must Prove

What It Does Not Need Yet

Evidence

Next Step After This

10. Weekly Review Template

Use at the end of each week.

Weekly Review

Week of:

What I Built

What I Studied

What I Wrote

What I Published or Shared

Evidence Produced

What Went Well

What Went Badly

What I Avoided

Biggest Lesson

Active Domains Status

| Domain | Status | Notes |

|---|---|---|

| | Active / Maintenance / Dormant | |

Artifacts Updated

What Should Continue Next Week

What Should Be Paused

Minimum Viable Next Week

11. Monthly Review Template

Use once per month.

Monthly Review

Month:

Summary of the Month

Main Artifacts Produced

GitHub Progress

Writing / Research Progress

Study Progress

Technical Progress

Mistakes and Failures

What I Avoided

What Became Clearer

What Became Too Much

Domain Status

| Domain | Active / Maintenance / Dormant | Notes |

|---|---|---|

| Software | | |

| AI | | |

| Math | | |

| Physics | | |

| EEE | | |

| Cybersecurity | | |

| Systems | | |

| Philosophy | | |

| Research/Writing | | |

| Design/Public Identity | | |

Best Evidence This Month

Worst Bottleneck

What to Stop Doing

Next Month Focus

One Honest Reflection

12. Seasonal Review Template

Use every 8–12 weeks.

Seasonal Review

Season Name:

Date Range:

Theme of the Season

Active Domains

Maintenance Domains

Dormant Domains

Major Artifact Target

Completed Artifacts

Partially Completed Artifacts

Public Outputs

GitHub / Portfolio Changes

Research / Writing Outputs

Foundation Improvements

What Worked

What Did Not Work

What Was Overambitious

What Should Be Paused Next Season

What Should Become Active Next Season

Next Season Theme

Next Season Main Artifact

Final Reflection

13. Yearly Review Template

Use once per year.

Yearly Body-of-Work Review

Year:

Year Theme

What I Built

What I Studied

What I Wrote

What I Published

What I Contributed

Strongest Artifacts

GitHub Review

Website / Portfolio Review

Research Review

Domain Maturity Review

|---|---|---|---|

| AI | | | |

| EEE | | | |

Biggest Wins

Biggest Failures

Repeated Patterns

What I Should Stop Doing

What I Should Double Down On

What Changed in My Thinking

What Service Did My Work Provide?

Next Year Theme

Next Year First Season

14. Mini Essay Template

Use for short essays.

Mini Essay

Title:

Date:

Domain:

Tags:

Question

What question is this essay trying to answer?

Core Idea

Explanation

Example

Objection or Limitation

Why It Matters

Connection to My Life / Work

Source or Reference

Unresolved Question

15. Source Note Template

Use for books, articles, papers, documentation, videos, and standards.

Source Note

Title:

Author:

Year:

Source Type:

Link / DOI:

Domain:

Tags:

Why I Saved This

Main Question

Main Claim

Key Ideas

Method / Approach

Evidence Used

Important Terms

Useful Quote

My Summary

What I Understand

What I Do Not Understand

How This Connects to My Work

Possible Use

Essay / project / report / literature map / reproduction / background

Reliability Notes

Follow-Up Sources

16. Paper Reading Template

Use for research papers.

Paper Reading Note

Paper Title:

Authors:

Year:

Venue:

Link / DOI:

Domain:

Tags:

1. Field / Subfield

2. Problem

What problem is the paper addressing?

3. Why the Problem Matters

4. Prior Work

5. Research Gap

6. Main Claim / Contribution

7. Method

8. Data / System / Experimental Setup

9. Metrics / Evaluation Criteria

10. Results

11. Key Figures / Tables

Figure/Table:

What it shows:

Why it matters:

12. Key Equations

Equation:

Meaning:

Where it is used:

13. Assumptions

14. Limitations

15. Threats to Validity

16. What I Understood

17. What I Did Not Understand

18. Possible Reproduction

19. Possible Extension

20. One-Screen Summary

17. Literature Map Template

Use when studying a research area.

Literature Map

Topic:

Date Started:

Domain:

Central Question

Search Terms

Foundational Sources

Recent Sources

Review / Survey Sources

Major Themes

Competing Approaches

|---|---|---|---|

| | | | |

What Researchers Agree On

What Researchers Disagree On

Methods Used

Datasets / Benchmarks / Systems

Gaps

Possible Research Questions

My Current Understanding

Next Sources to Read

18. Technical Report Template

Use for serious project reports.

Technical Report

Title:

Author:

Date:

Domain:

Status: Draft / Reviewed / Published

Abstract

Short summary of the report.

1. Motivation

Why does this work matter?

2. Background

What does the reader need to know?

3. Question / Problem

What is being investigated, built, tested, or solved?

4. Method

What did I do?

5. Implementation / Experiment

How was it built or tested?

6. Results

What happened?

7. Analysis

What do the results mean?

8. Limitations

What should not be overclaimed?

9. Failures / Unexpected Issues

What went wrong?

10. Future Work

What comes next?

11. References

Appendix

Extra notes, code snippets, tables, screenshots, measurements, or logs.

19. Project Case Study Template

Use for website or portfolio case studies.

Project Case Study: [Project Name]

Summary

What this project is.

Problem

What problem does it solve?

Motivation

Why I built it.

Users / Use Case

Who is it for?

Requirements

What did it need to do?

Design / Architecture

How is it structured?

Implementation

What was built?

Testing / Validation

How did I check it?

Results

What works?

Failures

What went wrong?

Lessons Learned

What do I understand now?

Limitations

What is still weak?

Future Work

What comes next?

Links

GitHub: Demo:

Report:

Docs:

20. GitHub README Template

Use for serious repositories.

Project Name

One-sentence explanation of what this project does.

Why This Exists

Explain the problem, motivation, or learning goal.

What It Does

Feature 1
Feature 2
Feature 3

Tech Stack / Tools

Architecture

Brief explanation of how the project is structured.

Setup


# commands here

Usage
Explain how to use it.

Examples / Screenshots
    - 

Tests
# test commands here

Results / Evidence
Screenshots, outputs, measurements, benchmarks, reports, or findings.
What I Learned
      - 

Limitations
      - 

Roadmap

> ● [ ]
> ● [ ]
> ● [ ]


References
      - 

License
      - 

---

# 21. AI Usage Review Template

Use for serious AI-assisted work.

```text

# AI Usage Review

Project / Output:
Date:

## Where AI Was Used

-

## What AI Helped With

-

## What I Verified

-

## What I Rejected or Changed

-

## Risks

Possible hallucinations, wrong assumptions, unsupported claims, bad code, bias, or
missing context:

-
## Human Understanding Check

Can I explain the output without AI?

Yes / No

Explanation:

-

## Final Verification Steps

1. 

2. 

3. 

## Disclosure Needed?

Yes / No

If yes, disclosure text:

-

## 22. AI Project Evaluation Template

Use for AI apps, RAG systems, agents, and model experiments.

# AI Project Evaluation

Project:

Date:

Model(s):

## Task

What should the AI system do?

-

## Inputs

-

## Expected Outputs

-
## Test Set

Number of examples:

Source of examples:

## Metrics / Judgement Criteria

- accuracy

- faithfulness

- citation quality

- usefulness

- latency

- cost

- refusal behavior

- tool-call correctness

- retrieval quality

## Results

-

## Failure Cases

1. 
2. 

3. 

## Root Causes

-

## Improvements Tried

-

## Before / After Comparison

-

## Remaining Limitations

-

## Next Evaluation

-

## 23. RAG Evaluation Template

Use for source-grounded assistants.

# RAG Evaluation

Project:

Date:

## Document Set

-

## Chunking Strategy

-

## Embedding Model

-

## Retrieval Method

-

## Generation Model
-

## Test Questions

1. 

2. 

3. 

## Retrieved Sources Inspection

Question:

Retrieved chunks:

Relevant? Yes / No

Notes:

-

## Answer Quality

Question:

Answer:

Source support:

Errors:
Missing information:

-

## Failure Categories

- bad chunking

- bad retrieval

- missing document

- wrong citation

- hallucination

- vague answer

- refusal failure

- unsupported confidence

## Improvements

-

## Next Test

-

## 24. Math Error Log Template

Use after math practice.

# Math Error Log

Date:

Topic:

Problem:

## My Mistake

-

## Why It Happened

-

## Correct Method

-

## Concept I Was Missing

-
## Similar Problem to Retry

-

## Revisit Date

-

## Status

Not reviewed / Reviewed / Fixed


## 25. Math Concept Note Template

Use for formulas, methods, and topics.

# Math Concept Note

Concept:

Topic:

Date:

## Definition
-

## Intuition

-

## Formula / Statement

-

## Derivation or Reason

-

## Example

-

## Non-Example

-

## Common Mistakes
-

## Applications

Software:

AI:

Physics:

EEE:

Cybersecurity:

Research:

## Practice Problems

-

## My Current Weakness

-


## 26. Physics Problem Log Template

Use for physics problems.

# Physics Problem Log
Date:

Topic:

Source:

Problem:

## Diagram

-

## Known Quantities

-

## Unknown Quantity

-

## Assumptions

-

## Physical Principle
Newton’s laws / conservation of energy / conservation of momentum / Maxwell / wave
equation / Schrödinger / other

## Equations

-

## Solution

-

## Unit Check

-

## Physical Interpretation

-

## Mistake / Confusion

-

## Similar Problem to Try
-


## 27. Physics Simulation Template

Use for simulation projects.

# Physics Simulation Report

Simulation:

Date:

Domain:

## Physical System

-

## Question

-

## Model

-
## Assumptions

-

## Equations

-

## Numerical Method

-

## Parameters

-

## Code Structure

-

## Results

-
## Plots / Visuals

-

## Interpretation

-

## Limitations

-

## Next Improvement

-


## 28. EEE Lab Report Template

Use for electronics experiments.

# Electronics Lab Report

Project / Circuit:

Date:
Domain:

Version:

## Objective

-

## Circuit Description

-

## Schematic

-

## Components

| Component | Value / Part Number | Notes |

|---|---|---|

| | | |

## Datasheets Checked

-
## Expected Behavior

-

## Calculations

-

## Simulation

Tool:

Result:

-

## Build Notes

-

## Measurement Setup

Equipment:

Settings:
-

## Measurements

| Point | Expected | Measured | Notes |

|---|---|---|---|

| | | | |

## Oscilloscope / Multimeter Evidence

-

## Problems Encountered

-

## Root Cause

-

## Fix / Revision

-
## Lessons Learned

-

## Safety Notes

-

## Next Version

-


## 29. PCB Review Checklist

Use before ordering a PCB.

# PCB Review Checklist

Project:

Date:

Board Version:

## Schematic Review
- [ ] Power input correct

- [ ] Ground connected properly

- [ ] Decoupling capacitors placed

- [ ] Connectors labeled

- [ ] Pinouts verified from datasheets

- [ ] Pull-ups/pull-downs checked

- [ ] Protection components considered

- [ ] Test points added where useful

- [ ] ERC passed or errors justified

## Footprint Review

- [ ] Every footprint checked against datasheet

- [ ] Pin numbering verified

- [ ] Package dimensions checked

- [ ] Connector orientation checked

- [ ] Mounting holes checked

- [ ] Silkscreen orientation clear

## Layout Review

- [ ] Trace widths suitable

- [ ] Clearances suitable
- [ ] Ground plane present if appropriate

- [ ] Power traces considered

- [ ] Sensitive signals routed carefully

- [ ] Decoupling capacitors near IC power pins

- [ ] No obvious routing bottlenecks

- [ ] DRC passed or errors justified

## Manufacturing Review

- [ ] Board dimensions checked

- [ ] Gerbers generated

- [ ] Drill files generated

- [ ] BOM generated

- [ ] Assembly notes written

- [ ] Manufacturer rules checked

## Bring-Up Plan

- [ ] Visual inspection plan

- [ ] Continuity test plan

- [ ] Power-only test plan

- [ ] Current-limit value chosen

- [ ] Test points identified

- [ ] First firmware/test procedure ready
## Final Decision

Order / Do not order

Reason:

-


## 30. Cybersecurity Scope Checklist

Use before any security testing.

# Cybersecurity Scope Checklist

Target / Lab:

Date:

## Environment Type

- [ ] My own system

- [ ] Local lab

- [ ] CTF / HTB / TryHackMe / PortSwigger

- [ ] Bug bounty program

- [ ] Written authorization
- [ ] Other:

## Authorization Confirmed?

Yes / No

Evidence of authorization:

-

## Scope

Allowed assets:

-

Out-of-scope assets:

-

Allowed testing types:

-
Prohibited testing types:

-

## Data Handling Rules

-

## Stopping Conditions

I must stop if:

-

## Reporting Channel

-

## Notes

-

## Proceed?
Yes / No


## 31. Cybersecurity Lab Writeup Template

Use for legal labs only.

# Cybersecurity Lab Writeup

Lab / Machine / Challenge:

Platform:

Date:

Difficulty:

Scope: Legal lab only

## Objective

-

## Initial Enumeration

-

## Findings
-

## Attack Path Summary

High-level explanation:

-

## Vulnerability / Weakness

-

## Root Cause

-

## Evidence

-

## Impact

-
## Remediation

-

## Defensive Notes

-

## What I Missed

-

## Lessons Learned

-

## Commands / Tools Used

Only include lab-safe notes.

-

## References
-


## 32. Vulnerability Report Template

Use for authorized reporting.

# Vulnerability Report

Title:

Date:

Reporter:

Program / Organization:

Affected Asset:

Scope Confirmed: Yes / No

## Summary

-

## Severity

-
## Preconditions

-

## Impact

-

## Steps to Reproduce

1. 

2. 

3. 

## Evidence

Screenshots, request/response examples, logs, or safe proof.

-

## Root Cause

-
## Remediation Recommendation

-

## Security Best Practice

-

## Data Handling Statement

-

## Retest Notes

-

## Timeline

-

## References

-

## 33. Philosophy Argument Map Template

Use for philosophy readings and personal beliefs.

# Argument Map

Topic:

Date:

Source / Thinker:

## Main Question

-

## Conclusion

-

## Premises

1. 

2. 

3. 
## Hidden Assumptions

-

## Argument Structure

Explain how the premises are supposed to support the conclusion.

-

## Strongest Objection

-

## Possible Reply

-

## My Current View

-

## What Would Change My Mind?
-

## Connection to Life / Work

-


## 34. Philosophy Concept Analysis

Template
Use for difficult concepts.

# Concept Analysis

Concept:

Date:

Domain:

## Ordinary Meaning

-

## Philosophical Meaning

-
## Competing Definitions

1. 

2. 

3. 

## Examples

-

## Non-Examples

-

## Borderline Cases

-

## Why the Concept Matters

-

## Confusions to Avoid
-

## My Current Understanding

-

## Open Questions

-


## 35. Philosophy Position Paper Template

Use for serious essays.

# Position Paper

Title:

Date:

Topic:

## Question

-
## Thesis

-

## Background

-

## Argument

Premise 1:

Premise 2:

Premise 3:

Conclusion:

## Objection

-

## Reply

-
## Alternative View

-

## Why This Matters

-

## Connection to My Life / Work

-

## Remaining Uncertainty

-

## References

-


## 36. Research Integrity Checklist

Use before publishing or sharing serious research.
# Research Integrity Checklist

Project / Paper:

Date:

## Sources

- [ ] All citations checked

- [ ] Sources actually support the claims

- [ ] Quotes are accurate

- [ ] Paraphrases are not plagiarism

- [ ] Foundational sources included where needed

- [ ] Recent sources checked where needed

## Claims

- [ ] Claims match evidence

- [ ] Limitations stated

- [ ] Uncertainty stated

- [ ] No exaggerated novelty

- [ ] Negative results preserved

## Methods
- [ ] Method described clearly

- [ ] Data/code environment documented

- [ ] Parameters recorded

- [ ] Reproducibility notes included

## AI Use

- [ ] AI use verified

- [ ] AI did not invent citations

- [ ] AI-generated claims checked

- [ ] Disclosure included if required

## Ethics

- [ ] No private data exposed

- [ ] No unsafe security details published

- [ ] Authorship is fair

- [ ] Conflicts of interest disclosed if relevant

## Final Decision

Publish / Revise / Do not publish yet

Reason:
-


## 37. Public Project Card Template

Use for the portfolio website.

# Project Card

Project Name:

One-Line Description:

Domain:

Software / AI / Systems / Hardware / Security / Math / Physics / Research / Philosophy /
Design

Status:

Active / Experimental / Published / Archived

Artifacts:

Code / Demo / Report / Case Study / Paper / PCB / Simulation / Essay

Links:

GitHub:

Demo:
Case Study:

Report:

Short Notes:

-


## 38. Body of Work Index Template

Use as the master public/private index.

# Body of Work Index

Last Updated:

## Software and Product Engineering

| Artifact | Status | Link | Notes |

|---|---|---|---|

| | | | |

## AI Systems and Research

| Artifact | Status | Link | Notes |

|---|---|---|---|
| | | | |

## Mathematics

| Artifact | Status | Link | Notes |

|---|---|---|---|

| | | | |

## Physics and Quantum

| Artifact | Status | Link | Notes |

|---|---|---|---|

| | | | |

## Electronics and Hardware

| Artifact | Status | Link | Notes |

|---|---|---|---|

| | | | |

## Cybersecurity

| Artifact | Status | Link | Notes |

|---|---|---|---|
| | | | |

## Systems / Linux / C / Rust

| Artifact | Status | Link | Notes |

|---|---|---|---|

| | | | |

## Philosophy

| Artifact | Status | Link | Notes |

|---|---|---|---|

| | | | |

## Research and Writing

| Artifact | Status | Link | Notes |

|---|---|---|---|

| | | | |

## Design and Public Identity

| Artifact | Status | Link | Notes |

|---|---|---|---|
| | | | |


## 39. Personal Website Page Template

Use for website pages.

# Page Title

Short intro explaining the purpose of this page.

## Featured

-

## Categories

-

## Current Work

-

## Completed Work
-

## In Progress

-

## Notes / Reflections

-

## Links

-


## 40. Public Monthly Build Log Template

Use for public updates.

# Month in Building — [Month Year]

## Built

-
## Studied

-

## Wrote

-

## Published

-

## Failed / Learned

-

## Best Artifact

-

## Next Month

-

## 41. Open-Source Contribution Template

Use when contributing to external projects.

# Open-Source Contribution Note

Project:

Repository:

Date:

## Why This Project?

-

## Setup Steps

-

## Issue / Contribution Target

-

## What I Tried
-

## Tests Run

-

## Change Made

-

## Pull Request Link

-

## Maintainer Feedback

-

## What I Learned

-

## Follow-Up
-


## 42. Failure Postmortem Template

Use when something breaks or fails.

# Failure Postmortem

Date:

Domain:

Project:

## What Failed?

-

## What I Expected

-

## What Actually Happened

-
## Immediate Cause

-

## Deeper Cause

-

## What I Tried

-

## What Fixed It

-

## What Did Not Fix It

-

## Prevention

-
## Lesson

-

## Follow-Up Task

-


## 43. Resource Intake Template

Use before adding a new book, course, tool, or resource.

# Resource Intake

Resource:

Link:

Domain:

Type: Book / Course / Documentation / Paper / Tool / Video / Other

## Why Add This?

-

## What Artifact Will It Support?
-

## Is It Primary, Secondary, or Optional?

-

## What Does It Replace?

-

## When Will I Use It?

-

## Completion Definition

-

## Keep / Reject / Later

Decision:

Reason:

-

## 44. Backlog Item Template

Use for project and essay ideas.

# Backlog Item

Idea:

Domain:

Type:

Project / Essay / Research Question / Tool / Circuit / Simulation / Report / Other

## Why It Matters

-

## Possible Artifact

-

## Minimum Version
-

## Dependencies

-

## Priority

Now / Soon / Later / Not Yet

## Next Action

-


## 45. Stop Doing Template

Use when pruning commitments.

# Stop Doing Review

Date:

## What Am I Doing Only From Guilt?
-

## What Project No Longer Matters?

-

## What Resource Is Redundant?

-

## What Domain Is Pretending to Be Active?

-

## What Tool Is Creating Friction?

-

## What Habit Is Fake Productivity?

-

## Decision
Delete / Archive / Pause / Merge / Simplify / Postpone

## Reason

-

## Replacement Action

-


## 46. Master Dashboard Skeleton

Use as the top-level dashboard.

# Master Dashboard

Last Updated:

## Active Domains

| Domain | Current Track | Current Project | Next Action |

|---|---|---|---|

| | | | |
## Maintenance Domains

| Domain | Maintenance Habit | Next Review |

|---|---|---|

| | | |

## Dormant Domains

| Domain | Pause Reason | Restart Trigger |

|---|---|---|

| | | |

## Active Projects

| Project | Domain | Artifact Target | Status | Link |

|---|---|---|---|---|

| | | | | |

## This Week

Main artifact:

Minimum viable week:

Deep work sessions:
## Research Pipeline

Sources to process:

Papers being read:

Essays in draft:

Reports in progress:

## Reviews

Weekly review:

Monthly review:

Seasonal review:

Yearly review:


## 47. AI Creation Template

# Domain AI Assistant Instruction Template

Assistant Name:

Domain:

Purpose:

What this AI is specifically for.
Current Syllabus:

List the exact book/course/module sequence this AI should follow.

Current Artifact:

What I am currently building/studying.

Allowed Tasks:

- Explain concepts

- Quiz me

- Check my work

- Give hints

- Generate practice problems

- Review my notes

- Track weak areas

Forbidden Tasks:

- Do the work before I attempt it

- Let me skip prerequisites

- Give final answers too early

- Invent sources

- Ignore safety/ethics

- Over-praise weak work

- Move me forward without testing recall
Response Style:

- Socratic when possible

- Ask me to attempt first

- Use my syllabus

- Track mistakes

- End with one next action

Testing Method:

- Ask recall questions

- Give mixed problems

- Ask for explanations without notes

- Revisit weak topics after spaced intervals

Memory / Context:

What this assistant should remember within the project.

Output Standard:

What counts as a good answer from this assistant.


## 48. The Template Usage Rule

These templates are tools.

They should not become a second full-time job.
Use them according to project seriousness.

Light Work
Use simple notes.

Medium Work
Use:

   - build log
   - definition of done
   - README

Serious Work
Use:

   - project definition
   - build logs
   - artifact tracker
   - case study
   - report
   - review

Research-Grade Work
Use:

   - source notes
   - paper reading notes
   - literature map
   - experiment log
   - technical report
   - research integrity checklist

The rule is:

        Use only enough structure to preserve momentum and truth.

## 49. Part 17 Final Standard

The standard for this template system is:


> I have reusable operating documents that help me plan, execute, document,
> review, publish, and recover without reinventing the process every time.


The templates should create:

   - less friction
   - more evidence
   - better notes
   - cleaner projects
   - stronger reports
   - safer cybersecurity work
   - better AI use
   - clearer philosophy
   - more honest research
   - more visible public output

They are not the work.

They support the work.