English · العربية · Español · Français · 日本語 · 한국어 · Tiếng Việt · 中文 (简体) · 中文(繁體) · Deutsch · Русский
Language options: English (current draft). Root-level multilingual README files are managed one-by-one in i18n/ (directory exists; files pending).
LifeReverseEngineering (LRE) is a personal deep-research workspace that turns profile context into actionable outputs across three execution tracks:
learn(LazyLearn): book plans and learning pathsearn(LazyEarn): investment ideas and thesis trackingIDEAS: research directions and project concepts
The repository is designed for iterative runs with single-copy updates, so each cycle refreshes the latest artifacts instead of endlessly appending duplicates.
LRE acts as a coordination and aggregation surface, while most domain implementation lives inside Git submodules:
learn/for learning and computational physics/chemistry workearn/for investment briefs, PDF artifacts, and static site outputsIDEAS/for idea-to-publication workflows and generated docs catalogs
At root, LRE focuses on:
- pipeline framing and orchestration handoff
- single-copy report artifacts in
notes/ - self-heal diagnostics in
tools/ - a root landing page deployed from
website/tolre.lazying.art
| Area | Primary Path | Responsibility |
|---|---|---|
| 🧭 Orchestration handoff | Root repo | Pipeline framing + coordination |
| 📄 Consolidated report | notes/lre_single_copy.md |
Single latest markdown briefing |
| 🩺 Diagnostics | tools/lre/ |
Self-heal snapshots and logs |
| 🌐 Public landing page | website/ |
Root GitHub Pages deployment |
| 🧠 Domain execution | learn/, earn/, IDEAS/ |
Track-specific implementation |
LRE is active and optimized for:
- high-frequency iterative updates
- evidence-aware research summaries
- cross-repo output synchronization
| Signal | State |
|---|---|
| Root pipeline posture | ✅ Active |
| Root Pages deployment | ✅ Enabled (website/) |
| Root i18n README variants | 🟡 Directory present, files pending |
| Output model | ✅ Single-copy overwrite/update |
- Three-track coordination model (
learn,earn,IDEAS) with clear responsibility boundaries. - Single-copy output policy for cleaner auditing and lower operational noise.
- Root-level GitHub Pages deployment from
website/only. - Track-level self-heal logging snapshots for debugging and prompt/tool evolution.
- Submodule-based architecture so each track can evolve independently.
- Existing root
i18n/directory reserved for multilingual README variants.
LifeReverseEngineering/
├── learn/ # LazyLearn submodule
├── earn/ # LazyEarn submodule
├── IDEAS/ # IDEAS submodule
├── notes/ # consolidated outputs (single-copy reports)
├── tools/ # self-heal logs and helper artifacts
└── website/ # static website for GitHub Pages
Expanded root map:
LifeReverseEngineering/
├── README.md
├── .gitmodules
├── .github/
│ ├── FUNDING.yml
│ └── workflows/static.yml
├── website/
│ ├── index.html
│ ├── CNAME
│ └── logos/
├── notes/
│ └── lre_single_copy.md
├── tools/
│ └── lre/
│ ├── profile_self_heal_latest.json
│ └── profile_self_heal_latest.log
├── i18n/ # exists, currently empty
├── learn/ # submodule
├── earn/ # submodule
└── IDEAS/ # submodule
LRE runs as a staged pipeline (orchestrated by prompt tools in the parent AgInTi repo):
- Profile stage: resolve identity anchors and evidence confidence.
- Book stage: generate growth-focused reading recommendations.
- Investment stage: draft opportunities, risk framing, and thesis notes.
- Ideas stage: propose research/project directions with next actions.
- Aggregation stage: build a single-copy markdown report.
- Sync stage: write latest outputs into
learn,earn, andIDEAS. - Reporting stage: produce final email/briefing content.
flowchart LR
A[Profile Stage\nidentity + evidence confidence] --> B[Book Stage\nlearning recommendations]
B --> C[Investment Stage\nrisk-aware thesis drafts]
C --> D[Ideas Stage\nresearch/project directions]
D --> E[Aggregation Stage\nnotes/lre_single_copy.md]
E --> F[Sync Stage\nlearn + earn + IDEAS]
F --> G[Reporting Stage\nbriefing/email output]
E --> H[tools/lre/*_self_heal_latest.json]
F --> I[website/index.html]
flowchart TB
O[AgInTi Orchestrator] --> R[LifeReverseEngineering Root]
R --> L[learn/ LazyLearn]
R --> E[earn/ LazyEarn]
R --> I[IDEAS/ IDEAS]
R --> N[notes/lre_single_copy.md]
R --> T[tools/lre/profile_self_heal_latest.*]
R --> W[website/ + Pages deploy]
This repository follows overwrite/update behavior for key summary files:
- Keep one current version of major notes.
- Replace old "latest" snapshots with new run outputs.
- Keep self-heal diagnostics in dedicated tool/log paths.
This makes daily/periodic runs clean, auditable, and easy to inspect.
| Artifact | Behavior |
|---|---|
notes/lre_single_copy.md |
Overwritten/updated with latest consolidated report |
tools/lre/profile_self_heal_latest.json |
Replaced with latest root self-heal snapshot |
tools/lre/profile_self_heal_latest.log |
Updated latest diagnostic log |
git2.30+ (recommended) with submodule support.- GitHub access to submodules listed in
.gitmodules. - SSH key configured for
git@github.com:lachlanchen/IDEAS.gitif using the current IDEAS submodule URL. - Optional tools depending on track work:
- Python 3.x + Jupyter stack (
learn/workflows) pandoc+xelatex(earn/PDF workflow)- Node.js 18 and
latexmk/xelatex(IDEAS/site + publication workflows)
- Python 3.x + Jupyter stack (
Clone with submodules initialized:
git clone --recurse-submodules https://github.com/lachlanchen/LifeReverseEngineering.git
cd LifeReverseEngineeringIf already cloned without submodules:
git submodule update --init --recursiveKeep submodules synced to their tracked refs:
git submodule sync --recursive
git submodule update --remote --recursiveTypical root-level usage is report-centric rather than app-runtime-centric.
- Inspect latest consolidated output:
sed -n '1,120p' notes/lre_single_copy.md- Inspect latest profile self-heal diagnostics:
sed -n '1,160p' tools/lre/profile_self_heal_latest.json
sed -n '1,80p' tools/lre/profile_self_heal_latest.log- Preview root website locally:
python3 -m http.server 8000 --directory website
# then open http://localhost:8000- Push
website/updates tomainto trigger root Pages deploy (.github/workflows/static.yml).
Defined in .gitmodules:
learn->https://github.com/lachlanchen/LazyLearn.gitearn->https://github.com/lachlanchen/LazyEarn.gitIDEAS->git@github.com:lachlanchen/IDEAS.git
- Static site source:
website/index.html - Custom domain target:
lre.lazying.art(fromwebsite/CNAME) - Root deploy workflow:
.github/workflows/static.yml - Deployment artifact scope:
website/only
- Root i18n directory exists:
i18n/ - Current state: no root translation files yet
- Submodules (
learn,earn,IDEAS) already maintain multilingual README variants in their owni18n/directories - Language-options policy at root: maintain a single top line in each README variant and avoid duplicate language-option headers
- Consolidated report:
notes/lre_single_copy.md - Root self-heal snapshot:
tools/lre/profile_self_heal_latest.json - Related per-track snapshots:
learn/tools/lre/books_self_heal_latest.jsonearn/tools/lre/investments_self_heal_latest.jsonIDEAS/tools/lre/ideas_self_heal_latest.json
ls -lt notes/lre_single_copy.md tools/lre/profile_self_heal_latest.jsonrg -n "weak|anchor|identity|non_empty" tools/lre/profile_self_heal_latest.jsoncd IDEAS
npm install --no-save marked
node scripts/generate_site.mjs# edit website/index.html
git add website/index.html .github/workflows/static.yml
git commit -m "Update LRE website"
git push origin main- This repo is a coordination layer, not a single packaged application.
- No root
package.json,pyproject.toml, or unified lockfile currently exists. - Root CI is deployment-focused (Pages), not test/lint-focused.
- The staged orchestration scripts are referenced as living in the parent AgInTi repository, not in this repo.
- The website intentionally uses static assets and no build step at root.
| Symptom | Check / Fix |
|---|---|
| Submodule is empty after clone | Run git submodule update --init --recursive. |
| IDEAS submodule authentication fails | Ensure GitHub SSH key access for git@github.com:lachlanchen/IDEAS.git, or switch submodule URL to HTTPS if needed. |
| Root Pages site did not update | Confirm changed files are under website/** or .github/workflows/static.yml and branch is main. |
| Website renders locally but not on custom domain | Verify website/CNAME contains lre.lazying.art and DNS is correctly pointed to GitHub Pages. |
| Self-heal report appears stale | Check file modification times in tools/lre/ and track run IDs in notes/lre_single_copy.md. |
Locale warnings (e.g., LC_ALL=C.UTF-8) appear in logs |
This is typically environment-level and non-fatal for report generation. |
- Add root multilingual README variants under
i18n/and keep language options synchronized. - Add root-level integrity checks (link verification + artifact freshness checks).
- Improve cross-track evidence quality dashboards based on self-heal snapshots.
- Clarify and automate parent-orchestrator handoff contracts from AgInTi -> LRE.
- Expand troubleshooting playbooks for repeated weak-signal scenarios.
- AgInTi: orchestration and prompt-tool system.
- LazyLearn (
learn/): learning and reading outputs. - LazyEarn (
earn/): investment outputs. - IDEAS (
IDEAS/): research/idea outputs.
Contributions are welcome for:
- improving root pipeline documentation
- hardening diagnostics and artifact quality checks
- enhancing website clarity and operational transparency
- adding root i18n README variants in a consistent format
Recommended process:
- Open an issue describing scope and affected track(s).
- Keep changes scoped to the correct layer (
rootvslearn/earn/IDEAS). - Include before/after notes for any workflow or command changes.
- If touching deployment behavior, include the exact path and trigger impact.
Funding and support links (from .github/FUNDING.yml):
- GitHub Sponsors: https://github.com/sponsors/lachlanchen
- Project network: https://lazying.art
- Community/chat: https://chat.lazying.art
- Related initiative: https://onlyideas.art
No root LICENSE file is present in this repository as of March 3, 2026.
Assumption: until a license is added, usage rights are not explicitly granted beyond standard GitHub visibility expectations. Add a LICENSE file to make reuse terms explicit.
